I’m having an issue where I’ve killed one peer to spin up another, but the Transactor still thinks the first peer is connected (I think), and won’t let the new one connect. The CloudWatch metrics report RemotePeers as the max, even hours after the other peer spun down.

Is there a way to have the transactor release that connection without taking down the transactor completely?

@jgdavey: a peer should definitely time out. You’re sure there aren’t other peers you’re not counting (e.g. console, REST server, etc.)?

Actually, I made an incorrect assumption. There’s an Datomic-unrelated problem going on.

Disregard.

And as always, thank you for the quick reply.