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.

Sign up for GitHub

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

Jump to bottom

sharding ddata + rememberEntries => entities not started after a restart. #19003

Closed
patriknw opened this issue Nov 24, 2015 · 2 comments
Closed

sharding ddata + rememberEntries => entities not started after a restart. #19003

patriknw opened this issue Nov 24, 2015 · 2 comments
Labels
1 - triaged Tickets that are safe to pick up for contributing in terms of likeliness of being accepted t:cluster-tools

Comments

@patriknw
Copy link
Member

patriknw commented Nov 24, 2015 •
edited

Reported in another unrelated issue: #18936 (comment)

it looks like actors in a shard were not started after a restart.

If you are using the ddata mode then the coordinator do not know about shards right after restart. But rememberEntries flag force the shards to store info about entries. So ddata+rememberEntries is a kind of "lazy persistent shards" from some point of view. You need to send message to any entry inside the persistent shard to init the replay process of this shard.

This is rather confusing, and if it can't be fixed it should be documented.
@patriknw patriknw added this to the 2.4.x milestone Nov 24, 2015
@patriknw patriknw added 1 - triaged Tickets that are safe to pick up for contributing in terms of likeliness of being accepted t:cluster-tools labels Nov 24, 2015
@patriknw patriknw mentioned this issue Nov 24, 2015
Closed
@jaapterwoerds
Copy link

Is there a way / workaround so that we can trigger loading of shards by addressing the shards instead of individual entries?

@rkuhn rkuhn removed the 1 - triaged Tickets that are safe to pick up for contributing in terms of likeliness of being accepted label Mar 9, 2016
@patriknw patriknw added the 1 - triaged Tickets that are safe to pick up for contributing in terms of likeliness of being accepted label Mar 9, 2016
@patriknw patriknw removed this from the 2.4.x milestone Jan 19, 2017
@patriknw
Copy link
Member Author

This will be fixed by #22154

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
1 - triaged Tickets that are safe to pick up for contributing in terms of likeliness of being accepted t:cluster-tools
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@patriknw @rkuhn @jaapterwoerds