Re: Changing a cluster name
Also you might want to explicitly do "nodetool flush system". I've recently done this in C* 2.2.6 and just "nodetool flush" would not have flushed the system keyspace, leading to the change in cluster name not being persisted across restarts. Cheers Am 29.06.2016 um 03:36 schrieb Surbhi Gupta: system.local uses local strategy . You need to update on all nodes . On 28 June 2016 at 14:51, Tyler Hobbs <ty...@datastax.com <javascript:_e(%7B%7D,'cvml','ty...@datastax.com');>> wrote: First, make sure that you call nodetool flush after modifying the system table. That's probably why it's not surviving the restart. Second, I believe you will have to do this across all nodes and restart them at the same time. Otherwise, cluster name mismatches will prevent the nodes from communicating with each other. On Fri, Jun 24, 2016 at 3:51 PM, Paul Fife <paulf...@gmail.com <javascript:_e(%7B%7D,'cvml','paulf...@gmail.com');>> wrote: I am following the instructions here to attempt to change the name of a cluster: https://wiki.apache.org/cassandra/FAQ#clustername_mismatch or at least the more up to date advice: http://stackoverflow.com/questions/22006887/cassandra-saved-cluster-name-test-cluster-configured-name I am able to query the system.local to verify the clusterName is modified, but when I restart Cassandra it fails, and the value is back at the original cluster name. Is this still possible, or are there changes preventing this from working anymore? I have attempted this several times and it did actually work the first time, but when I moved around to the other nodes it no longer worked. Thanks, Paul Fife -- Tyler Hobbs DataStax <http://datastax.com/> -- *Dominik Keil* Phone: + 49 (0) 621 150 207 31 Mobile: + 49 (0) 151 626 602 14 Movilizer GmbH Konrad-Zuse-Ring 30 68163 Mannheim Germany -- movilizer.com [image: Visit company website] <http://movilizer.com/> *Reinvent Your Mobile Enterprise* *-Movilizer is moving* After June 27th 2016 Movilizer's new headquarter will be *EASTSITE VIIIKonrad-Zuse-Ring 3068163 Mannheim* <http://movilizer.com/training> <http://movilizer.com/training> *Be the first to know:* Twitter <https://twitter.com/Movilizer> | LinkedIn <https://www.linkedin.com/company/movilizer-gmbh> | Facebook <https://www.facebook.com/Movilizer> | stack overflow <http://stackoverflow.com/questions/tagged/movilizer> Company's registered office: Mannheim HRB: 700323 / Country Court: Mannheim Managing Directors: Alberto Zamora, Jörg Bernauer, Oliver Lesche Please inform us immediately if this e-mail and/or any attachment was transmitted incompletely or was not intelligible. This e-mail and any attachment is for authorized use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender.
Re: C* 2.2.7 ?
+1 there's some bugs fixed we might be or sure are affected by and the change log has become quite large already mind voting von 2.2.7 soon? Am 21.06.2016 um 15:31 schrieb horschi: Hi, are there any plans to release 2.2.7 any time soon? kind regards, Christian -- *Dominik Keil* Phone: + 49 (0) 621 150 207 31 Mobile: + 49 (0) 151 626 602 14 Movilizer GmbH Konrad-Zuse-Ring 30 68163 Mannheim Germany -- movilizer.com [image: Visit company website] <http://movilizer.com/> *Reinvent Your Mobile Enterprise* *-Movilizer is moving* After June 27th 2016 Movilizer's new headquarter will be *EASTSITE VIIIKonrad-Zuse-Ring 3068163 Mannheim* <http://movilizer.com/training> <http://movilizer.com/training> *Be the first to know:* Twitter <https://twitter.com/Movilizer> | LinkedIn <https://www.linkedin.com/company/movilizer-gmbh> | Facebook <https://www.facebook.com/Movilizer> | stack overflow <http://stackoverflow.com/questions/tagged/movilizer> Company's registered office: Mannheim HRB: 700323 / Country Court: Mannheim Managing Directors: Alberto Zamora, Jörg Bernauer, Oliver Lesche Please inform us immediately if this e-mail and/or any attachment was transmitted incompletely or was not intelligible. This e-mail and any attachment is for authorized use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender.
Re: Nodetool clearsnapshot doesn't support Column Families
Hi, Here's Cassandra's JIRA: https://issues.apache.org/jira/browse/CASSANDRA As for your question: Yes, you can just rm -r a snapshot folder... nothing bad will happen, except the deletion of that snapshot, obviously :-) Regards Am 17.05.2016 um 18:42 schrieb Anubhav Kale: > > Hello, > > > > I noticed that clearsnapshot doesn’t support removing snapshots on a > per CF, like how snapshots lets you take it per CF. > > > > http://docs.datastax.com/en/cassandra/2.1/cassandra/tools/toolsClearSnapShot.html > > > > I couldn’t find a JIRA to address this. Is this intentional ? If so, I > am curious to understand the rationale. > > > > In absence of this, I would just rm –rf the folder to suit my > requirements. Are there any bad-effects of doing so ? > > > > Thanks ! > -- *Dominik Keil* Phone: + 49 (0) 621 150 207 31 Mobile: + 49 (0) 151 626 602 14 Movilizer GmbH Julius-Hatry-Strasse 1 68163 Mannheim Germany -- movilizer.com [image: Visit company website] <http://movilizer.com/> *Reinvent Your Mobile Enterprise* <http://movilizer.com/training> <http://movilizer.com/training> *Be the first to know:* Twitter <https://twitter.com/Movilizer> | LinkedIn <https://www.linkedin.com/company/movilizer-gmbh> | Facebook <https://www.facebook.com/Movilizer> | stack overflow <http://stackoverflow.com/questions/tagged/movilizer> Company's registered office: Mannheim HRB: 700323 / Country Court: Mannheim Managing Directors: Alberto Zamora, Jörg Bernauer, Oliver Lesche Please inform us immediately if this e-mail and/or any attachment was transmitted incompletely or was not intelligible. This e-mail and any attachment is for authorized use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender.
Re: Too many sstables with DateTieredCompactionStrategy
Are you using incremental repais?
Am 29.02.2016 um 14:36 schrieb Noorul Islam K M:
> Hi all,
>
> We are using below compaction settings for a table
>
> compaction = {'timestamp_resolution': 'MILLISECONDS',
> 'max_sstable_age_days': '365', 'base_time_seconds': '60', 'class':
> 'org.apache.cassandra.db.compaction.DateTieredCompactionStrategy'}
>
> But it is creating too many sstables. Currently number of sstables
> is 4. We have been injecting data for the last three days.
>
> We have set the compactionthroughput to 128 MB/s
>
> $ nodetool getcompactionthroughput
>
> Current compaction throughput: 128 MB/s
>
> But this is not helping.
>
> How can we control the number of sstables in this case?
>
> Thanks and Regards
> Noorul
--
*Dominik Keil*
Phone: + 49 (0) 621 150 207 31
Mobile: + 49 (0) 151 626 602 14
Movilizer GmbH
Julius-Hatry-Strasse 1
68163 Mannheim
Germany
--
movilizer.com
[image: Visit company website] <http://movilizer.com/>
*Reinvent Your Mobile Enterprise*
<http://movilizer.com/training>
<http://movilizer.com/training>
*Be the first to know:*
Twitter <https://twitter.com/Movilizer> | LinkedIn
<https://www.linkedin.com/company/movilizer-gmbh> | Facebook
<https://www.facebook.com/Movilizer> | stack overflow
<http://stackoverflow.com/questions/tagged/movilizer>
Company's registered office: Mannheim HRB: 700323 / Country Court: Mannheim
Managing Directors: Alberto Zamora, Jörg Bernauer, Oliver Lesche Please
inform us immediately if this e-mail and/or any attachment was transmitted
incompletely or was not intelligible.
This e-mail and any attachment is for authorized use by the intended
recipient(s) only. It may contain proprietary material, confidential
information and/or be subject to legal privilege. It should not be
copied, disclosed to, retained or used by any other party. If you are not
an intended recipient then please promptly delete this e-mail and any
attachment and all copies and inform the sender.
Re: Strategy tools for taking snapshots to load in another cluster instance
Hi Anishek, we are currently also thinking about how to do this in the midterm, though we don't have a test setup yet. My idea was do add one additional node to the source cluster but put it in a different DC as far as Cassandra is concerned. Using the network topology replication strategy you'd assign this DC an RF of 1 for each KS. Obviously you probably want to read and write in LOCAL_QUORUM them to not hamper performance and you need more disk space on that machine. But then, I think, you can just take a snapshot there and use sstableloader to load that into your destination cluster. Since I haven't tried this yet, I cannot tell you hoe feasible this is but it would be nice to get some input here if the idea is at least sound :-) Cheers Am 18.11.2015 um 11:23 schrieb Anishek Agarwal: > Hello > > We have 5 node prod cluster and 3 node test cluster. Is there a way i > can take snapshot of a table in prod and load it test cluster. The > cassandra versions are same. > > Even if there is a tool that can help with this it will be great. > > If not, how do people handle scenarios where data in prod is required > in staging/test clusters for testing to make sure things are correct ? > Does the cluster size have to be same to allow copying of relevant > snapshot data etc? > > > thanks > anishek -- *Dominik Keil* Movilizer GmbH Julius-Hatry-Strasse 1 68163 Mannheim Germany movilizer.com <http://movilizer.com> movilizer.com <http://movilizer.com> *Reinvent Your Mobile Enterprise* Movilizer Days 2015 - Save the date! <http://movilizer.com/save-the-date-2015> Be the first to know: Twitter <https://twitter.com/Movilizer> | LinkedIn <https://www.linkedin.com/company/movilizer-gmbh> | Facebook <https://www.facebook.com/Movilizer> _ Company's registered office: Mannheim HRB: 700323 / Country Court: Mannheim Managing Directors: Alberto Zamora, Jörg Bernauer, Oliver Lesche Please inform us immediately if this e-mail and/or any attachment was transmitted incompletely or was not intelligible. _ This e-mail and any attachment is for authorized use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender.
