You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@iotdb.apache.org by "Xiangdong Huang (Jira)" <ji...@apache.org> on 2019/12/31 12:00:06 UTC
[jira] [Commented] (IOTDB-397) printGC JVM parameter is not enabled
because of a bug in iotdb-env.sh
[ https://issues.apache.org/jira/browse/IOTDB-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17006068#comment-17006068 ]
Xiangdong Huang commented on IOTDB-397:
---------------------------------------
enable_gc.patch can be used for 0.8.x and 0.9.0 and 0.9.1.
> printGC JVM parameter is not enabled because of a bug in iotdb-env.sh
> ----------------------------------------------------------------------
>
> Key: IOTDB-397
> URL: https://issues.apache.org/jira/browse/IOTDB-397
> Project: Apache IoTDB
> Issue Type: Bug
> Affects Versions: 0.8.0, 0.9.0, 0.9.1, 0.8.1, 0.8.2
> Reporter: Xiangdong Huang
> Priority: Major
> Labels: pull-request-available
> Attachments: enable_gc.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Current though we set the printGC parameter, but we forgot to enable it..
> i.e., in iotdb-env.sh, though we set:
> IOTDB_JMX_OPTS="$IOTDB_JMX_OPTS -Xloggc:${IOTDB_HOME}/gc.log"
> , but latter, in line 153 and line 156, we set:
> IOTDB_JMX_OPTS="-Diotdb.jmx.local.port=$JMX_PORT"
> , which cleans all setting before...
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)