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
Everything was fine, and then the event suddenly died for no apparent reason
When I restart the application the application continues to consume events and after a period of a few days it automatically stops consuming
Below is the processing log of eventuate
Log
When eventuate is consumed, this segment usually only has 1 offset. But when the event has a problem, all the offsets are gathered here
To commit CI_DOP_V3_EVENT_CONSUMER io.eventuate.messaging.kafka.basic.consumer.OffsetTracker@59d137a1[state={CI_DOP_V3_EVENT-0=io.eventuate.messaging.kafka.basic.consumer.TopicPartitionOffsets@1f75b245[unprocessed=[52274]
I using mysql and I see that it always locked on before the event break down
OBJECT_NAME received_messages
LOCK_TYPE TABLE
LOCK_MODE IX
Do you have any ideals about this issue? Thank you very much!
The text was updated successfully, but these errors were encountered:
Problem
I register event consumers according to the following structure
My version core and message is 0.32.0.RELEASE
Everything was fine, and then the event suddenly died for no apparent reason
When I restart the application the application continues to consume events and after a period of a few days it automatically stops consuming
Below is the processing log of eventuate
Log
When eventuate is consumed, this segment usually only has 1 offset. But when the event has a problem, all the offsets are gathered here
To commit CI_DOP_V3_EVENT_CONSUMER io.eventuate.messaging.kafka.basic.consumer.OffsetTracker@59d137a1[state={CI_DOP_V3_EVENT-0=io.eventuate.messaging.kafka.basic.consumer.TopicPartitionOffsets@1f75b245[unprocessed=[52274]
I using mysql and I see that it always locked on before the event break down
OBJECT_NAME received_messages
LOCK_TYPE TABLE
LOCK_MODE IX
Do you have any ideals about this issue? Thank you very much!
The text was updated successfully, but these errors were encountered: