>
> The tombstone compaction options basically do this for you for the right
> settings (unchecked tombstone compaction = true, set threshold to 85% or
> so, don’t try to get clever and set it to something very close to 99%, the
> estimated tombstone ratio isn’t that accurate)
>
>
>
True. I have b
I can vouch for TWCS...we switched from DTCS to TWCS using Jeff's plugin w/
Cassandra 3.0.5 and just upgraded to 3.0.8 today and switched over to the
built-in version of TWCS.
-J
On Mon, Jul 11, 2016 at 1:38 PM, Jeff Jirsa
wrote:
> DTCS is deprecated in favor of TWCS in new versions, yes.
>
>
>
Hi Reza,
I want to ignore the clustering keys orders in my query? Can I do that?
>
I am not sure, I think you can't:
>From https://cassandra.apache.org/doc/cql3/CQL.html:
Another option is CLUSTERING ORDER. It allows to define the ordering of
> rows on disk. It takes the list of the clustering
@Alain, @Jeff
Thank you very much for your time. I really appreciate it!
Yes I found many posts/hints about TWCS, definitely look very promising. I
understand correctly that I can swap compaction strategy without any major
concern, right?
About the read repair, Am I correct in thinking that the
DTCS is deprecated in favor of TWCS in new versions, yes.
Worth mentioning that you can NOT disable blocking read repair which comes
naturally if you use CL > ONE.
> Also instead of major compactions (which comes with its set of issues /
> tradeoffs too) you can think of a script smart
Hi Kant.
it looks like ec2 instances cannot talk to each other using public IP's
"talk to each other" --> port 7000 (if not using ssl, 7001 if using it).
Make sure this port is open. From IP_1: telnet ip_2 7000 will tell you if
the port is opened.
"using public IP's" --> Are you using Ec2Snitch
Hi Jan,
> when I replace the content of a map-valued column (when I replace the
> complete map), will this create tombstones for those map entries that are
> not present in the new map?
This is almost correct, I would be more precise and say that it will create
a range tombstone on this map, an
@Jeff
Rather than being an alternative, isn't your compaction strategy going to
deprecate (and finally replace) DTCS ? That was my understanding from the
ticket CASSANDRA-9666.
@Riccardo
If you are interested in TWCS from Jeff, I believe it has been introduced
in 3.0.8 actually, not 3.0.7
https:
Hi,
it depends.
- If you defined the type as a frozen there will not be tombstone, as
the map is stored as one binary blob. The update is handled as a normal
upsert.
- If you do not use the frozen keyword you are right. There will be range
tombstones for all columns that have been deleted or updat
Hi,
when I replace the content of a map-valued column (when I replace the complete
map), will this create tombstones for those map entries that are not present in
the new map?
My expectation is 'yes', because the map is laid out as normal columns
internally so keys not in the new map should l
'unsubscribe cassandra' in google search (probably not the best keywords):
Result 1: http://www.planetcassandra.org/apache-cassandra-mailing-lists/
Result 2: http://mail-archives.apache.org/mod_mbox/cassandra-user/
Result 3: http://cassandra.apache.org/
I did the work for you: sending a message t
'unsubscribe cassandra' in google search (probably not the best keywords):
Result 1: http://www.planetcassandra.org/apache-cassandra-mailing-lists/
Result 2: http://mail-archives.apache.org/mod_mbox/cassandra-user/
Result 3: http://cassandra.apache.org/
I did the work for you: sending a message t
I would check your security group settings, you need to allow communication
on cassandra ports (ie 9042,...)
On Mon, Jul 11, 2016 at 8:17 AM, daemeon reiydelle
wrote:
> xWell, I seem to recall that the private IP's are valid for communications
> WITHIN one VPC. I assume you can log into one mach
13 matches
Mail list logo
