Fork me on GitHub
#datomic
<
2016-07-18
>
bhagany17:07:25

I'm beginning the process of getting datomic into production on aws, and running into problems. I'd like to start the transactor in a VPC, but ensure-cf created a security group outside of a VPC. I manually created a security group in the VPC and re-ran ensure-cf, which resulted in the error:

com.amazonaws.AmazonServiceException: Invalid value 'goodsie-datomic-production' for groupName. You may not reference Amazon VPC security groups by name. Please use the corresponding id for this operation.
So I replaced the name of the security group with its id, and got:
com.amazonaws.AmazonServiceException: Value (sg-feb18a85) for parameter GroupName is invalid. Group names may not be in the format sg-*.
I don't see any other id's for security groups. What kind of value does it want?

cap10morgan17:07:32

@bhagany: ran into and worked around this very thing. let me dig up the details.

bhagany17:07:09

@cap10morgan: excellent, thank you

cap10morgan18:07:50

@bhagany: I just switched the LaunchConfiguration’s Properties to use the SecurityGroups parameter (http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-as-launchconfig.html) and put our pre-existing VPC security group IDs into that (the sg-* values). This is all in the CF template JSON file.

bhagany18:07:42

okay, so just get to the point where datomic will generate the cf template, and edit it to be correct?

cap10morgan18:07:01

yes, that’s all I’ve found to make it work in a VPC, unfortunately.

bhagany18:07:22

no problem, I was about to do that anyway 🙂 thanks!

cap10morgan18:07:28

np, good luck

kschrader18:07:09

hey all, we moved to Datomic 0.9.5385 on Friday and now when I’m trying to do a data restore to our backup database from s3 I start getting one “Copied” message over and over again (i.e. “Copied 2223 segments, skipped 93335 segments.”) and then eventually the restore times out java.util.concurrent.ExecutionException: java.util.concurrent.ExecutionException: java.net.SocketTimeoutException: Read timed out

kschrader18:07:15

has anyone else seen this happen?

kschrader18:07:51

seemed to have worked after 3 tries

marshall18:07:32

@kschrader: Have you retried and had the same problem?

kschrader18:07:46

it just took 3 tries

kschrader18:07:56

haven’t done it again since then

kschrader18:07:07

it’s just the first time that I’ve ever seen it

kschrader18:07:26

is it a normal error to come across?

marshall19:07:26

it may be a transient failure of S3

kschrader19:07:06

ok, I’ll watch it and see if it comes up again

zane20:07:20

Is there a predicate for whether a value is a datomic connection?

Chris O’Donnell21:07:35

@zane: (or (instance? datomic.peer.Connection conn) (instance? datomic.peer.LocalConnection conn)) ?

Chris O’Donnell21:07:00

oops, missed datomic.peer.RemoteConnection