Re: Reg :- Multiple Node Cluster set up in Virtual Box

[@Nandan@]

Hi Users,
I successfully configured 2 Nodes Cluster , but when I configured 3rd Node
and try to join them , then 3rd node is not able to join Cluster and I am
getting below message. Please correct me in case of I am wrong at some
place.

> WARN  [GossipStage:1] 2017-11-07 17:01:42,706 TokenMetadata.java:215 -
> Token -2625048720051242117 changing ownership from /172.16.51.160 to /
> 172.16.51.185
> WARN  [GossipStage:1] 2017-11-07 17:01:42,707 TokenMetadata.java:215 -
> Token 2046352110807728035 changing ownership from /172.16.51.160 to /
> 172.16.51.185
> WARN  [GossipStage:1] 2017-11-07 17:01:42,708 TokenMetadata.java:215 -
> Token 6738112847220178646 changing ownership from /172.16.51.160 to /
> 172.16.51.185
> WARN  [GossipStage:1] 2017-11-07 17:01:42,710 TokenMetadata.java:215 -
> Token 5278402616817535783 changing ownership from /172.16.51.160 to /
> 172.16.51.185
> WARN  [GossipStage:1] 2017-11-07 17:01:42,710 TokenMetadata.java:215 -
> Token -4301762166942209316 changing ownership from /172.16.51.160 to /
> 172.16.51.185
> WARN  [GossipStage:1] 2017-11-07 17:01:42,711 TokenMetadata.java:215 -
> Token -5795150382485882189 changing ownership from /172.16.51.160 to /
> 172.16.51.185
> WARN  [GossipStage:1] 2017-11-07 17:01:42,711 TokenMetadata.java:215 -
> Token -7650474240486110510 changing ownership from /172.16.51.160 to /
> 172.16.51.185
> WARN  [GossipStage:1] 2017-11-07 17:01:42,712 TokenMetadata.java:215 -
> Token -7529017452803179703 changing ownership from /172.16.51.160 to /
> 172.16.51.185
> WARN  [GossipStage:1] 2017-11-07 17:01:42,713 TokenMetadata.java:215 -
> Token -6321052415922186365 changing ownership from /172.16.51.160 to /
> 172.16.51.185
> WARN  [GossipStage:1] 2017-11-07 17:01:42,713 TokenMetadata.java:215 -
> Token 505028918401730880 changing ownership from /172.16.51.160 to /
> 172.16.51.185
> WARN  [GossipStage:1] 2017-11-07 17:01:42,714 TokenMetadata.java:215 -
> Token -6468981120406928540 changing ownership from /172.16.51.160 to /
> 172.16.51.185
> WARN  [GossipStage:1] 2017-11-07 17:01:42,714 TokenMetadata.java:215 -
> Token -7886589494812723279 changing ownership from /172.16.51.160 to /
> 172.16.51.185
> WARN  [GossipStage:1] 2017-11-07 17:01:42,715 TokenMetadata.java:215 -
> Token 6159957549175666279 changing ownership from /172.16.51.160 to /
> 172.16.51.185
> WARN  [GossipStage:1] 2017-11-07 17:01:42,715 TokenMetadata.java:215 -
> Token 1371713730179023942 changing ownership from /172.16.51.160 to /
> 172.16.51.185
> WARN  [GossipStage:1] 2017-11-07 17:01:42,716 TokenMetadata.java:215 -
> Token 3849374212689985831 changing ownership from /172.16.51.160 to /
> 172.16.51.185
> WARN  [GossipStage:1] 2017-11-07 17:01:42,717 TokenMetadata.java:215 -
> Token -9130845474615238557 changing ownership from /172.16.51.160 to /
> 172.16.51.185
> WARN  [GossipStage:1] 2017-11-07 17:01:42,717 TokenMetadata.java:215 -
> Token -2166821314373815731 changing ownership from /172.16.51.160 to /
> 172.16.51.185
> WARN  [GossipStage:1] 2017-11-07 17:01:42,718 TokenMetadata.java:215 -
> Token 8172072992908340093 changing ownership from /172.16.51.160 to /
> 172.16.51.185
> WARN  [GossipStage:1] 2017-11-07 17:01:42,719 TokenMetadata.java:215 -
> Token 5862934089465703397 changing ownership from /172.16.51.160 to /
> 172.16.51.185
> WARN  [GossipStage:1] 2017-11-07 17:01:42,719 TokenMetadata.java:215 -
> Token 8683259820133858856 changing ownership from /172.16.51.160 to /
> 172.16.51.185
> WARN  [GossipStage:1] 2017-11-07 17:01:42,720 TokenMetadata.java:215 -
> Token -6722468819050104438 changing ownership from /172.16.51.160 to /
> 172.16.51.185
> WARN  [GossipStage:1] 2017-11-07 17:01:42,720 TokenMetadata.java:215 -
> Token 390606262920645821 changing ownership from /172.16.51.160 to /
> 172.16.51.185
> WARN  [GossipStage:1] 2017-11-07 17:01:42,721 TokenMetadata.java:215 -
> Token -2191770340916232589 changing ownership from /172.16.51.160 to /
> 172.16.51.185
> WARN  [GossipStage:1] 2017-11-07 17:01:42,721 TokenMetadata.java:215 -
> Token -2315498798364455538 changing ownership from /172.16.51.160 to /
> 172.16.51.185
> WARN  [GossipStage:1] 2017-11-07 17:01:42,722 TokenMetadata.java:215 -
> Token -4289328221922359195 changing ownership from /172.16.51.160 to /
> 172.16.51.185
> WARN  [GossipStage:1] 2017-11-07 17:01:42,722 TokenMetadata.java:215 -
> Token -3989195857321645521 changing ownership from /172.16.51.160 to /
> 172.16.51.185
> WARN  [GossipStage:1] 2017-11-07 17:01:42,723 TokenMetadata.java:215 -
> Token -6852043742105779264 changing ownership from /172.16.51.160 to /
> 172.16.51.185


