Github user anandsubbu commented on the issue:
https://github.com/apache/metron/pull/1132
> Please document the lifecycle for how pcap.properties is updated in the
README. It should be clear to users that they will need to restart parsers for
the changes to take effect after the initial install is performed. Can you
confirm, is that the way the properties are/will be deployed with this PR
@anandsubbu?
Hi @mmiklavc - there is no change in behavior from earlier to now. Nothing
changes from a usage perspective. Let me clarify more with an example for a
multi-node deployment...
**Earlier**
* User deploys metron
* `pcap.properties` file created with defaults under `$METRON_HOME/config`
* User hand edits the properties file (sets ZK quorum and other parameters
as required)
* Starts the topology per the instructions
[here](https://github.com/apache/metron/tree/master/metron-platform/metron-pcap-backend#starting-the-topology).
**Now**
* During deploy time, user is presented with a separate config tab in
Ambari to configure/reconfigure PCAP properties. If user chooses to leave them
untouched, the pcap.properties is initialized with appropriate defaults. ZK
quorum is auto-populated as well.
* `pcap.properties` file is created during metron-parsers startup step.
* Starts the topology per the instructions
[here](https://github.com/apache/metron/tree/master/metron-platform/metron-pcap-backend#starting-the-topology).
The steps in the
[README](https://github.com/apache/metron/tree/master/metron-platform/metron-pcap-backend)
still holds.
Now, we can add a note in the README to indicate that the PCAP properties
can be configured via the 'PCAP' tab in Ambari Metron config. But I noticed
this was not explicitly mentioned for other components (e.g.
[REST](https://github.com/apache/metron/tree/master/metron-interface/metron-rest#configuration),
[elasticsearch](https://github.com/apache/metron/tree/master/metron-platform/metron-elasticsearch#properties)).
Let me know if you prefer to have this added.
---
