| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
…SAO-18644) When several processes start together, each can find no agent stream or project and try to create it. The server keeps one and rejects the rest (HTTP 400 for a stream, HTTP 422 for a project, HTTP 500 on older servers). The rejected processes raised from SplunkAOLogger and failed at startup. After a failed create, look the stream or project up again and use what the winner made. For a project, wait briefly (5 look-ups, 0.2 s apart) because the winner may not have granted access yet. If it never appears, re-raise the original create error, so other failures still show. Co-Authored-By: Claude Code <noreply@anthropic.com>
…et-after-lost-create-race
…currently (SAO-18644) Co-Authored-By: Claude Code <noreply@anthropic.com>
| Back | FazBrowse Home | New Git URL |
Summary
Jira: SAO-18644
When several processes start together, each can find no agent stream or project and try to create it. The server keeps one and rejects the rest. Until now the rejected processes raised from SplunkAOLogger and failed at startup.
The server rejects the loser with HTTP 400 for a stream and HTTP 422 for a project. Older servers returned HTTP 500 after duplicates existed. The change does not depend on the status code.
This pairs with rungalileo/orbit#3159. That PR makes the server reject a duplicate stream name instead of silently creating a second stream. Without this SDK change, SDK processes that start together on a brand-new stream can fail at startup after that PR. This PR does not depend on it. It only changes what happens after a create has already failed, so it is safe on its own and with older servers. Shipping it first or together with the orbit change is recommended, not required.
Test plan
Neither run left a duplicate stream or project.
Notes