Is there any reason why NodesInfo response (JSON, REST) contains only a
fraction of data under 'os' section? I have seen response where it
contained only 'refresh_interval' value. cpu, mem and swap were gone. What
might have caused this?
Is there any reason why NodesInfo response (JSON, REST) contains only a
fraction of data under 'os' section? I have seen response where it
contained only 'refresh_interval' value. cpu, mem and swap were gone. What
might have caused this?
Can we test using any log level/package setup that the sigar is found and
loaded? Because the sigar libs were there so may be they were not loaded
for some reason.
On Mon, Apr 2, 2012 at 4:38 PM, Shay Banon kimchy@gmail.com wrote:
If sigar is not available, then just the refersh_interval will be filled.
Is there any reason why NodesInfo response (JSON, REST) contains only a
fraction of data under 'os' section? I have seen response where it
contained only 'refresh_interval' value. cpu, mem and swap were gone. What
might have caused this?
Can we test using any log level/package setup that the sigar is found and
loaded? Because the sigar libs were there so may be they were not loaded
for some reason.
On Mon, Apr 2, 2012 at 4:38 PM, Shay Banon kimchy@gmail.com wrote:
If sigar is not available, then just the refersh_interval will be filled.
Is there any reason why NodesInfo response (JSON, REST) contains only a
fraction of data under 'os' section? I have seen response where it
contained only 'refresh_interval' value. cpu, mem and swap were gone. What
might have caused this?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.