aajoshi/merge master into dev #3075
Closed
Conversation
This file contains hidden or 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
Merge master into dev
- Add isInstanceDrained method in HelixAdmin - Expose the method via instance update rest end point - Change the conditional checks order in isEvacuateFinished to improve latency
* this change returns false if the current state contains any resource with rebalance mode full auto or customized
Merge Apache Helix head into dev branch for internal release.
* Adding a new CrushEd2Rebalance Strategy which has CrushEd as base * using MM instead of using controller sycn and stop * adding doc strings * Addressed review comments * removed unnecessary file
Adding dev branch to run CI on raising against dev
…stance (#32) * adding check if resources are migrated from an unhealthy evacuated instance * removing comments * fixing TestErrorReplicaPersist * addressing review comments * addressing review comments * adding log line and removed Rebalance mode parameter * Changing log leve and updated the documentation --------- Co-authored-by: Anubhav Agarwal <anubagarwal@linkedin.com>
…lance Add support for virtual topology imbalance detection
Merge master into dev for release 1.4.4-dev-202506171200
…by Optional.empty() singleton
Fix global lock contention in DistClusterControllerStateModel caused by Optional.empty() singleton
… caused by Optional.empty() singleton" (#35)
Merge master into dev for release 1.4.5-dev-202507181030
This commit introduces an optional feature to make WAGED rebalancer behavior more consistent with CrushEd for disabled partition scenarios. When enabled, disabled partitions remain in OFFLINE state on their current instances rather than being immediately reassigned.
…e-to-relax-disabled-parition-hard-contraint Add optional relaxed disabled partition constraint for WAGED rebalancer
…by Optional.empty() singleton (#39)
…y which is required
* Enable updating EV configs on IS updates * Test fix
Merge master into dev for release release 1.4.4-dev-202508181200
* Remove and cleanup IZkStateListenerI0ItecImpl * Linter fixes * Add test for verification of null session * Debug CI * Refactor the test, trim the tests because of unncessary things * Try fix CI issue * Try fix CI issue: atempt2 * Fix CI test isolation: Add comprehensive system property cleanup - Save original values of MULTI_ZK_ENABLED, MSDS_SERVER_ENDPOINT_KEY, ZK_SESSION_TIMEOUT before test - Clear all multi-ZK properties at start to handle pollution from previous tests - Test then enables multi-ZK mode when needed with clean environment - Restore original values in finally block for proper test isolation - Prevents NoSuchElementException when MULTI_ZK_ENABLED is preset by other tests - Removes dependency on test execution order for reliable CI runs * Another try for test fix * Remove the deprecated IZkStateListener class * Clarofy comments * Addressed review comments
* Fix handleStateChanged stale logging * Add comment for identifying SyncConnected event * Create test * Address review comments
…or encounters nodes with no children during CRUSHED2 rebalancing (#49)
* Add diagnostic logging for CRUSHED2 rebalancer failures * Address review comments
…fig-match Validate instance config has fault zone type key
* FIx NPE for the swap out instances * Update swap out not * Revert changes to TestPerInstanceAccessor.java from PR
… calculate assignment (apache#3034) (#56) * prevent DROPPED messages when mapping cannot be computed * add test for CRUSHED resource * add message generation phase tst * fix test * respond feedback Co-authored-by: Grant Paláu Spencer <gspencer@linkedin.com>
…te topology nodes (#53) * Preserve IdealState when Topology exception is encountered * Add tests * Fix tests * Verify message dropped fix using test * Add integration test * Added assertion for verifier failrue
…eated workflows (#55) * Fix stale cache issue causing erroneous workflow deletion in WorkflowDispatcher * Address review comments * Remove redundant tests
…ns invalid hash (#61) * handling the case when jenkins hash returns 0 in straw2selector * removing unwanted lines * improving test case and addressing review comments --------- Co-authored-by: Anubhav Agarwal <anubagarwal@linkedin.com>
* Add Cluster-Level Instance Operation Count Metrics * Address review comments * Address review comments3
* Add Instance Operation Duration Metrics for Monitoring * Address review comments * Address review comments2 * Address review comments n * Address review comments n
* adding cluster topology validation when updating instance config * formatting the code * updated the logic to check the instance operation transition --------- Co-authored-by: Anubhav Agarwal <anubagarwal@linkedin.com>
* improve stoppable check APIs to include failure details * fix review comments --------- Co-authored-by: Laxman Ch <vchekka@linkedin.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
10 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issues
This PR merges linkedin/master into linkedin/dev for helix release
(#200 - Link your issue number here: You can write "Fixes #XXX". Please use the proper keyword so that the issue gets closed automatically. See https://docs.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue
Any of the following keywords can be used: close, closes, closed, fix, fixes, fixed, resolve, resolves, resolved)
Description
(Write a concise description including what, why, how)
Tests
NA
Changes that Break Backward Compatibility (Optional)
(Consider including all behavior changes for public methods or API. Also include these changes in merge description so that other developers are aware of these changes. This allows them to make relevant code changes in feature branches accounting for the new method/API behavior.)
Documentation (Optional)
(Link the GitHub wiki you added)
Commits
Code Quality
(helix-style-intellij.xml if IntelliJ IDE is used)