[
https://issues.apache.org/jira/browse/METRON-636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15798772#comment-15798772
]
ASF GitHub Bot commented on METRON-636:
---------------------------------------
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.
> Capture memory and cpu details as a part of platform-info script
> ----------------------------------------------------------------
>
> Key: METRON-636
> URL: https://issues.apache.org/jira/browse/METRON-636
> Project: Metron
> Issue Type: Improvement
> Affects Versions: 0.3.0
> Reporter: Anand Subramanian
> Assignee: Anand Subramanian
> Priority: Minor
>
> The platform-info.sh script currently does not capture the system memory
> footprints.
> Many issues reported by users when deploying quick dev or full dev single
> node deployments are due to system constraints (low memory for e.g.). It
> would be good to enhance the platform-info script so that it can ease out
> finding potential resource issues.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
