Github user nickwallen commented on the issue:
https://github.com/apache/incubator-metron/pull/400
Hi @anandsubbu - Under what scenarios do you think this additional
information would help?
The script was primarily made to capture 'static' bits of platform
information that might prevent a successful build or deployment of Metron.
The changes you have made have added some 'dynamic' bits; aka CPU, memory.
For these changes to help, the script would have to be run exactly when there
are high CPU/memory conditions. I don't know if this is possible.
What I have seen happen is that the guest OS maxes out memory and starts
harvesting/killing processes. This effectively kills some service needed by
Metron and prevents Metron from working. But once the processes are killed,
the memory use drops. So if I am having problems with Metron and run the
script it is just as likely to report no memory problems, even though it was
actually the lack of memory that caused the problem.
Maybe I am thinking about the use case wrong here. Please correct me if
you disagree.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
