Hi,
I am using cassandra version 2.1 . My goal is to do cassandra client to
node security using SSL with my self-signed CA.
Self-signed CA is giving me following files.
1. ca.crt
2. ca.key
3. client.csr
4. client.crt
5. client.key
6. client.p12
I am creating .jks (client.jks) file from client.p1
Hi,
We have Cassandra 2.2.1 on Windows 2008R2-64-bit.
We are noticing that during compaction Cassandra consumes all the available
memory for the VM and bring the VM to a crawl. compaction settings are
default, and we are using sized tiered compaction.
When investigating this, we find through VMMA
It was a process installed by IT that triggered this, when disabling the
process everything went to normal.
Thanks.
Alaa
On Fri, Oct 16, 2015 at 11:32 AM, Alaa Zubaidi (PDF)
wrote:
> Thanks guys,
> I will look into this more, and put an update here, if I find anything
>
> On Fri, Oct 16, 2015 a
On Sat, Oct 24, 2015 at 2:02 PM, Vasileios Vlachos <
vasileiosvlac...@gmail.com> wrote:
>
>> All other means of repair are optimizations which require a certain
>> amount of luck to happen to result in consistency.
>>
>
> Is that true regardless of the CL one uses? So, for example if writing
> QUO
Thanks, I am using most of the suggested parameters to tune compactions. To
clarify, when you say "The sstable_size_in_mb can be thought of a target
for the compaction process moving the file beyond L0." do you mean that
this property is ignored at memtable flush time, and so memtables are
already
The sstable_size_in_mb can be thought of a target for the compaction
process moving the file beyond L0.
Note: If there are more than 32 SSTables in L0, it will switch over to
doing STCS for L0 (you can disable this behavior by passing
-Dcassandra.disable_stcs_in_l0=true as a system property).
Wit
Rob,
Would you mind to elaborate further on this? I am a little concerned that
my understanding (nodetool repair is *not* the only way one can achieve
consistency) is not correct. I understand that if people use CL < QUORUM,
nodetool repair is the only way to go, but I just cannot see how can that
On Mon, Oct 26, 2015 at 7:58 PM, qihuang.zheng wrote:
> Recently we want to delete some c* nodes for data migration. C*
> verision:2.0.15
>
> we use *nodetool decommission* with *nohup: nohup nodetool decommission
> -h xxx *
>
> After execute 3 days already, seems this process did’t finished yet
Hi all,
The docs indicate that memtables are triggered to flush when data in the
commitlog is expiring or based on memtable_flush_period_in_ms.
But LCS has a specified sstable size; when using LCS are memtables flushed
when they hit the desired sstable size (default 160MB) or could L0 sstables
be
Hi Brian,
You can't unsubscribe using the mailing list email. There's a separate
email address for unsubscribing. You can find the unsubscribe email address
using the "Unsubscribe" link at the bottom of the page at
http://cassandra.apache.org
Steve
On Tue, Oct 27, 2015 at 4:44 AM, Brian Tarbox
I’m planning an upgrade from 2.0 to 2.1, and was reading about counters, and
ended up with a question. I read that in 2.0, counters are implemented by
storing deltas, and in 2.1, read-before-write is used to store totals instead.
What does this mean for the following scenario?
Suppose we have a
Searching for a well established company that can provide consulting and
operations support for private multi-dc production Cassandra cluster on
Windows OS. New project. OS is hosting mandate.
Troy Collinsworth
585-576-8761
I try spark-cassandra-connector. As our data from src table has ttl, and
saveToCassandra default does’t insert ttl .
fortunately we have a timestamp field indicate insert time. but
TTLOption.perRow should based on a column,
not support query this column then do calculation to setup ttl. so befor
unsubscribe
--
http://about.me/BrianTarbox
15 matches
Mail list logo
