This is interesting, because I am definitely seeing three different types of
values. See attached screenshot and link.
Link: https://gist.github.com/JensRantil/d162801812ca48ad3f75
Image/screenshot: https://www.dropbox.com/s/vczzgrf0vk9adzk/cqlsh-int.png?dl=0
Cheers,
Jens
———
Jens Rantil
> What do you mean by “cqlsh explicitely writes ‘null’ in those cells” ? Are
> you seing textual value “null” written in the cells ?
Just to clarify, I am seeing three types of output for an int field. It’s
either:
* Empty output. Nothing. Nil. Also ‘’.
* An integer written in green. Reg
Janne,
I filed CASSANDRA-8177 [1] for this. Maybe comment on the jira that you
are having the same problem.
Sean
[1] https://issues.apache.org/jira/browse/CASSANDRA-8177
On Thu, Oct 23, 2014 at 2:04 PM, Janne Jalkanen
wrote:
>
> On 23 Oct 2014, at 21:29 , Robert Coli wrote:
>
> On Thu, Oct
On Fri, Oct 24, 2014 at 6:38 AM, Jens Rantil wrote:
>
> Just to clarify, I am seeing three types of output for an int field. It’s
> either:
> * Empty output. Nothing. Nil. Also ‘’.
> * An integer written in green. Regexp: [0-9]+
> * Explicitly ‘null’ written in red letters.
>
Some types (incl
The Cassandra team is pleased to announce the release of Apache Cassandra
version 2.1.1.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source an
I'm also curious to know if this was ever resolved or if there's any other
recommended steps to take to continue to track it down. I'm seeing the same
issue in our production cluster, which is running Cassandra 2.0.10 and JVM
1.7u71, using the CMS collector. Just as described above, the issue is lo
Thanks very much for this maintenance release :-)
Are there any known issues with ccm on 2.1.1 (see trace below)?
Or does the release require time to propagate itself out?
Traceback (most recent call last):
File "/usr/local/bin/ccm", line 4, in
__import__('pkg_resources').run_script('ccm=
On Fri, Oct 24, 2014 at 6:36 PM, Ben Hood <0x6e6...@gmail.com> wrote:
> Or does the release require time to propagate itself out?
The ccm team inform me that the binaries might take up to 48 hours to
propagate their way out.
The Cassandra team is pleased to announce the release of Apache Cassandra
version 2.0.11.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source a
Hello
Anyone encountered the following issue and any workaround? Our Storm
topology was written in Clojure.
Our team is upgrading one of our storm topology from using cassandra 1.2 to
cassandra 2.0, and we have found one problem that is difficult to tackle
This certainly sounds like a JVM bug.
We are running C* 2.0.9 on pretty high end machines with pretty large heaps,
and don’t seem to have seen this (note we are on 7u67, so that might be an
interesting data point, though since the old thread predated that probably not)
1) From the app/java side
Commented and added a munin graph, if it helps. For the record, I’m happy with
-par performance for now.
/Janne
On 24 Oct 2014, at 18:59, Sean Bridges wrote:
> Janne,
>
> I filed CASSANDRA-8177 [1] for this. Maybe comment on the jira that you are
> having the same problem.
>
> Sean
>
> [
Actually - there is
-XX:+SafepointTimeout
which will print out offending threads (assuming you reach a 10 second pause)…
That is probably your best bet.
> On Oct 24, 2014, at 2:38 PM, graham sanderson wrote:
>
> This certainly sounds like a JVM bug.
>
> We are running C* 2.0.9 on pretty hig
And -XX:SafepointTimeoutDelay=xxx
to set how long before it dumps output (defaults to 1 I believe)…
Note it doesn’t actually timeout by default, it just prints the problematic
threads after that time and keeps on waiting
> On Oct 24, 2014, at 2:44 PM, graham sanderson wrote:
>
> Actually
I was wondering if anybody had any specific experiences with repair and
bootstrapping new nodes after switching to vnodes that they could share here
(or email me privately.) I mean, how was the performance of repair and
bootstrap impacted, cluster reliability, cluster load, ease of maintaining t
On Fri, Oct 24, 2014 at 3:54 PM, Jack Krupansky
wrote:
> I was wondering if anybody had any specific experiences with repair and
> bootstrapping new nodes after switching to vnodes that they could share
> here (or email me privately.) I mean, how was the performance of repair and
> bootstrap im
If anyone used incremental repair feature in 2.1 environment with
vnodes, I'd like to hear how it is doing.
Validation is the main time consuming part of repair, and it should be
much better after you switch to incremental.
I did some experiment regarding CASSANDRA-5220 like doing repairing
some r
17 matches
Mail list logo
