Hi,
We are short before going in prod with our cassandra cluster. Now I wonder if
this maybe (while still not fully in prod) a good moment to switch from the
3.0.x to the new tick-tock versions.
On planet cassandra the tick-tock article mentions:
“…We do recognize that it will take some time f
gt;
> cqlsh> SELECT * FROM foo.bar ;
>
> key | cluster | col
> -+-+-
>
> (0 rows)
>
>
>
> Is this really correct?
> I expected the result from the last select to be:
>
> key | cluster | col
> -+-+--
>1 | 1 | null
>
> (1 rows)
>
>
> Regards,
> Tommy
--
--
Marcin Pietraszek
17.60, real=20.60 secs]
Isn't it quite high?
Do you guys have any other thoughts? Which part of gc logs requires
more attention?
On Tue, Jul 21, 2015 at 4:22 PM, Marcin Pietraszek
wrote:
> Yup... it seems like it's gc fault
>
> gc logs
>
> 2015-07-21T14:19:54.336+: 287613
ul 20, 2015 at 9:18 AM, Jason Wee wrote:
> just a guess, gc?
>
> On Mon, Jul 20, 2015 at 3:15 PM, Marcin Pietraszek
> wrote:
>>
>> Hello!
>>
>> I've noticed a strange CPU utilisation patterns on machines in our
>> cluster. After C* daemon restart it b
Hello!
I've noticed a strange CPU utilisation patterns on machines in our
cluster. After C* daemon restart it behaves in a normal way, after a
few weeks since a restart CPU usage starts to raise. Currently on one
of the nodes (screenshots attached) cpu load is ~4. Shortly before
restart load raise
Hi!
Is there any way to force cqlsh to display LexicalUUIDType values in
"more readable way"?
Currently it looks like a hex value mixed with some strange chars (^t @ * g=)
http://www.wepaste.com/kbl/
--
mp
Hi!
We have 56 node cluster with C* 2.0.13 + CASSANDRA-9036 patch
installed. Assume we have nodes A, B, C, D, E. On some irregular basis
one of those nodes starts to report that subset of other nodes is in
DN state although C* deamon on all nodes is running:
A$ nodetool status
UN B
DN C
DN D
UN E
Strange,
could you paste here output of:
$ grep -n exec ./bin/cassandra
On Mon, Mar 31, 2014 at 8:05 PM, Tim Dunphy wrote:
> Is SELinux enabled?
>
>
> Nope! It's disabled.
>
>
> On Mon, Mar 31, 2014 at 2:50 PM, Michael Shuler wrote:
>
>> Is SELinux enabled?
>>
>
>
>
> --
> GPG me!!
>
> gpg --
Have you tried to run it as another user, not root?
On Mon, Mar 31, 2014 at 4:52 PM, Tim Dunphy wrote:
> Hi Marcin,
>
> Thanks! I'm running the bash shell. And for some reason it also looks
> like bash does understand 'exec'.
>
> [root@beta:~] #echo $SHELL
Hi Clint,
I'm guessing you are using vagrant. The thing is cassandra-chef-cookbook
use template cassandra.yaml.erb, where you can find:
"broadcast_address: <%= node[:cassandra][:broadcast_address] %>" which in
turn is equal to "node[:ipaddress]".
Value of node[:ipaddress] depends on how do you con
Hi Tim,
exec is a shell builtin command, what kind of shell do you use?
Please run:
$ echo $SHELL
$ exec
On Sat, Mar 29, 2014 at 11:10 PM, Tim Dunphy wrote:
> hey all..
>
> love using the cassandra database. however I've just installed 2.0.6 onto
> a new host running CentOS 6.5 and when I
oop/lib/commons-cli-1.2.jar:/usr/share/dse/hadoop/lib/commons-codec-1.4.jar:/usr/share/dse/hadoop/lib/commons-collections-3.2.1.jar:/usr/share/dse/hadoop/lib/commons-configuration-1.6.jar:/usr/share/dse/hadoop/lib/commons-digester-1.8.jar:/usr/share/dse/hadoop/lib/commons-el-1.0.jar:/usr/share/ds
Hi,
RSS or VIRT?
Could you paste output of:
$ ps -p `jps | awk '/CassandraDaemon/ {print $1}'` uww
please?
On Wed, Mar 26, 2014 at 5:20 PM, prem yadav wrote:
> Hi,
> in another thread, I has mentioned that we had issue with Cassandra
> getting killed by kernel due to OOM. Downgrading to jdk6_
ParNew GC (used by default in cassandra) uses 'stop-the-world' algorithm,
which means your application has to be stopped to do gc.
You can run jstat command to monitor gc activity and check if your write
performance is related to GC, eg:
$ jstat -gc 1s
But it shouldn't drop throughtput to 0 ops/s.
Hi,
you should set 'listen_address' to ip address of eth4.
'listen_address' is for communication between cassandra nodes (not clients).
Btw I hope you don't use NFS for commit log directory.
--
cheers
mc
On Wed, Mar 19, 2014 at 5:14 AM, Le Xu wrote:
> I'm currently using Cassandra 1.23 and
.
cheers,
/Marcin
me know if that is a bug or I do something wrong.
cheers,
/Marcin
Hi Hector,
thank you very much for your help, it does the trick.
cheers,
/Marcin
On 25/11/2010 17:27, Héctor Izquierdo Seliva wrote:
That happened to me too. Try with a ; at the end of the line.
El jue, 25-11-2010 a las 17:22 +, Marcin escribió:
Hi guys,
I am having weird problem
Hi guys,
I am having weird problem, cassandra is working but can't get
cassandra-cli to work.
When I run command - any command like even help and hit error I am not
getting any response any ideas?
P.S.
Running Cassandra 0.7.0 RC1
cheers,
/Marcin
>uuid($posts[0]->column->name);
$string = (string) $uuid;
$binary = $uuid->uuid;
cheers
On 20/03/2010 17:48, Jonathan Ellis wrote:
Cool, thanks!
Does it make it easy to use TimeUUID columns? Because that is the
biggest problem I see people having from PHP.
On Sat, Mar 20, 2010 at 7:32 A
Hi guys,
I would like to share with you link to the PHP client for Cassandra
build with flexibility and easy use in mind.
It implements some of the ORM concepts.
here you go:
http://code.google.com/p/simpletools-php/wiki/SimpleCassie
P.S.
Appreciate any feedback.
cheers,
/Marcin
Probably that was the reason of course ;-)
thanks for pointing it out.
cheers,
/Marcin
You have to wait for the flush to finish, of course.
On Fri, Mar 19, 2010 at 11:44 AM, Marcin wrote:
I have done that before plus compact and it didn't help? (I have been using
nodeprobe)
c
I have done that before plus compact and it didn't help? (I have been
using nodeprobe)
cheers,
/Marcin
Flush before you kill the process and restart will be much faster.
On Fri, Mar 19, 2010 at 9:40 AM, Marcin wrote:
Hi guys,
is there a way to avoid compacting, flushing and a
Hi guys,
is there a way to avoid compacting, flushing and all of this thing on
startup and perform it while node is running ?
It takes a lot of on startup.
cheers,
/Marcin
24 matches
Mail list logo