Thanks and Best Regards,
Nandan


On Tue, Nov 7, 2017 at 12:48 PM, @Nandan@ 
wrote:

> Hi All,
>
> Thanks for sharing all information.
> I am starting to work on this.
> Now Problem which I am getting right now is:-
> 1) How to select Network for Virtual Machine by which I can able to get
> different IP for different Virtual Box?
> 2) As I am using WIFI for HOST 

RE: Reg :- Multiple Node Cluster set up in Virtual Box

[Kyrylo Lebediev]

Nandan,

There are several options available how this can be done.

For example, you may configure 2 network adapters per each VM:
1) NAT: in order the VM to have access to the Internet
2) Host-only Adapter - for internode communication setup (listen_address, 
rpc_address). Static IP configuration should be used for these interfaces.

Regards,
Kyrill

From: @Nandan@ [mailto:nandanpriyadarshi...@gmail.com]
Sent: Tuesday, November 7, 2017 6:49 AM
To: user 
Subject: Re: Reg :- Multiple Node Cluster set up in Virtual Box

Hi All,

Thanks for sharing all information.
I am starting to work on this.
Now Problem which I am getting right now is:-
1) How to select Network for Virtual Machine by which I can able to get 
different IP for different Virtual Box?
2) As I am using WIFI for HOST machine which is Windows 10, so is there any 
internal configuration required or I need to select specific Network Adapter 
into Virtual Boxs by which  I will get IP1,IP2,IP3 for node1,node2,node3 
respectively.

Please give me some ideas.
Thanks in advance,
Nandan Priyadarshi


On Tue, Nov 7, 2017 at 8:28 AM, James Briggs 
> wrote:
Nandan: The original Datastax training classes (when it was still called 
Riptano)
used 3 virtualbox Debian instances to setup a Cassandra cluster.

Thanks, James Briggs.
--
Cassandra/MySQL DBA. Available in San Jose area or remote.
cass_top: https://github.com/jamesbriggs/cassandra-top


From: kurt greaves >
To: User >
Sent: Monday, November 6, 2017 3:08 PM
Subject: Re: Reg :- Multiple Node Cluster set up in Virtual Box

Worth keeping in mind that in 3.6 onwards nodes will not start unless they can 
contact a seed. Not quite SPOF but still problematic. 
CASSANDRA-13851​

Fwd: Stable Cassandra 3.x version for production

[shini gupta]

Hi

Which version of Cassandra 3.x is stable and production-ready?

Regards

Re: Stable Cassandra 3.x version for production

[Carlos Rolo]

DSE is already pushing 3.11 in 5.1

