Thanks... I ruled out the scripting part, issued the following and got a 
response:

ubuntu@graylog:~$ curl -XPOST 'host:9200/_cluster/reroute' -d '{
>     "commands" : [ {
>        "allocate" : {
>           "index" : "graylog_0",
>           "shard" : "0",
>           "node" : "Atum",
>           "allow_primary" : true
>         }
>       }
>     ]
>   }'
{"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"[allocate]
 
allocation of [graylog_0][0] on node 
{Atum}{U6oodK5vRpeql3-Ld5py6g}{ipaddr}{ipaddr:9300} is not allowed, reason: 
[YES(node passes include/exclude/require filters)][YES(shard not primary or 
relocation disabled)][YES(primary is already active)][YES(below shard 
recovery limit of [2])][YES(only a single data node is present)][YES(total 
shard limit disabled: [index: -1, cluster: -1] <= 0)][YES(allocation 
disabling is ignored)][YES(target node version [2.3.1] is same or newer 
than source node version [2.3.1])][YES(no allocation awareness 
enabled)][NO(shard cannot be allocated on same node 
[U6oodK5vRpeql3-Ld5py6g] it already exists on)][YES(allocation disabling is 
ignored)]"}],"type":"illegal_argument_exception","reason":"[allocate] 
allocation of [graylog_0][0] on node 
{Atum}{U6oodK5vRpeql3-Ld5py6g}{ipaddr}{ipaddr:9300} is not allowed, reason: 
[YES(node passes include/exclude/require filters)][YES(shard not primary or 
relocation disabled)][YES(primary is already active)][YES(below shard 
recovery limit of [2])][YES(only a single data node is present)][YES(total 
shard limit disabled: [index: -1, cluster: -1] <= 0)][YES(allocation 
disabling is ignored)][YES(target node version [2.3.1] is same or newer 
than source node version [2.3.1])][YES(no allocation awareness 
enabled)][NO(shard cannot be allocated on same node 
[U6oodK5vRpeql3-Ld5py6g] it already exists on)][YES(allocation disabling is 
ignored)]"},"status":400}ubuntu@graylog:~$

Thanks






On Thursday, August 25, 2016 at 12:45:57 PM UTC-4, Obie wrote:
>
> Hello,
>
> I'm running the VMware OVF and the root partition filled. I increased it 
> and all services start properly, but now all Elasticsearch shards are 
> unassigned.
>
>   Elasticsearch cluster is yellow. Shards: 12 active, 0 initializing, 0
>  relocating, 12 unassigned, What does this mean? 
> <http://docs.graylog.org/en/2.0/pages/configuring_es.html#cluster-status-explained>
>
> I read a post about deleting the alias deflector target but am not sure 
> how to do this, nor am I sure if this is the recommended fix.
>
> Any guidance?
>
> Thanks
>

-- 
You received this message because you are subscribed to the Google Groups 
"Graylog Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/graylog2/4a213d1b-2199-4a27-948a-c8f0870c9b90%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to