Open kaichaosun opened 3 hours ago
There seems some unnecessary loops for this scenario.
yep, which is why i had added a simple backoff in case of such errors. it should try 3 times and then wait for 5 secs before trying again. looks like you have no peers with this shard and hence causing this. The idea of sharded communities as i understand is that all shards would be supported by fleet nodes to begin with which means shards would be configured in fleet nodes before being used in the app.
We can't stop retrying for a specific error in a p2p network since we don't know if the condition may change in some time. but any suggestions are welcome.
it should try 3 times and then wait for 5 secs before trying again.
By looking into the log, the times is more than 3, the log file is basically not usable in this case.
it should try 3 times and then wait for 5 secs before trying again.
By looking into the log, the times is more than 3, the log file is basically not usable in this case.
hope you are using latest version of status-go because the fix has been merged only last week. can you also give an idea of how may time do you see the retry? also note that this can happen if a good number of subscriptions are made for same shard as well, because there may be multiple filter batches that me doing this.
@chaitanyaprem I probably used an old version.
Here is the log, https://drive.google.com/file/d/1oG7sGVKfVIDt23TaBPvd2mzm6eZH0K6p/view?usp=sharing Nearly all the content is about resubscribe.
@chaitanyaprem I probably used an old version.
Here is the log, https://drive.google.com/file/d/1oG7sGVKfVIDt23TaBPvd2mzm6eZH0K6p/view?usp=sharing Nearly all the content is about resubscribe.
Yep, better use the latest..I remember this was already reported from mobile team.
Describe the bug
I have created a community on shard 100, I see following logs flux in the log file,
There seems some unnecessary loops for this scenario. Using light mode.
cc @chaitanyaprem