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

Defining ManCenter in config causes PartitonMigration even though there is no data #11598

Closed
gokhanoner opened this issue Oct 17, 2017 · 0 comments
Closed

Comments

@gokhanoner
Copy link
Contributor

@gokhanoner gokhanoner commented Oct 17, 2017

When ManCenter is enabled, TimedMemberStateFactory.createMemState method get stats from Members. LocalMapStatsProvider.createAllLocalMapStats method calls partitionService.getPartition method without the triggerOwnerAssignment boolean flag. In a big cluster with no initial data, this causes partition migration for each joining member & increase cluster startup time significantly.

There may be other sources that causes this, like Diagnostics etc. It'd be good to check all of them if possible.

This is currently affecting a customer with > 100 member cluster.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.