Re: Cassandra 2.2.1 stuck at 100% on Windows

[Alaa Zubaidi (PDF)]

Thanks guys,
I will look into this more, and put an update here, if I find anything

On Fri, Oct 16, 2015 at 10:40 AM, Josh McKenzie 
wrote:

> One option: use process explorer to find out the TID's of the java process
> (instructions
> ),
> screen cap that, then also run jstack against the running cassandra process
> out to a file a few times (instructions
> 
> ).
>
> We should be able to at least link up the TID to the hex thread # in the
> jstack output to figure out who/what is spinning on there.
>
> On Fri, Oct 16, 2015 at 1:28 PM, Michael Shuler 
> wrote:
>
>> On 10/16/2015 12:02 PM, Alaa Zubaidi (PDF) wrote:
>>
>>> No OOM in any of the log files, and NO long GC at that time.
>>> I attached the last 2 minutes before it hangs until we restart cassandra
>>> after hour an half.
>>>
>>
>> Your logs show gossip issues with some seed nodes. `nodetool gossipinfo`
>> on all nodes might be an interesting place to start.
>>
>> --
>> Michael
>>
>
>


-- 

Alaa Zubaidi
PDF Solutions, Inc.
333 West San Carlos Street, Suite 1000
San Jose, CA 95110  USA
Tel: 408-283-5639
fax: 408-938-6479
email: alaa.zuba...@pdf.com

-- 
*This message may contain confidential and privileged information. If it 
has been sent to you in error, please reply to advise the sender of the 
error and then immediately permanently delete it and all attachments to it 
from your systems. If you are not the intended recipient, do not read, 
copy, disclose or otherwise use this message or any attachments to it. The 
sender disclaims any liability for such unauthorized use. PLEASE NOTE that 
all incoming e-mails sent to PDF e-mail accounts will be archived and may 
be scanned by us and/or by external service providers to detect and prevent 
threats to our systems, investigate illegal or inappropriate behavior, 
and/or eliminate unsolicited promotional e-mails (“spam”). If you have any 
concerns about this process, please contact us at *
*legal.departm...@pdf.com* *.*

[RELEASE] Apache Cassandra 2.1.11 released

[Jake Luciani]

The Cassandra team is pleased to announce the release of Apache Cassandra
version 2.1.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 and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 2.1 series. As always, please
pay
attention to the release notes[2] and Let us know[3] if you were to
encounter
any problem.

Enjoy!

[1]: http://goo.gl/mJCyUf (CHANGES.txt)
[2]: http://goo.gl/ax1w4y (NEWS.txt)
[3]: https://issues.apache.org/jira/browse/CASSANDRA

Re: Cassandra 2.2.1 stuck at 100% on Windows

[Michael Shuler]

On 10/16/2015 12:02 PM, Alaa Zubaidi (PDF) wrote:

No OOM in any of the log files, and NO long GC at that time.
I attached the last 2 minutes before it hangs until we restart cassandra
after hour an half.


Your logs show gossip issues with some seed nodes. `nodetool gossipinfo` 
on all nodes might be an interesting place to start.


--
Michael

Re: Cassandra 2.2.1 stuck at 100% on Windows

[Josh McKenzie]

One option: use process explorer to find out the TID's of the java process (
instructions
),
screen cap that, then also run jstack against the running cassandra process
out to a file a few times (instructions
).

We should be able to at least link up the TID to the hex thread # in the
jstack output to figure out who/what is spinning on there.

On Fri, Oct 16, 2015 at 1:28 PM, Michael Shuler 
wrote:

> On 10/16/2015 12:02 PM, Alaa Zubaidi (PDF) wrote:
>
>> No OOM in any of the log files, and NO long GC at that time.
>> I attached the last 2 minutes before it hangs until we restart cassandra
>> after hour an half.
>>
>
> Your logs show gossip issues with some seed nodes. `nodetool gossipinfo`
> on all nodes might be an interesting place to start.
>
> --
> Michael
>

[RELEASE] Apache Cassandra 2.2.3 released

[Jake Luciani]

The Cassandra team is pleased to announce the release of Apache Cassandra
version 2.2.3.

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 and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 2.2 series. As always, please
pay
attention to the release notes[2] and Let us know[3] if you were to
encounter
any problem.

Enjoy!

[1]: http://goo.gl/zLlUcO (CHANGES.txt)
[2]: http://goo.gl/pC433O (NEWS.txt)
[3]: https://issues.apache.org/jira/browse/CASSANDRA

How to read data from local cassandra cluster

[Adamantios Corais]

Hi,

