Fork me on GitHub
#datomic
<
2024-06-03
>
zerio17:06:46

anybody know what to do with this in datomic peer logs?

AMQ212054: Destination address={} is blocked. If the system is configured to block make sure you consume messages on this configuration
immediately after that we are seeing the dreaded tx timeout error: :db.error/transaction-timeout Transaction timed out.

jaret17:06:20

Can you share your peer logs? I believe we have a support case open via Jeff. If you don't want to share in here.

zerio17:06:48

@U1QJACBUM i've attached them to the ticket. i don't mind sharing them here either if you think that's better.

jaret17:06:49

I only saw transactor logs on the ticket. I did just notice this and I am looking into it:

datomic.ddb-values - {:ddb-values/get-deitem-consistent-retry "665df059-2461-4ee1-846a-05d55dabe116", :pid 3631, :tid 130269}

zerio17:06:06

oh sorry i can share peer logs as well.

jaret17:06:15

I suspect a DDB error ^ Can you confirm from DDB console that you have no errors or alerts and are not experiencing throttling (i.e. over provisioning levels on write or read)?

jaret17:06:50

If that request ID corresponds with whatever transaction request id is timing out we may want to open a ticket to DDB to get their input. I also would be curious for you to query to see if the transaction succeeded as during a timeout the peer would not know if a txn succeeded. And your logs that you provided do not show a failure other than this DDB level retry.

zerio18:06:32

we don't see any errors/warning or throttling. @U1QJACBUM

zerio18:06:41

i believe our ddb usage is on demand.

👍 1
zerio18:06:21

digging into that transaction now...

jaret18:06:11

I am dropping into a meeting. Will look for the peer logs on the case and the other info I requested there and will circle back after I am out of the meeting.

🙏 1