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
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
I posted an issue with Elastic HQ here:
https://github.com/royrusso/elasticsearch-HQ/issues/164
But just in case maybe an Elastic dev can have a look and see if it's
Elasticsearch issue or not.
Thanks
--
You received this message because you are subscribed to the Google Groups
elasticsearch
I posted an issue with Elastic HQ
here: https://github.com/royrusso/elasticsearch-HQ/issues/164
But just in case maybe an Elastic dev can have a look and see if it's
Elasticsearch issue or not.
Thanks
--
You received this message because you are subscribed to the Google Groups
elasticsearch
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 :)
Regards,
Mark Walkom
Infrastructure Engineer
Campaign Monitor
email: ma...@campaignmonitor.com
web: www.campaignmonitor.com
On 27 August
