http://www.datastax.com/support-forums/tags/amazon Software, Support, and Training for Apache Cassandra en-US Wed, 22 May 2013 10:52:24 +0000 http://bbpress.org/?v=1.0.3 q http://www.datastax.com/support-forums/search.php http://www.datastax.com/support-forums/topic/expanding-cluster-with-ami-version-issue#post-7303 Wed, 31 Oct 2012 18:40:09 +0000 joaquin 7303@http://www.datastax.com/support-forums/ <p>Thanks again for the report! </p> http://www.datastax.com/support-forums/topic/expanding-cluster-with-ami-version-issue#post-7302 Wed, 31 Oct 2012 18:28:56 +0000 Alain 7302@http://www.datastax.com/support-forums/ <p>Hi Joaquin,</p> <p>It works like a charm now.</p> <p>Thanks. </p> http://www.datastax.com/support-forums/topic/expanding-cluster-with-ami-version-issue#post-7297 Wed, 31 Oct 2012 17:50:40 +0000 joaquin 7297@http://www.datastax.com/support-forums/ <p>Hello,</p> <p>This is now patched in the AMI codebase.</p> <p>--release 1.1.2 should work now.</p> <p>Thanks for the bug report!</p> <p>Joaquin </p> http://www.datastax.com/support-forums/topic/expanding-cluster-with-ami-version-issue#post-7213 Tue, 30 Oct 2012 15:45:43 +0000 Alain 7213@http://www.datastax.com/support-forums/ <p>I just tried with the release 1.1.2-1 instead of 1.1.2:</p> <p>Result:</p> <p>Cluster started with these options:<br /> --clustername expand --totalnodes 1 --version community --release 1.1.2-1 --opscenter no</p> <p>------------------------------------<br /> DataStax AMI for DataStax Enterprise<br /> and DataStax Community<br /> AMI version 2.2<br /> DataStax Community version 1.1.6-1</p> <p>------------------------------------ </p> http://www.datastax.com/support-forums/topic/expanding-cluster-with-ami-version-issue#post-7210 Tue, 30 Oct 2012 14:49:23 +0000 Alain 7210@http://www.datastax.com/support-forums/ <p>Hi joaquin,</p> <p>3 month after my last message I need to extend my cluster again and finally can try your solution.</p> <p>in my console after adding an instance I have :</p> <p>Cluster started with these options:<br /> --clustername expand --totalnodes 1 --version community --opscenter no --release 1.1.2</p> <p>But "nodetool -h localhost" version returns<br /> ReleaseVersion: 1.1.6</p> <p>Did I make any mistake ? </p> http://www.datastax.com/support-forums/topic/adding-new-node-to-cassandra-cluster#post-3222 Wed, 18 Jul 2012 10:43:23 +0000 ylitvinov 3222@http://www.datastax.com/support-forums/ <p>Hello.</p> <p>I've installed Cassandra cluster from 6 nodes as described here: <a href="http://www.datastax.com/docs/1.1/install/install_ami" rel="nofollow">http://www.datastax.com/docs/1.1/install/install_ami</a>. I've specified --totalnodes 6 during cluster installation.</p> <p>What is the suggested way to add new Cassandra node to cluster?<br /> How the parameter "--totalnodes" should be changed for the cluster? </p> http://www.datastax.com/support-forums/topic/not-able-to-stop-cassandra-community-amazon-instance#post-3146 Tue, 17 Jul 2012 00:18:53 +0000 joaquin 3146@http://www.datastax.com/support-forums/ <p>Hello,</p> <p>Unfortunately, only EBS backed instances can be stopped. Ephemeral backed instances cannot be.</p> <p>But since this was an often enough request, I've added this experimental functionality to the cassandralauncher:<br /> <a href="https://github.com/joaquincasares/cassandralauncher/blob/master/docs/new_features.md#s3-store-and-restore" rel="nofollow">https://github.com/joaquincasares/cassandralauncher/blob/master/docs/new_features.md#s3-store-and-restore</a></p> <p>This tool is written by me and updated in parallel to the ComboAMI, but is not supported by DataStax. Feel free to look into the store and restore functionality to see if that works for your current scenario.</p> <p>The code is simple enough to modify if you want to use it in-house:<br /> <a href="https://github.com/joaquincasares/cassandralauncher/blob/master/cassandralauncher/datastax_s3_store" rel="nofollow">https://github.com/joaquincasares/cassandralauncher/blob/master/cassandralauncher/datastax_s3_store</a><br /> <a href="https://github.com/joaquincasares/cassandralauncher/blob/master/cassandralauncher/datastax_s3_restore" rel="nofollow">https://github.com/joaquincasares/cassandralauncher/blob/master/cassandralauncher/datastax_s3_restore</a></p> <p>Legal note:<br /> Keep in mind that each node has to be stored and that there is no guarantee from DataStax that protects against data loss.</p> <p>Thanks,<br /> Joaquin </p> http://www.datastax.com/support-forums/topic/expanding-cluster-with-ami-version-issue#post-3145 Tue, 17 Jul 2012 00:12:21 +0000 joaquin 3145@http://www.datastax.com/support-forums/ <p>Hello Alain,</p> <p>Use the --release option to set your DSE/DSC version.<br /> <a href="https://github.com/riptano/ComboAMI/blob/2.2/SWITCHES.md" rel="nofollow">https://github.com/riptano/ComboAMI/blob/2.2/SWITCHES.md</a></p> <p>I've messaged our docs team to ensure this option is visible through our docs as well.</p> <p>Thanks,<br /> Joaquin </p> http://www.datastax.com/support-forums/topic/expanding-cluster-with-ami-version-issue#post-3119 Mon, 16 Jul 2012 09:01:45 +0000 Alain 3119@http://www.datastax.com/support-forums/ <p>Hi, I'm trying to expand my cluster on Amazon EC2. The point is my cluster is on version 1.0.9 and the new nodes generated by the AMI will be on 1.1.2. I would like to stay on 1.0.x version for now.</p> <p>How can I add capacity ?</p> <p>Alain </p> http://www.datastax.com/support-forums/topic/not-able-to-stop-cassandra-community-amazon-instance#post-3029 Fri, 13 Jul 2012 14:24:42 +0000 ylitvinov 3029@http://www.datastax.com/support-forums/ <p>Hello.</p> <p>I've followed instructions "Initializing a Cassandra Cluster on Amazon EC2 Using the DataStax AMI" (<a href="http://www.datastax.com/docs/1.1/install/install_ami" rel="nofollow">http://www.datastax.com/docs/1.1/install/install_ami</a>) and successfully started new Cassandra instance.</p> <p>Unfortunately, it's not possible to Stop it from Amazon Management Console. Only Terminate and Reboot actions are available.</p> <p>Is there any way to Stop it?<br /> If not, then what is the suggesting way to avoid extra cost from having running instance (currently we don't need, but we don't want to terminate it because that will lead to data loss). </p> http://www.datastax.com/support-forums/topic/technical-question-about-opscenter#post-404 Thu, 04 Aug 2011 19:35:11 +0000 nickmbailey 404@http://www.datastax.com/support-forums/ <p>It would be possible to bundle the agent into the ami.</p> <p>The agent needs 3 things in order to work with opscenter: The ip for opscenter, the agent's own ip, and the correct ssl files.</p> <p>The ip for opscenter and the agent ip are located in a config file at '/var/lib/opscenter-agent/conf/address.yaml'. You will need to configure those properties correctly when the new ec2 server boots up.</p> <p>The ssl files that opscenter uses are generated when the main opscenter package is installed, and are lcoated in /var/lib/opscenter/ssl/. The correct files for the agent are then installed at /var/lib/opscenter-agent/ssl on the agent machines. You can use the same set of files between installations if you wish. So if you configure your machines to always use the same ssl files and configure the ips in address.yaml you should be able to do something like this. </p> http://www.datastax.com/support-forums/topic/technical-question-about-opscenter#post-403 Thu, 04 Aug 2011 18:55:24 +0000 blueplastic 403@http://www.datastax.com/support-forums/ <p>I have a question about some of the details of OpsCenter's Column Family in Cassandra.</p> <p>We are working on building a recyclable demo of Cassandra in Amazon using custom AMIs and EBS volumes. I have a question about whether OpsCenter can be installed permanently into the AMIs or whether we would have to reinstall it each time we respawn the cluster (with different IPs) using the AMIs.</p> <p>Say I have 5 Amazon EC2 nodes running Brisk 1.0 and the first node has OpsCenter installed on it. The Cassandra database (including the OpsCenter CF) is not on the local ephemeral drives, but rather on EBS volumes that were connected to the 5 nodes. </p> <p>Then I permanently store each node as an AMI that I can relaunch later to respawn the cluster. So, typically we will terminate the 5 nodes, but keep the databases intact on the 5 EBS volumes. When we want to show a demo of Cassandra, we'll launch 5 new EC2 nodes (from 5 individualized AMIs) and reconnect the 5 EBS volumes to the new EC2 nodes. Note that the IP addresses for the new 5 nodes will be different than the old five nodes. We have some puppet scripts that will update the YAML file and other configuration files on the fresh 5 nodes before starting Cassandra.</p> <p>Casssandra restarts fine and reconnects to all of the databases on the EBS drive. But my question is regarding OpsCenter.</p> <p>When OpsCenter is first installed, it detects the Amazon Private IPs for all 5 nodes and installs Agents on them and creates a special OpsCenter Column Family to store metrics.</p> <p>My question is: In our recyclable demo, can we install OpsCenter on the first node and the agents on the rest of the nodes BEFORE saving our permanent AMIs? Are the private IPs for the cluster stored that OpsCenter Column family so that it would get confused/break if the cluster started up with different IPs? </p> <p>Currently, we don't have OpsCenter on the AMIs. Instead every time we launch a fresh 5 nodes, we reinstall OpsCenter and the Agents.</p> <p>We would like to automate this and make the respawn process faster by just baking OpsCenter into the AMI so even if we relaunch the cluster with new private IPs, we don't have to reinstall OpsCenter.</p> <p>Is it possible to do what we want to do?</p> <p>- Sameer </p>