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
After upgrading tdengine from 3.1.0.3 to 3.3.0.3, the server keep logging MND ERROR trans:12443, stage keep on commitAction since Transaction context switch, failedTimes:178. Although I can connect to the server with taos client and jdbc, I am not sure is there any potential defect about this logs?
05/27 13:16:05.215477 00000034 C DND The daemon initialized successfully
05/27 13:16:05.595924 00000079 C MND trans:12443, continue to execute, stage:commitAction createTime:1716282892835 topHalf:1
05/27 13:16:05.595998 00000079 C MND trans:12443, action:0 not executed since Transaction context switch. numOfActions:1
05/27 13:16:05.596016 00000079 C MND ERROR trans:12443, stage keep on commitAction since Transaction context switch, failedTimes:10
05/27 13:16:05.609592 00000078 C MND vgId:6, state changed by status msg, old state:leader restored:0 canRead:0 new state:leader restored:1 canRead:1, dnode:1
05/27 13:16:05.609638 00000078 C MND db:1.ishare_report, stateTs changed by status msg, old stateTs:1716815764604 new stateTs:1716815765609
05/27 13:16:05.609646 00000078 C MND vgId:646, state changed by status msg, old state:follower restored:0 canRead:0 new state:leader restored:1 canRead:1, dnode:1
05/27 13:16:05.609654 00000078 C MND db:1.tmq_test_callback, stateTs changed by status msg, old stateTs:1716815748571 new stateTs:1716815765609
05/27 13:16:05.609660 00000078 C MND vgId:7, state changed by status msg, old state:follower restored:0 canRead:0 new state:leader restored:1 canRead:1, dnode:1
05/27 13:16:05.609726 00000078 C MND vgId:647, state changed by status msg, old state:follower restored:0 canRead:0 new state:leader restored:1 canRead:1, dnode:1
05/27 13:16:07.605237 00000079 C MND trans:12443, continue to execute, stage:commitAction createTime:1716282892835 topHalf:1
05/27 13:16:07.605316 00000079 C MND trans:12443, action:0 not executed since Transaction context switch. numOfActions:1
05/27 13:16:07.605325 00000079 C MND ERROR trans:12443, stage keep on commitAction since Transaction context switch, failedTimes:11
05/27 13:16:09.613426 00000079 C MND trans:12443, continue to execute, stage:commitAction createTime:1716282892835 topHalf:1
05/27 13:16:09.613511 00000079 C MND trans:12443, action:0 not executed since Transaction context switch. numOfActions:1
05/27 13:16:09.613518 00000079 C MND ERROR trans:12443, stage keep on commitAction since Transaction context switch, failedTimes:12
05/27 13:16:11.619087 00000079 C MND trans:12443, continue to execute, stage:commitAction createTime:1716282892835 topHalf:1
05/27 13:16:11.619218 00000079 C MND trans:12443, action:0 not executed since Transaction context switch. numOfActions:1
05/27 13:16:11.619228 00000079 C MND ERROR trans:12443, stage keep on commitAction since Transaction context switch, failedTimes:13
The text was updated successfully, but these errors were encountered:
After upgrading tdengine from 3.1.0.3 to 3.3.0.3, the server keep logging
MND ERROR trans:12443, stage keep on commitAction since Transaction context switch, failedTimes:178
. Although I can connect to the server with taos client and jdbc, I am not sure is there any potential defect about this logs?The text was updated successfully, but these errors were encountered: