Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
N
neoppod
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Iliya Manolov
neoppod
Commits
35491a4a
Commit
35491a4a
authored
Apr 01, 2016
by
Julien Muchembled
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Document cluster states
parent
b1ea96c0
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
23 additions
and
0 deletions
+23
-0
neo/lib/protocol.py
neo/lib/protocol.py
+23
-0
No files found.
neo/lib/protocol.py
View file @
35491a4a
...
...
@@ -78,12 +78,35 @@ def ErrorCodes():
@
Enum
def
ClusterStates
():
# Once the primary master is elected, the cluster has a state, which is
# initially RECOVERING, during which the master:
# - first recovers its own data by reading it from storage nodes;
# - waits for the partition table be operational;
# - automatically switch to VERIFYING if the cluster can be safely started.
# Whenever the partition table becomes non-operational again, the cluster
# goes back to this state.
RECOVERING
# Transient state, used to:
# - replay the transaction log, in case of unclean shutdown;
# - and actually truncate the DB if the user asked to do so.
# Then, the cluster either goes to RUNNING or STARTING_BACKUP state.
VERIFYING
# Normal operation. The DB is read-writable by clients.
RUNNING
# Transient state to shutdown the whole cluster.
STOPPING
# Transient state, during which the master (re)connect to the upstream
# master.
STARTING_BACKUP
# Backup operation. The master is notified of new transactions thanks to
# invalidations and orders storage nodes to fetch them from upstream.
# Because cells are synchronized independently, the DB is often
# inconsistent.
# TODO: allow clients to connect for read-only operations
BACKINGUP
# Transient state, when the user decides to go back to RUNNING state.
# The master stays in this state until the DB is consistent again.
# In case of failure, the cluster will go back to backup mode.
STOPPING_BACKUP
@
Enum
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment