negative updated results

[florakarniav]

Hello, I've been using the yahoo streaming benchmark in different environments and since yesterday I tried it on an 32-core intel xeon machine (but using only 8 cores for flink with taskset). I see negative results in the updated file (e.g. -70646). Can I get some help with this issue?

[Yitian-Zhang]

This problem is most likely caused by the non-synchronization of the system time among worker nodes in your cluster. When the benchmark system runs, the start timestamp will be created based on the system time of one node in the cluster, and then the last updated timestamp will be created based on other worker node (if the tasks were distributed among different nodes) when the final result written to Redis. Hence, if the time among different nodes is not synchronized, it is possible that the difference between the two timestamps is negative. So you can check the system time of worker nodes in your cluster and then run the benchmark after keeping them synchronization.

[varuy322]

This problem is most likely caused by the non-synchronization of the system time among worker nodes in your cluster. When the benchmark system runs, the start timestamp will be created based on the system time of one node in the cluster, and then the last updated timestamp will be created based on other worker node (if the tasks were distributed among different nodes) when the final result written to Redis. Hence, if the time among different nodes is not synchronized, it is possible that the difference between the two timestamps is negative. So you can check the system time of worker nodes in your cluster and then run the benchmark after keeping them synchronization.

That's odd, I came across this issue. I checked the component configuration and code, nothing seemed to be wrong. Do you solve this by synchronize cluster system time?

[Yitian-Zhang]

This problem is most likely caused by the non-synchronization of the system time among worker nodes in your cluster. When the benchmark system runs, the start timestamp will be created based on the system time of one node in the cluster, and then the last updated timestamp will be created based on other worker node (if the tasks were distributed among different nodes) when the final result written to Redis. Hence, if the time among different nodes is not synchronized, it is possible that the difference between the two timestamps is negative. So you can check the system time of worker nodes in your cluster and then run the benchmark after keeping them synchronization.

That's odd, I came across this issue. I checked the component configuration and code, nothing seemed to be wrong. Do you solve this by synchronize cluster system time?

Yes, I encountered the same issue that negative updated values. And I solved this problem by synchronize cluster system time.

[HQBIAO]

I came across this issue

Have you solved this problem,I came across this issue too