spqr icon indicating copy to clipboard operation
spqr copied to clipboard

What I should do after getting `multishard state is out of sync`?

Open Denchick opened this issue 3 years ago • 1 comments

DEBUG4: 2022/11/18 06:22:36.689840 sending &{String:DROP TABLE IF EXISTS sbtest1} to sh shard02
DEBUG2: 2022/11/18 06:22:36.690048 multishard server init: got *pgproto3.NoticeResponse msg from shard01 shard
DEBUG1: 2022/11/18 06:22:36.690075 complete relay iter with TX idle
DEBUG1: 2022/11/18 06:22:36.690080 unroute multishard route
DEBUG3: 2022/11/18 06:22:36.690090 sending *pgproto3.ReadyForQuery to client
LOG: 2022/11/18 06:22:36.690123 end of tx unrouting from [{shard01 true} {shard02 true}]
LOG: 2022/11/18 06:22:36.690129 unrouting from datashard shard01
LOG: 2022/11/18 06:22:36.690134 unrouting from datashard shard02
DEBUG5: 2022/11/18 06:22:36.690140 client iter done with multishard state is out of sync
LOG: 2022/11/18 06:22:36.690442 multishard server: got *pgproto3.CommandComplete message from shard01 shard while rollback after error
DEBUG3: 2022/11/18 06:22:36.696279 Received <nil> from client

Denchick avatar Nov 18 '22 06:11 Denchick

One more problem with multi shard

DEBUG2: 2022/11/18 09:38:45.812381 multishard server init: got *pgproto3.ReadyForQuery msg from shard01 shard
DEBUG2: 2022/11/18 09:38:45.812387 multishard server init: got *pgproto3.ParameterStatus msg from shard02 shard
DEBUG2: 2022/11/18 09:38:45.812391 multishard server init: got *pgproto3.ReadyForQuery msg from shard02 shard
DEBUG1: 2022/11/18 09:38:45.812404 flush message buff
DEBUG1: 2022/11/18 09:38:45.812412 flushing {String:DROP TABLE IF EXISTS sbtest1} waitForResp: true replyCl: true
DEBUG2: 2022/11/18 09:38:45.812429 process query &{DROP TABLE IF EXISTS sbtest1}
DEBUG4: 2022/11/18 09:38:45.812434 sending &{String:DROP TABLE IF EXISTS sbtest1} to sh shard01
DEBUG4: 2022/11/18 09:38:45.812465 sending &{String:DROP TABLE IF EXISTS sbtest1} to sh shard02
DEBUG2: 2022/11/18 09:38:46.813610 multishard server init: got *pgproto3.ErrorResponse msg from shard01 shard
ERROR: 2022/11/18 09:38:46.813639 err got is [canceling statement due to lock timeout]
DEBUG3: 2022/11/18 09:38:46.813668 sending *pgproto3.ErrorResponse to client
DEBUG1: 2022/11/18 09:38:46.813720 complete relay iter with TX unknown
DEBUG1: 2022/11/18 09:38:46.813726 unroute multishard route
DEBUG3: 2022/11/18 09:38:46.813730 sending *pgproto3.ReadyForQuery to client
LOG: 2022/11/18 09:38:46.813767 end of tx unrouting from [{shard01 true} {shard02 true}]
LOG: 2022/11/18 09:38:46.813773 unrouting from datashard shard01
LOG: 2022/11/18 09:38:46.813778 unrouting from datashard shard02
DEBUG1: 2022/11/18 09:38:46.813785 active shards are 0x9ebee0
DEBUG3: 2022/11/18 09:38:46.813902 Received *pgproto3.Terminate from client
DEBUG1: 2022/11/18 09:38:46.813912 received *pgproto3.Terminate msg, 0xc00056c518
DEBUG3: 2022/11/18 09:38:46.813919 Received <nil> from client

Denchick avatar Nov 18 '22 09:11 Denchick

Stale issue

Denchick avatar Nov 04 '24 13:11 Denchick