If you're going into 3.x either 3.11.1 or 3.0.15. I would recommend 3.11.1
to take advantage of a couple of features (ex: Slow query log) that you
don't have on 3.0.

If you're stable on 2.x and you don't need any new feature, you can leave
it there safely (although the latest releases are probably the last ones
you will see).

Regards,

Carlos Juzarte Rolo
Cassandra Consultant / Datastax Certified Architect / Cassandra MVP

Pythian - Love your data

rolo@pythian | Twitter: @cjrolo | Skype: cjr2k3 | Linkedin:
*linkedin.com/in/carlosjuzarterolo
*
Mobile: +351 918 918 100
www.pythian.com

On Tue, Nov 7, 2017 at 1:35 PM, Herbert Fischer <
herbert.fisc...@crossengage.io> wrote:

> I know that people usually prefers to use the 3.0.x branch because that's
> the one that is underneath DSE.
>
> I've never heard of anyone using Cassandra > 3.0.x on production.
>
>
>
> On Tue, Nov 7, 2017 at 11:29 AM, shini gupta 
> wrote:
>
>>
>>
>> Hi
>>
>> Which version of Cassandra 3.x is stable and production-ready?
>>
>> Regards
>>
>
>
>
> --
> Herbert Fischer | Senior IT Architect
> CrossEngage GmbH | Bertha-Benz Straße 5 | 10557 Berlin
> 
>
> E-Mail: herbert.fisc...@crossengage.io
> Web: www.crossengage.io
>
> Amtsgericht Berlin-Charlottenburg | HRB 169537 B
> Geschäftsführer: Dr. Markus Wübben, Manuel Hinz | USt-IdNr.: DE301504202
>

-- 


--

Re: Stable Cassandra 3.x version for production

[Herbert Fischer]

I know that people usually prefers to use the 3.0.x branch because that's
the one that is underneath DSE.

I've never heard of anyone using Cassandra > 3.0.x on production.



On Tue, Nov 7, 2017 at 11:29 AM, shini gupta  wrote:

>
>
> Hi
>
> Which version of Cassandra 3.x is stable and production-ready?
>
> Regards
>



-- 
Herbert Fischer | Senior IT Architect
CrossEngage GmbH | Bertha-Benz Straße 5 | 10557 Berlin

E-Mail: herbert.fisc...@crossengage.io
Web: www.crossengage.io

Amtsgericht Berlin-Charlottenburg | HRB 169537 B
Geschäftsführer: Dr. Markus Wübben, Manuel Hinz | USt-IdNr.: DE301504202

RE: Stable Cassandra 3.x version for production

[Harika Vangapelli -T (hvangape - AKRAYA INC at Cisco)]

We are using version 3.7 in prod.

