On 2/28/2012 8:16 AM, Shawn Heisey wrote:
Due to the End of Life announcement for Java6, I am going to need to
upgrade to Java 7 in the very near future. I'm running Solr 3.5.0
modified with a couple of JIRA patches.
https://blogs.oracle.com/henrik/entry/updated_java_6_eol_date
I saw the announcement that Java 7u1 had fixed all the known bugs
relating to Solr. Is there anything I need to be aware of when
upgrading? These are the commandline switches I am using that apply
to Java itself:
-Xms8192M
-Xmx8192M
-XX:NewSize=6144M
-XX:SurvivorRatio=4
-XX:+UseParNewGC
-XX:+UseConcMarkSweepGC
-XX:+CMSParallelRemarkEnabled
I assume from the lack of response that either there are no foreseeable
problems or the potential problems are so bad that nobody wants to
mention them.
I would upgrade to Java 7 on my secondary index servers first. My SolrJ
build program is normally colocated on one of the primary index servers,
though corosync/pacemaker can move it in the event of a machine failure.
Here's a more targeted question:
In simple terms, this means that for a testing period of several weeks,
my SolrJ application will be running a different Java version than one
of my indexes, and the same version as the other index. The Java 7
announcement on the Solr page says that there are unicode changes when
upgrading to Java 7. Will those changes cause problems with SolrJ on
one java version and the index on another?
Thanks,
Shawn
