[jira] [Updated] (HIVE-23938) LLAP: JDK11 - some GC log file rotation related jvm arguments cannot be used anymore

2020-10-12 Thread Jira 


 [ 
https://issues.apache.org/jira/browse/HIVE-23938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

László Bodor updated HIVE-23938:

Fix Version/s: 4.0.0

> LLAP: JDK11 - some GC log file rotation related jvm arguments cannot be used 
> anymore
> 
>
> Key: HIVE-23938
> URL: https://issues.apache.org/jira/browse/HIVE-23938
> Project: Hive
>  Issue Type: Improvement
>Reporter: László Bodor
>Assignee: László Bodor
>Priority: Major
>  Labels: pull-request-available
> Fix For: 4.0.0
>
> Attachments: gc_2020-07-27-13.log, gc_2020-07-29-12.jdk8.log, 
> llap_new_gc_options_fail_on_jdk8.log
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> https://github.com/apache/hive/blob/master/llap-server/bin/runLlapDaemon.sh#L55
> {code}
> JAVA_OPTS_BASE="-server -Djava.net.preferIPv4Stack=true -XX:+UseNUMA 
> -XX:+PrintGCDetails -verbose:gc -XX:+UseGCLogFileRotation 
> -XX:NumberOfGCLogFiles=4 -XX:GCLogFileSize=100M -XX:+PrintGCDateStamps"
> {code}
> on JDK11 I got something like:
> {code}
> + exec /usr/lib/jvm/jre-11-openjdk/bin/java -Dproc_llapdaemon -Xms32000m 
> -Xmx64000m -Dhttp.maxConnections=17 -XX:+UseG1GC -XX:+ResizeTLAB -XX:+UseNUMA 
> -XX:+AggressiveOpts -XX:MetaspaceSize=1024m 
> -XX:InitiatingHeapOccupancyPercent=80 -XX:MaxGCPauseMillis=200 
> -XX:+PreserveFramePointer -XX:AllocatePrefetchStyle=2 
> -Dhttp.maxConnections=10 -Dasync.profiler.home=/grid/0/async-profiler -server 
> -Djava.net.preferIPv4Stack=true -XX:+UseNUMA -XX:+PrintGCDetails -verbose:gc 
> -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=4 -XX:GCLogFileSize=100M 
> -XX:+PrintGCDateStamps 
> -Xloggc:/grid/2/yarn/container-logs/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/gc_2020-07-27-12.log
>  
> ... 
> org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon
> OpenJDK 64-Bit Server VM warning: Option AggressiveOpts was deprecated in 
> version 11.0 and will likely be removed in a future release.
> Unrecognized VM option 'UseGCLogFileRotation'
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> {code}
> These are not valid in JDK11:
> {code}
> -XX:+UseGCLogFileRotation
> -XX:NumberOfGCLogFiles
> -XX:GCLogFileSize
> -XX:+PrintGCTimeStamps
> -XX:+PrintGCDateStamps
> {code}
> Instead something like:
> {code}
> -Xlog:gc*,safepoint:gc.log:time,uptime:filecount=4,filesize=100M
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (HIVE-23938) LLAP: JDK11 - some GC log file rotation related jvm arguments cannot be used anymore

2020-09-07 Thread Jira 


 [ 
https://issues.apache.org/jira/browse/HIVE-23938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

László Bodor updated HIVE-23938:

Attachment: llap_new_gc_options_fail_on_jdk8.log

> LLAP: JDK11 - some GC log file rotation related jvm arguments cannot be used 
> anymore
> 
>
> Key: HIVE-23938
> URL: https://issues.apache.org/jira/browse/HIVE-23938
> Project: Hive
>  Issue Type: Improvement
>Reporter: László Bodor
>Assignee: László Bodor
>Priority: Major
>  Labels: pull-request-available
> Attachments: gc_2020-07-27-13.log, gc_2020-07-29-12.jdk8.log, 
> llap_new_gc_options_fail_on_jdk8.log
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> https://github.com/apache/hive/blob/master/llap-server/bin/runLlapDaemon.sh#L55
> {code}
> JAVA_OPTS_BASE="-server -Djava.net.preferIPv4Stack=true -XX:+UseNUMA 
> -XX:+PrintGCDetails -verbose:gc -XX:+UseGCLogFileRotation 
> -XX:NumberOfGCLogFiles=4 -XX:GCLogFileSize=100M -XX:+PrintGCDateStamps"
> {code}
> on JDK11 I got something like:
> {code}
> + exec /usr/lib/jvm/jre-11-openjdk/bin/java -Dproc_llapdaemon -Xms32000m 
> -Xmx64000m -Dhttp.maxConnections=17 -XX:+UseG1GC -XX:+ResizeTLAB -XX:+UseNUMA 
> -XX:+AggressiveOpts -XX:MetaspaceSize=1024m 
> -XX:InitiatingHeapOccupancyPercent=80 -XX:MaxGCPauseMillis=200 
> -XX:+PreserveFramePointer -XX:AllocatePrefetchStyle=2 
> -Dhttp.maxConnections=10 -Dasync.profiler.home=/grid/0/async-profiler -server 
> -Djava.net.preferIPv4Stack=true -XX:+UseNUMA -XX:+PrintGCDetails -verbose:gc 
> -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=4 -XX:GCLogFileSize=100M 
> -XX:+PrintGCDateStamps 
> -Xloggc:/grid/2/yarn/container-logs/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/gc_2020-07-27-12.log
>  
> ... 
> org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon
> OpenJDK 64-Bit Server VM warning: Option AggressiveOpts was deprecated in 
> version 11.0 and will likely be removed in a future release.
> Unrecognized VM option 'UseGCLogFileRotation'
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> {code}
> These are not valid in JDK11:
> {code}
> -XX:+UseGCLogFileRotation
> -XX:NumberOfGCLogFiles
> -XX:GCLogFileSize
> -XX:+PrintGCTimeStamps
> -XX:+PrintGCDateStamps
> {code}
> Instead something like:
> {code}
> -Xlog:gc*,safepoint:gc.log:time,uptime:filecount=4,filesize=100M
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (HIVE-23938) LLAP: JDK11 - some GC log file rotation related jvm arguments cannot be used anymore

2020-08-25 Thread ASF GitHub Bot (Jira) 


 [ 
https://issues.apache.org/jira/browse/HIVE-23938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated HIVE-23938:
--
Labels: pull-request-available  (was: )

> LLAP: JDK11 - some GC log file rotation related jvm arguments cannot be used 
> anymore
> 
>
> Key: HIVE-23938
> URL: https://issues.apache.org/jira/browse/HIVE-23938
> Project: Hive
>  Issue Type: Improvement
>Reporter: László Bodor
>Assignee: László Bodor
>Priority: Major
>  Labels: pull-request-available
> Attachments: gc_2020-07-27-13.log, gc_2020-07-29-12.jdk8.log
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> https://github.com/apache/hive/blob/master/llap-server/bin/runLlapDaemon.sh#L55
> {code}
> JAVA_OPTS_BASE="-server -Djava.net.preferIPv4Stack=true -XX:+UseNUMA 
> -XX:+PrintGCDetails -verbose:gc -XX:+UseGCLogFileRotation 
> -XX:NumberOfGCLogFiles=4 -XX:GCLogFileSize=100M -XX:+PrintGCDateStamps"
> {code}
> on JDK11 I got something like:
> {code}
> + exec /usr/lib/jvm/jre-11-openjdk/bin/java -Dproc_llapdaemon -Xms32000m 
> -Xmx64000m -Dhttp.maxConnections=17 -XX:+UseG1GC -XX:+ResizeTLAB -XX:+UseNUMA 
> -XX:+AggressiveOpts -XX:MetaspaceSize=1024m 
> -XX:InitiatingHeapOccupancyPercent=80 -XX:MaxGCPauseMillis=200 
> -XX:+PreserveFramePointer -XX:AllocatePrefetchStyle=2 
> -Dhttp.maxConnections=10 -Dasync.profiler.home=/grid/0/async-profiler -server 
> -Djava.net.preferIPv4Stack=true -XX:+UseNUMA -XX:+PrintGCDetails -verbose:gc 
> -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=4 -XX:GCLogFileSize=100M 
> -XX:+PrintGCDateStamps 
> -Xloggc:/grid/2/yarn/container-logs/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/gc_2020-07-27-12.log
>  
> ... 
> org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon
> OpenJDK 64-Bit Server VM warning: Option AggressiveOpts was deprecated in 
> version 11.0 and will likely be removed in a future release.
> Unrecognized VM option 'UseGCLogFileRotation'
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> {code}
> These are not valid in JDK11:
> {code}
> -XX:+UseGCLogFileRotation
> -XX:NumberOfGCLogFiles
> -XX:GCLogFileSize
> -XX:+PrintGCTimeStamps
> -XX:+PrintGCDateStamps
> {code}
> Instead something like:
> {code}
> -Xlog:gc*,safepoint:gc.log:time,uptime:filecount=4,filesize=100M
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (HIVE-23938) LLAP: JDK11 - some GC log file rotation related jvm arguments cannot be used anymore

2020-08-13 Thread Jira 


 [ 
https://issues.apache.org/jira/browse/HIVE-23938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

László Bodor updated HIVE-23938:

Attachment: gc_2020-07-29-12.jdk8.log

> LLAP: JDK11 - some GC log file rotation related jvm arguments cannot be used 
> anymore
> 
>
> Key: HIVE-23938
> URL: https://issues.apache.org/jira/browse/HIVE-23938
> Project: Hive
>  Issue Type: Improvement
>Reporter: László Bodor
>Assignee: László Bodor
>Priority: Major
> Attachments: gc_2020-07-27-13.log, gc_2020-07-29-12.jdk8.log
>
>
> https://github.com/apache/hive/blob/master/llap-server/bin/runLlapDaemon.sh#L55
> {code}
> JAVA_OPTS_BASE="-server -Djava.net.preferIPv4Stack=true -XX:+UseNUMA 
> -XX:+PrintGCDetails -verbose:gc -XX:+UseGCLogFileRotation 
> -XX:NumberOfGCLogFiles=4 -XX:GCLogFileSize=100M -XX:+PrintGCDateStamps"
> {code}
> on JDK11 I got something like:
> {code}
> + exec /usr/lib/jvm/jre-11-openjdk/bin/java -Dproc_llapdaemon -Xms32000m 
> -Xmx64000m -Dhttp.maxConnections=17 -XX:+UseG1GC -XX:+ResizeTLAB -XX:+UseNUMA 
> -XX:+AggressiveOpts -XX:MetaspaceSize=1024m 
> -XX:InitiatingHeapOccupancyPercent=80 -XX:MaxGCPauseMillis=200 
> -XX:+PreserveFramePointer -XX:AllocatePrefetchStyle=2 
> -Dhttp.maxConnections=10 -Dasync.profiler.home=/grid/0/async-profiler -server 
> -Djava.net.preferIPv4Stack=true -XX:+UseNUMA -XX:+PrintGCDetails -verbose:gc 
> -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=4 -XX:GCLogFileSize=100M 
> -XX:+PrintGCDateStamps 
> -Xloggc:/grid/2/yarn/container-logs/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/gc_2020-07-27-12.log
>  
> ... 
> org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon
> OpenJDK 64-Bit Server VM warning: Option AggressiveOpts was deprecated in 
> version 11.0 and will likely be removed in a future release.
> Unrecognized VM option 'UseGCLogFileRotation'
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> {code}
> These are not valid in JDK11:
> {code}
> -XX:+UseGCLogFileRotation
> -XX:NumberOfGCLogFiles
> -XX:GCLogFileSize
> -XX:+PrintGCTimeStamps
> -XX:+PrintGCDateStamps
> {code}
> Instead something like:
> {code}
> -Xlog:gc*,safepoint:gc.log:time,uptime:filecount=4,filesize=100M
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (HIVE-23938) LLAP: JDK11 - some GC log file rotation related jvm arguments cannot be used anymore

2020-07-27 Thread Jira 


 [ 
https://issues.apache.org/jira/browse/HIVE-23938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

László Bodor updated HIVE-23938:

Description: 
https://github.com/apache/hive/blob/master/llap-server/bin/runLlapDaemon.sh#L55
{code}
JAVA_OPTS_BASE="-server -Djava.net.preferIPv4Stack=true -XX:+UseNUMA 
-XX:+PrintGCDetails -verbose:gc -XX:+UseGCLogFileRotation 
-XX:NumberOfGCLogFiles=4 -XX:GCLogFileSize=100M -XX:+PrintGCDateStamps"
{code}

on JDK11 I got something like:
{code}
+ exec /usr/lib/jvm/jre-11-openjdk/bin/java -Dproc_llapdaemon -Xms32000m 
-Xmx64000m -Dhttp.maxConnections=17 -XX:+UseG1GC -XX:+ResizeTLAB -XX:+UseNUMA 
-XX:+AggressiveOpts -XX:MetaspaceSize=1024m 
-XX:InitiatingHeapOccupancyPercent=80 -XX:MaxGCPauseMillis=200 
-XX:+PreserveFramePointer -XX:AllocatePrefetchStyle=2 -Dhttp.maxConnections=10 
-Dasync.profiler.home=/grid/0/async-profiler -server 
-Djava.net.preferIPv4Stack=true -XX:+UseNUMA -XX:+PrintGCDetails -verbose:gc 
-XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=4 -XX:GCLogFileSize=100M 
-XX:+PrintGCDateStamps 
-Xloggc:/grid/2/yarn/container-logs/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/gc_2020-07-27-12.log
 
... 
org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon

OpenJDK 64-Bit Server VM warning: Option AggressiveOpts was deprecated in 
version 11.0 and will likely be removed in a future release.
Unrecognized VM option 'UseGCLogFileRotation'
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
{code}

These are not valid in JDK11:
{code}
-XX:+UseGCLogFileRotation
-XX:NumberOfGCLogFiles
-XX:GCLogFileSize
-XX:+PrintGCTimeStamps
-XX:+PrintGCDateStamps
{code}

Instead something like:
{code}
-Xlog:gc*,safepoint:gc.log:time,uptime:filecount=4,filesize=100M
{code}

  was:
https://github.com/apache/hive/blob/master/llap-server/bin/runLlapDaemon.sh#L55
{code}
JAVA_OPTS_BASE="-server -Djava.net.preferIPv4Stack=true -XX:+UseNUMA 
-XX:+PrintGCDetails -verbose:gc -XX:+UseGCLogFileRotation 
-XX:NumberOfGCLogFiles=4 -XX:GCLogFileSize=100M -XX:+PrintGCDateStamps"
{code}

on JDK11 I got something like:
{code}
+ exec /usr/lib/jvm/jre-11-openjdk/bin/java -Dproc_llapdaemon -Xms32000m 
-Xmx64000m -Dhttp.maxConnections=17 -XX:+UseG1GC -XX:+ResizeTLAB -XX:+UseNUMA 
-XX:+AggressiveOpts -XX:MetaspaceSize=1024m 
-XX:InitiatingHeapOccupancyPercent=80 -XX:MaxGCPauseMillis=200 
-XX:+PreserveFramePointer -XX:AllocatePrefetchStyle=2 -Dhttp.maxConnections=10 
-Dasync.profiler.home=/grid/0/async-profiler -server 
-Djava.net.preferIPv4Stack=true -XX:+UseNUMA -XX:+PrintGCDetails -verbose:gc 
-XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=4 -XX:GCLogFileSize=100M 
-XX:+PrintGCDateStamps 
-Xloggc:/grid/2/yarn/container-logs/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/gc_2020-07-27-12.log
 
-Djava.io.tmpdir=/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/tmp/
 -Dlog4j.configurationFile= 
-Dllap.daemon.log.dir=/grid/2/yarn/container-logs/application_1595375468459_0113/container_e26_1595375468459_0113_01_09
 
-Dllap.daemon.log.file=llap-daemon-lbodor-ctr-e141-1563959304486-69251-01-11.hwx.site.log
 -Dllap.daemon.root.logger=query-routing -Dllap.daemon.log.level=INFO 
-classpath 
'/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib/conf/:/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib//lib/*:/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib//lib/tez/*:/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib//lib/udfs/*:.:'
 org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon
OpenJDK 64-Bit Server VM warning: Option AggressiveOpts was deprecated in 
version 11.0 and will likely be removed in a future release.
Unrecognized VM option 'UseGCLogFileRotation'
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
{code}

These are not valid in JDK11:
{code}
-XX:+UseGCLogFileRotation
-XX:NumberOfGCLogFiles
-XX:GCLogFileSize
-XX:+PrintGCTimeStamps
-XX:+PrintGCDateStamps
{code}

Instead something like:
{code}
-Xlog:gc*,safepoint:gc.log:time,uptime:filecount=4,filesize=100M
{code}


> LLAP: JDK11 - some GC log file rotation related jvm arguments cannot be used 
> anymore
> 
>
> Key: HIVE-23938
> URL: https://issues.apache.org/jira/browse/HIVE-23938
> Project: Hive
>  Issue Type: Improvement
>Reporter: László Bodor
>Assignee: László Bodor
>Priority: Major
>

[jira] [Updated] (HIVE-23938) LLAP: JDK11 - some GC log file rotation related jvm arguments cannot be used anymore

2020-07-27 Thread Jira 


 [ 
https://issues.apache.org/jira/browse/HIVE-23938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

László Bodor updated HIVE-23938:

Attachment: gc_2020-07-27-13.log

> LLAP: JDK11 - some GC log file rotation related jvm arguments cannot be used 
> anymore
> 
>
> Key: HIVE-23938
> URL: https://issues.apache.org/jira/browse/HIVE-23938
> Project: Hive
>  Issue Type: Improvement
>Reporter: László Bodor
>Assignee: László Bodor
>Priority: Major
> Attachments: gc_2020-07-27-13.log
>
>
> https://github.com/apache/hive/blob/master/llap-server/bin/runLlapDaemon.sh#L55
> {code}
> JAVA_OPTS_BASE="-server -Djava.net.preferIPv4Stack=true -XX:+UseNUMA 
> -XX:+PrintGCDetails -verbose:gc -XX:+UseGCLogFileRotation 
> -XX:NumberOfGCLogFiles=4 -XX:GCLogFileSize=100M -XX:+PrintGCDateStamps"
> {code}
> on JDK11 I got something like:
> {code}
> + exec /usr/lib/jvm/jre-11-openjdk/bin/java -Dproc_llapdaemon -Xms32000m 
> -Xmx64000m -Dhttp.maxConnections=17 -XX:+UseG1GC -XX:+ResizeTLAB -XX:+UseNUMA 
> -XX:+AggressiveOpts -XX:MetaspaceSize=1024m 
> -XX:InitiatingHeapOccupancyPercent=80 -XX:MaxGCPauseMillis=200 
> -XX:+PreserveFramePointer -XX:AllocatePrefetchStyle=2 
> -Dhttp.maxConnections=10 -Dasync.profiler.home=/grid/0/async-profiler -server 
> -Djava.net.preferIPv4Stack=true -XX:+UseNUMA -XX:+PrintGCDetails -verbose:gc 
> -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=4 -XX:GCLogFileSize=100M 
> -XX:+PrintGCDateStamps 
> -Xloggc:/grid/2/yarn/container-logs/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/gc_2020-07-27-12.log
>  
> -Djava.io.tmpdir=/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/tmp/
>  -Dlog4j.configurationFile= 
> -Dllap.daemon.log.dir=/grid/2/yarn/container-logs/application_1595375468459_0113/container_e26_1595375468459_0113_01_09
>  
> -Dllap.daemon.log.file=llap-daemon-lbodor-ctr-e141-1563959304486-69251-01-11.hwx.site.log
>  -Dllap.daemon.root.logger=query-routing -Dllap.daemon.log.level=INFO 
> -classpath 
> '/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib/conf/:/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib//lib/*:/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib//lib/tez/*:/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib//lib/udfs/*:.:'
>  org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon
> OpenJDK 64-Bit Server VM warning: Option AggressiveOpts was deprecated in 
> version 11.0 and will likely be removed in a future release.
> Unrecognized VM option 'UseGCLogFileRotation'
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> {code}
> These are not valid in JDK11:
> {code}
> -XX:+UseGCLogFileRotation
> -XX:NumberOfGCLogFiles
> -XX:GCLogFileSize
> -XX:+PrintGCTimeStamps
> -XX:+PrintGCDateStamps
> {code}
> Instead something like:
> {code}
> -Xlog:gc*,safepoint:gc.log:time,uptime:filecount=4,filesize=100M
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (HIVE-23938) LLAP: JDK11 - some GC log file rotation related jvm arguments cannot be used anymore

2020-07-27 Thread Jira 


 [ 
https://issues.apache.org/jira/browse/HIVE-23938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

László Bodor updated HIVE-23938:

Description: 
https://github.com/apache/hive/blob/master/llap-server/bin/runLlapDaemon.sh#L55
{code}
JAVA_OPTS_BASE="-server -Djava.net.preferIPv4Stack=true -XX:+UseNUMA 
-XX:+PrintGCDetails -verbose:gc -XX:+UseGCLogFileRotation 
-XX:NumberOfGCLogFiles=4 -XX:GCLogFileSize=100M -XX:+PrintGCDateStamps"
{code}

on JDK11 I got something like:
{code}
+ exec /usr/lib/jvm/jre-11-openjdk/bin/java -Dproc_llapdaemon -Xms32000m 
-Xmx64000m -Dhttp.maxConnections=17 -XX:+UseG1GC -XX:+ResizeTLAB -XX:+UseNUMA 
-XX:+AggressiveOpts -XX:MetaspaceSize=1024m 
-XX:InitiatingHeapOccupancyPercent=80 -XX:MaxGCPauseMillis=200 
-XX:+PreserveFramePointer -XX:AllocatePrefetchStyle=2 -Dhttp.maxConnections=10 
-Dasync.profiler.home=/grid/0/async-profiler -server 
-Djava.net.preferIPv4Stack=true -XX:+UseNUMA -XX:+PrintGCDetails -verbose:gc 
-XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=4 -XX:GCLogFileSize=100M 
-XX:+PrintGCDateStamps 
-Xloggc:/grid/2/yarn/container-logs/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/gc_2020-07-27-12.log
 
-Djava.io.tmpdir=/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/tmp/
 -Dlog4j.configurationFile= 
-Dllap.daemon.log.dir=/grid/2/yarn/container-logs/application_1595375468459_0113/container_e26_1595375468459_0113_01_09
 
-Dllap.daemon.log.file=llap-daemon-lbodor-ctr-e141-1563959304486-69251-01-11.hwx.site.log
 -Dllap.daemon.root.logger=query-routing -Dllap.daemon.log.level=INFO 
-classpath 
'/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib/conf/:/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib//lib/*:/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib//lib/tez/*:/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib//lib/udfs/*:.:'
 org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon
OpenJDK 64-Bit Server VM warning: Option AggressiveOpts was deprecated in 
version 11.0 and will likely be removed in a future release.
Unrecognized VM option 'UseGCLogFileRotation'
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
{code}

These are not valid in JDK11:
{code}
-XX:+UseGCLogFileRotation
-XX:NumberOfGCLogFiles
-XX:GCLogFileSize
-XX:+PrintGCTimeStamps
-XX:+PrintGCDateStamps
{code}

Instead something like:
{code}
-Xlog:gc*,safepoint:gc.log:time,uptime:filecount=4,filesize=100M
{code}

  was:
https://github.com/apache/hive/blob/master/llap-server/bin/runLlapDaemon.sh#L55
{code}
JAVA_OPTS_BASE="-server -Djava.net.preferIPv4Stack=true -XX:+UseNUMA 
-XX:+PrintGCDetails -verbose:gc -XX:+UseGCLogFileRotation 
-XX:NumberOfGCLogFiles=4 -XX:GCLogFileSize=100M -XX:+PrintGCDateStamps"
{code}

on JDK11 I got something like:
{code}
+ exec /usr/lib/jvm/jre-11-openjdk/bin/java -Dproc_llapdaemon -Xms32000m 
-Xmx64000m -Dhttp.maxConnections=17 -XX:+UseG1GC -XX:+ResizeTLAB -XX:+UseNUMA 
-XX:+AggressiveOpts -XX:MetaspaceSize=1024m 
-XX:InitiatingHeapOccupancyPercent=80 -XX:MaxGCPauseMillis=200 
-XX:+PreserveFramePointer -XX:AllocatePrefetchStyle=2 -Dhttp.maxConnections=10 
-Dasync.profiler.home=/grid/0/async-profiler -server 
-Djava.net.preferIPv4Stack=true -XX:+UseNUMA -XX:+PrintGCDetails -verbose:gc 
-XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=4 -XX:GCLogFileSize=100M 
-XX:+PrintGCDateStamps 
-Xloggc:/grid/2/yarn/container-logs/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/gc_2020-07-27-12.log
 
-Djava.io.tmpdir=/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/tmp/
 -Dlog4j.configurationFile= 
-Dllap.daemon.log.dir=/grid/2/yarn/container-logs/application_1595375468459_0113/container_e26_1595375468459_0113_01_09
 
-Dllap.daemon.log.file=llap-daemon-lbodor-ctr-e141-1563959304486-69251-01-11.hwx.site.log
 -Dllap.daemon.root.logger=query-routing -Dllap.daemon.log.level=INFO 
-classpath 
'/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib/conf/:/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib//lib/*:/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib//lib/tez/*:/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib//lib/udfs/*:.:'
 org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon
OpenJDK 64-Bit Server VM

[jira] [Updated] (HIVE-23938) LLAP: JDK11 - some GC log file rotation related jvm arguments cannot be used anymore

2020-07-27 Thread Jira 


 [ 
https://issues.apache.org/jira/browse/HIVE-23938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

László Bodor updated HIVE-23938:

Description: 
https://github.com/apache/hive/blob/master/llap-server/bin/runLlapDaemon.sh#L55
{code}
JAVA_OPTS_BASE="-server -Djava.net.preferIPv4Stack=true -XX:+UseNUMA 
-XX:+PrintGCDetails -verbose:gc -XX:+UseGCLogFileRotation 
-XX:NumberOfGCLogFiles=4 -XX:GCLogFileSize=100M -XX:+PrintGCDateStamps"
{code}

on JDK11 I got something like:
{code}
+ exec /usr/lib/jvm/jre-11-openjdk/bin/java -Dproc_llapdaemon -Xms32000m 
-Xmx64000m -Dhttp.maxConnections=17 -XX:+UseG1GC -XX:+ResizeTLAB -XX:+UseNUMA 
-XX:+AggressiveOpts -XX:MetaspaceSize=1024m 
-XX:InitiatingHeapOccupancyPercent=80 -XX:MaxGCPauseMillis=200 
-XX:+PreserveFramePointer -XX:AllocatePrefetchStyle=2 -Dhttp.maxConnections=10 
-Dasync.profiler.home=/grid/0/async-profiler -server 
-Djava.net.preferIPv4Stack=true -XX:+UseNUMA -XX:+PrintGCDetails -verbose:gc 
-XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=4 -XX:GCLogFileSize=100M 
-XX:+PrintGCDateStamps 
-Xloggc:/grid/2/yarn/container-logs/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/gc_2020-07-27-12.log
 
-Djava.io.tmpdir=/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/tmp/
 -Dlog4j.configurationFile= 
-Dllap.daemon.log.dir=/grid/2/yarn/container-logs/application_1595375468459_0113/container_e26_1595375468459_0113_01_09
 
-Dllap.daemon.log.file=llap-daemon-lbodor-ctr-e141-1563959304486-69251-01-11.hwx.site.log
 -Dllap.daemon.root.logger=query-routing -Dllap.daemon.log.level=INFO 
-classpath 
'/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib/conf/:/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib//lib/*:/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib//lib/tez/*:/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib//lib/udfs/*:.:'
 org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon
OpenJDK 64-Bit Server VM warning: Option AggressiveOpts was deprecated in 
version 11.0 and will likely be removed in a future release.
Unrecognized VM option 'UseGCLogFileRotation'
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
{code}

There are not valid in JDK11:
{code}
-XX:+UseGCLogFileRotation
-XX:NumberOfGCLogFiles
-XX:GCLogFileSize
-XX:+PrintGCTimeStamps
-XX:+PrintGCDateStamps
{code}

Instead something like:
{code}
-Xlog:gc*,safepoint:gc.log:time,uptime:filecount=4,filesize=100M
{code}

  was:
https://github.com/apache/hive/blob/master/llap-server/bin/runLlapDaemon.sh#L55
{code}
JAVA_OPTS_BASE="-server -Djava.net.preferIPv4Stack=true -XX:+UseNUMA 
-XX:+PrintGCDetails -verbose:gc -XX:+UseGCLogFileRotation 
-XX:NumberOfGCLogFiles=4 -XX:GCLogFileSize=100M -XX:+PrintGCDateStamps"
{code}

on JDK11 I got something like:
{code}
+ exec /usr/lib/jvm/jre-11-openjdk/bin/java -Dproc_llapdaemon -Xms32000m 
-Xmx64000m -Dhttp.maxConnections=17 -XX:+UseG1GC -XX:+ResizeTLAB -XX:+UseNUMA 
-XX:+AggressiveOpts -XX:MetaspaceSize=1024m 
-XX:InitiatingHeapOccupancyPercent=80 -XX:MaxGCPauseMillis=200 
-XX:+PreserveFramePointer -XX:AllocatePrefetchStyle=2 -Dhttp.maxConnections=10 
-Dasync.profiler.home=/grid/0/async-profiler -server 
-Djava.net.preferIPv4Stack=true -XX:+UseNUMA -XX:+PrintGCDetails -verbose:gc 
-XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=4 -XX:GCLogFileSize=100M 
-XX:+PrintGCDateStamps 
-Xloggc:/grid/2/yarn/container-logs/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/gc_2020-07-27-12.log
 
-Djava.io.tmpdir=/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/tmp/
 -Dlog4j.configurationFile= 
-Dllap.daemon.log.dir=/grid/2/yarn/container-logs/application_1595375468459_0113/container_e26_1595375468459_0113_01_09
 
-Dllap.daemon.log.file=llap-daemon-lbodor-ctr-e141-1563959304486-69251-01-11.hwx.site.log
 -Dllap.daemon.root.logger=query-routing -Dllap.daemon.log.level=INFO 
-classpath 
'/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib/conf/:/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib//lib/*:/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib//lib/tez/*:/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib//lib/udfs/*:.:'
 org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon
OpenJDK 64-Bit Server VM

[jira] [Updated] (HIVE-23938) LLAP: JDK11 - some GC log file rotation related jvm arguments cannot be used anymore

2020-07-27 Thread Jira 


 [ 
https://issues.apache.org/jira/browse/HIVE-23938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

László Bodor updated HIVE-23938:

Description: 
https://github.com/apache/hive/blob/master/llap-server/bin/runLlapDaemon.sh#L55
{code}
JAVA_OPTS_BASE="-server -Djava.net.preferIPv4Stack=true -XX:+UseNUMA 
-XX:+PrintGCDetails -verbose:gc -XX:+UseGCLogFileRotation 
-XX:NumberOfGCLogFiles=4 -XX:GCLogFileSize=100M -XX:+PrintGCDateStamps"
{code}

on JDK11 I got something like:
{code}
+ exec /usr/lib/jvm/jre-11-openjdk/bin/java -Dproc_llapdaemon -Xms32000m 
-Xmx64000m -Dhttp.maxConnections=17 -XX:+UseG1GC -XX:+ResizeTLAB -XX:+UseNUMA 
-XX:+AggressiveOpts -XX:MetaspaceSize=1024m 
-XX:InitiatingHeapOccupancyPercent=80 -XX:MaxGCPauseMillis=200 
-XX:+PreserveFramePointer -XX:AllocatePrefetchStyle=2 -Dhttp.maxConnections=10 
-Dasync.profiler.home=/grid/0/async-profiler -server 
-Djava.net.preferIPv4Stack=true -XX:+UseNUMA -XX:+PrintGCDetails -verbose:gc 
-XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=4 -XX:GCLogFileSize=100M 
-XX:+PrintGCDateStamps 
-Xloggc:/grid/2/yarn/container-logs/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/gc_2020-07-27-12.log
 
-Djava.io.tmpdir=/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/tmp/
 -Dlog4j.configurationFile= 
-Dllap.daemon.log.dir=/grid/2/yarn/container-logs/application_1595375468459_0113/container_e26_1595375468459_0113_01_09
 
-Dllap.daemon.log.file=llap-daemon-lbodor-ctr-e141-1563959304486-69251-01-11.hwx.site.log
 -Dllap.daemon.root.logger=query-routing -Dllap.daemon.log.level=INFO 
-classpath 
'/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib/conf/:/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib//lib/*:/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib//lib/tez/*:/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib//lib/udfs/*:.:'
 org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon
OpenJDK 64-Bit Server VM warning: Option AggressiveOpts was deprecated in 
version 11.0 and will likely be removed in a future release.
Unrecognized VM option 'UseGCLogFileRotation'
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
{code}

There are not valid in JDK11:
{code}
-XX:+UseGCLogFileRotation
-XX:NumberOfGCLogFiles
-XX:GCLogFileSize 
{code}

Instead something like:
{code}
-Xlog:gc*,safepoint:gc.log:time,uptime:filecount=4,filesize=100M
{code}

  was:
https://github.com/apache/hive/blob/master/llap-server/bin/runLlapDaemon.sh#L55
{code}
JAVA_OPTS_BASE="-server -Djava.net.preferIPv4Stack=true -XX:+UseNUMA 
-XX:+PrintGCDetails -verbose:gc -XX:+UseGCLogFileRotation 
-XX:NumberOfGCLogFiles=4 -XX:GCLogFileSize=100M -XX:+PrintGCDateStamps"
{code}

on JDK11 I got something like:
{code}
+ exec /usr/lib/jvm/jre-11-openjdk/bin/java -Dproc_llapdaemon -Xms32000m 
-Xmx64000m -Dhttp.maxConnections=17 -XX:+UseG1GC -XX:+ResizeTLAB -XX:+UseNUMA 
-XX:+AggressiveOpts -XX:MetaspaceSize=1024m 
-XX:InitiatingHeapOccupancyPercent=80 -XX:MaxGCPauseMillis=200 
-XX:+PreserveFramePointer -XX:AllocatePrefetchStyle=2 -Dhttp.maxConnections=10 
-Dasync.profiler.home=/grid/0/async-profiler -server 
-Djava.net.preferIPv4Stack=true -XX:+UseNUMA -XX:+PrintGCDetails -verbose:gc 
-XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=4 -XX:GCLogFileSize=100M 
-XX:+PrintGCDateStamps 
-Xloggc:/grid/2/yarn/container-logs/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/gc_2020-07-27-12.log
 
-Djava.io.tmpdir=/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/tmp/
 -Dlog4j.configurationFile= 
-Dllap.daemon.log.dir=/grid/2/yarn/container-logs/application_1595375468459_0113/container_e26_1595375468459_0113_01_09
 
-Dllap.daemon.log.file=llap-daemon-lbodor-ctr-e141-1563959304486-69251-01-11.hwx.site.log
 -Dllap.daemon.root.logger=query-routing -Dllap.daemon.log.level=INFO 
-classpath 
'/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib/conf/:/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib//lib/*:/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib//lib/tez/*:/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib//lib/udfs/*:.:'
 org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon
OpenJDK 64-Bit Server VM warning: Option AggressiveOpts was deprecated in

[jira] [Updated] (HIVE-23938) LLAP: JDK11 - some GC log file rotation related jvm arguments cannot be used anymore

2020-07-27 Thread Jira 


 [ 
https://issues.apache.org/jira/browse/HIVE-23938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

László Bodor updated HIVE-23938:

Description: 
https://github.com/apache/hive/blob/master/llap-server/bin/runLlapDaemon.sh#L55
{code}
JAVA_OPTS_BASE="-server -Djava.net.preferIPv4Stack=true -XX:+UseNUMA 
-XX:+PrintGCDetails -verbose:gc -XX:+UseGCLogFileRotation 
-XX:NumberOfGCLogFiles=4 -XX:GCLogFileSize=100M -XX:+PrintGCDateStamps"
{code}

on JDK11 I got something like:
{code}
+ exec /usr/lib/jvm/jre-11-openjdk/bin/java -Dproc_llapdaemon -Xms32000m 
-Xmx64000m -Dhttp.maxConnections=17 -XX:+UseG1GC -XX:+ResizeTLAB -XX:+UseNUMA 
-XX:+AggressiveOpts -XX:MetaspaceSize=1024m 
-XX:InitiatingHeapOccupancyPercent=80 -XX:MaxGCPauseMillis=200 
-XX:+PreserveFramePointer -XX:AllocatePrefetchStyle=2 -Dhttp.maxConnections=10 
-Dasync.profiler.home=/grid/0/async-profiler -server 
-Djava.net.preferIPv4Stack=true -XX:+UseNUMA -XX:+PrintGCDetails -verbose:gc 
-XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=4 -XX:GCLogFileSize=100M 
-XX:+PrintGCDateStamps 
-Xloggc:/grid/2/yarn/container-logs/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/gc_2020-07-27-12.log
 
-Djava.io.tmpdir=/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/tmp/
 -Dlog4j.configurationFile= 
-Dllap.daemon.log.dir=/grid/2/yarn/container-logs/application_1595375468459_0113/container_e26_1595375468459_0113_01_09
 
-Dllap.daemon.log.file=llap-daemon-lbodor-ctr-e141-1563959304486-69251-01-11.hwx.site.log
 -Dllap.daemon.root.logger=query-routing -Dllap.daemon.log.level=INFO 
-classpath 
'/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib/conf/:/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib//lib/*:/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib//lib/tez/*:/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib//lib/udfs/*:.:'
 org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon
OpenJDK 64-Bit Server VM warning: Option AggressiveOpts was deprecated in 
version 11.0 and will likely be removed in a future release.
Unrecognized VM option 'UseGCLogFileRotation'
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
{code}

There are not valid in JDK11:
{code}
-XX:+UseGCLogFileRotation
-XX:NumberOfGCLogFiles
-XX:GCLogFileSize 
{code}

Instead something like:
{code}
java -Xlog:gc*,safepoint:gc.log:time,uptime:filecount=4,filesize=100M ...
{code}

  was:
https://github.com/apache/hive/blob/master/llap-server/bin/runLlapDaemon.sh#L55
{code}
JAVA_OPTS_BASE="-server -Djava.net.preferIPv4Stack=true -XX:+UseNUMA 
-XX:+PrintGCDetails -verbose:gc -XX:+UseGCLogFileRotation 
-XX:NumberOfGCLogFiles=4 -XX:GCLogFileSize=100M -XX:+PrintGCDateStamps"
{code}

on JDK11 I got something like:
{code}
+ exec /usr/lib/jvm/jre-11-openjdk/bin/java -Dproc_llapdaemon -Xms32000m 
-Xmx64000m -Dhttp.maxConnections=17 -XX:+UseG1GC -XX:+ResizeTLAB -XX:+UseNUMA 
-XX:+AggressiveOpts -XX:MetaspaceSize=1024m 
-XX:InitiatingHeapOccupancyPercent=80 -XX:MaxGCPauseMillis=200 
-XX:+PreserveFramePointer -XX:AllocatePrefetchStyle=2 -Dhttp.maxConnections=10 
-Dasync.profiler.home=/grid/0/async-profiler -server 
-Djava.net.preferIPv4Stack=true -XX:+UseNUMA -XX:+PrintGCDetails -verbose:gc 
-XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=4 -XX:GCLogFileSize=100M 
-XX:+PrintGCDateStamps 
-Xloggc:/grid/2/yarn/container-logs/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/gc_2020-07-27-12.log
 
-Djava.io.tmpdir=/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/tmp/
 -Dlog4j.configurationFile= 
-Dllap.daemon.log.dir=/grid/2/yarn/container-logs/application_1595375468459_0113/container_e26_1595375468459_0113_01_09
 
-Dllap.daemon.log.file=llap-daemon-lbodor-ctr-e141-1563959304486-69251-01-11.hwx.site.log
 -Dllap.daemon.root.logger=query-routing -Dllap.daemon.log.level=INFO 
-classpath 
'/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib/conf/:/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib//lib/*:/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib//lib/tez/*:/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib//lib/udfs/*:.:'
 org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon
OpenJDK 64-Bit Server VM warning: Option AggressiveOpts was

[jira] [Updated] (HIVE-23938) LLAP: JDK11 - some GC log file rotation related jvm arguments cannot be used anymore

2020-07-27 Thread Jira 


 [ 
https://issues.apache.org/jira/browse/HIVE-23938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

László Bodor updated HIVE-23938:

Description: 
https://github.com/apache/hive/blob/master/llap-server/bin/runLlapDaemon.sh#L55
{code}
JAVA_OPTS_BASE="-server -Djava.net.preferIPv4Stack=true -XX:+UseNUMA 
-XX:+PrintGCDetails -verbose:gc -XX:+UseGCLogFileRotation 
-XX:NumberOfGCLogFiles=4 -XX:GCLogFileSize=100M -XX:+PrintGCDateStamps"
{code}

on JDK11 I got something like:
{code}
+ exec /usr/lib/jvm/jre-11-openjdk/bin/java -Dproc_llapdaemon -Xms32000m 
-Xmx64000m -Dhttp.maxConnections=17 -XX:+UseG1GC -XX:+ResizeTLAB -XX:+UseNUMA 
-XX:+AggressiveOpts -XX:MetaspaceSize=1024m 
-XX:InitiatingHeapOccupancyPercent=80 -XX:MaxGCPauseMillis=200 
-XX:+PreserveFramePointer -XX:AllocatePrefetchStyle=2 -Dhttp.maxConnections=10 
-Dasync.profiler.home=/grid/0/async-profiler -server 
-Djava.net.preferIPv4Stack=true -XX:+UseNUMA -XX:+PrintGCDetails -verbose:gc 
-XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=4 -XX:GCLogFileSize=100M 
-XX:+PrintGCDateStamps 
-Xloggc:/grid/2/yarn/container-logs/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/gc_2020-07-27-12.log
 
-Djava.io.tmpdir=/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/tmp/
 -Dlog4j.configurationFile= 
-Dllap.daemon.log.dir=/grid/2/yarn/container-logs/application_1595375468459_0113/container_e26_1595375468459_0113_01_09
 
-Dllap.daemon.log.file=llap-daemon-lbodor-ctr-e141-1563959304486-69251-01-11.hwx.site.log
 -Dllap.daemon.root.logger=query-routing -Dllap.daemon.log.level=INFO 
-classpath 
'/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib/conf/:/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib//lib/*:/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib//lib/tez/*:/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/lib//lib/udfs/*:.:'
 org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon
OpenJDK 64-Bit Server VM warning: Option AggressiveOpts was deprecated in 
version 11.0 and will likely be removed in a future release.
Unrecognized VM option 'UseGCLogFileRotation'
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
{code}

> LLAP: JDK11 - some GC log file rotation related jvm arguments cannot be used 
> anymore
> 
>
> Key: HIVE-23938
> URL: https://issues.apache.org/jira/browse/HIVE-23938
> Project: Hive
>  Issue Type: Improvement
>Reporter: László Bodor
>Assignee: László Bodor
>Priority: Major
>
> https://github.com/apache/hive/blob/master/llap-server/bin/runLlapDaemon.sh#L55
> {code}
> JAVA_OPTS_BASE="-server -Djava.net.preferIPv4Stack=true -XX:+UseNUMA 
> -XX:+PrintGCDetails -verbose:gc -XX:+UseGCLogFileRotation 
> -XX:NumberOfGCLogFiles=4 -XX:GCLogFileSize=100M -XX:+PrintGCDateStamps"
> {code}
> on JDK11 I got something like:
> {code}
> + exec /usr/lib/jvm/jre-11-openjdk/bin/java -Dproc_llapdaemon -Xms32000m 
> -Xmx64000m -Dhttp.maxConnections=17 -XX:+UseG1GC -XX:+ResizeTLAB -XX:+UseNUMA 
> -XX:+AggressiveOpts -XX:MetaspaceSize=1024m 
> -XX:InitiatingHeapOccupancyPercent=80 -XX:MaxGCPauseMillis=200 
> -XX:+PreserveFramePointer -XX:AllocatePrefetchStyle=2 
> -Dhttp.maxConnections=10 -Dasync.profiler.home=/grid/0/async-profiler -server 
> -Djava.net.preferIPv4Stack=true -XX:+UseNUMA -XX:+PrintGCDetails -verbose:gc 
> -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=4 -XX:GCLogFileSize=100M 
> -XX:+PrintGCDateStamps 
> -Xloggc:/grid/2/yarn/container-logs/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/gc_2020-07-27-12.log
>  
> -Djava.io.tmpdir=/grid/ssd/yarn/nm/usercache/lbodor/appcache/application_1595375468459_0113/container_e26_1595375468459_0113_01_09/tmp/
>  -Dlog4j.configurationFile= 
> -Dllap.daemon.log.dir=/grid/2/yarn/container-logs/application_1595375468459_0113/container_e26_1595375468459_0113_01_09
>  
> -Dllap.daemon.log.file=llap-daemon-lbodor-ctr-e141-1563959304486-69251-01-11.hwx.site.log
>  -Dllap.daemon.root.logger=query-routing -Dllap.daemon.log.level=INFO 
> -classpath 
>