[http://wwwin.cisco.com/c/dam/cec/organizations/gmcc/services-tools/signaturetool/images/logo/logo_gradient.png]



Harika Vangapelli
Engineer - IT
hvang...@cisco.com
Tel:

Cisco Systems, Inc.



United States
cisco.com


[http://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif]Think before you 
print.

This email may contain confidential and privileged material for the sole use of 
the intended recipient. Any review, use, distribution or disclosure by others 
is strictly prohibited. If you are not the intended recipient (or authorized to 
receive for the recipient), please contact the sender by reply email and delete 
all copies of this message.
Please click 
here for 
Company Registration Information.


From: shini gupta [mailto:gupta.sh...@gmail.com]
Sent: Tuesday, November 7, 2017 2:30 AM
To: user@cassandra.apache.org
Subject: Fwd: Stable Cassandra 3.x version for production



Hi

Which version of Cassandra 3.x is stable and production-ready?

Regards

Re: Stable Cassandra 3.x version for production

[Jeff Jirsa]

3.0.15 is likely fine for production, but like any database, you should
test it with your data in a test environment prior to deploying to prod.

I haven't personally used 3.11.1, though the important parts are likely
very similar to 3.0.15.




On Tue, Nov 7, 2017 at 5:35 AM, Herbert Fischer <
herbert.fisc...@crossengage.io> wrote:

> I know that people usually prefers to use the 3.0.x branch because that's
> the one that is underneath DSE.
>
> I've never heard of anyone using Cassandra > 3.0.x on production.
>
>
>
> On Tue, Nov 7, 2017 at 11:29 AM, shini gupta 
> wrote:
>
>>
>>
>> Hi
>>
>> Which version of Cassandra 3.x is stable and production-ready?
>>
>> Regards
>>
>
>
>
> --
> Herbert Fischer | Senior IT Architect
> CrossEngage GmbH | Bertha-Benz Straße 5 | 10557 Berlin
> 
>
> E-Mail: herbert.fisc...@crossengage.io
> Web: www.crossengage.io
>
> Amtsgericht Berlin-Charlottenburg | HRB 169537 B
> Geschäftsführer: Dr. Markus Wübben, Manuel Hinz | USt-IdNr.: DE301504202
>

RE: Stable Cassandra 3.x version for production

[Steinmaurer, Thomas]

Latest DSE is based on 3.11 (possibly due to CASSANDRA-12269, but just a guess).

For us (only), none of 3.0+/3.11+ qualifies for production to be honest, when 
you are familiar with having 2.1 in production.


· 3.0 needs more hardware resources to handle the same load => 
https://issues.apache.org/jira/browse/CASSANDRA-12269. Improved (close/back to 
2.1 level) in 3.11

· With 3.11.0 we are seeing the following memory leak (at least here, 
but possibly nobody else out there, cause the ticket gets close to zero 
attention *g*): https://issues.apache.org/jira/browse/CASSANDRA-13929

· From an operational perspective, the repair area got much more 
troublesome compared to 2.1 when introducing incremental repairs being the 
default in 2.2+

We stay on 2.1 for now.

Just my opinion.

Thomas

From: Herbert Fischer [mailto:herbert.fisc...@crossengage.io]
Sent: Dienstag, 07. November 2017 14:35
To: user@cassandra.apache.org
Subject: Re: Stable Cassandra 3.x version for production

I know that people usually prefers to use the 3.0.x branch because that's the 
one that is underneath DSE.

I've never heard of anyone using Cassandra > 3.0.x on production.



On Tue, Nov 7, 2017 at 11:29 AM, shini gupta 
> wrote:


Hi

Which version of Cassandra 3.x is stable and production-ready?

Regards



--
Herbert Fischer | Senior IT Architect
CrossEngage GmbH | Bertha-Benz Straße 5 | 10557 Berlin

E-Mail: herbert.fisc...@crossengage.io
Web: www.crossengage.io

Amtsgericht Berlin-Charlottenburg | HRB 169537 B
Geschäftsführer: Dr. Markus Wübben, Manuel Hinz | USt-IdNr.: DE301504202
The contents of this e-mail are intended for the named addressee only. It 
contains information that may be confidential. Unless you are the named 
addressee or an authorized designee, you may not copy or use it, or disclose it 
to anyone else. If you received it in error please notify us immediately and 
then destroy it. Dynatrace Austria GmbH (registration number FN 91482h) is a 
company registered in Linz whose registered office is at 4040 Linz, Austria, 
Freistädterstraße 313

Re: 3.0.6 - CorruptSSTableException

[Riccardo Ferrari]

Thanks you Adama,

Even though it refers to an older C* version it is still a good starting
point, thanks!

I ended up restoring the table from a previous snapshot. The server booted
up ok and joined the ring. Hopefully the repair process will take care of
synching back the node.

Best,

On Tue, Nov 7, 2017 at 6:54 PM,  wrote:

> Hi Riccardo,
>
>
>
> The following may help me, as the case described there is similar to yours
> !
>
> https://engineering.gosquared.com/dealing-corrupt-sstable-cassandra
>
>
>
> Regards.
>
>
>
> *De :* Riccardo Ferrari [mailto:ferra...@gmail.com]
> *Envoyé :* lundi 6 novembre 2017 16:16
> *À :* user@cassandra.apache.org
> *Objet :* 3.0.6 - CorruptSSTableException
>
>
>
> Hi list,
>
>
>
> It happened that one of our EC2 instance of our cluster got rebooted.
> Unfortunately when back Cassandra 3.0.6 failed to restart complaining about:
>
>
>
> ERROR [NonPeriodicTasks:1] 2017-11-04 03:44:20,019 LogTransaction.java:204
> - Unable to delete //system/local/ma-292-big-Data.db as it
> does not exist
>
> ERROR [CompactionExecutor:1] 2017-11-04 03:44:20,136
> CassandraDaemon.java:195 - Exception in thread
> Thread[CompactionExecutor:1,1,main]
>
> org.apache.cassandra.io.sstable.CorruptSSTableException: Corrupted:
> //system/local/ma-294-big-Data.db
>
>  at org.apache.cassandra.io.sstable.format.big.BigTableScanner$
> KeyScanningIterator.computeNext(BigTableScanner.java:351)
> ~[apache-cassandra-3.0.6.jar:3.0.6]
>
>
>
> I tried to run an sstablescrub system local with no luck as it seems to
> get stuck in an endless loop:
>
>
>
> Scrubbing BigTableReader(path='//system/local/ma-293-big-Data.db')
> (5862 bytes)
>
> WARNING: Error reading row (stacktrace follows):
>
> Retrying from row index; data is 5855 bytes starting at 7
>
> WARNING: Retry failed too. Skipping to next row (retry's stacktrace
> follows)
>
> WARNING: Error reading row (stacktrace follows):
>
> WARNING: Row starting at position 0 is unreadable; skipping to next
>
> WARNING: Data file row position 7 differs from index file row position -1
>
> WARNING: Error reading row (stacktrace follows):
>
>
>
> I do have a snapshot taken 3 hours before the crash.
>
> Is it safe to restore that snapshot and run a repair?
>
> Is there anything else I can try to recover ?
>
>
>
> Any help much appreciated,
>
> regards
>
> _
>
> 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: Stable Cassandra 3.x version for production

[Jon Haddad]

I regularly work with teams that have 3.11.{0.1} in prod, and would recommend 
it for new clusters.  

Avoid materialized views and SASI until you really understand how they work and 
their limitations.  MVs solve about one use case correctly, SASI is good if 
you’re querying a single partition *but* it’s missing a pretty important 
optimization of addressing rows directly, so if you’ve got huge partitions you 
pay a massive price for using them.  Check out 
https://issues.apache.org/jira/browse/CASSANDRA-11990 
 for details.

> On Nov 7, 2017, at 9:23 AM, Harika Vangapelli -T (hvangape - AKRAYA INC at 
> Cisco)  wrote:
> 
> We are using version 3.7 in prod.
>  
> 
>  
> Harika Vangapelli
> Engineer - IT
> hvang...@cisco.com 
> Tel:
> Cisco Systems, Inc.
> 
> 
> 
> United States
> cisco.com  
> Think before you print.
> This email may contain confidential and privileged material for the sole use 
> of the intended recipient. Any review, use, distribution or disclosure by 
> others is strictly prohibited. If you are not the intended recipient (or 
> authorized to receive for the recipient), please contact the sender by reply 
> email and delete all copies of this message.
> Please click here 
>  for 
> Company Registration Information.
>  
> From: shini gupta [mailto:gupta.sh...@gmail.com] 
> Sent: Tuesday, November 7, 2017 2:30 AM
> To: user@cassandra.apache.org
> Subject: Fwd: Stable Cassandra 3.x version for production
>  
>  
>  
> Hi
>  
> Which version of Cassandra 3.x is stable and production-ready?
> 
> Regards

RE: 3.0.6 - CorruptSSTableException

[adama.diabate]

Hi Riccardo,

The following may help me, as the case described there is similar to yours !
https://engineering.gosquared.com/dealing-corrupt-sstable-cassandra

Regards.

De : Riccardo Ferrari [mailto:ferra...@gmail.com]
Envoyé : lundi 6 novembre 2017 16:16
À : user@cassandra.apache.org
Objet : 3.0.6 - CorruptSSTableException

Hi list,

It happened that one of our EC2 instance of our cluster got rebooted. 
Unfortunately when back Cassandra 3.0.6 failed to restart complaining about:

ERROR [NonPeriodicTasks:1] 2017-11-04 03:44:20,019 LogTransaction.java:204 - 
Unable to delete //system/local/ma-292-big-Data.db as it does not 
exist
ERROR [CompactionExecutor:1] 2017-11-04 03:44:20,136 CassandraDaemon.java:195 - 
Exception in thread Thread[CompactionExecutor:1,1,main]
org.apache.cassandra.io.sstable.CorruptSSTableException: Corrupted: 
//system/local/ma-294-big-Data.db
 at 
org.apache.cassandra.io.sstable.format.big.BigTableScanner$KeyScanningIterator.computeNext(BigTableScanner.java:351)
 ~[apache-cassandra-3.0.6.jar:3.0.6]

I tried to run an sstablescrub system local with no luck as it seems to get 
stuck in an endless loop:

Scrubbing BigTableReader(path='//system/local/ma-293-big-Data.db') 
(5862 bytes)
WARNING: Error reading row (stacktrace follows):
Retrying from row index; data is 5855 bytes starting at 7
WARNING: Retry failed too. Skipping to next row (retry's stacktrace follows)
WARNING: Error reading row (stacktrace follows):
WARNING: Row starting at position 0 is unreadable; skipping to next
WARNING: Data file row position 7 differs from index file row position -1
WARNING: Error reading row (stacktrace follows):

I do have a snapshot taken 3 hours before the crash.
Is it safe to restore that snapshot and run a repair?
Is there anything else I can try to recover ?

Any help much appreciated,
regards

_

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: system_auth permissions issue C* 2.0.14

[Chandan Goel]

Hi Avinash,

Please see if you have given permissions to the user (logged in) on the table 
and all related Materialized Views.

Thanks
Chandan

From: pabbireddy avinash [mailto:pabbireddyavin...@gmail.com]
Sent: Friday, November 03, 2017 3:06 PM
To: user@cassandra.apache.org
Subject: system_auth permissions issue C* 2.0.14

Hi,
We are seeing system_auth related exceptions from application side on cassandra 
2.0.14 .


at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267) 
[jersey-common-2.14.jar:na]
at org.glassfish.jersey.internal.Errors.process(Errors.java:315) 
[jersey-common-2.14.jar:na]
at org.glassfish.jersey.internal.Errors.process(Errors.java:297) 
[jersey-common-2.14.jar:na]
... 33 lines omitted ...
Caused by: com.datastax.driver.core.exceptions.UnauthorizedException: User has 
no MODIFY permission on  so that all nodes will have system_auth data .


Please help me understand this issue .

Regards,
Avinash.

RE: Cassandra using a ton of native memory

[Austin Sharp]

Follow-up for anyone interested: disabling the Windows page file (which Windows 
makes kind of a pain) appears to resolve all issues. Cassandra is still using 
lots of memory but it gives it up as appropriate.

From: DuyHai Doan [mailto:doanduy...@gmail.com]
Sent: Friday, November 3, 2017 11:25
To: user 
Subject: Re: Cassandra using a ton of native memory

8Gb of RAM being a recommended production setting for most of the workload out 
there. Having only 16Gb of RAM, and because Cassandra is relying a lot on 
system page cache, there should be no surprise that your 16Gb being eaten up.

On Fri, Nov 3, 2017 at 5:40 PM, Austin Sharp 
> wrote:
I’ve investigated further. It appears that the performance issues are because 
Cassandra’s memory-mapped files (*.db files) fill up the physical memory and 
start being swapped to disk. Is this related to recommendations to disable 
swapping on a machine where Cassandra is installed? Should I disable 
memory-mapped IO?

I can see issues in JIRA related to Windows memory-mapped I/O but they all 
appear to be fixed prior to 3.11.

From: Austin Sharp [mailto:austin.sh...@seeq.com]
Sent: Thursday, November 2, 2017 17:51
To: user@cassandra.apache.org
Subject: Cassandra using a ton of native memory


Hi,



I have a problem with Cassandra 3.11.0 on Windows. I'm testing a workload w= 
ith a lot of read-then-writes that had no significant problems on Cassandra=  
2.x. However, now when this workload continues for a while (perhaps an hou= r), 
Cassandra or its JVM effectively use up all of the machine's 16GB of me= mory. 
Cassandra is started with -Xmx2147M, and JMX shows <2GB heap memory a= nd 
<100MB of off-heap memory. However, when I use something like Process Ex= 
plorer, I see that Cassandra has 10 to 11GB of memory in its working set, a= nd 
Windows shows essentially no free memory at all. Once the system has no = free 
memory, other processes suffer long sequences of unresponsiveness.



I can't see anything terribly wrong from JMX metrics or log files - they ne= 
ver show more than 1GB of non-heap memory. Where should I look to investiga= te 
this further?



Thanks,

Austin