OpenJDK is not recommended? Why

2014-01-28 Thread Kumar Ranjan
I am in process of setting 2 node cluster with C* version 2.0.4. When I
started each node, it failed to communicate thus, each are running separate
and not in same ring. So started looking at the log files are saw the
message below:

WARN [main] 2014-01-28 06:02:17,861 CassandraDaemon.java (line 155) OpenJDK
is not recommended. Please upgrade to the newest Oracle Java release

Is this message informational only or can it be real issue? Is this why,
two nodes are not in a ring?

-- Kumar


Re: OpenJDK is not recommended? Why

2014-01-28 Thread Colin
Open jdk has known issues and they will raise their ugly little head from time 
to time-i have experienced them myself.

To be safe, I would use the latest oracle 7 release.

You may also be experiencing a configuration issue, make sure one node is 
specified as the seed node and that the other node knows that address as well.  
There's a good guide to configuration on the datastax website.

--
Colin 
+1 320 221 9531

 

> On Jan 28, 2014, at 9:55 PM, Kumar Ranjan  wrote:
> 
> I am in process of setting 2 node cluster with C* version 2.0.4. When I 
> started each node, it failed to communicate thus, each are running separate 
> and not in same ring. So started looking at the log files are saw the message 
> below:
> 
> WARN [main] 2014-01-28 06:02:17,861 CassandraDaemon.java (line 155) OpenJDK 
> is not recommended. Please upgrade to the newest Oracle Java release
> 
> Is this message informational only or can it be real issue? Is this why, two 
> nodes are not in a ring?
> 
> -- Kumar 


Re: OpenJDK is not recommended? Why

2014-01-28 Thread Michael Shuler

On 01/28/2014 09:55 PM, Kumar Ranjan wrote:

I am in process of setting 2 node cluster with C* version 2.0.4. When I
started each node, it failed to communicate thus, each are running
separate and not in same ring. So started looking at the log files are
saw the message below:


This is probably just a configuration issue and not likely to be the 
fault of OpenJDK.  OpenJDK is ok for testing the waters and light dev 
work; it is the reference architecture for Oracle Java SE 7.



WARN [main] 2014-01-28 06:02:17,861 CassandraDaemon.java (line 155)
OpenJDK is not recommended. Please upgrade to the newest Oracle Java release

Is this message informational only or can it be real issue?


Source of the above warning has some comments (attached, so they don't 
wrap so badly, I hope).


https://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=blob;f=src/java/org/apache/cassandra/service/CassandraDaemon.java;h=424dbfa58ec72ea812362e2b428d0c4534626307;hb=HEAD#l106

--
Kind regards,
Michael

dc0bc878 (Jonathan Ellis  2013-03-07 18:08:59 + 106) // log 
warnings for different kinds of sub-optimal JVMs.  tldr use 64-bit Oracle >= 
1.6u32
dc0bc878 (Jonathan Ellis  2013-03-07 18:08:59 + 107) if 
(!System.getProperty("os.arch").contains("64"))
dc0bc878 (Jonathan Ellis  2013-03-07 18:08:59 + 108) 
logger.info("32bit JVM detected.  It is recommended to run Cassandra on a 64bit 
JVM for better performance.");
d1e91a77 (Jonathan Ellis  2013-03-07 17:59:35 + 109) String 
javaVersion = System.getProperty("java.version");
d1e91a77 (Jonathan Ellis  2013-03-07 17:59:35 + 110) String 
javaVmName = System.getProperty("java.vm.name");
d1e91a77 (Jonathan Ellis  2013-03-07 17:59:35 + 111) 
logger.info("JVM vendor/version: {}/{}", javaVmName, javaVersion);
d1e91a77 (Jonathan Ellis  2013-03-07 17:59:35 + 112) if 
(javaVmName.contains("OpenJDK"))
d1e91a77 (Jonathan Ellis  2013-03-07 17:59:35 + 113) {
d1e91a77 (Jonathan Ellis  2013-03-07 17:59:35 + 114) // 
There is essentially no QA done on OpenJDK builds, and
d1e91a77 (Jonathan Ellis  2013-03-07 17:59:35 + 115) // 
clusters running OpenJDK have seen many heap and load issues.
d1e91a77 (Jonathan Ellis  2013-03-07 17:59:35 + 116) 
logger.warn("OpenJDK is not recommended. Please upgrade to the newest Oracle 
Java release");
d1e91a77 (Jonathan Ellis  2013-03-07 17:59:35 + 117) }
d1e91a77 (Jonathan Ellis  2013-03-07 17:59:35 + 118) else if 
(!javaVmName.contains("HotSpot"))
d1e91a77 (Jonathan Ellis  2013-03-07 17:59:35 + 119) {
d1e91a77 (Jonathan Ellis  2013-03-07 17:59:35 + 120) 
logger.warn("Non-Oracle JVM detected.  Some features, such as immediate unmap 
of compacted SSTables, may not work as intended");
d1e91a77 (Jonathan Ellis  2013-03-07 17:59:35 + 121) }


Re: OpenJDK is not recommended? Why

2014-01-28 Thread Kumar Ranjan
Yes got rid of openJDK and installed oracle version and warning went away.
Happy happy...Thank you folks..


On Tue, Jan 28, 2014 at 11:59 PM, Michael Shuler wrote:

> On 01/28/2014 09:55 PM, Kumar Ranjan wrote:
>
>> I am in process of setting 2 node cluster with C* version 2.0.4. When I
>> started each node, it failed to communicate thus, each are running
>> separate and not in same ring. So started looking at the log files are
>> saw the message below:
>>
>
> This is probably just a configuration issue and not likely to be the fault
> of OpenJDK.  OpenJDK is ok for testing the waters and light dev work; it is
> the reference architecture for Oracle Java SE 7.
>
>
>  WARN [main] 2014-01-28 06:02:17,861 CassandraDaemon.java (line 155)
>> OpenJDK is not recommended. Please upgrade to the newest Oracle Java
>> release
>>
>> Is this message informational only or can it be real issue?
>>
>
> Source of the above warning has some comments (attached, so they don't
> wrap so badly, I hope).
>
> https://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=
> blob;f=src/java/org/apache/cassandra/service/CassandraDaemon.java;h=
> 424dbfa58ec72ea812362e2b428d0c4534626307;hb=HEAD#l106
>
> --
> Kind regards,
> Michael
>
>