Yes, there are some trivial modifications to JVM settings for Java 11 new
way to activate GC logging, but really that's peanuts.

To be also more precise : we still build our topologies using JDK8, but we
use Java 11 runtime to run Storm Nimbus, Nimbus UI, Supervisor, etc.
processes.

Kind regards,
Alexandre



Le jeu. 5 sept. 2019 à 10:51, Dharmarajan Rajendran <
[email protected]> a écrit :

> Thanks Stig, Alexandre, Andrew for your comments.
>
> For your information
> I tried upgrading java version from 8 to 11 (openjdk) in our dev
> environment. I found that the worker process is not started and throwing
> below error in worker.log.
>
> 2019-09-04 10:11:23.054 STDERR [INFO] Unrecognized VM option
> 'PrintGCDateStamps'
> 2019-09-04 10:11:23.072 STDERR [INFO] Error: Could not create the Java
> Virtual Machine.
> 2019-09-04 10:11:23.073 STDERR [INFO] Error: A fatal exception has
> occurred. Program will exit.
> 2019-09-04 10:13:26.211 STDERR [INFO] [0.001s][warning][gc] -Xloggc is
> deprecated. Will use -Xlog:gc:artifacts/gc.log instead.
> 2019-09-04 10:13:26.211 STDERR [INFO] Unrecognized VM option
> 'PrintGCDateStamps'
> 2019-09-04 10:13:26.249 STDERR [INFO] Error: Could not create the Java
> Virtual Machine.
> 2019-09-04 10:13:26.252 STDERR [INFO] Error: A fatal exception has
> occurred. Program will exit.
>
> It looks like some of the default JVM options defined for worker
> process are not supported by java 11. So I have overridden the default JVM
> options in supervisor storm.yaml file and it started working
> https://github.com/apache/storm/blob/master/conf/defaults.yaml
> Default:
> worker.childopts: "-Xmx%HEAP-MEM%m -XX:+PrintGCDetails
> -Xloggc:artifacts/gc.log -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps
> -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=10 -XX:GCLogFileSize=1M
> -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=artifacts/heapdump"
> Updated to  (removed unsupported JVM options )
> worker.childopts: "-Xmx768m -Xlog:gc:artifacts/gc.log 
> -XX:+HeapDumpOnOutOfMemoryError
> -XX:HeapDumpPath=artifacts/heapdump"
>
>
> Thanks
> Dharmarajan
>
> On Wed, Sep 4, 2019 at 8:03 PM Andrew Xor <[email protected]>
> wrote:
>
>> Storm 2.0 compiles and runs fine using Java 11, at least in my
>> experience...
>>
>> On Wed, Sep 4, 2019 at 5:28 PM Stig Rohde Døssing <[email protected]>
>> wrote:
>>
>>> It doesn't support Java 11. Storm 2.0.0 has had work done to support
>>> Java 11, but the Cassandra and Hadoop parts are blocked by those projects
>>> lacking support so far. I think the rest of Storm 2.0.0 is likely to work.
>>>
>>> I don't believe you need to follow any special steps to migrate to Java
>>> 11.
>>>
>>> Den ons. 4. sep. 2019 kl. 11.30 skrev Dharmarajan Rajendran <
>>> [email protected]>:
>>>
>>>> Hi All,
>>>>
>>>> We are currently running storm 1.2.1 on java 8. We are planning to
>>>> upgrade java 8 to java 11 (openjdk).
>>>> Does storm 1.2.1 support java 11? Kindly advise if i need to do follow
>>>> any steps to run storm 1.2.1 on java 11.
>>>>
>>>> Thanks
>>>> Dharmarajan
>>>>
>>>

Reply via email to