metron-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (METRON-1695) Expose pcap properties through Ambari
Date Thu, 04 Oct 2018 16:04:00 GMT


ASF GitHub Bot commented on METRON-1695:

Github user anandsubbu commented on the issue:
    Thanks much @nickwallen for giving it another spin!
    Hey @MohanDV , let me know if my below explanation makes sense. @nickwallen , would you
have any thoughts on this?
    > @MohanDV , as a part of my commit, I have moved all the UI related elements from
REST to the PCAP config tab.
    > In my understanding, the following parameters are not directly related to the PCAP
core service, but are functionally related to REST (used by the PCAP query panel UI):
    > * pdml.script.path
    > * base.path
    > * base.interim.result.path
    > * final.output.path
    > * page.size
    > * yarn.queue
    > * finalizer.threadpool.size
    > For this reason, I did not move these properties out of the rest_application.yml.
    > > @MohanDV Changing a REST Setting triggers Ambari to Restart PCAP Topology
    > With my current changes, modifying any config setting in the PCAP tab will require
restarting both Metron PCAP and Metron REST services--which is necessary since user can change
a PCAP-service related property or a PCAP-REST related property (or both). The converse, which
you noted, i.e. changing any REST config does not require restarting the PCAP topology. Here's
a screenshot after making changes to REST config...
    > ![image](

> Expose pcap properties through Ambari
> -------------------------------------
>                 Key: METRON-1695
>                 URL:
>             Project: Metron
>          Issue Type: Bug
>            Reporter: Anand Subramanian
>            Assignee: Anand Subramanian
>            Priority: Major
> Currently, the $METRON_HOME/config/ file is hardcoded with the defaults.
One has to hand edit the file before deploying the PCAP topology. These properties should be
configurable via Ambari.

This message was sent by Atlassian JIRA

View raw message