-
Notifications
You must be signed in to change notification settings - Fork 19
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
Remove more unnecessary DsState
variants
#1550
Conversation
a6d1a0d
to
81b65c5
Compare
7c40c94
to
a9d7090
Compare
9f06089
to
9d73e80
Compare
* │ │ ▼ └───►───┐ │ ║ ║ | ||
* │ bad│ ┌────┴──────┐ │ │ ║ ║ | ||
* │ region│ │ Wait │ │ │ ║ ║ | ||
* │ │ ▼ └───►───┐ other │ ║ ║ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Heh, we probably don't need the arrow going form new -> new.
* │ │ ▼ └───►───┐ other │ ║ ║ | ||
* │ bad│ ┌────┴──────┐ │ failures ║ ║ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any other failures, other than the connection going away?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, going back to New
is the universal behavior for any failures before going active.
9d73e80
to
f610a22
Compare
(staged on top of #1549)
DsState::Migrating
is not yet implementedDsState::Disconnected
is another transient state (see Remove transient states inDsState
#1526). It's assigned inDownstairsClient::restart_connection
(which halts the IO task), then we switch toDsState::New
once the IO task halts. Those two states are never actually handled differently, so we can switch toDsState::New
immediately