# Gce plugin configuration as command arguments **URL:** \ **Category:** Elasticsearch\ **Created:** [September 23, 2016, 11:28am UTC](https://discuss.elastic.co/t/gce-plugin-configuration-as-command-arguments/61376 "2016-09-23T11:28:54Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![zozo6015](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zozo6015/32/12117_2.png) [@zozo6015](https://discuss.elastic.co/u/zozo6015)\ **Post date:** [September 23, 2016, 11:28am UTC](https://discuss.elastic.co/t/gce-plugin-configuration-as-command-arguments/61376/1 "2016-09-23T11:28:54Z")
Hello, For various reasons I have to run multiple elasticsearch cluster instances within the same boxes therefore I spin up each cluster as a command line with configurable arguments. I need to configure the gce plugin for autodiscovery. Any suggestion how to do that? Thanks in advance. Peter ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [September 23, 2016, 1:02pm UTC](https://discuss.elastic.co/t/gce-plugin-configuration-as-command-arguments/61376/2 "2016-09-23T13:02:08Z")
You can't really do that. GCE plugin expects only one machine running. Related: [https://www.elastic.co/guide/en/elasticsearch/plugins/current/cloud-gce-usage-discovery-port.html](https://www.elastic.co/guide/en/elasticsearch/plugins/current/cloud-gce-usage-discovery-port.html) ---
**Author:** ![zozo6015](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zozo6015/32/12117_2.png) [@zozo6015](https://discuss.elastic.co/u/zozo6015)\ **Post date:** [September 23, 2016, 1:43pm UTC](https://discuss.elastic.co/t/gce-plugin-configuration-as-command-arguments/61376/3 "2016-09-23T13:43:05Z")
Thanks, I actually find out that the issue I am having is not related to autodiscovery. For some reason I have a number of unallocated shards. Since at the first glance all the unallocated shards were from the same nodes I assumed that the autodiscovery is not working. Now I need to figure out how to fix the unallocated shards thing. If I set the number of replicas to 0 that mean no replication then there are no unallocated shards but as soon as I increase the number of replications the unallocated shards would pop up. Any suggestions? ---
**Author:** ![MarkOStewart](https://avatars.discourse-cdn.com/v4/letter/m/898d66/32.png) [@MarkOStewart](https://discuss.elastic.co/u/MarkOStewart)\ **Post date:** [September 23, 2016, 2:09pm UTC](https://discuss.elastic.co/t/gce-plugin-configuration-as-command-arguments/61376/4 "2016-09-23T14:09:47Z")
Do you have more than one data node? if not you will always have a yellow condition as the replica cannot be on the same node as data? I had that same problem when I first started learning Elasticsearch with a one node cluster. ---
**Author:** ![zozo6015](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zozo6015/32/12117_2.png) [@zozo6015](https://discuss.elastic.co/u/zozo6015)\ **Post date:** [September 23, 2016, 2:14pm UTC](https://discuss.elastic.co/t/gce-plugin-configuration-as-command-arguments/61376/5 "2016-09-23T14:14:25Z")
I am running a 3 node cluster, I do not specify the number of the data nodes. Therefore I am assuming that all the nodes are data nodes. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 10:17pm UTC](https://discuss.elastic.co/t/gce-plugin-configuration-as-command-arguments/61376/6 "2017-07-05T22:17:42Z")
Closed on July 5, 2017, 10:17pm UTC