Details
-
Bug
-
Resolution: Fixed
-
Critical
-
6.0.0
-
component cluster
-
Untriaged
-
-
Unknown
Description
Build : 6.0.0-1592
Test : -test tests/eventing/test_eventing_rebalance_timers.yml -scope tests/eventing/scope_eventing_rebalance_timers.yml
Scale : 2
Iteration : 1st
There is a step in the test to failover 2 KV nodes. During this time, eventing log reports the following fatal errors on 172.23.104.19. This is reported 6816 times in the logs. This does not visibly block any operation though.
2018-09-01T05:45:10.342-07:00 [Fatal] DCP[{eventing:tbahHeMq-8064:172.23.104.19:8096_172.23.104.25:11210_worker_timer_op_0_GetSeqNos}] ##abcd GetVBmap([172.23.104.25:11210]) failed: vbmap: Invalid KV node no -1 for vb 51
|
2018-09-01T05:45:10.411-07:00 [Fatal] DCP[{eventing:tbahHeMq-8065:172.23.104.19:8096_172.23.104.16:11210_worker_bucket_op_complex_function_1_GetSeqNos}] ##abcd GetVBmap([172.23.104.16:11210]) failed: vbmap: Invalid KV node no -1 for vb 51
|
2018-09-01T05:45:10.694-07:00 [Fatal] DCP[{eventing:tbahHeMq-8066:172.23.104.19:8096_172.23.104.16:11210_worker_bucket_op_function_1_GetSeqNos}] ##abcd GetVBmap([172.23.104.16:11210]) failed: vbmap: Invalid KV node no -1 for vb 51
|
2018-09-01T05:45:10.815-07:00 [Fatal] DCP[{eventing:tbahHeMq-8067:172.23.104.19:8096_172.23.104.23:11210_worker_timer_op_complex_0_GetSeqNos}] ##abcd GetVBmap([172.23.104.23:11210]) failed: vbmap: Invalid KV node no -1 for vb 51
|
Ask here is to:
1. See if logging these as fatal errors is really necessary. Fatal errors could be flagged by support or customers. If these errors are benign, we can log them as errors or warnings.
2. See if can reduce the logging instead of logging it 6816 times.
3. Since there is no visible damage done, QE will check in similar functional tests if there is a functional impact of this. But pls analyze if there is any.