Hi,
offheap_objects was removed in releases 3.2.x then reintroduced in release
3.4: I vould like to know if someone has used offheap_objects in Cassandra 2.1:
stable or not, improvement observed or not...
Thanks.
Ahmed
_
Jack Krupansky gmail.com> writes:
>
>
> If your data is replicated properly (RF=3) and you do QUORUM reads and
writes, you should be able to shut down one node, adjust the configuration,
and restart that node and all should be fine. Do it quickly enough (less
than an hour) and the node shoul
Robert Coli eventbrite.com> writes:
>
> On Mon, Mar 7, 2016 at 2:57 AM, Krzysztof Księżyk
gmail.com> wrote:I see on lsof output that even if keyspace
> is not queried, Cassandra keeps files opened, so I guess it's not safe to
> hotswap, but I'd like to make sure.
>
>
> It is not safe for exa
Cassandra : 3.3
CQLSH : 5.0.1
Is it possible to set up cassandra/cqlsh so that if any node is down, cqlsh
will automatically try to connect to the other surviving nodes, instead of
erroring out. I know it is possible to supply ip_address and port of the UP
node as arguments to cqlsh, but
The referenced article is accurate as far as NULL is concerned, but please
also note that there is now the ability to specify UNSET to avoid
unnecessary tombstones (as of Cassandra 2.2.0):
https://issues.apache.org/jira/browse/CASSANDRA-7304
Adam
On Tue, Mar 8, 2016 at 12:15 PM, Henry M wrote:
Check out Al's Tuning Guide. He discusses offheap objects.
https://tobert.github.io/pages/als-cassandra-21-tuning-guide.html
On Wed, Mar 9, 2016 at 1:54 AM wrote:
> Hi,
>
>
>
> offheap_objects was removed in releases 3.2.x then reintroduced in
> release 3.4: I vould like to know if someone ha
We use them. No signs of stability problems in 2.1 that we’ve attributed to
offheap objects.
From: "aeljami@orange.com"
Reply-To: "user@cassandra.apache.org"
Date: Wednesday, March 9, 2016 at 1:54 AM
To: user
Subject: [C*2.1]memtable_allocation_type: offheap_objects
Hi,
offheap_obj
Hi,
I have question about ntpd. In certain clusters where new datacenters were
added since 1 week we stood-up those machines didn't have ntpd running on them.
Will it cause any problem if we enable or start ntpd now on those newly added
datacenters.
Thanks.
If you don’t overwrite or delete data, it’s not a concern.
If the clocks show a time in the past instead of in the future, it’s not a
concern.
If the clock has drifted significantly into the future, when you start NTP you
may be writing data with timestamps lower than timestamps on data that alr
How far out of sync are the nodes? A few minutes or less? Many hours?
Worst case, you could simply take the entire cluster down until that future
time has passed and then bring it back up.
-- Jack Krupansky
On Wed, Mar 9, 2016 at 11:27 AM, Jeff Jirsa
wrote:
> If you don’t overwrite or delete
On Wed, Mar 9, 2016 at 8:09 AM, Rakesh Kumar wrote:
>
> Is it possible to set up cassandra/cqlsh so that if any node is down,
> cqlsh will automatically try to connect to the other surviving nodes,
> instead of erroring out. I know it is possible to supply ip_address and
> port of the UP node as
the clock is about 30 to 40 seconds behind.
From: Jack Krupansky
To: user@cassandra.apache.org
Sent: Wednesday, March 9, 2016 11:31 AM
Subject: Re: ntpd clock sync
How far out of sync are the nodes? A few minutes or less? Many hours?
Worst case, you could simply take the entire clus
Thanks Adam, that's good to know.
On Wed, Mar 9, 2016 at 7:42 AM, Adam Holmberg
wrote:
> The referenced article is accurate as far as NULL is concerned, but please
> also note that there is now the ability to specify UNSET to avoid
> unnecessary tombstones (as of Cassandra 2.2.0):
> https://issu
Hello,
I keep getting an exception about a clustering key being too long, like
com.datastax.driver.core.exceptions.InvalidQueryException: The sum of
all clustering columns is too long (72650 > 65535)
at
com.datastax.driver.core.Responses$Error.asException(Responses.java:136)
at
Hi Emīls,
Directing this question to the Java driver mailing list will give you
better chances to get an answer:
https://groups.google.com/a/lists.datastax.com/forum/#!forum/java-driver-user
(as a side note, I haven't seen this one before)
On Wed, Mar 9, 2016 at 11:52 AM, Emīls Šolmanis
wrote:
Hey Alex,
I did do a grep for that message in the driver code base and it seems like
it's not there, so I think this is coming from the server.
Only thing I can think of is us exceeding one of the limits (e.g., the 65K
collection item one) and then the error message being super misleading.
I'll c
On Mon, Mar 7, 2016 at 1:25 PM, Nate McCall wrote:
>
>> Rob, can you remember which bug/jira this was? I have not been able to
>> find it.
>> I'm using 2.1.9.
>>
>
> https://issues.apache.org/jira/browse/CASSANDRA-7953
>
> Rob may have a different one, but I've something similar from this issue.
Cassandra : 3.3
CQLSH : 5.0.1
If there is a typo in the column name of the copy command, we get this:
copy mytable
(event_id,event_class_cd,event_ts,receive_ts,event_source_instance,client_id,client_id_type,event_tag,event_udf,client_event_date)
from '/pathtofile.dat'
with DELIMITER = '|'
Thanks, Rob, but... I'll continue to do my best to strongly (vehemently, or
is there an even stronger word for me to use?!) discourage use of Cassandra
in under 4/8 GB of memory. Hey, I just want people to be happy, and trying
to run Cassandra in under 8 GB (or 4 GB for dev) is just... asking for
t
Thank you for reporting this.
I've filed https://issues.apache.org/jira/browse/CASSANDRA-11333.
On Thu, Mar 10, 2016 at 6:16 AM, Rakesh Kumar wrote:
> Cassandra : 3.3
> CQLSH : 5.0.1
>
> If there is a typo in the column name of the copy command, we get this:
>
> copy mytable
> (event_id,ev
On Tue, Mar 8, 2016 at 8:39 PM, Jean Carlo
wrote:
> Hi guys,
>
> I use cassandra stress to populate the next table
>
> CREATE TABLE cf1 (
> kvalue text,
> ktype text,
> prov text,
> dname text,
> dattrib blob,
> dvalue text,
> PRIMARY KEY (kvalue, ktype, prov, dname)
>
Hello there,
I'm wondering is there a good way to measure the write amplification of
Cassandra?
I'm thinking it could be calculated by (size of mutations written to the
node)/(number of bytes written to the disk).
Do we already have the metrics of "size of mutations written to the node"?
I did n
22 matches
Mail list logo
