1- The vendor info for client nodes is not returned. I assume that HQ is
using standard REST interface and Elasticsearch not returning the info
(Maybe its a Windows SIGAR/Permission issue ???). I posted the response
JSon with the bug.
2- HQ doesn't handle gracefully the fact that the info is not returned.
(It's throwing JavaScript exception, but nothing shows up on the screen so
you think it's "frozen", when it's not)
On Tuesday, 26 August 2014 19:06:35 UTC-4, Mark Walkom wrote:
ElasticHQ is a community plugin, the ES devs can't help here.
I have raised issues against ElasticHQ in the past and Roy has fixed them
pretty quickly
Development seems to have stalled on ElasticHQ for whatever reason, but
look at the various forks, several people have fixed bugs, including
perhaps the one you're running into.
On Wednesday, August 27, 2014 10:27:41 AM UTC-4, John Smith wrote:
I know, but i think it's 2 issues...
1- The vendor info for client nodes is not returned. I assume that HQ is
using standard REST interface and Elasticsearch not returning the info
(Maybe its a Windows SIGAR/Permission issue ???). I posted the response
JSon with the bug.
2- HQ doesn't handle gracefully the fact that the info is not returned.
(It's throwing JavaScript exception, but nothing shows up on the screen so
you think it's "frozen", when it's not)
On Tuesday, 26 August 2014 19:06:35 UTC-4, Mark Walkom wrote:
ElasticHQ is a community plugin, the ES devs can't help here.
I have raised issues against ElasticHQ in the past and Roy has fixed them
pretty quickly
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.