[
https://issues.apache.org/jira/browse/BIGTOP-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13244765#comment-13244765
]
Patrick Taylor Ramsey commented on BIGTOP-502:
----------------------------------------------
Is there a reason that we're defaulting to a fixed string instead of somehow
"cleaning up" the hostname (ie, by replacing the dots with dashes, or cut -d.
-f1)?
> Flume NG init script should pass --name "agent" instead of --name "<hostname>"
> ------------------------------------------------------------------------------
>
> Key: BIGTOP-502
> URL: https://issues.apache.org/jira/browse/BIGTOP-502
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.3.0, 0.4.0
> Environment: [CentOS 5.7 64-bit]
> Reporter: Will McQueen
> Assignee: Bruno Mahé
> Priority: Critical
> Fix For: 0.4.0
>
> Attachments: BIGTOP-502.patch
>
>
> The /etc/init.d/flume-ng-node init script currently passes this option:
> --name <hostname>
> ...to /usr/bin/flume-ng, but the option needs to be a constant name, "agent"
> (literally, w/o quotes), like this:
> --name agent
> The reason is because Flume NG currently can't properly parse a dot-separated
> hostname because dots are used as namepace delimiters. So instead we should
> probably hardcode it to the name "agent" as the default name of the agent
> (while still retaining the ability to specify a different node by specifying
> the FLUME_NODE_NAME).
> Thank you.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
