Re: CQL collections and Solr dynamic fields
Well, the doc does state that limitation - *In CQL-based Solr cores, the Solr schema fields that are dynamic and multivalued are not supported* - but DataStax will have to clarify whether that is still true and true for lists and sets. See: http://docs.datastax.com/en/datastax_enterprise/4.7//datastax_enterprise/srch/srchDynFlds.html -- Jack Krupansky On Mon, Jun 22, 2015 at 10:23 AM, Moshe Kranc moshekr...@gmail.com wrote: Lists and sets are implemented as multivalue fields, and dse solr does not support dynamic multivalue fields. Therefore, I conclude that dse solr does not support dynamic field search for sets and lists, I. E. I will have to modify the solr schema and re-index each time I add a new CQL llist or set. Is my logic correct? On Monday, June 22, 2015, Jack Krupansky jack.krupan...@gmail.com wrote: List and set collections are mapped to multivalued Solr fields - a Solr query will match on any of the values in a multivalued Solr field (or keywords within those multiple values for Solr tokenized text fields.) See: http://docs.datastax.com/en/datastax_enterprise/4.7//datastax_enterprise/srch/srchSolrType.html -- Jack Krupansky On Mon, Jun 22, 2015 at 4:32 AM, Moshe Kranc moshekr...@gmail.com wrote: In the DSE 4.7 advanced tutorial, there is an example of using a CQL map together with Solr dynamic fields, so that every map entry is automatically indexed by Solr. Does this work for the other CQL collections, namely lists and sets? Can I define CQL lists and sets to use Solr dynamic fields, so they are automatically indexed by Solr?
Re: Detect Repair is finish
You can do this with two nodetool commands: nodetool compactionstats will check on active Merkle Tree calculations. nodetool netstats will list out any active repair streams. Aaron Morton posted a Bash script/command a while back that you can just paste into the (linux) command line to monitor active streams for you: while true; do date; diff (nodetool -h localhost netstats) (sleep 5 nodetool -h localhost netstats); done Hope this helps, Aaron Ploetz On Mon, Jun 22, 2015 at 8:40 AM, Jean Tremblay jean.tremb...@zen-innovations.com wrote: Hi, What is the best way to see if a repair is finished? Is there a JMX object or is there a command to see if a repair is finished? What happens if by mistake an operator starts a repair before the previous is not yet finished? Will they execute both one after the other or at the same time? Thanks for your help. Jean
[RELEASE] Apache Cassandra 2.0.16 released
The Cassandra team is pleased to announce the release of Apache Cassandra version 2.0.16. Apache Cassandra is a fully distributed database. It is the right choice when you need scalability and high availability without compromising performance. http://cassandra.apache.org/ Downloads of source and binary distributions are listed in our download section: http://cassandra.apache.org/download/ This version is a bug fix release[1] on the 2.0 series. As always, please pay attention to the release notes[2] and Let us know[3] if you were to encounter any problem. Enjoy! [1]: http://goo.gl/XtSTxA (CHANGES.txt) [2]: http://goo.gl/9NHMdH (NEWS.txt) [3]: https://issues.apache.org/jira/browse/CASSANDRA
Re: Detect Repair is finish
On Mon, Jun 22, 2015 at 6:40 AM, Jean Tremblay jean.tremb...@zen-innovations.com wrote: What is the best way to see if a repair is finished? Is there a JMX object or is there a command to see if a repair is finished? What happens if by mistake an operator starts a repair before the previous is not yet finished? Will they execute both one after the other or at the same time? Circa (unreleased) 2.2.0 : https://issues.apache.org/jira/browse/CASSANDRA-5483 =Rob
Re: how the binary ‘cassandra’ will recognize the path to the file cassandra.yaml ?
in a tarball installation, the location of cassandra.yaml is defined by the property $CASSANDRA_CONF defined on bin/cassandra.in.sh this file is located by the bin/cassandra binary, and can be in one of the following directories: bin/cassandra.in.sh ~/.cassandra.in.sh /usr/share/cassandra/cassandra.in.sh /usr/local/share/cassandra/cassandra.in.sh /opt/cassandra/cassandra.in.sh you may find documentation on that by reading the CONTROLLING STARTUP section of your bin/cassandra executable 2015-06-20 9:28 GMT-03:00 Thouraya TH thouray...@gmail.com: Hi all; I have, yesterday, downloaded cassandra archive and unpack it. I have this following structure: https://www.dropbox.com/s/4s0xb1os3gi8dr6/cassandra.PNG?dl=0 I have change some configs in the yaml (listen_address, seeds, rpc_address). My question: how the binary ‘cassandra’ will recognize the path to the file cassandra.yaml ? Thanks a lot. Best Regards.
Re: CQL collections and Solr dynamic fields
List and set collections are mapped to multivalued Solr fields - a Solr query will match on any of the values in a multivalued Solr field (or keywords within those multiple values for Solr tokenized text fields.) See: http://docs.datastax.com/en/datastax_enterprise/4.7//datastax_enterprise/srch/srchSolrType.html -- Jack Krupansky On Mon, Jun 22, 2015 at 4:32 AM, Moshe Kranc moshekr...@gmail.com wrote: In the DSE 4.7 advanced tutorial, there is an example of using a CQL map together with Solr dynamic fields, so that every map entry is automatically indexed by Solr. Does this work for the other CQL collections, namely lists and sets? Can I define CQL lists and sets to use Solr dynamic fields, so they are automatically indexed by Solr?
CQL collections and Solr dynamic fields
In the DSE 4.7 advanced tutorial, there is an example of using a CQL map together with Solr dynamic fields, so that every map entry is automatically indexed by Solr. Does this work for the other CQL collections, namely lists and sets? Can I define CQL lists and sets to use Solr dynamic fields, so they are automatically indexed by Solr?
Re: Create a smaller cluster based on snapshost
Hi, I'm aware of at least 2 ways: 1. create 6 node cluster, restore snapshot to it from original cluster; and reduce this second cluster to 3 nodes. in this case, you should be careful in picking nodes to be decommissioned to avoid additional rebalance of cluster and changing tokens. 2. prepare the original cluster for multi-DC configuration; add second DC with 3 nodes. in this case, you can also switch to vnodes in 2nd, new DC, which is good idea hope this helps. 2015-06-22 6:25 GMT+03:00 John Wong gokoproj...@gmail.com: Hi. Supposed I have a 6-node cluster running and I want to build a 3-node cluster based on that 6-node cluster. What is the recommended way to quickly build such cluster? Each node is about 120Gb and we have RF=3. We are on Cassandra 1.2.19 and we are not using vnode. My initial research shows it can either be done with sstableloader or restore using snapshot and fix the token range. In the case of sstableloader, given it is streaming, and we are restoring from a live server, this seems to be a slow process if we throttle the traffic. Even if I take this route, do I just pick 3 node out of the 6 nodes in any random order? In the case of restoring from snapshots I have restored a 6-node replica with just copying snapshot files (along with schema files), run nodetool refresh, and should be able to complete in a few hours. But now with smaller replica, do I again just pick snapshots from any 3 nodes? What and why do I need to fix token range (from what I read)? Any feedback is appreciated. Thanks. John -- with best regards, Vitalii Skakun
Re: system-hints compaction all the time
what's your questions?
On Mon, Jun 22, 2015 at 12:05 AM, 曹志富 cao.zh...@gmail.com wrote:
the logger like this :
INFO [CompactionExecutor:501] 2015-06-21 21:42:36,306
CompactionTask.java:140 - Compacting
[SSTableReader(path='/home/ant/apache-cassandra-2.1.6/bin/../data/data/system/hints/system-hints-ka-365-Data.db')]
INFO [CompactionExecutor:501] 2015-06-21 21:42:37,782
CompactionTask.java:270 - Compacted 1 sstables to
[bin/../data/data/system/hints/system-hints-ka-366,]. 18,710,207 bytes to
18,710,207 (~100% of original) in 1,476ms = 12.089054MB/s. 11 total
partitions merged to 11. Partition merge counts were {1:11, }
INFO [CompactionExecutor:502] 2015-06-21 21:52:37,784
CompactionTask.java:140 - Compacting
[SSTableReader(path='/home/ant/apache-cassandra-2.1.6/bin/../data/data/system/hints/system-hints-ka-366-Data.db')]
INFO [CompactionExecutor:502] 2015-06-21 21:52:39,223
CompactionTask.java:270 - Compacted 1 sstables to
[bin/../data/data/system/hints/system-hints-ka-367,]. 18,710,207 bytes to
18,710,207 (~100% of original) in 1,438ms = 12.408515MB/s. 11 total
partitions merged to 11. Partition merge counts were {1:11, }
INFO [CompactionExecutor:503] 2015-06-21 22:02:39,224
CompactionTask.java:140 - Compacting
[SSTableReader(path='/home/ant/apache-cassandra-2.1.6/bin/../data/data/system/hints
/system-hints-ka-367-Data.db')]
INFO [CompactionExecutor:503] 2015-06-21 22:02:40,742
CompactionTask.java:270 - Compacted 1 sstables to
[bin/../data/data/system/hints/system-hints-ka-368,]. 18,710,207 byte
s to 18,710,207 (~100% of original) in 1,517ms = 11.762323MB/s. 11 total
partitions merged to 11. Partition merge counts were {1:11, }
INFO [CompactionExecutor:504] 2015-06-21 22:12:40,743
CompactionTask.java:140 - Compacting
[SSTableReader(path='/home/ant/apache-cassandra-2.1.6/bin/../data/data/system/hints
/system-hints-ka-368-Data.db')]
INFO [CompactionExecutor:504] 2015-06-21 22:12:42,262
CompactionTask.java:270 - Compacted 1 sstables to
[bin/../data/data/system/hints/system-hints-ka-369,]. 18,710,207 byte
s to 18,710,207 (~100% of original) in 1,518ms = 11.754574MB/s. 11 total
partitions merged to 11. Partition merge counts were {1:11, }
INFO [CompactionExecutor:505] 2015-06-21 22:22:42,264
CompactionTask.java:140 - Compacting
[SSTableReader(path='/home/ant/apache-cassandra-2.1.6/bin/../data/data/system/hints
/system-hints-ka-369-Data.db')]
INFO [CompactionExecutor:505] 2015-06-21 22:22:43,750
CompactionTask.java:270 - Compacted 1 sstables to
[bin/../data/data/system/hints/system-hints-ka-370,]. 18,710,207 byte
s to 18,710,207 (~100% of original) in 1,486ms = 12.007701MB/s. 11 total
partitions merged to 11. Partition merge counts were {1:11, }
C* 2.1.6
--
Ranger Tsao
[RELEASE] Apache Cassandra 2.1.7 released
The Cassandra team is pleased to announce the release of Apache Cassandra version 2.1.7. Apache Cassandra is a fully distributed database. It is the right choice when you need scalability and high availability without compromising performance. http://cassandra.apache.org/ Downloads of source and binary distributions are listed in our download section: http://cassandra.apache.org/download/ This version is a bug fix release[1] on the 2.1 series. As always, please pay attention to the release notes[2] and Let us know[3] if you were to encounter any problem. Enjoy! [1]: http://goo.gl/0AxLpL (CHANGES.txt) [2]: http://goo.gl/kkEDSi (NEWS.txt) [3]: https://issues.apache.org/jira/browse/CASSANDRA
Re: CQL collections and Solr dynamic fields
Please do get that clarified - the doc currently says that lists and sets are implemented as multvalued fields, which contradicts your statement. Yes, map collections are implemented as dynamic fields, but list and set collections are somewhat different - or at least the doc says that they are: *Collection list and set: multi-valued field.* -- Jack Krupansky On Mon, Jun 22, 2015 at 9:47 PM, Sebastian Estevez sebastian.este...@datastax.com wrote: Quick clarification, collections are implemented as dynamic fields in DSE (not multivalued fields). Fields that are both dynamic and multivalued are not supported, therefore, you cannot use multivalued fields for collections. All the best, [image: datastax_logo.png] http://www.datastax.com/ Sebastián Estévez Solutions Architect | 954 905 8615 | sebastian.este...@datastax.com [image: linkedin.png] https://www.linkedin.com/company/datastax [image: facebook.png] https://www.facebook.com/datastax [image: twitter.png] https://twitter.com/datastax [image: g+.png] https://plus.google.com/+Datastax/about http://feeds.feedburner.com/datastax http://cassandrasummit-datastax.com/ DataStax is the fastest, most scalable distributed database technology, delivering Apache Cassandra to the world’s most innovative enterprises. Datastax is built to be agile, always-on, and predictably scalable to any size. With more than 500 customers in 45 countries, DataStax is the database technology and transactional backbone of choice for the worlds most innovative companies such as Netflix, Adobe, Intuit, and eBay. On Mon, Jun 22, 2015 at 11:23 AM, Jack Krupansky jack.krupan...@gmail.com wrote: Well, the doc does state that limitation - *In CQL-based Solr cores, the Solr schema fields that are dynamic and multivalued are not supported* - but DataStax will have to clarify whether that is still true and true for lists and sets. See: http://docs.datastax.com/en/datastax_enterprise/4.7//datastax_enterprise/srch/srchDynFlds.html -- Jack Krupansky On Mon, Jun 22, 2015 at 10:23 AM, Moshe Kranc moshekr...@gmail.com wrote: Lists and sets are implemented as multivalue fields, and dse solr does not support dynamic multivalue fields. Therefore, I conclude that dse solr does not support dynamic field search for sets and lists, I. E. I will have to modify the solr schema and re-index each time I add a new CQL llist or set. Is my logic correct? On Monday, June 22, 2015, Jack Krupansky jack.krupan...@gmail.com wrote: List and set collections are mapped to multivalued Solr fields - a Solr query will match on any of the values in a multivalued Solr field (or keywords within those multiple values for Solr tokenized text fields.) See: http://docs.datastax.com/en/datastax_enterprise/4.7//datastax_enterprise/srch/srchSolrType.html -- Jack Krupansky On Mon, Jun 22, 2015 at 4:32 AM, Moshe Kranc moshekr...@gmail.com wrote: In the DSE 4.7 advanced tutorial, there is an example of using a CQL map together with Solr dynamic fields, so that every map entry is automatically indexed by Solr. Does this work for the other CQL collections, namely lists and sets? Can I define CQL lists and sets to use Solr dynamic fields, so they are automatically indexed by Solr?
Re: CQL collections and Solr dynamic fields
Quick clarification, collections are implemented as dynamic fields in DSE (not multivalued fields). Fields that are both dynamic and multivalued are not supported, therefore, you cannot use multivalued fields for collections. All the best, [image: datastax_logo.png] http://www.datastax.com/ Sebastián Estévez Solutions Architect | 954 905 8615 | sebastian.este...@datastax.com [image: linkedin.png] https://www.linkedin.com/company/datastax [image: facebook.png] https://www.facebook.com/datastax [image: twitter.png] https://twitter.com/datastax [image: g+.png] https://plus.google.com/+Datastax/about http://feeds.feedburner.com/datastax http://cassandrasummit-datastax.com/ DataStax is the fastest, most scalable distributed database technology, delivering Apache Cassandra to the world’s most innovative enterprises. Datastax is built to be agile, always-on, and predictably scalable to any size. With more than 500 customers in 45 countries, DataStax is the database technology and transactional backbone of choice for the worlds most innovative companies such as Netflix, Adobe, Intuit, and eBay. On Mon, Jun 22, 2015 at 11:23 AM, Jack Krupansky jack.krupan...@gmail.com wrote: Well, the doc does state that limitation - *In CQL-based Solr cores, the Solr schema fields that are dynamic and multivalued are not supported* - but DataStax will have to clarify whether that is still true and true for lists and sets. See: http://docs.datastax.com/en/datastax_enterprise/4.7//datastax_enterprise/srch/srchDynFlds.html -- Jack Krupansky On Mon, Jun 22, 2015 at 10:23 AM, Moshe Kranc moshekr...@gmail.com wrote: Lists and sets are implemented as multivalue fields, and dse solr does not support dynamic multivalue fields. Therefore, I conclude that dse solr does not support dynamic field search for sets and lists, I. E. I will have to modify the solr schema and re-index each time I add a new CQL llist or set. Is my logic correct? On Monday, June 22, 2015, Jack Krupansky jack.krupan...@gmail.com wrote: List and set collections are mapped to multivalued Solr fields - a Solr query will match on any of the values in a multivalued Solr field (or keywords within those multiple values for Solr tokenized text fields.) See: http://docs.datastax.com/en/datastax_enterprise/4.7//datastax_enterprise/srch/srchSolrType.html -- Jack Krupansky On Mon, Jun 22, 2015 at 4:32 AM, Moshe Kranc moshekr...@gmail.com wrote: In the DSE 4.7 advanced tutorial, there is an example of using a CQL map together with Solr dynamic fields, so that every map entry is automatically indexed by Solr. Does this work for the other CQL collections, namely lists and sets? Can I define CQL lists and sets to use Solr dynamic fields, so they are automatically indexed by Solr?
Re: system-hints compaction all the time
this is unusual.
--
Ranger Tsao
2015-06-22 16:06 GMT+08:00 Jason Wee peich...@gmail.com:
what's your questions?
On Mon, Jun 22, 2015 at 12:05 AM, 曹志富 cao.zh...@gmail.com wrote:
the logger like this :
INFO [CompactionExecutor:501] 2015-06-21 21:42:36,306
CompactionTask.java:140 - Compacting
[SSTableReader(path='/home/ant/apache-cassandra-2.1.6/bin/../data/data/system/hints/system-hints-ka-365-Data.db')]
INFO [CompactionExecutor:501] 2015-06-21 21:42:37,782
CompactionTask.java:270 - Compacted 1 sstables to
[bin/../data/data/system/hints/system-hints-ka-366,]. 18,710,207 bytes to
18,710,207 (~100% of original) in 1,476ms = 12.089054MB/s. 11 total
partitions merged to 11. Partition merge counts were {1:11, }
INFO [CompactionExecutor:502] 2015-06-21 21:52:37,784
CompactionTask.java:140 - Compacting
[SSTableReader(path='/home/ant/apache-cassandra-2.1.6/bin/../data/data/system/hints/system-hints-ka-366-Data.db')]
INFO [CompactionExecutor:502] 2015-06-21 21:52:39,223
CompactionTask.java:270 - Compacted 1 sstables to
[bin/../data/data/system/hints/system-hints-ka-367,]. 18,710,207 bytes to
18,710,207 (~100% of original) in 1,438ms = 12.408515MB/s. 11 total
partitions merged to 11. Partition merge counts were {1:11, }
INFO [CompactionExecutor:503] 2015-06-21 22:02:39,224
CompactionTask.java:140 - Compacting
[SSTableReader(path='/home/ant/apache-cassandra-2.1.6/bin/../data/data/system/hints
/system-hints-ka-367-Data.db')]
INFO [CompactionExecutor:503] 2015-06-21 22:02:40,742
CompactionTask.java:270 - Compacted 1 sstables to
[bin/../data/data/system/hints/system-hints-ka-368,]. 18,710,207 byte
s to 18,710,207 (~100% of original) in 1,517ms = 11.762323MB/s. 11 total
partitions merged to 11. Partition merge counts were {1:11, }
INFO [CompactionExecutor:504] 2015-06-21 22:12:40,743
CompactionTask.java:140 - Compacting
[SSTableReader(path='/home/ant/apache-cassandra-2.1.6/bin/../data/data/system/hints
/system-hints-ka-368-Data.db')]
INFO [CompactionExecutor:504] 2015-06-21 22:12:42,262
CompactionTask.java:270 - Compacted 1 sstables to
[bin/../data/data/system/hints/system-hints-ka-369,]. 18,710,207 byte
s to 18,710,207 (~100% of original) in 1,518ms = 11.754574MB/s. 11 total
partitions merged to 11. Partition merge counts were {1:11, }
INFO [CompactionExecutor:505] 2015-06-21 22:22:42,264
CompactionTask.java:140 - Compacting
[SSTableReader(path='/home/ant/apache-cassandra-2.1.6/bin/../data/data/system/hints
/system-hints-ka-369-Data.db')]
INFO [CompactionExecutor:505] 2015-06-21 22:22:43,750
CompactionTask.java:270 - Compacted 1 sstables to
[bin/../data/data/system/hints/system-hints-ka-370,]. 18,710,207 byte
s to 18,710,207 (~100% of original) in 1,486ms = 12.007701MB/s. 11 total
partitions merged to 11. Partition merge counts were {1:11, }
C* 2.1.6
--
Ranger Tsao
Re: CQL collections and Solr dynamic fields
Jack thanks for your reply. I apologize for the confusion caused by my previous statement. I was thinking just of maps when I replied. Correction - *Lists and Sets are indexed as multivalued fields in DSE Search and Maps are stored as dynamic fields in DSE Search. * Both are indexed automatically once you have created your core appropriately. My second statement was accurate, fields cannot be both dynamic and multivalued. All the best, [image: datastax_logo.png] http://www.datastax.com/ Sebastián Estévez Solutions Architect | 954 905 8615 | sebastian.este...@datastax.com [image: linkedin.png] https://www.linkedin.com/company/datastax [image: facebook.png] https://www.facebook.com/datastax [image: twitter.png] https://twitter.com/datastax [image: g+.png] https://plus.google.com/+Datastax/about http://feeds.feedburner.com/datastax http://cassandrasummit-datastax.com/ DataStax is the fastest, most scalable distributed database technology, delivering Apache Cassandra to the world’s most innovative enterprises. Datastax is built to be agile, always-on, and predictably scalable to any size. With more than 500 customers in 45 countries, DataStax is the database technology and transactional backbone of choice for the worlds most innovative companies such as Netflix, Adobe, Intuit, and eBay. On Mon, Jun 22, 2015 at 10:42 PM, Jack Krupansky jack.krupan...@gmail.com wrote: Please do get that clarified - the doc currently says that lists and sets are implemented as multvalued fields, which contradicts your statement. Yes, map collections are implemented as dynamic fields, but list and set collections are somewhat different - or at least the doc says that they are: *Collection list and set: multi-valued field.* -- Jack Krupansky On Mon, Jun 22, 2015 at 9:47 PM, Sebastian Estevez sebastian.este...@datastax.com wrote: Quick clarification, collections are implemented as dynamic fields in DSE (not multivalued fields). Fields that are both dynamic and multivalued are not supported, therefore, you cannot use multivalued fields for collections. All the best, [image: datastax_logo.png] http://www.datastax.com/ Sebastián Estévez Solutions Architect | 954 905 8615 | sebastian.este...@datastax.com [image: linkedin.png] https://www.linkedin.com/company/datastax [image: facebook.png] https://www.facebook.com/datastax [image: twitter.png] https://twitter.com/datastax [image: g+.png] https://plus.google.com/+Datastax/about http://feeds.feedburner.com/datastax http://cassandrasummit-datastax.com/ DataStax is the fastest, most scalable distributed database technology, delivering Apache Cassandra to the world’s most innovative enterprises. Datastax is built to be agile, always-on, and predictably scalable to any size. With more than 500 customers in 45 countries, DataStax is the database technology and transactional backbone of choice for the worlds most innovative companies such as Netflix, Adobe, Intuit, and eBay. On Mon, Jun 22, 2015 at 11:23 AM, Jack Krupansky jack.krupan...@gmail.com wrote: Well, the doc does state that limitation - *In CQL-based Solr cores, the Solr schema fields that are dynamic and multivalued are not supported* - but DataStax will have to clarify whether that is still true and true for lists and sets. See: http://docs.datastax.com/en/datastax_enterprise/4.7//datastax_enterprise/srch/srchDynFlds.html -- Jack Krupansky On Mon, Jun 22, 2015 at 10:23 AM, Moshe Kranc moshekr...@gmail.com wrote: Lists and sets are implemented as multivalue fields, and dse solr does not support dynamic multivalue fields. Therefore, I conclude that dse solr does not support dynamic field search for sets and lists, I. E. I will have to modify the solr schema and re-index each time I add a new CQL llist or set. Is my logic correct? On Monday, June 22, 2015, Jack Krupansky jack.krupan...@gmail.com wrote: List and set collections are mapped to multivalued Solr fields - a Solr query will match on any of the values in a multivalued Solr field (or keywords within those multiple values for Solr tokenized text fields.) See: http://docs.datastax.com/en/datastax_enterprise/4.7//datastax_enterprise/srch/srchSolrType.html -- Jack Krupansky On Mon, Jun 22, 2015 at 4:32 AM, Moshe Kranc moshekr...@gmail.com wrote: In the DSE 4.7 advanced tutorial, there is an example of using a CQL map together with Solr dynamic fields, so that every map entry is automatically indexed by Solr. Does this work for the other CQL collections, namely lists and sets? Can I define CQL lists and sets to use Solr dynamic fields, so they are automatically indexed by Solr?
Counters 2.1 Accuracy
Hi All, I'm fairly new to Cassandra and am planning on using it as a datastore for an Apache Spark cluster. The use case is fairly simple, read the raw data and perform aggregates and push the rolled up data back to Cassandra. The data models will use counters pretty heavily so I'd like to understand what kind of accuracy should I expect from Cassandra 2.1 when increment the counters. - http://www.datastax.com/dev/blog/whats-new-in-cassandra-2-1-a-better-implementation-of-counters The blog post above states that the new counter implementations are safer although I'm not sure what that means in practice. Will the counters be 99.99% accurate? How often will they be over or under counted? Thanks, Mike.
Memtable Flush Queue Size
Hi, I could see that the configuration for the memtable_flush_queue_size has been removed in the following commit: https://github.com/apache/cassandra/commit/4b54b8acd21999ad4394feb93deb7cca1de445c0#diff-b66584c9ce7b64019b5db5a531deeda1 https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fapache%2Fcassandra%2Fcommit%2F4b54b8acd21999ad4394feb93deb7cca1de445c0%23diff-b66584c9ce7b64019b5db5a531deeda1sa=Dsntz=1usg=AFQjCNGQtBYQQSONkqY6M5tDHx3WMDEZYg But the documentation http://docs.datastax.com/en/cassandra/2.1/cassandra/configuration/configCassandra_yaml_r.html?scroll=reference_ds_qfg_n1r_1k__memtable_flush_queue_size mentions about the existence of the same. I would like to know behaviour of memtable flushing after this change. Does it still put in the queue to be flushed by asynchronous threads? Please help me in this regard. Thanks, Jagadeesh Mohan
Re: connections remain on CLOSE_WAIT state after process is killed after upgrade to 2.0.15
For the record: https://issues.apache.org/jira/browse/CASSANDRA-9630 On Mon, Jun 15, 2015 at 7:19 PM, Paulo Ricardo Motta Gomes paulo.mo...@chaordicsystems.com wrote: Just a quick update, I was able to fix the problem by reverting the patch CASSANDRA-8336 in our custom cassandra build. I don't know the root cause yet though. I will open a JIRA ticket and post here for reference later. On Fri, Jun 12, 2015 at 11:31 AM, Paulo Ricardo Motta Gomes paulo.mo...@chaordicsystems.com wrote: Hello, We recently upgraded a cluster from 2.0.12 to 2.0.15 and now whenever we stop/kill a cassandra process, some other nodes keep a connection with the dead node in the CLOSE_WAIT state on port 7000 for about 5-20 minutes. So, if I start the killed node again, it cannot handshake with the nodes which have a connection on the CLOSE_WAIT state until that connection is closed, so they remain on the down state to each other for 5-20 minutes, until they can handshake again. I believe this is somehow related to the fixes CASSANDRA-8336 and CASSANDRA-9238, and also could be a duplicate of CASSANDRA-8072. I will continue to investigate to see if I find more evidences, but any help at this point would be appreciated, or at least a confirmation that it could be related to any of these tickets. Cheers, -- *Paulo Motta* Chaordic | *Platform* *www.chaordic.com.br http://www.chaordic.com.br/* +55 48 3232.3200 -- *Paulo Motta* Chaordic | *Platform* *www.chaordic.com.br http://www.chaordic.com.br/* +55 48 3232.3200 -- *Paulo Motta* Chaordic | *Platform* *www.chaordic.com.br http://www.chaordic.com.br/* +55 48 3232.3200
Detect Repair is finish
Hi, What is the best way to see if a repair is finished? Is there a JMX object or is there a command to see if a repair is finished? What happens if by mistake an operator starts a repair before the previous is not yet finished? Will they execute both one after the other or at the same time? Thanks for your help. Jean
Re: CQL collections and Solr dynamic fields
Lists and sets are implemented as multivalue fields, and dse solr does not support dynamic multivalue fields. Therefore, I conclude that dse solr does not support dynamic field search for sets and lists, I. E. I will have to modify the solr schema and re-index each time I add a new CQL llist or set. Is my logic correct? On Monday, June 22, 2015, Jack Krupansky jack.krupan...@gmail.com wrote: List and set collections are mapped to multivalued Solr fields - a Solr query will match on any of the values in a multivalued Solr field (or keywords within those multiple values for Solr tokenized text fields.) See: http://docs.datastax.com/en/datastax_enterprise/4.7//datastax_enterprise/srch/srchSolrType.html -- Jack Krupansky On Mon, Jun 22, 2015 at 4:32 AM, Moshe Kranc moshekr...@gmail.com javascript:_e(%7B%7D,'cvml','moshekr...@gmail.com'); wrote: In the DSE 4.7 advanced tutorial, there is an example of using a CQL map together with Solr dynamic fields, so that every map entry is automatically indexed by Solr. Does this work for the other CQL collections, namely lists and sets? Can I define CQL lists and sets to use Solr dynamic fields, so they are automatically indexed by Solr?
