Skip to content

Fixes to MultipleManagerStartupWaitIT#6214

Merged
dlmarion merged 1 commit intoapache:mainfrom
dlmarion:MultipleManagerStartupWaitIT-fixes
Mar 13, 2026
Merged

Fixes to MultipleManagerStartupWaitIT#6214
dlmarion merged 1 commit intoapache:mainfrom
dlmarion:MultipleManagerStartupWaitIT-fixes

Conversation

@dlmarion
Copy link
Contributor

No description provided.

@dlmarion dlmarion added this to the 4.0.0 milestone Mar 12, 2026
@dlmarion dlmarion self-assigned this Mar 12, 2026
// Start the 2nd Manager
getCluster().getConfig().getClusterServerConfiguration().setNumManagers(2);
getCluster().start();
// Don't call Cluster.start, it's synchronized and the thread
Copy link
Contributor

Choose a reason for hiding this comment

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

This comment helped me understand why setup is called in a background thread. Would setUp() block forever if min managers was set to 2?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

min manager is set to 2 in configure(), but we started mini accumulo with the default number of managers (1). So the thread that is starting mini is stuck in verifyUp() waiting for the one manager that we started to grab the primary lock. However, the manager hasn't gotten that far in Manager.run because it's waiting for 2 managers.

Would setUp() block forever if min managers was set to 2?

It is set to 2 at line 46 above, and will block for 5m according to the property set at line 47.

@dlmarion dlmarion merged commit 81fae3a into apache:main Mar 13, 2026
9 checks passed
@dlmarion dlmarion deleted the MultipleManagerStartupWaitIT-fixes branch March 13, 2026 11:42
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