You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flume.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/11/20 04:15:34 UTC

[jira] [Commented] (FLUME-1594) Document JMX options

    [ https://issues.apache.org/jira/browse/FLUME-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14218929#comment-14218929 ] 

ASF subversion and git services commented on FLUME-1594:
--------------------------------------------------------

Commit 35de8ff18d096bd41caf3dabbcadc70b7d90ac40 in flume's branch refs/heads/trunk from [~roshan_naik]
[ https://git-wip-us.apache.org/repos/asf?p=flume.git;h=35de8ff ]

FLUME-1594. Document JMX options

(Ashish Paliwal via Roshan Naik)


> Document JMX options
> --------------------
>
>                 Key: FLUME-1594
>                 URL: https://issues.apache.org/jira/browse/FLUME-1594
>             Project: Flume
>          Issue Type: Documentation
>          Components: Configuration
>    Affects Versions: v1.3.0, v1.4.0
>            Reporter: Will McQueen
>            Assignee: Ashish Paliwal
>         Attachments: FLUME-1594-0.patch
>
>
> We should add to the Flume User Guide a section on how to enable JMX, and a sample using JConsole. We can reference this link in the docs too:
>      http://docs.oracle.com/javase/6/docs/technotes/guides/management/agent.html
> The following sample JVM args (set in flume-env.sh) allow me to successfully use JConsole to monitor a remove Flume agent:
>      JAVA_OPTS="-Xms1024m -Xmx1024m -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=5445 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false"



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