"which appilcation is trying to write large writes and to which keyspace
and table it is trying to write ??"
--> I don't think there is something such as audit trail for each CQL
query.
You may want to enable slow query logger on the client side (driver side)
and bet on the fact that the queries
There is a lot of pre-flight checks when starting the cassandra server and
they took time.
For integration testing, I have developped a modified CassandraDeamon here
that remove pretty most of those checks:
https://github.com/doanduyhai/Achilles/blob/master/achilles-embedded/src/main/java/info/ar
Thanks. I've disabled durable writes but this is still pretty slow (about
10 seconds).
What issues did you run into with your impl?
On Wed, Oct 19, 2016 at 12:15 PM, DuyHai Doan wrote:
> There is a lot of pre-flight checks when starting the cassandra server and
> they took time.
>
> For integra
As I said, when I bootstrap the server and create some keyspace, sometimes
the schema is not fully initialized and when the test code tried to insert
data, it fails.
I did not have time to dig into the source code to find the root cause,
maybe it's something really stupid and simple to fix. If you
Have you tried starting Cassandra with -Dcassandra.unsafesystem=true ?
On Wed, Oct 19, 2016 at 9:31 AM, DuyHai Doan wrote:
> As I said, when I bootstrap the server and create some keyspace, sometimes
> the schema is not fully initialized and when the test code tried to insert
> data, it fails.
Horschi, you are the hero gotham deserves.
Test time reduced from 10 seconds to 800 ms
On Wed, Oct 19, 2016 at 12:40 PM, horschi wrote:
> Have you tried starting Cassandra with -Dcassandra.unsafesystem=true ?
>
>
> On Wed, Oct 19, 2016 at 9:31 AM, DuyHai Doan wrote:
>
>> As I said, when I boot
Ohh didn't know such system property exist, nice idea!
On Wed, Oct 19, 2016 at 9:40 AM, horschi wrote:
> Have you tried starting Cassandra with -Dcassandra.unsafesystem=true ?
>
>
> On Wed, Oct 19, 2016 at 9:31 AM, DuyHai Doan wrote:
>
>> As I said, when I bootstrap the server and create some k
is there a way to start the incremental repair using the reaper. we
completed full repair successfully and after that i tried to run the
incremental run but getting the below error.
A repair run already exist for the same cluster/keyspace/table but with a
different incremental repair value.Reques
can Cassandra cluster direct or load balance the requests by detecting the
resource usage of a particular node?
The coordinator can optimize latency for a SELECT by asking data from the
lowest-latency replica using DynamicSnitch. It's not really load balancing
per se but it's the closest idea.
What exactly do you mean by "resource usage"? If you mean "data size on disk" -
no.
If you mean "current CPU usage" - it depends on query. Modify query should be
be sent to all nodes owning specific partition key.
For read queries see
http://www.datastax.com/dev/blog/dynamic-snitching-in-cassa
I mean disk/cpu/network usage but I understand what Dynamic snitch does!
On Wed, Oct 19, 2016 at 3:34 AM, Vladimir Yudovin
wrote:
> What exactly do you mean by "resource usage"? If you mean "data size on
> disk" - no.
> If you mean "current CPU usage" - it depends on query. Modify query should
Hi, Ben
Thank you for your reply.
> The AWS instance type you are using is not appropriate for a production
workload
I agree with you. I use it for a just verification of the C* behavior.
So I really want to understand the actual mechanism of the write request
blocking. I would appreciate if yo
Hi Abhishek,
This shows you have two repair units for the same keyspace/table with
different incremental repair settings.
Can you delete your prior repair run (the one with incremental repair set
to false) and then create the new one with incremental repair set to true ?
Let me know how that work
Hi Alex,
that i already did and it worked but my question is if the passed value of
incremental repair flag is different from the existing value then it
should allow to create new repair_unit instead of getting repair_unit based
on cluster name/ keyspace /column combination.
and also if i delete
Abhishek,
can you file an issue on our github repo so that we can further discuss
this ? https://github.com/thelastpickle/cassandra-reaper/issues
Thanks,
On Wed, Oct 19, 2016 at 1:20 PM Abhishek Aggarwal <
abhishek.aggarwa...@snapdeal.com> wrote:
> Hi Alex,
>
> that i already did and it worked
Thanks Doan, will try to enable slow query for app side and will let you
know if it helps or not.
Thanks
James.
On Wed, Oct 19, 2016 at 2:59 AM, DuyHai Doan wrote:
> "which appilcation is trying to write large writes and to which keyspace
> and table it is trying to write ??"
>
> --> I don't t
Hi all,
We use Cassandra 2.1.11 in our product, and we update the Java Drive from
Astyanax(Thrift API) to DataStax Java Driver(Cql) recently, but we
encounter a difficult issue as following, please help us, thanks in advance.
Previously we were using Astyanax API, and we can insert empty timeuuid
Hi,
what does it exactly mean 'empty timeuuid'? UUID takes 16 bytes for storage,
so it should be either null, or some value. Do you mean 'zero' UUID?
Best regards, Vladimir Yudovin,
Winguzone - Hosted Cloud Cassandra
Launch your cluster in minutes.
On Wed, 19 Oct 2016 09:16:29 -
Hey,
We are upgrading from cassandra 2.1 to cassandra 2.2.
With cassandra 2.1 we would periodically repair all nodes, using the -pr
flag.
With cassandra 2.2, the same repair takes a very long time, as cassandra
does an anti compaction after the repair. This anti compaction causes
most (all
Hi Sean,
you should be able to do that by running subrange repairs, which is the
only type of repair that wouldn't trigger anticompaction AFAIK.
Beware that now you will have sstables marked as repaired and others marked
as unrepaired, which will never be compacted together.
You might want to flag
Another question on a same note would be what would be the fastest way to do
repairs of size 10TB cluster ? Full repairs are taking days. So among repair
parallel or repair sub range which is faster in the case of say adding a new
node to the cluster?
Sent from my iPhone
> On Oct 19, 2016, at
Hi Kant,
subrange is a form of full repair, so it will just split the repair process
in smaller yet sequential pieces of work (repair is started giving a start
and end token). Overall, you should not expect improvements other than
having less overstreaming and better chances of success if your clu
Thanks! How do I do an incremental repair when I add a new node?
Sent from my iPhone
> On Oct 19, 2016, at 9:54 AM, Alexander Dejanovski
> wrote:
>
> Hi Kant,
>
> subrange is a form of full repair, so it will just split the repair process
> in smaller yet sequential pieces of work (repair is
Also any suggestions on a tool to orchestrate the incremental repair? Like say
most commonly used
Sent from my iPhone
> On Oct 19, 2016, at 9:54 AM, Alexander Dejanovski
> wrote:
>
> Hi Kant,
>
> subrange is a form of full repair, so it will just split the repair process
> in smaller yet s
Can you explain why you would want to run repair for new nodes?
Aren't you talking about bootstrap, which is not related to repair actually?
Le mer. 19 oct. 2016 18:57, Kant Kodali a écrit :
> Thanks! How do I do an incremental repair when I add a new node?
>
> Sent from my iPhone
>
> On Oct 19
Thanks, we will try that.
Sean
On 16-10-19 09:34 AM, Alexander Dejanovski wrote:
Hi Sean,
you should be able to do that by running subrange repairs, which is
the only type of repair that wouldn't trigger anticompaction AFAIK.
Beware that now you will have sstables marked as repaired and other
Unsubscribe
There aren't that many tools I know to orchestrate repairs and we maintain
a fork of Reaper, that was made by Spotify, and handles incremental repair
: https://github.com/thelastpickle/cassandra-reaper
We just added Cassandra as storage back end (only postgres currently) in
one of the branches, wh
Sorry I shouldn't have said adding a node. Sometimes data seems to be corrupted
or inconsistent in which case would like to run a repair.
Sent from my iPhone
> On Oct 19, 2016, at 10:10 AM, Sean Bridges
> wrote:
>
> Thanks, we will try that.
>
> Sean
>
>> On 16-10-19 09:34 AM, Alexander De
Dear Apache Enthusiast,
ApacheCon Sevilla is now less than a month out, and we need your help
getting the word out. Please tell your colleagues, your friends, and
members of related technical communities, about this event. Rates go up
November 3rd, so register today!
ApacheCon, and Apache Big Dat
Hi,
Is there any public listing of cassandra performance test results with
cstar or cassandra-stress for read and write, with mention of
configurations modified from default and cassandra version.
It would be useful to not redo and do optimisations for cassandra wrt
Threadpools / JVM tuning / Cac
Hi All
I am proud to announce we are making available our production build of
Cassandra 3.7 that we run at Instaclustr (both for ourselves and our
customers). Our release of Cassandra 3.7 includes a number of backported
patches from later versions of Cassandra e.g. 3.8 and 3.9 but doesn't
include
Hi Ben,
Thanks for this awesome contribution. I'm eager to give it a try and test
it out.
Best,
Matija
On Wed, Oct 19, 2016 at 8:55 PM, Ben Bromhead wrote:
> Hi All
>
> I am proud to announce we are making available our production build of
> Cassandra 3.7 that we run at Instaclustr (both for o
Wow, thank you for doing this. This sentiment regarding stability seems to
be widespread. Is the team reconsidering the whole tick-tock cadence? If
not, I would add my voice to those asking that it is revisited.
Steve
On Wed, Oct 19, 2016 at 1:00 PM Matija Gobec wrote:
> Hi Ben,
>
> Thanks for
+1
On Wed, Oct 19, 2016 at 2:07 PM, sfesc...@gmail.com
wrote:
> Wow, thank you for doing this. This sentiment regarding stability seems to
> be widespread. Is the team reconsidering the whole tick-tock cadence? If
> not, I would add my voice to those asking that it is revisited.
>
> Steve
>
> On
Awesome!
On Wed, Oct 19, 2016 at 2:57 PM Jason J. W. Williams <
jasonjwwilli...@gmail.com> wrote:
> +1
>
> On Wed, Oct 19, 2016 at 2:07 PM, sfesc...@gmail.com
> wrote:
>
> Wow, thank you for doing this. This sentiment regarding stability seems to
> be widespread. Is the team reconsidering the wh
unsubscribe
On 19 October 2016 at 21:07, sfesc...@gmail.com wrote:
> Wow, thank you for doing this. This sentiment regarding stability seems to
> be widespread. Is the team reconsidering the whole tick-tock cadence? If
> not, I would add my voice to those asking that it is revisited.
There has certainly be
Hi Vladimir,
Indeed, that's a little weird, I think it is like a empty string: '' but is
a timeuuid value. We have many such records that inserted by Astyanax API,
when we select it in cqlsh, it is like as below, note the column4 is
timeuuid, it is not null or some value, just "empty".
key
Have you already tried using unset values?
http://www.datastax.com/dev/blog/datastax-java-driver-3-0-0-released#unset-values
They are only available starting with protocol version 4 however.
On Thu, Oct 20, 2016 at 10:19 AM, Lijun Huang wrote:
> Hi Vladimir,
>
> Indeed, that's a little weird,
Thanks Stefania, we haven't tried before, and I think the version is not
matched, we are still using,
[cqlsh 4.1.1 | Cassandra 2.1.11 | CQL spec 3.1.1 | Thrift protocol 19.39.0]
On Thu, Oct 20, 2016 at 10:33 AM, Stefania Alborghetti <
stefania.alborghe...@datastax.com> wrote:
> Have you already t
On 19 October 2016 at 17:13, Alexander Dejanovski
wrote:
> There aren't that many tools I know to orchestrate repairs and we maintain
> a fork of Reaper, that was made by Spotify, and handles incremental repair
> : https://github.com/thelastpickle/cassandra-reaper
Looks like you're using subran
Hi Kurt,
we're not actually.
Reaper performs full repair by subrange but does incremental repair on all
ranges at once, node by node.
Subrange is incompatible with incremental repair anyway.
Cheers,
On Thu, Oct 20, 2016 at 5:24 AM kurt Greaves wrote:
>
> On 19 October 2016 at 17:13, Alexander
You're correct, cassandra 2.1 is still using protocol version 3. You need
at least version 2.2.
On Thu, Oct 20, 2016 at 11:18 AM, Lijun Huang wrote:
> Thanks Stefania, we haven't tried before, and I think the version is not
> matched, we are still using,
> [cqlsh 4.1.1 | Cassandra 2.1.11 | CQL s
45 matches
Mail list logo
