This repository has been archived by the owner on Nov 6, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Secret Store, Intermittent hung up on Key generation session #11141
Comments
Hey, That error is related to std::time::Instant::duration_since which is may because of a faulty clock or bug in /cc @svyatonik @grbIzl any clues? |
@zean00 Could you, please:
|
Here is what I have after applying try_ss_instant_fix patch. I didn't get panic backtrace this time
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Secret store frequently failed to generate server key session and just hung up (resulting in request timeout), need to restart all secret store nodes to recover
Expected Behaviour
Key generation success, if error occurred should return error message immediately and should not causing request timeout.
Actual
I rarely have successful request of key generation in 10 request sequentially, one hang up, I need to restart all secret store node to be able to get expected response from secret store. This issue is not occurred in ocean protocol fork (I'm using their docker images of parity fork with secret store - oceanprotocol/parity-ethereum:master)
Step to Reproduce
Invoke POST /shadow/[DOCUMENT_ID]/[SIGNED_DOCUMENT_ID]/1
Notes
This is not specific on key generation session, sometimes this happening on document key store request or document key retrieval. I suspect this is related to cluster communication / coordination
Configuration
Log
The text was updated successfully, but these errors were encountered: