ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jaimin D Jetly (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-13239) Incomplete REST API implementation for Flume.
Date Fri, 11 Dec 2015 22:29:46 GMT

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

Jaimin D Jetly commented on AMBARI-13239:
-----------------------------------------

[~colmanmadden]
Ambari does support Flume Agent controls (Stop and Start) from Flume summary page. Using these
controls, Flume agent can be individually stopped/started.
I am attaching the snapshot of these controls that I am referring to this ticket. [^Flume
Agent Controls.png]


> Incomplete REST API implementation for Flume.
> ---------------------------------------------
>
>                 Key: AMBARI-13239
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13239
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0
>         Environment: CENTOS 6.7, Hortonworks HDP 2.3
>            Reporter: Colman Madden
>            Priority: Blocker
>              Labels: features
>             Fix For: 2.2.0
>
>         Attachments: Flume Agent Controls.png
>
>
> There is no REST API functionality available for the stopping and starting of Individual
Flume Agents, Currently it requires the Flume service as a whole to be stopped/started.
> Also no functionality available to flush a new flume config to disk without restarting
the whole flume service (every agent on every host)



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

Mime
View raw message