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
order leakage #1173
Comments
collected infos... node was running for 1.5h, number of orders should be
output of log: prices are set with |
A possible reason for this is that this |
catched such a double order in BTCZ/JEUR-PLG20 orderbook:
there are 2 asks from the same pubkey, there should be only one |
If you notice that you can fix a bug please feel free to work on it without explicit approval in the future. We can discuss the details after you open a PR. |
The reason is most likely in another place, in I guess it's more likely to happen with a big number of orders per node. @cipig Could you please check if the problem is fixed in the https://github.com/KomodoPlatform/atomicDEX-API/tree/orderbook_fixes? |
thanks, problem fixed |
MM2 from dev branch (which seems to fix the deadlock reported in #1172) leaks orders. Their number (as seen from seednodes) increase all the time till it reaches a point where seed nodes disconnect you. This happens on all my nodes, does not matter how many orders they initially had.
This is the real number of orders from all my nodes (when running from mm2.1 branch, so without the leak):
When running from dev branch, the number of orders increases slowly but steadily over time. This is from the node that actually has
orders_uuids=2634
after running for couple hours:if this happens, i see orders double... i use
setprice
to set orders, which cancels previous orders from that pair, but this seems to not always happen like it should, so then i see 2 bids in the orderbook from that node instead of just onestrange is that both have the same
"age": xxxxxxxx
in the orderbooki will run dev branch again for a while on one of the nodes and add the output from
my_orders
and the log fileThe text was updated successfully, but these errors were encountered: