incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Edward Capriolo <edlinuxg...@gmail.com>
Subject Re: Which Java on Fedora? Sun's or GNU's?
Date Wed, 29 Dec 2010 17:27:41 GMT
On Wed, Dec 29, 2010 at 11:29 AM, Eric Evans <eevans@rackspace.com> wrote:
> On Wed, 2010-12-29 at 10:56 -0500, Edward Capriolo wrote:
>> Cassandra pushes your JVM hard. Do not count on your distro which
>> might provide versions of things that are 3 months to 2 years old.
>
> Come on.  If it worked fine 3 months ago, then chances are it will
> continue to.  This is one of the reasons that people choose
> (environmentally )stable distro releases (which are often supported for
> much longer than 2 years).
>
>> Chosing what your distro gives your prepare to be disappointed and
>> have to upgrade as soon as you get some respectable load.  If you are
>> using sun/oracle (That still feels strange to say JVM oracle) you want
>> something much higher then just 1.6.0. Go for the latest and greatest
>> 1.6.21 or higher JRE/JDK 1.6.23.
>
> FWIW, the wiki says: "For Sun's jvm, this means at least u19; u21 is
> better."
>
>> I install the JDK (not the JRE) because its a super set and hey I just
>> might feel like compiling something.
>>
>> Other not so great options... rpm -Uvh --force --skip-deps (If you
>> know you have a Java that your RPM manager does not know about)
>
> No.  If this is really the situation, then it's disingenuous to offer
> the package at all, and it should be dropped.   I don't think these
> command line arguments should ever appear on a public mailing list.
>
>> Get source RPM strip out the Java dependency (If you know you have a
>> Java that your RPM manager does not know about)
>> Create a source RPM with nothing in it that "PROVIDES JAVA" (If you
>> know you have a Java that your RPM manager does not know about)
>
> --
> Eric Evans
> eevans@rackspace.com
>
>
If it worked fine three months ago and you came into Cassandra IRC
with a random JVM problem the first thing someone would tell you to do
is probably update to the latest JVM :)

Some distro's go for perceived stability over bug/performance
enhancements in there package choices. For example (a major unnamed
linux distribution) still ships mysql 5.0 rather then 5.1, or
BerkelyDB that NEVER gets upgraded. Why? Tracking these packages and
all the downstream changes from code that links to mysql or BDB would
result in way to much churn, that would make them look less stable and
"enterprise like".

Another major distribution allows anyone to submit a package, as a
result they end up with hundreds/thousands of packages that NEVER get
updated or supported in any meaningful way.

As for Cassandra there are two key components Java and Cassandra. If
you are just taking whatever the distro gives you for these things,
you should probably do more research.

As to not letting the cat out of the bag on what you can do with RPM.
I agree, half heartedly. RPM is a glorified tar, and when it begins
insisting you need 40 dependent libraries you do not really need
(which is very common especially in the RPM Java world) because some
applet in the buried in an example somewhere just might need
x11....Well I am more likely to edit the source RPM and make myself
happy then let RPM install all of gnome just so the RPM is happy.

In this case OpenJDK or SUN should meet the java >=1.6.0 requirement.

Edward

Mime
View raw message