Closed wiz closed 3 years ago
Pricenode crashes on startup if any providers are unavailable for first query
That's part of the general pricenode architecture. It is not related to my recent change.
It would also "crash" (i.e. fail to start) if a fee rate provider like mempool.space would return any issues. In fact, even before the recent change, it would have failed to start if the first BA or Poloniex queries would have failed.
So its part of the general architecture of how @Components
(providers) are initialized. If it fails to initialize, it retries a couple times, but if it cannot get them to properly initialize, it assumes smth is wrong and aborts.
The behavior does make sense: if the pricenode starts, but cannot get a specific price, what would it return to the Bisq nodes? A price of 0? It also has no cached prices from previous queries, cause this is on startup.
So from what I can tell, changing this behavior would:
A simple alternative / workaround would be to add the ability to ignore or skip some providers on startup, like
./bisq-pricenode --skipProviders=Bitflyer
But that is also not trivial:
Bitpay
So this could be a simpler alternative, but also not that straightforward.
That's part of the general pricenode architecture. It is not related to my recent change.
Yes, I am not blaming you, I'm just asking you to fix this since you are familiar with the pricenode code :)
A simple alternative / workaround would be to add the ability to ignore or skip some providers on startup, like
No, the pricenode always needs to startup 100% of the time. It's insane that it can fail to start if not all providers are responding.
The behavior does make sense: if the pricenode starts, but cannot get a specific price, what would it return to the Bisq nodes? A price of 0? It also has no cached prices from previous queries, cause this is on startup.
Can't you simply handle the exception and set that provider's weight to zero until the provider starts returning valid data again?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I restarted my pricenode and it kept crashing due to issues with Binance's API. Apparently it was undergoing maintenance. See https://www.binance.com/en/support/announcement/1344e0dd30e843a8801aa58e23d6d82e. binance crash.txt
In order to get it running, I removed the binance provider but then encountered different errors with huobi, though it didnt crash it. huobi error.txt
@cd2357 can you please look at this critical issue ASAP?