You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For tests where the target throughput is > 4000 ops/s and search_clients > 4000, OSB stalls and does not report results. This only happens if target throughput is set. Based on the OSB logs, some workers never meet at the joinpoint and this is preventing OSB from reporting results.
On the target cluster, the run appears to have completed in the expected time and the target throughput is achieved.
The cause is not clear but it seems to be related to the target-throughput pathway and also in how Thespianpy workers are missing (the suspicion is that they exit prematurely and cause OSB to stall.)
This may be related to the issue reported in #318.
The text was updated successfully, but these errors were encountered:
gkamat
changed the title
[BUG] OSB hangs when runs carried out with
[BUG] OSB hangs when runs carried out with large number of clients
Sep 9, 2024
IanHoang
changed the title
[BUG] OSB hangs when runs carried out with large number of clients
[BUG] OSB hangs when runs carried out with large number of clients and target-throughput enabled
Sep 11, 2024
Describe the bug
For tests where the target throughput is > 4000 ops/s and search_clients > 4000, OSB stalls and does not report results. This only happens if target throughput is set. Based on the OSB logs, some workers never meet at the joinpoint and this is preventing OSB from reporting results.
On the target cluster, the run appears to have completed in the expected time and the target throughput is achieved.
The cause is not clear but it seems to be related to the target-throughput pathway and also in how Thespianpy workers are missing (the suspicion is that they exit prematurely and cause OSB to stall.)
This may be related to the issue reported in #318.
The text was updated successfully, but these errors were encountered: