Glad you got it going!
There is a REST call you can make to priam telling it to double the cluster
size (/v1/cassconfig/double_ring), it will pre fill all SimpleDB entries for
when the nodes come online, you then change the number of nodes on the
autoscale group. Now that Priam supports C* 1.2
Thanks a lot Ben, actually I managed to make it work erasing the SimpleDB
Priam uses to keeps instances... I would pulled the last commit from the
repo, not sure if it helped or not.
But you message made me curious about something... How do you do to add
more Cassandra nodes on the fly? Just upda
Off the top of my head I would check to make sure the Autoscaling Group you
created is restricted to a single Availability Zone, also Priam sets the
number of EC2 instances it expects based on the maximum instance count you
set on your scaling group (it did this last time i checked a few months
ago
One additional important info, I checked here and the seeds seems really
different on each node. The command
echo `curl http://127.0.0.1:8080/Priam/REST/v1/cassconfig/get_seeds`
returns ip2 on first node and ip1,ip1 on second node.
Any idea why? It's probably what is causing cassandra to die, right
Hello Ben, Thanks for the willingness to help,
2013/2/27 Ben Bromhead
>
> Have your added the priam java agent to cassandras JVM argurments (e.g.
> -javaagent:$CASS_HOME/lib/priam-cass-extensions-1.1.15.jar) and does the
> web container running priam have permissions to write to the cassandra
>
Hi Marcelo
A few questions:
Have your added the priam java agent to cassandras JVM argurments (e.g.
-javaagent:$CASS_HOME/lib/priam-cass-extensions-1.1.15.jar) and does the
web container running priam have permissions to write to the cassandra
config directory? Also what do the priam logs say?
