datomic 2023-10-23 | Slack Archive

tjg15:10:13

Hi! I’ve just created Datomic Pro transactor on an EC2 instance. I can reach it on localhost. But I can’t reach it from the outside — not even an EC2 instance on the same VPC The weird thing is, this used to work — I exited & restarted a test bin/transactor that I started months ago, and it just stopped working! Naturally, I tried the bin/datomic create-cf-stack ..., but doesn’t work either Does anyone know what’s happening?

# I can telnet to this successfully, no matter where. So it's not a
# firewall problem.
$ nc -lk -p 4334

# I can only telnet to this on localhost. Not from another EC2
# instance on the same VPC nor anywhere else.
#
# I even tried setting `aws-ingress-cidrs=0.0.0.0/0` in the
# properties file, but doesn't work.
$ bin/transactor -Ddatomic.printConnectionInfo=true -Ddatomic.log=console config/my.properties

tjg15:10:03

My properties file:

protocol=ddb
host=localhost
port=4334
alt-host=ec2-....us-east-1.compute.amazonaws.com
aws-ingress-cidrs=0.0.0.0/0
aws-dynamodb-table=foo-abdce
aws-dynamodb-region=us-east-1
aws-transactor-role=datomic-aws-transactor-7
aws-peer-role=datomic-aws-peer-7
memory-index-threshold=32m
memory-index-max=256m
object-cache-max=128m

Ben Kamphaus16:10:31

does it work if you set host to 0.0.0.0 ? I also see a us-west-2 ec2 alt-host and a us-east-1 dynamodb region

tjg16:10:11

Ah yes, thanks, yeah I anonymized this example’s region, but forgot to change that part 😛

tjg16:10:20

Aha! Thanks, it looks like it works, at least in my telnet smoke-test! Ok, let’s see if it works as a transactor serving ddb…

uwo17:10:10

Is it still the case that the only way to efficiently walk an index in reverse is with index-pull?

uwo17:10:21

(I'm using on-prem)

2023-10-23

Channels