I have install Cassandra locally (DataStax Enterprise to be specific).
Everything seems to work ok. For example, I can upload a test file into CFS
or open a Spark REPL.

However, when it comes to my very own Spark application, I can't understand
how to modify sc.textFile("/user/testuser/words.txt") so that I can read
the file I just uploaded to my local DataStax installation.

How should I refer to the associated host?



*// Adamantios*

any update about CASSANDRA-10420

[Lu, Boying]

Hi, All,

Can anyone give some suggestions about the 
https://issues.apache.org/jira/browse/CASSANDRA-10420 ?

We are waiting for a solution of it.

Thanks

Boying

Re: any update about CASSANDRA-10420

[Carlos Rolo]

Can you provide more information?

The description is generic, driver version and a test case that the devs
can use to reproduce the bug would be optimal.

I'm not involved in the development of cassandra, but that bug description
doesn't seem complete. Maybe it is a driver bug and not a Cassandra bug?



Regards,

Carlos Juzarte Rolo
Cassandra Consultant

Pythian - Love your data

rolo@pythian | Twitter: @cjrolo | Linkedin: *linkedin.com/in/carlosjuzarterolo
*
Mobile: +351 91 891 81 00 | Tel: +1 613 565 8696 x1649
www.pythian.com

On Fri, Oct 16, 2015 at 10:16 AM, Lu, Boying  wrote:

> Hi, All,
>
>
>
> Can anyone give some suggestions about the
> https://issues.apache.org/jira/browse/CASSANDRA-10420 ?
>
>
>
> We are waiting for a solution of it.
>
>
>
> Thanks
>
>
>
> Boying
>

-- 


--

management and monitoring nodetool repair

[aeljami.ext]

Hi,
I'm looking for a tool for management and monitoring of the status of nodetool 
repair.

Currently I am trying to test cassandra-reaper, but if you tested other tools 
thank you to share.

Thanks

_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

Re: Re : Replication factor for system_auth keyspace

[Victor Chen]

To elaborate on what Robert said, I think with most things technology
related, the answer with these sorts of questions (i.e. "ideal settings")
is usually "it depends." Remember that technology is a tool that we use to
accomplish something we want. It's just a mechanism that we as humans use
to exert our wishes on other things. In this case, cassandra allows us to
exert our wishes on the data we need to have available. So think for a
second about what you want? To be less philosophical and more practical,
how many nodes you are comfortable losing or likely to lose? How many
copies of your system_auth keyspace do you want to have always available?

Also, what do you mean by "really long?" What version of cassandra are you
using? If you are on 2.1, look at migrating to incremental repair. That it
takes so long for such a small keyspace leads me to believe you're using
sequential repair ...

-V

On Thu, Oct 15, 2015 at 7:46 PM, Robert Coli  wrote:

> On Thu, Oct 15, 2015 at 10:24 AM, sai krishnam raju potturi <
> pskraj...@gmail.com> wrote:
>
>>   we are deploying a new cluster with 2 datacenters, 48 nodes in each DC.
>> For the system_auth keyspace, what should be the ideal replication_factor
>> set?
>>
>> We tried setting the replication factor equal to the number of nodes in a
>> datacenter, and the repair for the system_auth keyspace took really long.
>> Your suggestions would be of great help.
>>
>
> More than 1 and a lot less than 48.
>
> =Rob
>
>

Re: Re : Replication factor for system_auth keyspace

[sai krishnam raju potturi]

thanks guys for the advice. We were running parallel repairs earlier, with
cassandra version 2.0.14. As pointed out having set the replication factor
really huge for system_auth was causing the repair to take really long.

thanks
Sai

On Fri, Oct 16, 2015 at 9:56 AM, Victor Chen 
wrote:

> To elaborate on what Robert said, I think with most things technology
> related, the answer with these sorts of questions (i.e. "ideal settings")
> is usually "it depends." Remember that technology is a tool that we use to
> accomplish something we want. It's just a mechanism that we as humans use
> to exert our wishes on other things. In this case, cassandra allows us to
> exert our wishes on the data we need to have available. So think for a
> second about what you want? To be less philosophical and more practical,
> how many nodes you are comfortable losing or likely to lose? How many
> copies of your system_auth keyspace do you want to have always available?
>
> Also, what do you mean by "really long?" What version of cassandra are you
> using? If you are on 2.1, look at migrating to incremental repair. That it
> takes so long for such a small keyspace leads me to believe you're using
> sequential repair ...
>
> -V
>
> On Thu, Oct 15, 2015 at 7:46 PM, Robert Coli  wrote:
>
>> On Thu, Oct 15, 2015 at 10:24 AM, sai krishnam raju potturi <
>> pskraj...@gmail.com> wrote:
>>
>>>   we are deploying a new cluster with 2 datacenters, 48 nodes in each
>>> DC. For the system_auth keyspace, what should be the ideal
>>> replication_factor set?
>>>
>>> We tried setting the replication factor equal to the number of nodes in
>>> a datacenter, and the repair for the system_auth keyspace took really long.
>>> Your suggestions would be of great help.
>>>
>>
>> More than 1 and a lot less than 48.
>>
>> =Rob
>>
>>
>

