Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
N
neo
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Labels
Merge Requests
2
Merge Requests
2
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Jobs
Commits
Open sidebar
Kirill Smelkov
neo
Commits
167ad36b
Commit
167ad36b
authored
Jul 10, 2015
by
Julien Muchembled
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Better handling of NotReady error
parent
8ec87379
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
9 additions
and
1 deletion
+9
-1
TODO
TODO
+4
-0
neo/lib/handler.py
neo/lib/handler.py
+5
-1
No files found.
TODO
View file @
167ad36b
...
@@ -34,6 +34,10 @@
...
@@ -34,6 +34,10 @@
- Empty storages rejected during recovery process
- Empty storages rejected during recovery process
Masters implies in the election process should still reject any connection
Masters implies in the election process should still reject any connection
as the primary master is still unknown.
as the primary master is still unknown.
- Wait before reconnecting to a node after an error. For example, a backup
storage node that is rejected because the upstream cluster is not ready
currently reconnects in loop without delay, using 100% CPU and
flooding logs.
- Implement transaction garbage collection API (FEATURE)
- Implement transaction garbage collection API (FEATURE)
NEO packing implementation does not update transaction metadata when
NEO packing implementation does not update transaction metadata when
deleting object revisions. This inconsistency must be made possible to
deleting object revisions. This inconsistency must be made possible to
...
...
neo/lib/handler.py
View file @
167ad36b
...
@@ -174,10 +174,14 @@ class EventHandler(object):
...
@@ -174,10 +174,14 @@ class EventHandler(object):
except
(
AttributeError
,
ValueError
):
except
(
AttributeError
,
ValueError
):
raise
UnexpectedPacketError
(
message
)
raise
UnexpectedPacketError
(
message
)
# XXX: For some errors, the connection should have been closed by the remote
# peer. But what happens if it's not the case because of some bug ?
def
protocolError
(
self
,
conn
,
message
):
def
protocolError
(
self
,
conn
,
message
):
# the connection should have been closed by the remote peer
logging
.
error
(
'protocol error: %s'
,
message
)
logging
.
error
(
'protocol error: %s'
,
message
)
def
notReadyError
(
self
,
conn
,
message
):
logging
.
error
(
'not ready: %s'
,
message
)
def
timeoutError
(
self
,
conn
,
message
):
def
timeoutError
(
self
,
conn
,
message
):
logging
.
error
(
'timeout error: %s'
,
message
)
logging
.
error
(
'timeout error: %s'
,
message
)
...
...
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