You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by "Jeff Zhang (JIRA)" <ji...@apache.org> on 2016/07/15 06:18:20 UTC

[jira] [Created] (ZEPPELIN-1185) ZEPPELIN_INTP_JAVA_OPTS should not use ZEPPELIN_JAVA_OPTS as default value

Jeff Zhang created ZEPPELIN-1185:
------------------------------------

             Summary: ZEPPELIN_INTP_JAVA_OPTS should not use ZEPPELIN_JAVA_OPTS as default value
                 Key: ZEPPELIN-1185
                 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1185
             Project: Zeppelin
          Issue Type: Improvement
          Components: Core
    Affects Versions: 0.6.0
            Reporter: Jeff Zhang
            Priority: Minor


For now, if ZEPPELIN_INTP_JAVA_OPTS is not defined it would use ZEPPELIN_JAVA_OPTS. I don't think it make sense to do that implicitly as it may not be the user intend to do.  If user want to specify custom java opts for interpreter process, then let them do it by himself.  

Besides this introduce some unexpected behavior, e.g. I set ZEPPELIN_JAVA_OPTS as following to remote debug, but this setting will also apply to the remote interpreter process which cause it hang there. 

{code}
export ZEPPELIN_JAVA_OPTS="-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=5005"
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)