cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amitkumar Ghatwal (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13345) Increasing the per thread stack size to atleast 512k
Date Fri, 17 Mar 2017 14:35:41 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-13345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15930049#comment-15930049
] 

Amitkumar Ghatwal commented on CASSANDRA-13345:
-----------------------------------------------

[~snazy] -  yes i agree with your comments partially .What i was  trying to say is that if
Cassandra server fails to start with-  Per thread stack size " --Xss256k " on ppc64le-arch.
Can we please at least ensure that if arch != ppc64le , use the default value of 256K , whereas
if arch == ppc64le , value to be used is 512k. I guess if we keep a check to ensure that if
arch !=ppc64le , we will continue to use the existing value.



> Increasing the per thread stack size to atleast 512k 
> -----------------------------------------------------
>
>                 Key: CASSANDRA-13345
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13345
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Configuration
>         Environment: Set up details
> $ lscpu
> Architecture:          ppc64le
> Byte Order:            Little Endian
> CPU(s):                160
> On-line CPU(s) list:   0-159
> Thread(s) per core:    8
> Core(s) per socket:    5
> Socket(s):             4
> NUMA node(s):          4
> Model:                 2.1 (pvr 004b 0201)
> Model name:            POWER8E (raw), altivec supported
> CPU max MHz:           3690.0000
> CPU min MHz:           2061.0000
> L1d cache:             64K
> L1i cache:             32K
> L2 cache:              512K
> L3 cache:              8192K
> NUMA node0 CPU(s):     0-39
> NUMA node1 CPU(s):     40-79
> NUMA node16 CPU(s):    80-119
> NUMA node17 CPU(s):    120-159
> $ cat /etc/os-release
> NAME="Ubuntu"
> VERSION="16.04.1 LTS (Xenial Xerus)"
> ID=ubuntu
> ID_LIKE=debian
> PRETTY_NAME="Ubuntu 16.04.1 LTS"
> VERSION_ID="16.04"
> HOME_URL="http://www.ubuntu.com/"
> SUPPORT_URL="http://help.ubuntu.com/"
> BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
> VERSION_CODENAME=xenial
> UBUNTU_CODENAME=xenial
> $ arch
> ppc64le
> $ java -version
> openjdk version "1.8.0_121"
> OpenJDK Runtime Environment (build 1.8.0_121-8u121-b13-0ubuntu1.16.04.2-b13)
> OpenJDK 64-Bit Server VM (build 25.121-b13, mixed mode)
>            Reporter: Amitkumar Ghatwal
>            Priority: Minor
>
> Hi All,
> I followed the below steps 
> ```
> $ git clone https://github.com/apache/cassandra.git
> $ cd cassandra/
> $ ant
> $ bin/cassandra -f
> The stack size specified is too small, Specify at least 328k
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> ```
> After getting this , i had to upgrade the thread stack size to 512kb in 'conf/jvm.options'
> ```
> $ git diff conf/jvm.options
> diff --git a/conf/jvm.options b/conf/jvm.options
> index 49b2196..00c03ce 100644
> --- a/conf/jvm.options
> +++ b/conf/jvm.options
> @@ -99,7 +99,7 @@
>  -XX:+HeapDumpOnOutOfMemoryError
>  # Per-thread stack size.
> --Xss256k
> +-Xss512k
>  # Larger interned string table, for gossip's benefit (CASSANDRA-6410)
>  -XX:StringTableSize=1000003
> ```
> Thereafter i was able to start the Cassandra server successfully.
> Could you please consider increasing the stack size to '512k' in 'conf/jvm.options.
> Similar to  "https://issues.apache.org/jira/browse/CASSANDRA-13300". Let me know if we
can increase the stack size in the Apache Cassandra trunk.
> Thanks for support provided so far , and let me know
> Regards,
> Amit



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message