Fork me on GitHub
#datomic
<
2021-03-23
>
tatut08:03:19

is there an easy way to restart query group nodes without redeploying ions? I have some things nodes do on startup that I’d like them to redo

tatut09:03:55

it seems AWS autoscaling groups has an “instance refresh” functionality, which looks like it would fit the bill

Joe Lane12:03:33

Does that restart the machine or replace it?

tatut13:03:17

it creates new instances

tatut13:03:59

tried it in our dev env that is also production topology, and it worked well

Joe Lane13:03:00

Glad it worked for you. An important thing to remember is that i3.large / i3.xlarge instances support local valcache on the NVMe SSDs. If you replace instances with new ones, you lose a 500 / 1000 GB SSD backed cache of your database (per qg instance) and the new instances will need to rebuild that cache, one miss at a time. Maybe it's not a problem for your situation, but if you find that you're troubleshooting operational issues (degraded query performance, for example), refreshing (aka replacing) the instances shouldn't be the first thing you try. All of the above assumes your QG instances are either i3.large or i3.xlarge.

tatut08:03:26

good to know… not a problem here as this is a temporary measure for something that happens rarely

Michael Stokley22:03:31

can we cancel or abort an in progress write?

Joe Lane23:03:18

Do you mean a transaction?

Michael Stokley23:03:26

yes, a transaction