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
Hi,
I came this by accident (forgot to change threadcount):
When opcount is set to 1 and threadcount to e.g. 2, it causes the first thread to stop after 1 operation, but the second thread runs endlessly.
This is due to the threadopcount calculation in the following lines:
I am not sure what the intended behaviour is, but I would suggest to either throw an exception (when opcount < threadcount) or alter the calculation to pass e.g. a negative opcount to those ClientThreads that will not need to issue operations.
The text was updated successfully, but these errors were encountered:
Hi,
I came this by accident (forgot to change threadcount):
When opcount is set to 1 and threadcount to e.g. 2, it causes the first thread to stop after 1 operation, but the second thread runs endlessly.
This is due to the threadopcount calculation in the following lines:
YCSB/core/src/main/java/com/yahoo/ycsb/Client.java
Lines 432 to 437 in 2f03a2f
When threadopcount is 0 the loop in ClientThread will run endlessly
YCSB/core/src/main/java/com/yahoo/ycsb/ClientThread.java
Line 116 in 2f03a2f
I am not sure what the intended behaviour is, but I would suggest to either throw an exception (when opcount < threadcount) or alter the calculation to pass e.g. a negative opcount to those ClientThreads that will not need to issue operations.
The text was updated successfully, but these errors were encountered: