Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adjust metadata networking options #2589

Merged
merged 3 commits into from
Jan 30, 2025
Merged

Adjust metadata networking options #2589

merged 3 commits into from
Jan 30, 2025

Conversation

Copy link

github-actions bot commented Jan 30, 2025

Test Results

  7 files  ±0    7 suites  ±0   4m 11s ⏱️ + 1m 17s
 45 tests ±0   43 ✅  - 1  1 💤 ±0  0 ❌ ±0  1 🔥 +1 
174 runs  ±0  170 ✅  - 1  3 💤 ±0  0 ❌ ±0  1 🔥 +1 

For more details on these errors, see this check.

Results for commit 3b08b24. ± Comparison against base commit d1a31ea.

♻️ This comment has been updated with latest results.

Copy link
Contributor

@tillrohrmann tillrohrmann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. +1 for merging :-)

Re-implemented the logic to propose new loglet configurations directly on any bifrost node. This unlocks the next PR which will use the auto_extend feature to auto-recover.

```
// intentionally empty
```
@AhmedSoliman AhmedSoliman force-pushed the pr2589 branch 2 times, most recently from a031a2a to 7f9ed44 Compare January 30, 2025 17:32
In certain scenarios, if the appender is known to be running with "permission" to extend the chain, it'll run out of patience and will attempt to perform reconfiguration itself. This works really well, but it might compete with a cluster controller that thinks a different placement should take place. The auto-recovery mechanism only kicks in after 3 seconds (configurable) and we can see that the appender will attempt to reconfigure the loglet if it's sealed.

At the moment, this will get the system out of trouble in certain scenarios.

```
// intentionally empty
```
@AhmedSoliman AhmedSoliman merged commit 3b08b24 into main Jan 30, 2025
44 of 49 checks passed
@AhmedSoliman AhmedSoliman deleted the pr2589 branch January 30, 2025 18:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants