-
Notifications
You must be signed in to change notification settings - Fork 573
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
12402: Aggregate equivalent client streams r=deepthidevaki a=deepthidevaki ## Description Aggregates client streams with the same `streamType` and `metadata` to a single stream that is registered with the server. Payloads pushed to this server stream will be distributed to one of the registered client stream. Currently, the client stream is picked randomly. Later, we can employ a better strategy to chose the client stream to push the payload. The streamId for the aggregated stream is generated randomly. When all existing client streams are removed, the corresponding server stream will also be removed. When a new client stream is registered with the same streamType and metadata, a new aggregated stream will be created with a new streamId. This is ok, because as long there is an aggregated stream in the registry, new client streams will be added to it. Not re-using the previous streamId also helps to prevent edge cases where concurrent remove (of old aggregated stream) and add (of new aggregated stream) requests caused by retried resulting in inconsistent state. ## Related issues closes #12253 12406: ci(integration): split module and integration test jobs r=megglos a=megglos ## Description Reduces overall runtime as the module tests and qa-integration tests cannot run in parallel due to the maven module inter-dependencies. Thus extracting module ITs into a dedicated job allows us to get the overall IT stages down to ~ 10 minutes, while on main the `Integration tests` job that combines module and qa integration tests shows runtimes of about 15m. By that chance introduced a shared IT job setup that can be configured through a matrix. By also looking at the unit test summary I wondered why the s3 unit tests take about 2m to complete, which is where I found that some ITs were actually run as unit tests. I made sure they are run as ITs going forward [by renaming them](3b5781f). In total the whole CI run duration is not dominated by the integration test job anymore but by multiple that oscillate around 10m. relates to #12028 12421: feat: default to a better raft request timeout r=oleschoenburg a=oleschoenburg Using the old default values of: ```yaml zeebe.broker: cluster: electionTimeout: 2.5s raft: enablePriorityElection: true experimental: maxAppendsPerFollower: 2 raft: requestTimeout: 5s ``` the loss of 2 requests between primary(leader) and secondary(follower) could trigger unnecessary re-election because the secondary would not receive any requests from the primary for at least 5 seconds which exceeds election timeout. This changes the default request timeout to always match the default election timeout. Using all default values, we get at least one more request attempt between primary and secondary before re-election and probably more, depending on the exact timing when requests are sent. closes #12009 12426: Disable test results comment r=npepinpe a=remcowesterhoud ## Description <!-- Please explain the changes you made here. --> Disables the test results comment that gets added to PRs. As a team it was decided this was not useful. ## Related issues <!-- Which issues are closed by this PR or are related --> closes # 12428: test(qa): save logs of zeebe containers if the test fails r=deepthidevaki a=deepthidevaki ## Description There were no logs from the brokers or gateway. So it was not possible to debug flaky test #12396 Co-authored-by: Deepthi Devaki Akkoorath <deepthidevaki@gmail.com> Co-authored-by: Meggle (Sebastian Bathke) <sebastian.bathke@camunda.com> Co-authored-by: Sebastian Bathke (Meggle) <sebastian.bathke@camunda.com> Co-authored-by: Ole Schönburg <ole.schoenburg@gmail.com> Co-authored-by: Remco Westerhoud <remco@westerhoud.nl>
- Loading branch information
Showing
20 changed files
with
416 additions
and
210 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.