Re: Replacing disks

2016-02-29 Thread Michał Łowicki
On Mon, Feb 29, 2016 at 8:52 AM, Alain RODRIGUEZ wrote: > I wrote that a few days ago: > http://thelastpickle.com/blog/2016/02/25/removing-a-disk-mapping-from-cassandra.html > > I believe this might help you. > Yes, looks promising. Thanks! > C*heers, > --- > > Alain Rodrig

Too many sstables with DateTieredCompactionStrategy

2016-02-29 Thread 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

Re: Too many sstables with DateTieredCompactionStrategy

2016-02-29 Thread Marcus Eriksson
why do you have 'timestamp_resolution': 'MILLISECONDS'? It should be left as default (MICROSECONDS) unless you do "USING TIMESTAMP "-inserts, see https://issues.apache.org/jira/browse/CASSANDRA-11041 On Mon, Feb 29, 2016 at 2:36 PM, Noorul Islam K M wrote: > > Hi all, > > We are using below comp

Re: Too many sstables with DateTieredCompactionStrategy

2016-02-29 Thread Dominik Keil
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

Re: Too many sstables with DateTieredCompactionStrategy

2016-02-29 Thread Noorul Islam Kamal Malmiyoda
Yes, we have enabled it on OpsCenter. Is that the reason? On Feb 29, 2016 8:07 PM, "Dominik Keil" wrote: > 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_resol

Re: Too many sstables with DateTieredCompactionStrategy

2016-02-29 Thread Alain RODRIGUEZ
Might be due to this: Fixed in 2.1.12 (Assuming you are using C*2.1): https://issues.apache.org/jira/browse/CASSANDRA-10422 Some question to have more context: 1. What C* version are you using? 2. Do you use vnodes? 3. How many vnodes per node? 4. How many nodes / DC do you have?

Re: Too many sstables with DateTieredCompactionStrategy

2016-02-29 Thread Noorul Islam K M
Alain RODRIGUEZ writes: > Might be due to this: > > Fixed in 2.1.12 (Assuming you are using C*2.1): > https://issues.apache.org/jira/browse/CASSANDRA-10422 > > Some question to have more context: > > >1. What C* version are you using? We are using DSE 4.8.3, hence Apache Cassandra 2.1.12.104

Practical limit on number of column families

2016-02-29 Thread Fernando Jimenez
Hi all I have a use case for Cassandra that would require creating a large number of column families. I have found references to early versions of Cassandra where each column family would require a fixed amount of memory on all nodes, effectively imposing an upper limit on the total number of C

Re: Practical limit on number of column families

2016-02-29 Thread Robert Wille
Yes, there is memory overhead for each column family, effectively limiting the number of column families. The general wisdom is that you should limit yourself to a few hundred. Robert On Feb 29, 2016, at 10:30 AM, Fernando Jimenez mailto:fernando.jime...@wealth-port.com>> wrote: Hi all I ha

Re: Too many sstables with DateTieredCompactionStrategy

2016-02-29 Thread Noorul Islam Kamal Malmiyoda
Hello Marcus, I altered the table to set timestamp_resolution to 'MICROSECONDS'. I waited for sometime, but the sstable count did not come down. Do you think I should specific command to reduce the count of sstables after setting this? Thanks and Regards Noorul On Mon, Feb 29, 2016 at 7:22 PM,

Re: Checking replication status

2016-02-29 Thread Jimmy Lin
hi Bryan, I guess I want to find out if there is any way to tell when data will become consistent again in both cases. if the node being down shorter than the max_hint_window(say 2 hours out of 3 hrs max), is there anyway to check the log or JMX etc to see if the hint queue size back to zero or lo

Re: how to read parent_repair_history table?

2016-02-29 Thread Jimmy Lin
is there any other better way to find out a node's token range? I see systems.peers column family seems to include range information, so that is promising but when I look at both datastax java driver and python driver, its API both require a keyspace name and host name, I wonder why ? http://doc

Re: Too many sstables with DateTieredCompactionStrategy

2016-02-29 Thread Lyubo Kamenov
Maybe increase the number of tables that can be compacted by minor compactions[1], i.e. max_threshold (default is set to 32). 1. https://docs.datastax.com/en/cql/3.1/cql/cql_reference/compactSubprop.html?scroll=compactSubprop__compactionSubpropertiesDTCS On Mon, Feb 29, 2016 at 9:28 PM, Noorul Is

Re: Too many sstables with DateTieredCompactionStrategy

2016-02-29 Thread Noorul Islam K M
Lyubo Kamenov writes: > Maybe increase the number of tables that can be compacted by minor > compactions[1], > i.e. max_threshold (default is set to 32). > > 1. > https://docs.datastax.com/en/cql/3.1/cql/cql_reference/compactSubprop.html?scroll=compactSubprop__compactionSubpropertiesDTCS > I see

Re: Practical limit on number of column families

2016-02-29 Thread Jack Krupansky
3,000 entries? What's an "entry"? Do you mean row, column, or... what? You are using the obsolete terminology of CQL2 and Thrift - column family. With CQL3 you should be creating "tables". The practical recommendation of an upper limit of a few hundred tables across all key spaces remains. Techni