<p dir="auto"><strong>Elasticsearch version</strong>:<br>
1.7.5</p>
<p dir="auto"><strong>JVM version</strong>:<br>
1.8.0_40-64</p>
<p dir="auto"><strong>OS version</strong>:<br>
centos6</p>
<p dir="auto"><strong>Description of the problem including expected versus actual behavior</strong>:<br>
The current merge count is different between _cat/nodes and _stats/merges.  We show multiple merges being performed on the _cat/nodes api, however, _stats/merges shows no merges being performed for any index.  We are not sure what is the true merge activity on the cluster.  Also, is there a way to see what shards are bing merged?</p>
<p dir="auto"><a target="_blank" rel="noopener noreferrer nofollow" href="https://cloud.githubusercontent.com/assets/6633418/14191693/f8057626-f75e-11e5-9a62-10c0c76de164.png"><img src="https://cloud.githubusercontent.com/assets/6633418/14191693/f8057626-f75e-11e5-9a62-10c0c76de164.png" alt="cat-nodes" style="max-width: 100%;"></a><br>
<a target="_blank" rel="noopener noreferrer nofollow" href="https://cloud.githubusercontent.com/assets/6633418/14191712/0a9e1cf2-f75f-11e5-85f9-27187f099f09.png"><img src="https://cloud.githubusercontent.com/assets/6633418/14191712/0a9e1cf2-f75f-11e5-85f9-27187f099f09.png" alt="stats-merges" style="max-width: 100%;"></a></p>
<p dir="auto"><strong>Steps to reproduce</strong>:<br>
We are not sure how the cluster gets into this state.  We have experienced this multiple times.  We have not found a way to clear what we think are stuck merges without bouncing the nodes.</p>
<p dir="auto"><strong>Provide logs (if relevant)</strong>:</p>
<p dir="auto">Marvel Sense is not working over ssl, it hangs when it tried to connect to the elasticsearch API.The rest of Marvel seems to be working fine, as does the elasticsearch API if called directly.</p>
<p dir="auto">I am using a freshly installed elasticsearch 1.4.1 and the latest Marvel.</p>
<p dir="auto">Elasticsearch is exposed on the internet over SSL as <a href="https://mydomain/" rel="nofollow">https://mydomain/</a>.</p>
<p dir="auto">When I profile the javascript in the browser, I can see that Marvel Sense actually tries to make the calls to the API over http, even though the API and Marval are using https. My Elasticsearch installation is not available over the internet to anything other than https. I have nginx installed, which passes the elasticsearch calls from 443 to 9200. Again this all works fine when calling the Elasticsearch API or the plugins etc.</p>
<p dir="auto">Marvel Sense ignores the url that is in the config file (plugins/marvel/_site/kibana/config.js). It goes to http even if I hardcode the elasticsearch with a https prefix.</p>