Hi Paulo,
There you go https://issues.apache.org/jira/browse/CASSANDRA-12631
Tell me if there is more info I can provide/test fix.
I wonder how the original CASSANDRA-9748 get closed?
I also try the setup on 2.2.5 which is one of the fix versions without success.
Did this setup ever work?
Thanks
Mark,
Is there some official Apache policy on which sites it's appropriate to
link to on an Apache mailing list? If so, could you please post a link to
it so we can all understand the rules. Or is this your personal opinion on
what you'd like to see here?
Thanks!
On Mon, Sep 12, 2016 at 7:34 AM,
On 2016-09-12 09:38 (-0700), daemeon reiydelle wrote:
> Re. throughput. That looks slow for jumbo with 10g. Check your networks.
>
>
It's extremely unlikely you'll be able to saturate a 10g link with a single
instance cassandra.
Faster Cassandra streaming is a work in progress - being able
Generally if you foresee the partitions getting out of control in terms of
size, a method often employed is to bucket according to some criteria. For
example, if I have a time series use case, I might bucket by month or week.
That presumes you can foresee it though. As far as limiting that ca
On 2016-09-12 10:17 (-0700), Anshu Vajpayee wrote:
> Thanks Jeff. I got the answer now.
> Is there any way to put guardrail to avoid large partition from cassandra
> side? I know it is modeling problem and cassandra writes warning on
> system. log for large partition. But I think there shou
Thanks Jeff. I got the answer now.
Is there any way to put guardrail to avoid large partition from cassandra
side? I know it is modeling problem and cassandra writes warning on
system. log for large partition. But I think there should be a way to put
restriction for it from Cassandra side.
On 1
Mark,
As you admitted: "I subscribed to the mailing list on 22 August" and "my
minimal technical knowledge of Cassandra", then why you're even posting
something that's not providing real help to the Cassandra user community?
As stated in RFC 1855 (https://www.ietf.org/rfc/rfc1855.txt), section
3.
On 2016-09-08 18:53 (-0700), Anshu Vajpayee wrote:
> Is there any way to get partition size for a partition key ?
>
Anshu,
The simple answer to your question is that it is not currently possible to get
a partition size for an arbitrary key without quite a lot of work (basically
you'd have t
ubsubscribe
Glad to hear,
Thanks for dropping this here for the record ;-).
C*heers,
---
Alain Rodriguez - al...@thelastpickle.com
France
The Last Pickle - Apache Cassandra Consulting
http://www.thelastpickle.com
2016-09-12 17:15 GMT+02:00 Jacek Luczak :
> Hi Alain,
>
> that was actual
Alexandr,
>> Are there any performance pros or cons?
I would do some benchmarking under realistic data load before going
forward with this data model. I don't have numbers to back this up,
but if the column in question is in the key, I'd be concerned about
the cost of comparing and sorting blobs
Hi Alain,
that was actually a HW issue. The nodes that were behaving badly had a
buggy BIOS that was doing some bad things with power management. That
all resulted in wrong handling of P-states and CPUs were not going
into a full speed. It took a while for me to find it out but now all
is fine, we
It's due to the fact that DataStax hired a bunch of people to write high
quality docs over the last several years that have been linked to from all
over the internet since the company started publishing them. Rankings are
computed by a number of things, one of them being inbound links.
I'm not su
Hello Alexandr,
I replied on the Java driver mailing list. TL;DR: you forgot to flip your
buffers.
Thanks,
Alexandre
On Mon, Sep 12, 2016 at 3:59 PM Alexandr Porunov
wrote:
>
> *Hello,*
>
> *I am using DataStax Java Driver and can not execute "save" command with
> the object mapper.*
>
> *I h
*Hello,*
*I am using DataStax Java Driver and can not execute "save" command with
the object mapper.*
*I have next table:*
CREATE TABLE media_upload.audio_info (
swift_id blob,
size bigint,
audio_id blob,
last_succeed_segment bigint,
PRIMARY KEY (swift_id)
);
*Here is my table in Java
In US english it is also debatable over which words are profane.
https://simple.wikipedia.org/wiki/Profanity
Different words can be profanity to different people, and what words are
thought of as profanity in English can change over time.
Suggestion:
https://www.youtube.com/watch?v=L0MK7qz13bU
O
> don't you think it might be better to keep applying the migration
procedure whatever the version ?
yes, it probably makes sense to keep the procedure for huge datasets to
avoid the cost of anti-compaction. but there seems to be some confusion
where people think it's *required* the procedure, whi
The guidelines stipulate no "excessive or unnecessary" profanity. Perhaps
you also decide what qualifies as necessary or non-excessive?
To summarise my view of this entire discussion: policing users is just...
mind boggling. Well worthy of profanity.
On 12 September 2016 at 14:16, Mark Thoma
This seems like a bug, it seems we always bind the outgoing socket to the
private/listen address. Would you mind opening a JIRA and posting the link
here?
Thanks
2016-09-12 3:35 GMT-03:00 Amir Dafny-Man :
> Hi,
>
>
>
> I followed the docs (http://docs.datastax.com/en/cassandra/3.x/cassandra/
> c
Hi Paulo,
don't you think it might be better to keep applying the migration procedure
whatever the version ?
Anticompaction is pretty expensive on big SSTables and if the cluster has a
lot of data, the first run might be very very long if the nodes are dense,
and especially with a high number of v
On 12/09/2016 12:51, Benedict Elliott Smith wrote:
Please tone down your language. There is no need for profanity.
Now is probably a good time to remind everyone of the Apache Code of
Conduct:
http://www.apache.org/foundation/policies/conduct.html
> (a link to 3rd party docs in response to
On 12/09/2016 13:57, Ryan Svihla wrote:
> It was just the first place google turned up, I made an answer late in the
> evening trying to help someone out on my own free time.
Thanks for the background Ryan. That is really useful.
Googling for "CQL" and the first Apache hosted result (for me any
> Are there equivalent JIRAs for the TODOs somewhere?
Not that I know of, but I think you can create a github pull request for
punctual doc updates and AFAIK a jira ticket will be automatically created
from it.
Alternatively, feel free to open a JIRA meta-ticket with subtasks for doc
TODOs and pu
It was just the first place google turned up, I made an answer late in the
evening trying to help someone out on my own free time.
Regards,
Ryan Svihla
> On Sep 12, 2016, at 6:34 AM, Mark Thomas wrote:
>
>> On 11/09/2016 23:07, Ryan Svihla wrote:
>> 1. A batch with updates to a single partit
> I truncate a table lcs, Then I inserted one line and I used nodetool
flush to have all the sstables. Using a RF 3 I ran a repair -inc directly
and I observed that the value of Reaired At was equal 0.
Were you able to troubleshoot this? The value of repairedAt should be
mutated even when there is
> Can you clarify me please if what you said here applies for the version
2.1.14.
yes
2016-09-06 5:50 GMT-03:00 Jean Carlo :
> Hi Paulo
>
> Can you clarify me please if what you said here
>
> 1. Migration procedure is no longer necessary after CASSANDRA-8004, and
> since you never ran repair bef
Migration procedure is no longer required for incremental repair as of
2.1.4 since CASSANDRA-8004, which was the reason why the migration
procedure was required for LCS before. The migration procedure is only
useful now to skip validation on already repaired sstables in the first
incremental repair
(a link to 3rd party docs in response to a question when an equivalent link
> to project hosted docs was available)
>
No, it wasn't. Or at least the link you sent was not remotely the same as
the link in the email you responded to, which was about how to understand
your partition sizes - not the
On 11/09/2016 23:07, Ryan Svihla wrote:
> 1. A batch with updates to a single partition turns into a single
> mutation so partition writes aren't possible (so may as well use
> Unlogged batches)
> 2. Yes, so use local_serial or serial reads and all updates you want to
> honor LWT need to be LWT as
On 09/09/2016 21:11, Benedict Elliott Smith wrote:
> Come on. This kind of inconsistent 'policing' is not helpful.
How is it inconsistent? Since I subscribed to the mailing list on 22
August, this is the first instance I have seen of anyone providing a
link to third party docs rather than the equi
Are there equivalent JIRAs for the TODOs somewhere?
Jens
On Mon, Sep 12, 2016 at 9:58 AM Brice Dutheil
wrote:
> Really nice update !
>
> There's still some todos ;)
> http://cassandra.apache.org/doc/latest/architecture/storage_engine.html
> http://cassandra.apache.org/doc/latest/architecture/gu
David,
Were you the one who wrote the article? I just finished reading it. It's
excellent! I'm also excited that running mutable infrastructure on
containers is maturing. I have a few specific questions you (or someone
else!) might be able to answer.
1. In the article you state
> We deployed 1,0
Really nice update !
There's still some todos ;)
http://cassandra.apache.org/doc/latest/architecture/storage_engine.html
http://cassandra.apache.org/doc/latest/architecture/guarantees.html
http://cassandra.apache.org/doc/latest/operating/read_repair.html
...
-- Brice
On Mon, Sep 12, 2016 at 6:
33 matches
Mail list logo
