mentId=21428&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-21428>
>> a while back and mean initialization time with a 40 node cluster with auth
>> was ~251ms). Have you tried executing several trials of Cluster.connect
>> within a single JVM
Hi,
I'm going to try to update the DataStax's Java Driver version from 2.1.8 to
3.1.3.
First I ran the test program and measured the time with both drivers v2.1.8
and v3.1.3.
The test program is simply Build a Cluster and connect to it and execute a
simple select statement, and close the Cluster.
ommit log is not required any more so it's rewinding.
>
> See: http://docs.datastax.com/en/cassandra/3.x/cassandra/
> dml/dmlHowDataWritten.html
>
>
>
> 2016年12月8日(木) 17:45 Satoshi Hikida :
>
>> Hi,
>>
>> I have a question about commit log.
>>
>
Hi,
I have a question about commit log.
When commit log segment files are remove actually?
I'm running a single node cluster for a few weeks to test C* performance.
My simple test have been issuing only read and write requests to the
cluster, then the data size (SSTables size) are increasing mon
Hi, all.
I have a question about "batch" commit log sync behavior with C* version
2.2.8.
Here's what I have done:
* set commitlog_sync to the "batch" mode as follows:
> commitlog_sync: batch
> commitlog_sync_batch_window_in_ms: 1
* ran a script which inserts the data to a table
* prepared
; Even if you can't/don't want to upgrade the instance type, the other steps
> will help things.
>
> Ben
>
> On Tue, 11 Oct 2016 at 10:23 Satoshi Hikida wrote:
>
>> Hi,
>>
>> I'm investigating the read/write performance of the C* (Ver. 2.2.8).
>
Hi,
I'm investigating the read/write performance of the C* (Ver. 2.2.8).
However, I have an issue about memtable flushing which forces the spiky
write throughput. And then it affects the latency of the client's requests.
So I want to know the answers for the following questions.
1. Is there any
oes that explain the
> longer time ?
>
> - Rajath
>
>
> Rajath Subramanyam
>
>
> On Fri, Jul 15, 2016 at 12:20 AM, Satoshi Hikida
> wrote:
>
>> Hi Prasenjit
>>
>> Thank you for your reply.
>>
>> However, I
e frequent incremental backups than full backups.
>
> Hope this helps,
> Prasenjit
>
> On Wed, Jul 13, 2016 at 11:54 PM, Satoshi Hikida
> wrote:
>
>> Hi,
>>
>> I want to know the actual advantage of using incremental backup.
>>
>> I've re
Hi,
I have two questions about anti-entropy repair.
Q1:
According to the DataStax document, it's recommended to run full repair
weekly or monthly. Is it needed even if repair with partitioner range
option ("nodetool repair -pr", in C* v2.2+) is set to run periodically for
every node in the cluste
Hi,
I want to know the actual advantage of using incremental backup.
I've read through the DataStax document and it says the merit of using
incremental backup is as follows:
- It allows storing backups offsite without transferring entire snapshots
- With incremental backups and snapshots, it can
mostly bug fixes until the next major stable, to one
>>>> where every odd minor version is a bug fix-only...likely mostly for the
>>>> previous even. The goal being a relatively continuously stable code base in
>>>> odd minor versions.
>>>>
>>>
Hi,
I'm also looking for the most stable version of the Cassandra, too. I read
Carlos's blog post. According to his article, I guess 2.1.x is the most
stable version, is it right? I prefer to use the most stable version rather
than many advanced features. For satisfy my purpose, should I use 2.1.X
04-20 0:19 GMT-03:00 Satoshi Hikida :
>
>> Hi,
>>
>> I'm looking forward to a patch (file) for this bug(CASSANDRA-11344) to
>> apply C* version 2.2.5. Is there available patch for that version? I
>> watched link(https://issues.apache.org/jira/browse/CASSANDRA-1
Hi,
I'm looking forward to a patch (file) for this bug(CASSANDRA-11344) to
apply C* version 2.2.5. Is there available patch for that version? I
watched link(https://issues.apache.org/jira/browse/CASSANDRA-11344) but
couldn't find patch file or something like that. Or is there any
workaround to a
ry, such as dropping the table,
> snapshots, compactions, streaming, there may me other operations I'm not
> familiar with.
>
> Q4. Correct, these are temporary files. Once again, in 3.0 things are
> different and the temporary files have been replaced by transaction logs
> (
On Thu, Mar 17, 2016 at 3:56 PM, Satoshi Hikida wrote:
> Thank you for your very useful advice!
>
>
> Definitely, I'm using Cassandra V2.2.5 not 3.x. And basically I've
> understood what does these logs mean. But I have more a few questions. So I
> would very m
pool of
> page-aligned buffers, and sharing the NIO file channels amongst the readers
> of an sstable, refer to CASSANDRA-8897
> <https://issues.apache.org/jira/browse/CASSANDRA-8897> and CASSANDRA-8893
> <https://issues.apache.org/jira/browse/CASSANDRA-8893> for more detail
Hi,
I have been working on some experiments for Cassandra and found some log
messages as follows in debug.log.
I am not sure what it exactly is, so I would appreciate if someone gives me
some explanations about it.
In my verification, a Cassandra node runs as a stand-alone server on Amazon
EC2 in
19 matches
Mail list logo