Re: LOCAL_SERIAL

[Eric Stevens]

There's more to leader election than keeping a handful of keys up to date.
There's also more to distributed coordination than leader election alone.
Some of the hairiest problems surround failure conditions that are not easy
to test or plan for.

Sure, you could build it all yourself using Cassandra (local_serial or CAS
would be fine), but it's largely a solved problem, and better tested than a
home grown solution is likely to be.  Don't be afraid of hard problems, but
also don't fall prey to NIH syndrome.

On Thu, Oct 15, 2015 at 9:43 AM Jon Haddad  wrote:

> ZK seems a little overkill for just 1 feature though.  LOCAL_SERIAL is
> fine if all you want to do is keep a handful of keys up to date.
>
> There’s a massive cost in adding something new to your infrastructure, and
> imo, very little gain in this case.
>
> On Oct 15, 2015, at 8:29 AM, Eric Stevens  wrote:
>
> You probably could, but if I were you, I'd consider a tool built for that
> purpose, such as Zookeeper.  It'd open up access to a lot of other great
> cluster coordination features.
>
> On Thu, Oct 15, 2015 at 8:47 AM Jan Algermissen <
> algermissen1...@icloud.com> wrote:
>
>> Hi,
>>
>> suppose I have two data centers and want to coordinate a bunch of
>> services in each data center (for example to load data into a per-DC system
>> that is not DC-aware (Solr)).
>>
>> Does it make sense to use CAS functionality with explicit LOCAL_SERIAL to
>> 'elect' a leader per data center to do the work?
>>
>> So instead of saying 'for this query, LOCAL_SERIAL is enough for me' this
>> would be like saying 'I want XYZ to happen exactly once, per data center'.
>> - All services would try to do XYZ, but only one instance *per datacenter*
>> will actually become the leader and succeed.
>>
>> Makes sense?
>>
>> Jan
>>
>
>

Re: Cassandra 2.2.1 stuck at 100% on Windows

[Alaa Zubaidi (PDF)]

Thanks Rob,

No OOM in any of the log files, and NO long GC at that time.
I attached the last 2 minutes before it hangs until we restart cassandra
after hour an half.
Regards,
Alaa

On Thu, Oct 15, 2015 at 6:29 PM, Robert Coli  wrote:

> On Thu, Oct 15, 2015 at 6:04 PM, Alaa Zubaidi (PDF) 
> wrote:
>
>> We are running Cassandra 2.2.1 on Windows 2008R2, and we see that
>> multiple Nodes are stuck at 99% CPU bringing the whole VM to a halt.
>> We suspect that there is another process that IT/Windows is causing the
>> CPU issue, but the problem is Cassandra does NOT recover, the CPU
>> utilization start climbing until the VM is not usable. If we restart
>> Cassandra, things go back to normal.
>>
>
> Most cases where a JVM does not recover and churns at maxed CPU are the
> result of GC failure and/or OOM.
>
> Check your logs for OOM and long GCs.
>
> Also FWIW you are among a relatively small group of Windows operators.
> Other than with the people working at datastax to support Windows, there is
> not a whole lot of well understood operational best practice for Cassandra
> on Windows.
>
> =Rob
>
>


-- 

Alaa Zubaidi
PDF Solutions, Inc.
333 West San Carlos Street, Suite 1000
San Jose, CA 95110  USA
Tel: 408-283-5639
fax: 408-938-6479
email: alaa.zuba...@pdf.com

-- 
*This message may contain confidential and privileged information. If it 
has been sent to you in error, please reply to advise the sender of the 
error and then immediately permanently delete it and all attachments to it 
from your systems. If you are not the intended recipient, do not read, 
copy, disclose or otherwise use this message or any attachments to it. The 
sender disclaims any liability for such unauthorized use. PLEASE NOTE that 
all incoming e-mails sent to PDF e-mail accounts will be archived and may 
be scanned by us and/or by external service providers to detect and prevent 
threats to our systems, investigate illegal or inappropriate behavior, 
and/or eliminate unsolicited promotional e-mails (“spam”). If you have any 
concerns about this process, please contact us at *
*legal.departm...@pdf.com* *.*


07.log
Description: Binary data