This repository has been archived by the owner on Sep 10, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
Investigate nectar closing connection with cnd #106
Labels
bug
Something isn't working
Comments
It seems this issue is actually not time related, but it happens when we publish a new order. Might be related to an error happening on publication of the order or when cnd fetches the new orders from nectar. I just had a transaction drop that happened after a successful swap, after about 2 minutes after a swap execution, that lead to a balance change that lead to new orders being published. nectar:
|
da-kami
changed the title
Investigate nectar closing connection with cnd after 10 minutes
Investigate nectar closing connection with cnd
Aug 16, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Setup
System: MacOS Catalina 10.15.5
cnd
nectar
cnd
tonectar
(using nectar's port and localhost IP-adr)Nectar's rate update (and hence order publication) set to 10 minutes.
on nectar branch https://github.com/coblox/nectar/tree/new-orderbook
Behaviour
The connection between Nectar and cnd is just closed after 10 minutes.
Note that this always happens at the moment, not matter if during, after swap execution, or just order fetching.
Note that Nectar was set to publish orders only every 10 minutes (fetch rate after 10 minutes and place new order based on it). This might be related, but not necessarily.
Example logs where cnd dials nectar and then just runs fetching orders until connection is closed is below.
cnd:
nectar:
Another example log where it happens after (successful) swap execution:
cnd:
nectar:
Expected Behaviour
A stable connection over long period of time between Nectar and cnd.
Nectar should only close the connection if there is a problem.
The text was updated successfully, but these errors were encountered: