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
Recently, I observed that the meta continuously prints the WARN logs: WARN risingwave_meta::manager::sink_coordination::coordinator_worker: current epoch is 7476731719516160 but get request from 7476732374876160
There are dozens of StarRocks sinks in my cluster, some of them with a parallelism of 3. when I changed all of the sinks' parallelism to 1, the WARN log disappeared.
Error message/log
No response
To Reproduce
Creating starrocks sink with parallelism greater than 1 and sink_decouple enabled.
Expected behavior
No response
How did you deploy RisingWave?
No response
The version of RisingWave
2.0.2
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
Recently, I observed that the meta continuously prints the WARN logs:
WARN risingwave_meta::manager::sink_coordination::coordinator_worker: current epoch is 7476731719516160 but get request from 7476732374876160
There are dozens of StarRocks sinks in my cluster, some of them with a parallelism of 3. when I changed all of the sinks' parallelism to 1, the WARN log disappeared.
Error message/log
No response
To Reproduce
Creating starrocks sink with parallelism greater than 1 and sink_decouple enabled.
Expected behavior
No response
How did you deploy RisingWave?
No response
The version of RisingWave
2.0.2
Additional context
No response
The text was updated successfully, but these errors were encountered: