What kind of balance are you querying for? Also, when querying server 2, was the transaction already propagated from server 1 to server 2 (as pending transaction)?
In general, I'm not sure if the Bitcoin network protocol is suitable for synchronizing load-balanced servers. It might be much easier to introduce server affinity to your load balancing logic. On 06/29/2017 01:32 PM, Ajit Soman wrote: > We have setup two same bitcoin back-end server for load balancing > purpose. We are facing an issue on transaction. Consider that a user X > is going to perform a bitcoin transaction. user X is able to perform > transaction successfully using SERVER 1 . When user X calls get our > balance API he gets actual balance from SERVER 1 after that he calls the > balance API one more time this time load balancer redirect request to > SERVER 2, he get his previous balance before transaction. After 1 > confirmation user X is able to see actual balance. > > Can anybody suggest how to deal with this issue? > > -- > You received this message because you are subscribed to the Google > Groups "bitcoinj" group. > To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "bitcoinj" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
