<p dir="auto"><strong>Elasticsearch version</strong>: 5.0.0-alpha1</p>
<p dir="auto"><strong>JVM version</strong>: 1.8.0_51</p>
<p dir="auto"><strong>OS version</strong>: CentOS 6.6</p>
<p dir="auto"><strong>Description of the problem including expected versus actual behavior</strong>:<br>
I try to install elasticsearch plugin such as elasticsearch-head and elasticsearch-kopf. The example below occurs on both elasticsearch-head and elasticsearch-kopf.</p>
<p dir="auto">I run <code class="notranslate">./bin/elasticsearch-plugin install mobz/elasticsearch-head</code>, and I got MalformedURLException: no protocol. It seems that elasticsearch-5.0.0-alpha1 asking for full URL.</p>
<p dir="auto">If I supply another full URL to install:<br>
<code class="notranslate">./bin/elasticsearch-plugin install https://github.com/mobz/elasticsearch-head</code><br>
I got this error message:<br>
<code class="notranslate">ERROR: </code>elasticsearch<code class="notranslate"> directory is missing in the plugin zip</code></p>
<p dir="auto">Looks like there are some changes in the elasticsearch plugin module. Is this a bug or expected behavior? Does the package require specific folder or specific stuffs to be compatible to elasticsearch-5.0.0-alpha1?</p>
<p dir="auto">Thanks!</p>
<p dir="auto">I was playing around with master last night in a distributed set up<br>
with two servers and replicas = 0, while running queries on 50<br>
threads.</p>
<p dir="auto">When I ran similar tests with replicas=1, I didn't have any issues. I<br>
plan to use replicas=1 in the real world and this testing was just for<br>
performance numbers.</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="One test that I ran was adding a new node. While this was occurring, I
saw large swaths of exceptions for queries that look like this:
http://gist.github.com/551622

These appear to be failures related to the shard reallocating."><pre class="notranslate"><code class="notranslate">One test that I ran was adding a new node. While this was occurring, I
saw large swaths of exceptions for queries that look like this:
http://gist.github.com/551622

These appear to be failures related to the shard reallocating.
</code></pre></div>