# New install of elasticsearch (on Lion), status red, unassigned\_shards, nothing in the logs
**URL:** https://discuss.elastic.co/t/new-install-of-elasticsearch-on-lion-status-red-unassigned-shards-nothing-in-the-logs/5989
**Category:** Elasticsearch
**Created:** [November 28, 2011, 11:01am UTC](https://discuss.elastic.co/t/new-install-of-elasticsearch-on-lion-status-red-unassigned-shards-nothing-in-the-logs/5989 "2011-11-28T11:01:39Z")
**Posts on this page:** 12
**Page:** 1
### Author:  [@doug\_livesey](https://discuss.elastic.co/u/doug_livesey)
#### Post date: [November 28, 2011, 11:01am UTC](https://discuss.elastic.co/t/new-install-of-elasticsearch-on-lion-status-red-unassigned-shards-nothing-in-the-logs/5989/1 "2011-11-28T11:01:39Z")
Hi -- I have a new install of elasticsearch on my dev machine after
upgrading to OSX Lion.
Now, when I try to start elasticsearch, and check the cluster health, I get
this:
{
"cluster\_name" : "elasticsearch",
"status" : "red",
"timed\_out" : false,
"number\_of\_nodes" : 2,
"number\_of\_data\_nodes" : 2,
"active\_primary\_shards" : 7,
"active\_shards" : 14,
"relocating\_shards" : 0,
"initializing\_shards" : 0,
"unassigned\_shards" : 6
}
It stays at these values indefinitely. I've looked in the logs, but there's
no hint of any errors in there.
Can anyone offer any advice as to how to investigate this further?
It's the basic elasticsearch install started up with bin/elasticsearch, so
should be working, as far as I can tell.
I guess, with my machine being upgraded to Lion, this could be a java issue?
But I'm rather out of my depth with java.
Incidentally, I tried to use my previous install of ES (0.17.5) to see if
that still worked, and that also had unassigned shards, but was typically
in status yellow.
Thanks,
Doug.
---
### Author:  [@kimchy](https://discuss.elastic.co/u/kimchy)
#### Post date: [November 28, 2011, 11:22am UTC](https://discuss.elastic.co/t/new-install-of-elasticsearch-on-lion-status-red-unassigned-shards-nothing-in-the-logs/5989/2 "2011-11-28T11:22:28Z")
Is that only your machine? There seems to be 2 nodes there, is that what
there should be? Its not a Java issue, more seems like a change in the data
location, or maybe something got deleted? Need more info as to the amount
of nodes in the cluster, and gist the cluster state.
On Mon, Nov 28, 2011 at 1:01 PM, doug livesey [biot023@gmail.com](mailto:biot023@gmail.com) wrote:
> Hi -- I have a new install of elasticsearch on my dev machine after
> upgrading to OSX Lion.
> Now, when I try to start elasticsearch, and check the cluster health, I
> get this:
>
> {
> "cluster\_name" : "elasticsearch",
> "status" : "red",
> "timed\_out" : false,
> "number\_of\_nodes" : 2,
> "number\_of\_data\_nodes" : 2,
> "active\_primary\_shards" : 7,
> "active\_shards" : 14,
> "relocating\_shards" : 0,
> "initializing\_shards" : 0,
> "unassigned\_shards" : 6
> }
>
> It stays at these values indefinitely. I've looked in the logs, but
> there's no hint of any errors in there.
> Can anyone offer any advice as to how to investigate this further?
> It's the basic elasticsearch install started up with bin/elasticsearch, so
> should be working, as far as I can tell.
> I guess, with my machine being upgraded to Lion, this could be a java
> issue?
> But I'm rather out of my depth with java.
> Incidentally, I tried to use my previous install of ES (0.17.5) to see if
> that still worked, and that also had unassigned shards, but was typically
> in status yellow.
> Thanks,
> Doug.
---
### Author:  [@doug\_livesey](https://discuss.elastic.co/u/doug_livesey)
#### Post date: [November 28, 2011, 12:40pm UTC](https://discuss.elastic.co/t/new-install-of-elasticsearch-on-lion-status-red-unassigned-shards-nothing-in-the-logs/5989/3 "2011-11-28T12:40:54Z")
Hi -- it's a new install of ES, configured to use the (new for this
install) data and log directories /var/data/elasticsearch-0.18.4/ and
/var/log/elasticsearch-0.18.4/
It also reported this same error when I first uncompressed the tarball and
ran it with the defaults.
I have had another version of ES on this machine (under Snow Leopard),
which used /var/data/elasticsearch/ and /var/log/elasticsearch/, but I
thought that the installs were self-contained, and therefore shouldn't
interfere with each other?
Maybe I could try a totally fresh install -- could anyone advise me on what
files to delete to achieve this? I thought it would just be the
elasticsearch directory, and any that I'd specified separately.
Thanks,
Doug.
On 28 November 2011 11:22, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote:
> Is that only your machine? There seems to be 2 nodes there, is that what
> there should be? Its not a Java issue, more seems like a change in the data
> location, or maybe something got deleted? Need more info as to the amount
> of nodes in the cluster, and gist the cluster state.
>
> On Mon, Nov 28, 2011 at 1:01 PM, doug livesey [biot023@gmail.com](mailto:biot023@gmail.com) wrote:
>
> > Hi -- I have a new install of elasticsearch on my dev machine after
> > upgrading to OSX Lion.
> > Now, when I try to start elasticsearch, and check the cluster health, I
> > get this:
> >
> > {
> > "cluster\_name" : "elasticsearch",
> > "status" : "red",
> > "timed\_out" : false,
> > "number\_of\_nodes" : 2,
> > "number\_of\_data\_nodes" : 2,
> > "active\_primary\_shards" : 7,
> > "active\_shards" : 14,
> > "relocating\_shards" : 0,
> > "initializing\_shards" : 0,
> > "unassigned\_shards" : 6
> > }
> >
> > It stays at these values indefinitely. I've looked in the logs, but
> > there's no hint of any errors in there.
> > Can anyone offer any advice as to how to investigate this further?
> > It's the basic elasticsearch install started up with bin/elasticsearch,
> > so should be working, as far as I can tell.
> > I guess, with my machine being upgraded to Lion, this could be a java
> > issue?
> > But I'm rather out of my depth with java.
> > Incidentally, I tried to use my previous install of ES (0.17.5) to see if
> > that still worked, and that also had unassigned shards, but was typically
> > in status yellow.
> > Thanks,
> > Doug.
---
### Author:  [@doug\_livesey](https://discuss.elastic.co/u/doug_livesey)
#### Post date: [November 28, 2011, 12:51pm UTC](https://discuss.elastic.co/t/new-install-of-elasticsearch-on-lion-status-red-unassigned-shards-nothing-in-the-logs/5989/4 "2011-11-28T12:51:00Z")
Hi -- I deleted all data and log files, and restarted my machine, and we
seem to be green, now.
I'm re-indexing all my items, and it seems to be running slower than it
did, but I'll keep an eye on that & make sure it is.
Thanks for the sanity check! 🙂
Doug.
On 28 November 2011 12:40, doug livesey [biot023@gmail.com](mailto:biot023@gmail.com) wrote:
> Hi -- it's a new install of ES, configured to use the (new for this
> install) data and log directories /var/data/elasticsearch-0.18.4/ and
> /var/log/elasticsearch-0.18.4/
> It also reported this same error when I first uncompressed the tarball and
> ran it with the defaults.
> I have had another version of ES on this machine (under Snow Leopard),
> which used /var/data/elasticsearch/ and /var/log/elasticsearch/, but I
> thought that the installs were self-contained, and therefore shouldn't
> interfere with each other?
> Maybe I could try a totally fresh install -- could anyone advise me on
> what files to delete to achieve this? I thought it would just be the
> elasticsearch directory, and any that I'd specified separately.
> Thanks,
> Doug.
>
> On 28 November 2011 11:22, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote:
>
> > Is that only your machine? There seems to be 2 nodes there, is that what
> > there should be? Its not a Java issue, more seems like a change in the data
> > location, or maybe something got deleted? Need more info as to the amount
> > of nodes in the cluster, and gist the cluster state.
> >
> > On Mon, Nov 28, 2011 at 1:01 PM, doug livesey [biot023@gmail.com](mailto:biot023@gmail.com) wrote:
> >
> > > Hi -- I have a new install of elasticsearch on my dev machine after
> > > upgrading to OSX Lion.
> > > Now, when I try to start elasticsearch, and check the cluster health, I
> > > get this:
> > >
> > > {
> > > "cluster\_name" : "elasticsearch",
> > > "status" : "red",
> > > "timed\_out" : false,
> > > "number\_of\_nodes" : 2,
> > > "number\_of\_data\_nodes" : 2,
> > > "active\_primary\_shards" : 7,
> > > "active\_shards" : 14,
> > > "relocating\_shards" : 0,
> > > "initializing\_shards" : 0,
> > > "unassigned\_shards" : 6
> > > }
> > >
> > > It stays at these values indefinitely. I've looked in the logs, but
> > > there's no hint of any errors in there.
> > > Can anyone offer any advice as to how to investigate this further?
> > > It's the basic elasticsearch install started up with bin/elasticsearch,
> > > so should be working, as far as I can tell.
> > > I guess, with my machine being upgraded to Lion, this could be a java
> > > issue?
> > > But I'm rather out of my depth with java.
> > > Incidentally, I tried to use my previous install of ES (0.17.5) to see
> > > if that still worked, and that also had unassigned shards, but was
> > > typically in status yellow.
> > > Thanks,
> > > Doug.
---
### Author:  [@kimchy](https://discuss.elastic.co/u/kimchy)
#### Post date: [November 28, 2011, 12:57pm UTC](https://discuss.elastic.co/t/new-install-of-elasticsearch-on-lion-status-red-unassigned-shards-nothing-in-the-logs/5989/5 "2011-11-28T12:57:45Z")
Something was still strange in your setup, since it reported that there
were two instances running, and I think, based on your feedback, that you
expect only one to run? Just do ps -ef | grep elasticsearch and check how
many instances you have...
On Mon, Nov 28, 2011 at 2:51 PM, doug livesey [biot023@gmail.com](mailto:biot023@gmail.com) wrote:
> Hi -- I deleted all data and log files, and restarted my machine, and we
> seem to be green, now.
> I'm re-indexing all my items, and it seems to be running slower than it
> did, but I'll keep an eye on that & make sure it is.
> Thanks for the sanity check! 🙂
> Doug.
>
> On 28 November 2011 12:40, doug livesey [biot023@gmail.com](mailto:biot023@gmail.com) wrote:
>
> > Hi -- it's a new install of ES, configured to use the (new for this
> > install) data and log directories /var/data/elasticsearch-0.18.4/ and
> > /var/log/elasticsearch-0.18.4/
> > It also reported this same error when I first uncompressed the tarball
> > and ran it with the defaults.
> > I have had another version of ES on this machine (under Snow Leopard),
> > which used /var/data/elasticsearch/ and /var/log/elasticsearch/, but I
> > thought that the installs were self-contained, and therefore shouldn't
> > interfere with each other?
> > Maybe I could try a totally fresh install -- could anyone advise me on
> > what files to delete to achieve this? I thought it would just be the
> > elasticsearch directory, and any that I'd specified separately.
> > Thanks,
> > Doug.
> >
> > On 28 November 2011 11:22, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote:
> >
> > > Is that only your machine? There seems to be 2 nodes there, is that what
> > > there should be? Its not a Java issue, more seems like a change in the data
> > > location, or maybe something got deleted? Need more info as to the amount
> > > of nodes in the cluster, and gist the cluster state.
> > >
> > > On Mon, Nov 28, 2011 at 1:01 PM, doug livesey [biot023@gmail.com](mailto:biot023@gmail.com) wrote:
> > >
> > > > Hi -- I have a new install of elasticsearch on my dev machine after
> > > > upgrading to OSX Lion.
> > > > Now, when I try to start elasticsearch, and check the cluster health, I
> > > > get this:
> > > >
> > > > {
> > > > "cluster\_name" : "elasticsearch",
> > > > "status" : "red",
> > > > "timed\_out" : false,
> > > > "number\_of\_nodes" : 2,
> > > > "number\_of\_data\_nodes" : 2,
> > > > "active\_primary\_shards" : 7,
> > > > "active\_shards" : 14,
> > > > "relocating\_shards" : 0,
> > > > "initializing\_shards" : 0,
> > > > "unassigned\_shards" : 6
> > > > }
> > > >
> > > > It stays at these values indefinitely. I've looked in the logs, but
> > > > there's no hint of any errors in there.
> > > > Can anyone offer any advice as to how to investigate this further?
> > > > It's the basic elasticsearch install started up with bin/elasticsearch,
> > > > so should be working, as far as I can tell.
> > > > I guess, with my machine being upgraded to Lion, this could be a java
> > > > issue?
> > > > But I'm rather out of my depth with java.
> > > > Incidentally, I tried to use my previous install of ES (0.17.5) to see
> > > > if that still worked, and that also had unassigned shards, but was
> > > > typically in status yellow.
> > > > Thanks,
> > > > Doug.
---
### Author:  [@doug\_livesey](https://discuss.elastic.co/u/doug_livesey)
#### Post date: [November 28, 2011, 1:30pm UTC](https://discuss.elastic.co/t/new-install-of-elasticsearch-on-lion-status-red-unassigned-shards-nothing-in-the-logs/5989/6 "2011-11-28T13:30:12Z")
Yeah, something's up -- it's being very slow.
I get this with ps:
$ ps aux | grep elastic
douglivesey 340 0.1 3.8 3765632 318788 s000 S+ 12:45pm
1:05.07 /usr/bin/java -Xms256m -Xmx1g -Xss128k -XX:+UseParNewGC
-XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -XX:SurvivorRatio=8
-XX:MaxTenuringThreshold=1 -XX:CMSInitiatingOccupancyFraction=75
-XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError
-Delasticsearch -Des.path.home=/Users/douglivesey/bin/elasticsearch-0.18.4
-Des-foreground=yes -cp
:/Users/douglivesey/bin/elasticsearch-0.18.4/lib/_:/Users/douglivesey/bin/elasticsearch-0.18.4/lib/sigar/_
org.elasticsearch.bootstrap.Elasticsearch
And the health report is:
{
"cluster\_name" : "elasticsearch",
"status" : "green",
"timed\_out" : false,
"number\_of\_nodes" : 2,
"number\_of\_data\_nodes" : 2,
"active\_primary\_shards" : 10,
"active\_shards" : 20,
"relocating\_shards" : 0,
"initializing\_shards" : 0,
"unassigned\_shards" : 0
}
Which is green, but (as you say) seems to think that I have 2 nodes.
Is there something I can do in the config to stop this? I've not explicitly
set any node counts.
On 28 November 2011 12:57, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote:
> Something was still strange in your setup, since it reported that there
> were two instances running, and I think, based on your feedback, that you
> expect only one to run? Just do ps -ef | grep elasticsearch and check how
> many instances you have...
>
> On Mon, Nov 28, 2011 at 2:51 PM, doug livesey [biot023@gmail.com](mailto:biot023@gmail.com) wrote:
>
> > Hi -- I deleted all data and log files, and restarted my machine, and we
> > seem to be green, now.
> > I'm re-indexing all my items, and it seems to be running slower than it
> > did, but I'll keep an eye on that & make sure it is.
> > Thanks for the sanity check! 🙂
> > Doug.
> >
> > On 28 November 2011 12:40, doug livesey [biot023@gmail.com](mailto:biot023@gmail.com) wrote:
> >
> > > Hi -- it's a new install of ES, configured to use the (new for this
> > > install) data and log directories /var/data/elasticsearch-0.18.4/ and
> > > /var/log/elasticsearch-0.18.4/
> > > It also reported this same error when I first uncompressed the tarball
> > > and ran it with the defaults.
> > > I have had another version of ES on this machine (under Snow Leopard),
> > > which used /var/data/elasticsearch/ and /var/log/elasticsearch/, but I
> > > thought that the installs were self-contained, and therefore shouldn't
> > > interfere with each other?
> > > Maybe I could try a totally fresh install -- could anyone advise me on
> > > what files to delete to achieve this? I thought it would just be the
> > > elasticsearch directory, and any that I'd specified separately.
> > > Thanks,
> > > Doug.
> > >
> > > On 28 November 2011 11:22, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote:
> > >
> > > > Is that only your machine? There seems to be 2 nodes there, is that
> > > > what there should be? Its not a Java issue, more seems like a change in the
> > > > data location, or maybe something got deleted? Need more info as to the
> > > > amount of nodes in the cluster, and gist the cluster state.
> > > >
> > > > On Mon, Nov 28, 2011 at 1:01 PM, doug livesey [biot023@gmail.com](mailto:biot023@gmail.com)wrote:
> > > >
> > > > > Hi -- I have a new install of elasticsearch on my dev machine after
> > > > > upgrading to OSX Lion.
> > > > > Now, when I try to start elasticsearch, and check the cluster health,
> > > > > I get this:
> > > > >
> > > > > {
> > > > > "cluster\_name" : "elasticsearch",
> > > > > "status" : "red",
> > > > > "timed\_out" : false,
> > > > > "number\_of\_nodes" : 2,
> > > > > "number\_of\_data\_nodes" : 2,
> > > > > "active\_primary\_shards" : 7,
> > > > > "active\_shards" : 14,
> > > > > "relocating\_shards" : 0,
> > > > > "initializing\_shards" : 0,
> > > > > "unassigned\_shards" : 6
> > > > > }
> > > > >
> > > > > It stays at these values indefinitely. I've looked in the logs, but
> > > > > there's no hint of any errors in there.
> > > > > Can anyone offer any advice as to how to investigate this further?
> > > > > It's the basic elasticsearch install started up with
> > > > > bin/elasticsearch, so should be working, as far as I can tell.
> > > > > I guess, with my machine being upgraded to Lion, this could be a java
> > > > > issue?
> > > > > But I'm rather out of my depth with java.
> > > > > Incidentally, I tried to use my previous install of ES (0.17.5) to see
> > > > > if that still worked, and that also had unassigned shards, but was
> > > > > typically in status yellow.
> > > > > Thanks,
> > > > > Doug.
---
### Author:  [@kimchy](https://discuss.elastic.co/u/kimchy)
#### Post date: [November 28, 2011, 6:25pm UTC](https://discuss.elastic.co/t/new-install-of-elasticsearch-on-lion-status-red-unassigned-shards-nothing-in-the-logs/5989/7 "2011-11-28T18:25:37Z")
Check the logs, see where the second node is coming from (it will show you
the IP for it). Maybe someone else is running ES in your network. You can
disable multicast discovery in the configuration.
On Mon, Nov 28, 2011 at 3:30 PM, doug livesey [biot023@gmail.com](mailto:biot023@gmail.com) wrote:
> Yeah, something's up -- it's being very slow.
> I get this with ps:
>
> $ ps aux | grep elastic
> douglivesey 340 0.1 3.8 3765632 318788 s000 S+ 12:45pm
> 1:05.07 /usr/bin/java -Xms256m -Xmx1g -Xss128k -XX:+UseParNewGC
> -XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -XX:SurvivorRatio=8
> -XX:MaxTenuringThreshold=1 -XX:CMSInitiatingOccupancyFraction=75
> -XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError
> -Delasticsearch -Des.path.home=/Users/douglivesey/bin/elasticsearch-0.18.4
> -Des-foreground=yes -cp
> :/Users/douglivesey/bin/elasticsearch-0.18.4/lib/_:/Users/douglivesey/bin/elasticsearch-0.18.4/lib/sigar/_
> org.elasticsearch.bootstrap.Elasticsearch
>
> And the health report is:
>
> {
> "cluster\_name" : "elasticsearch",
> "status" : "green",
> "timed\_out" : false,
> "number\_of\_nodes" : 2,
> "number\_of\_data\_nodes" : 2,
> "active\_primary\_shards" : 10,
> "active\_shards" : 20,
> "relocating\_shards" : 0,
> "initializing\_shards" : 0,
> "unassigned\_shards" : 0
> }
>
> Which is green, but (as you say) seems to think that I have 2 nodes.
> Is there something I can do in the config to stop this? I've not
> explicitly set any node counts.
>
> On 28 November 2011 12:57, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote:
>
> > Something was still strange in your setup, since it reported that there
> > were two instances running, and I think, based on your feedback, that you
> > expect only one to run? Just do ps -ef | grep elasticsearch and check how
> > many instances you have...
> >
> > On Mon, Nov 28, 2011 at 2:51 PM, doug livesey [biot023@gmail.com](mailto:biot023@gmail.com) wrote:
> >
> > > Hi -- I deleted all data and log files, and restarted my machine, and we
> > > seem to be green, now.
> > > I'm re-indexing all my items, and it seems to be running slower than it
> > > did, but I'll keep an eye on that & make sure it is.
> > > Thanks for the sanity check! 🙂
> > > Doug.
> > >
> > > On 28 November 2011 12:40, doug livesey [biot023@gmail.com](mailto:biot023@gmail.com) wrote:
> > >
> > > > Hi -- it's a new install of ES, configured to use the (new for this
> > > > install) data and log directories /var/data/elasticsearch-0.18.4/ and
> > > > /var/log/elasticsearch-0.18.4/
> > > > It also reported this same error when I first uncompressed the tarball
> > > > and ran it with the defaults.
> > > > I have had another version of ES on this machine (under Snow Leopard),
> > > > which used /var/data/elasticsearch/ and /var/log/elasticsearch/, but I
> > > > thought that the installs were self-contained, and therefore shouldn't
> > > > interfere with each other?
> > > > Maybe I could try a totally fresh install -- could anyone advise me on
> > > > what files to delete to achieve this? I thought it would just be the
> > > > elasticsearch directory, and any that I'd specified separately.
> > > > Thanks,
> > > > Doug.
> > > >
> > > > On 28 November 2011 11:22, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote:
> > > >
> > > > > Is that only your machine? There seems to be 2 nodes there, is that
> > > > > what there should be? Its not a Java issue, more seems like a change in the
> > > > > data location, or maybe something got deleted? Need more info as to the
> > > > > amount of nodes in the cluster, and gist the cluster state.
> > > > >
> > > > > On Mon, Nov 28, 2011 at 1:01 PM, doug livesey [biot023@gmail.com](mailto:biot023@gmail.com)wrote:
> > > > >
> > > > > > Hi -- I have a new install of elasticsearch on my dev machine after
> > > > > > upgrading to OSX Lion.
> > > > > > Now, when I try to start elasticsearch, and check the cluster health,
> > > > > > I get this:
> > > > > >
> > > > > > {
> > > > > > "cluster\_name" : "elasticsearch",
> > > > > > "status" : "red",
> > > > > > "timed\_out" : false,
> > > > > > "number\_of\_nodes" : 2,
> > > > > > "number\_of\_data\_nodes" : 2,
> > > > > > "active\_primary\_shards" : 7,
> > > > > > "active\_shards" : 14,
> > > > > > "relocating\_shards" : 0,
> > > > > > "initializing\_shards" : 0,
> > > > > > "unassigned\_shards" : 6
> > > > > > }
> > > > > >
> > > > > > It stays at these values indefinitely. I've looked in the logs, but
> > > > > > there's no hint of any errors in there.
> > > > > > Can anyone offer any advice as to how to investigate this further?
> > > > > > It's the basic elasticsearch install started up with
> > > > > > bin/elasticsearch, so should be working, as far as I can tell.
> > > > > > I guess, with my machine being upgraded to Lion, this could be a java
> > > > > > issue?
> > > > > > But I'm rather out of my depth with java.
> > > > > > Incidentally, I tried to use my previous install of ES (0.17.5) to
> > > > > > see if that still worked, and that also had unassigned shards, but was
> > > > > > typically in status yellow.
> > > > > > Thanks,
> > > > > > Doug.
---
### Author:  [@doug\_livesey](https://discuss.elastic.co/u/doug_livesey)
#### Post date: [November 29, 2011, 12:26am UTC](https://discuss.elastic.co/t/new-install-of-elasticsearch-on-lion-status-red-unassigned-shards-nothing-in-the-logs/5989/8 "2011-11-29T00:26:33Z")
Hi -- only just spotted this reply, sorry -- I was at choir practice! 🙂
Now I'm at home, and the only computer around is mine. I've just started
the service with the -f option, and this is the output I get:
[2011-11-29 00:19:41,576][INFO][node] [Storm, Susan]
{0.18.4}[1806]: initializing ...
[2011-11-29 00:19:41,589][INFO][plugins] [Storm, Susan]
loaded , sites
[2011-11-29 00:19:44,291][INFO][node] [Storm, Susan]
{0.18.4}[1806]: initialized
[2011-11-29 00:19:44,303][INFO][node] [Storm, Susan]
{0.18.4}[1806]: starting ...
[2011-11-29 00:19:44,413][INFO][transport] [Storm, Susan]
bound\_address {inet[/0.0.0.0:9300]}, publish\_address {inet[/192.168.0.2:9300
]}
[2011-11-29 00:19:47,512][INFO][cluster.service] [Storm, Susan]
new\_master [Storm, Susan][v8UXExqiQxesxSoj8StQTg][inet[/192.168.0.2:9300]],
reason: zen-disco-join (elected\_as\_master)
[2011-11-29 00:19:47,565][INFO][discovery] [Storm, Susan]
elasticsearch/v8UXExqiQxesxSoj8StQTg
[2011-11-29 00:19:47,674][INFO][http] [Storm, Susan]
bound\_address {inet[/0.0.0.0:9200]}, publish\_address {inet[/192.168.0.2:9200
]}
[2011-11-29 00:19:47,675][INFO][node] [Storm, Susan]
{0.18.4}[1806]: started
[2011-11-29 00:19:48,425][INFO][gateway] [Storm, Susan]
recovered [2] indices into cluster\_state
When I check the health of my cluster, I get this:
{
"cluster\_name" : "elasticsearch",
"status" : "yellow",
"timed\_out" : false,
"number\_of\_nodes" : 1,
"number\_of\_data\_nodes" : 1,
"active\_primary\_shards" : 10,
"active\_shards" : 10,
"relocating\_shards" : 0,
"initializing\_shards" : 0,
"unassigned\_shards" : 10
}
Could it be expecting another server, there?
I'm afraid I'm quite at a loss as to how to investigate this further, so
really appreciate your help, thanks.
Doug.
On 28 November 2011 18:25, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote:
> Check the logs, see where the second node is coming from (it will show you
> the IP for it). Maybe someone else is running ES in your network. You can
> disable multicast discovery in the configuration.
>
> On Mon, Nov 28, 2011 at 3:30 PM, doug livesey [biot023@gmail.com](mailto:biot023@gmail.com) wrote:
>
> > Yeah, something's up -- it's being very slow.
> > I get this with ps:
> >
> > $ ps aux | grep elastic
> > douglivesey 340 0.1 3.8 3765632 318788 s000 S+ 12:45pm
> > 1:05.07 /usr/bin/java -Xms256m -Xmx1g -Xss128k -XX:+UseParNewGC
> > -XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -XX:SurvivorRatio=8
> > -XX:MaxTenuringThreshold=1 -XX:CMSInitiatingOccupancyFraction=75
> > -XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError
> > -Delasticsearch -Des.path.home=/Users/douglivesey/bin/elasticsearch-0.18.4
> > -Des-foreground=yes -cp
> > :/Users/douglivesey/bin/elasticsearch-0.18.4/lib/_:/Users/douglivesey/bin/elasticsearch-0.18.4/lib/sigar/_
> > org.elasticsearch.bootstrap.Elasticsearch
> >
> > And the health report is:
> >
> > {
> > "cluster\_name" : "elasticsearch",
> > "status" : "green",
> > "timed\_out" : false,
> > "number\_of\_nodes" : 2,
> > "number\_of\_data\_nodes" : 2,
> > "active\_primary\_shards" : 10,
> > "active\_shards" : 20,
> > "relocating\_shards" : 0,
> > "initializing\_shards" : 0,
> > "unassigned\_shards" : 0
> > }
> >
> > Which is green, but (as you say) seems to think that I have 2 nodes.
> > Is there something I can do in the config to stop this? I've not
> > explicitly set any node counts.
> >
> > On 28 November 2011 12:57, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote:
> >
> > > Something was still strange in your setup, since it reported that there
> > > were two instances running, and I think, based on your feedback, that you
> > > expect only one to run? Just do ps -ef | grep elasticsearch and check how
> > > many instances you have...
> > >
> > > On Mon, Nov 28, 2011 at 2:51 PM, doug livesey [biot023@gmail.com](mailto:biot023@gmail.com) wrote:
> > >
> > > > Hi -- I deleted all data and log files, and restarted my machine, and
> > > > we seem to be green, now.
> > > > I'm re-indexing all my items, and it seems to be running slower than it
> > > > did, but I'll keep an eye on that & make sure it is.
> > > > Thanks for the sanity check! 🙂
> > > > Doug.
> > > >
> > > > On 28 November 2011 12:40, doug livesey [biot023@gmail.com](mailto:biot023@gmail.com) wrote:
> > > >
> > > > > Hi -- it's a new install of ES, configured to use the (new for this
> > > > > install) data and log directories /var/data/elasticsearch-0.18.4/ and
> > > > > /var/log/elasticsearch-0.18.4/
> > > > > It also reported this same error when I first uncompressed the tarball
> > > > > and ran it with the defaults.
> > > > > I have had another version of ES on this machine (under Snow Leopard),
> > > > > which used /var/data/elasticsearch/ and /var/log/elasticsearch/, but I
> > > > > thought that the installs were self-contained, and therefore shouldn't
> > > > > interfere with each other?
> > > > > Maybe I could try a totally fresh install -- could anyone advise me on
> > > > > what files to delete to achieve this? I thought it would just be the
> > > > > elasticsearch directory, and any that I'd specified separately.
> > > > > Thanks,
> > > > > Doug.
> > > > >
> > > > > On 28 November 2011 11:22, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote:
> > > > >
> > > > > > Is that only your machine? There seems to be 2 nodes there, is that
> > > > > > what there should be? Its not a Java issue, more seems like a change in the
> > > > > > data location, or maybe something got deleted? Need more info as to the
> > > > > > amount of nodes in the cluster, and gist the cluster state.
> > > > > >
> > > > > > On Mon, Nov 28, 2011 at 1:01 PM, doug livesey [biot023@gmail.com](mailto:biot023@gmail.com)wrote:
> > > > > >
> > > > > > > Hi -- I have a new install of elasticsearch on my dev machine after
> > > > > > > upgrading to OSX Lion.
> > > > > > > Now, when I try to start elasticsearch, and check the cluster
> > > > > > > health, I get this:
> > > > > > >
> > > > > > > {
> > > > > > > "cluster\_name" : "elasticsearch",
> > > > > > > "status" : "red",
> > > > > > > "timed\_out" : false,
> > > > > > > "number\_of\_nodes" : 2,
> > > > > > > "number\_of\_data\_nodes" : 2,
> > > > > > > "active\_primary\_shards" : 7,
> > > > > > > "active\_shards" : 14,
> > > > > > > "relocating\_shards" : 0,
> > > > > > > "initializing\_shards" : 0,
> > > > > > > "unassigned\_shards" : 6
> > > > > > > }
> > > > > > >
> > > > > > > It stays at these values indefinitely. I've looked in the logs, but
> > > > > > > there's no hint of any errors in there.
> > > > > > > Can anyone offer any advice as to how to investigate this further?
> > > > > > > It's the basic elasticsearch install started up with
> > > > > > > bin/elasticsearch, so should be working, as far as I can tell.
> > > > > > > I guess, with my machine being upgraded to Lion, this could be a
> > > > > > > java issue?
> > > > > > > But I'm rather out of my depth with java.
> > > > > > > Incidentally, I tried to use my previous install of ES (0.17.5) to
> > > > > > > see if that still worked, and that also had unassigned shards, but was
> > > > > > > typically in status yellow.
> > > > > > > Thanks,
> > > > > > > Doug.
---
### Author:  [@kimchy](https://discuss.elastic.co/u/kimchy)
#### Post date: [November 29, 2011, 7:03am UTC](https://discuss.elastic.co/t/new-install-of-elasticsearch-on-lion-status-red-unassigned-shards-nothing-in-the-logs/5989/9 "2011-11-29T07:03:36Z")
Now you have a single node, not two (at home). So I think you are joining
another node started in the network at home. The reason why you have 10
shards unassigned and yellow state is because you have indices that are
created with number\_of\_replicas set to 1, but, since you have just a single
node, it makes not sense to allocate both shard copies on the same node.
On Tue, Nov 29, 2011 at 2:26 AM, doug livesey [biot023@gmail.com](mailto:biot023@gmail.com) wrote:
> Hi -- only just spotted this reply, sorry -- I was at choir practice! 🙂
> Now I'm at home, and the only computer around is mine. I've just started
> the service with the -f option, and this is the output I get:
>
> [2011-11-29 00:19:41,576][INFO][node] [Storm, Susan]
> {0.18.4}[1806]: initializing ...
> [2011-11-29 00:19:41,589][INFO][plugins] [Storm, Susan]
> loaded , sites
> [2011-11-29 00:19:44,291][INFO][node] [Storm, Susan]
> {0.18.4}[1806]: initialized
> [2011-11-29 00:19:44,303][INFO][node] [Storm, Susan]
> {0.18.4}[1806]: starting ...
> [2011-11-29 00:19:44,413][INFO][transport] [Storm, Susan]
> bound\_address {inet[/0.0.0.0:9300]}, publish\_address {inet[/
> 192.168.0.2:9300]}
> [2011-11-29 00:19:47,512][INFO][cluster.service] [Storm, Susan]
> new\_master [Storm, Susan][v8UXExqiQxesxSoj8StQTg][inet[/192.168.0.2:9300]],
> reason: zen-disco-join (elected\_as\_master)
> [2011-11-29 00:19:47,565][INFO][discovery] [Storm, Susan]
> elasticsearch/v8UXExqiQxesxSoj8StQTg
> [2011-11-29 00:19:47,674][INFO][http] [Storm, Susan]
> bound\_address {inet[/0.0.0.0:9200]}, publish\_address {inet[/
> 192.168.0.2:9200]}
> [2011-11-29 00:19:47,675][INFO][node] [Storm, Susan]
> {0.18.4}[1806]: started
> [2011-11-29 00:19:48,425][INFO][gateway] [Storm, Susan]
> recovered [2] indices into cluster\_state
>
> When I check the health of my cluster, I get this:
>
> {
> "cluster\_name" : "elasticsearch",
> "status" : "yellow",
> "timed\_out" : false,
> "number\_of\_nodes" : 1,
> "number\_of\_data\_nodes" : 1,
> "active\_primary\_shards" : 10,
> "active\_shards" : 10,
> "relocating\_shards" : 0,
> "initializing\_shards" : 0,
> "unassigned\_shards" : 10
> }
>
> Could it be expecting another server, there?
> I'm afraid I'm quite at a loss as to how to investigate this further, so
> really appreciate your help, thanks.
> Doug.
>
> On 28 November 2011 18:25, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote:
>
> > Check the logs, see where the second node is coming from (it will show
> > you the IP for it). Maybe someone else is running ES in your network. You
> > can disable multicast discovery in the configuration.
> >
> > On Mon, Nov 28, 2011 at 3:30 PM, doug livesey [biot023@gmail.com](mailto:biot023@gmail.com) wrote:
> >
> > > Yeah, something's up -- it's being very slow.
> > > I get this with ps:
> > >
> > > $ ps aux | grep elastic
> > > douglivesey 340 0.1 3.8 3765632 318788 s000 S+ 12:45pm
> > > 1:05.07 /usr/bin/java -Xms256m -Xmx1g -Xss128k -XX:+UseParNewGC
> > > -XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -XX:SurvivorRatio=8
> > > -XX:MaxTenuringThreshold=1 -XX:CMSInitiatingOccupancyFraction=75
> > > -XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError
> > > -Delasticsearch -Des.path.home=/Users/douglivesey/bin/elasticsearch-0.18.4
> > > -Des-foreground=yes -cp
> > > :/Users/douglivesey/bin/elasticsearch-0.18.4/lib/_:/Users/douglivesey/bin/elasticsearch-0.18.4/lib/sigar/_
> > > org.elasticsearch.bootstrap.Elasticsearch
> > >
> > > And the health report is:
> > >
> > > {
> > > "cluster\_name" : "elasticsearch",
> > > "status" : "green",
> > > "timed\_out" : false,
> > > "number\_of\_nodes" : 2,
> > > "number\_of\_data\_nodes" : 2,
> > > "active\_primary\_shards" : 10,
> > > "active\_shards" : 20,
> > > "relocating\_shards" : 0,
> > > "initializing\_shards" : 0,
> > > "unassigned\_shards" : 0
> > > }
> > >
> > > Which is green, but (as you say) seems to think that I have 2 nodes.
> > > Is there something I can do in the config to stop this? I've not
> > > explicitly set any node counts.
> > >
> > > On 28 November 2011 12:57, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote:
> > >
> > > > Something was still strange in your setup, since it reported that there
> > > > were two instances running, and I think, based on your feedback, that you
> > > > expect only one to run? Just do ps -ef | grep elasticsearch and check how
> > > > many instances you have...
> > > >
> > > > On Mon, Nov 28, 2011 at 2:51 PM, doug livesey [biot023@gmail.com](mailto:biot023@gmail.com)wrote:
> > > >
> > > > > Hi -- I deleted all data and log files, and restarted my machine, and
> > > > > we seem to be green, now.
> > > > > I'm re-indexing all my items, and it seems to be running slower than
> > > > > it did, but I'll keep an eye on that & make sure it is.
> > > > > Thanks for the sanity check! 🙂
> > > > > Doug.
> > > > >
> > > > > On 28 November 2011 12:40, doug livesey [biot023@gmail.com](mailto:biot023@gmail.com) wrote:
> > > > >
> > > > > > Hi -- it's a new install of ES, configured to use the (new for this
> > > > > > install) data and log directories /var/data/elasticsearch-0.18.4/ and
> > > > > > /var/log/elasticsearch-0.18.4/
> > > > > > It also reported this same error when I first uncompressed the
> > > > > > tarball and ran it with the defaults.
> > > > > > I have had another version of ES on this machine (under Snow
> > > > > > Leopard), which used /var/data/elasticsearch/ and /var/log/elasticsearch/,
> > > > > > but I thought that the installs were self-contained, and therefore
> > > > > > shouldn't interfere with each other?
> > > > > > Maybe I could try a totally fresh install -- could anyone advise me
> > > > > > on what files to delete to achieve this? I thought it would just be the
> > > > > > elasticsearch directory, and any that I'd specified separately.
> > > > > > Thanks,
> > > > > > Doug.
> > > > > >
> > > > > > On 28 November 2011 11:22, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote:
> > > > > >
> > > > > > > Is that only your machine? There seems to be 2 nodes there, is that
> > > > > > > what there should be? Its not a Java issue, more seems like a change in the
> > > > > > > data location, or maybe something got deleted? Need more info as to the
> > > > > > > amount of nodes in the cluster, and gist the cluster state.
> > > > > > >
> > > > > > > On Mon, Nov 28, 2011 at 1:01 PM, doug livesey [biot023@gmail.com](mailto:biot023@gmail.com)wrote:
> > > > > > >
> > > > > > > > Hi -- I have a new install of elasticsearch on my dev machine after
> > > > > > > > upgrading to OSX Lion.
> > > > > > > > Now, when I try to start elasticsearch, and check the cluster
> > > > > > > > health, I get this:
> > > > > > > >
> > > > > > > > {
> > > > > > > > "cluster\_name" : "elasticsearch",
> > > > > > > > "status" : "red",
> > > > > > > > "timed\_out" : false,
> > > > > > > > "number\_of\_nodes" : 2,
> > > > > > > > "number\_of\_data\_nodes" : 2,
> > > > > > > > "active\_primary\_shards" : 7,
> > > > > > > > "active\_shards" : 14,
> > > > > > > > "relocating\_shards" : 0,
> > > > > > > > "initializing\_shards" : 0,
> > > > > > > > "unassigned\_shards" : 6
> > > > > > > > }
> > > > > > > >
> > > > > > > > It stays at these values indefinitely. I've looked in the logs, but
> > > > > > > > there's no hint of any errors in there.
> > > > > > > > Can anyone offer any advice as to how to investigate this further?
> > > > > > > > It's the basic elasticsearch install started up with
> > > > > > > > bin/elasticsearch, so should be working, as far as I can tell.
> > > > > > > > I guess, with my machine being upgraded to Lion, this could be a
> > > > > > > > java issue?
> > > > > > > > But I'm rather out of my depth with java.
> > > > > > > > Incidentally, I tried to use my previous install of ES (0.17.5) to
> > > > > > > > see if that still worked, and that also had unassigned shards, but was
> > > > > > > > typically in status yellow.
> > > > > > > > Thanks,
> > > > > > > > Doug.
---
### Author:  [@doug\_livesey](https://discuss.elastic.co/u/doug_livesey)
#### Post date: [November 29, 2011, 10:15am UTC](https://discuss.elastic.co/t/new-install-of-elasticsearch-on-lion-status-red-unassigned-shards-nothing-in-the-logs/5989/10 "2011-11-29T10:15:17Z")
Right, so is there something I should change in my config?
Maybe get rid of the number of replicas? I don't have a network at home --
just my computer and the wifi router, so I guess that's why shards aren't
getting assigned.
On 29 November 2011 07:03, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote:
> Now you have a single node, not two (at home). So I think you are joining
> another node started in the network at home. The reason why you have 10
> shards unassigned and yellow state is because you have indices that are
> created with number\_of\_replicas set to 1, but, since you have just a single
> node, it makes not sense to allocate both shard copies on the same node.
>
> On Tue, Nov 29, 2011 at 2:26 AM, doug livesey [biot023@gmail.com](mailto:biot023@gmail.com) wrote:
>
> > Hi -- only just spotted this reply, sorry -- I was at choir practice! 🙂
> > Now I'm at home, and the only computer around is mine. I've just started
> > the service with the -f option, and this is the output I get:
> >
> > [2011-11-29 00:19:41,576][INFO][node] [Storm,
> > Susan] {0.18.4}[1806]: initializing ...
> > [2011-11-29 00:19:41,589][INFO][plugins] [Storm,
> > Susan] loaded , sites
> > [2011-11-29 00:19:44,291][INFO][node] [Storm,
> > Susan] {0.18.4}[1806]: initialized
> > [2011-11-29 00:19:44,303][INFO][node] [Storm,
> > Susan] {0.18.4}[1806]: starting ...
> > [2011-11-29 00:19:44,413][INFO][transport] [Storm,
> > Susan] bound\_address {inet[/0.0.0.0:9300]}, publish\_address {inet[/
> > 192.168.0.2:9300]}
> > [2011-11-29 00:19:47,512][INFO][cluster.service] [Storm,
> > Susan] new\_master [Storm,
> > Susan][v8UXExqiQxesxSoj8StQTg][inet[/192.168.0.2:9300]], reason:
> > zen-disco-join (elected\_as\_master)
> > [2011-11-29 00:19:47,565][INFO][discovery] [Storm,
> > Susan] elasticsearch/v8UXExqiQxesxSoj8StQTg
> > [2011-11-29 00:19:47,674][INFO][http] [Storm,
> > Susan] bound\_address {inet[/0.0.0.0:9200]}, publish\_address {inet[/
> > 192.168.0.2:9200]}
> > [2011-11-29 00:19:47,675][INFO][node] [Storm,
> > Susan] {0.18.4}[1806]: started
> > [2011-11-29 00:19:48,425][INFO][gateway] [Storm,
> > Susan] recovered [2] indices into cluster\_state
> >
> > When I check the health of my cluster, I get this:
> >
> > {
> > "cluster\_name" : "elasticsearch",
> > "status" : "yellow",
> > "timed\_out" : false,
> > "number\_of\_nodes" : 1,
> > "number\_of\_data\_nodes" : 1,
> > "active\_primary\_shards" : 10,
> > "active\_shards" : 10,
> > "relocating\_shards" : 0,
> > "initializing\_shards" : 0,
> > "unassigned\_shards" : 10
> > }
> >
> > Could it be expecting another server, there?
> > I'm afraid I'm quite at a loss as to how to investigate this further, so
> > really appreciate your help, thanks.
> > Doug.
> >
> > On 28 November 2011 18:25, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote:
> >
> > > Check the logs, see where the second node is coming from (it will show
> > > you the IP for it). Maybe someone else is running ES in your network. You
> > > can disable multicast discovery in the configuration.
> > >
> > > On Mon, Nov 28, 2011 at 3:30 PM, doug livesey [biot023@gmail.com](mailto:biot023@gmail.com) wrote:
> > >
> > > > Yeah, something's up -- it's being very slow.
> > > > I get this with ps:
> > > >
> > > > $ ps aux | grep elastic
> > > > douglivesey 340 0.1 3.8 3765632 318788 s000 S+ 12:45pm
> > > > 1:05.07 /usr/bin/java -Xms256m -Xmx1g -Xss128k -XX:+UseParNewGC
> > > > -XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -XX:SurvivorRatio=8
> > > > -XX:MaxTenuringThreshold=1 -XX:CMSInitiatingOccupancyFraction=75
> > > > -XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError
> > > > -Delasticsearch -Des.path.home=/Users/douglivesey/bin/elasticsearch-0.18.4
> > > > -Des-foreground=yes -cp
> > > > :/Users/douglivesey/bin/elasticsearch-0.18.4/lib/_:/Users/douglivesey/bin/elasticsearch-0.18.4/lib/sigar/_
> > > > org.elasticsearch.bootstrap.Elasticsearch
> > > >
> > > > And the health report is:
> > > >
> > > > {
> > > > "cluster\_name" : "elasticsearch",
> > > > "status" : "green",
> > > > "timed\_out" : false,
> > > > "number\_of\_nodes" : 2,
> > > > "number\_of\_data\_nodes" : 2,
> > > > "active\_primary\_shards" : 10,
> > > > "active\_shards" : 20,
> > > > "relocating\_shards" : 0,
> > > > "initializing\_shards" : 0,
> > > > "unassigned\_shards" : 0
> > > > }
> > > >
> > > > Which is green, but (as you say) seems to think that I have 2 nodes.
> > > > Is there something I can do in the config to stop this? I've not
> > > > explicitly set any node counts.
> > > >
> > > > On 28 November 2011 12:57, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote:
> > > >
> > > > > Something was still strange in your setup, since it reported that
> > > > > there were two instances running, and I think, based on your feedback, that
> > > > > you expect only one to run? Just do ps -ef | grep elasticsearch and check
> > > > > how many instances you have...
> > > > >
> > > > > On Mon, Nov 28, 2011 at 2:51 PM, doug livesey [biot023@gmail.com](mailto:biot023@gmail.com)wrote:
> > > > >
> > > > > > Hi -- I deleted all data and log files, and restarted my machine, and
> > > > > > we seem to be green, now.
> > > > > > I'm re-indexing all my items, and it seems to be running slower than
> > > > > > it did, but I'll keep an eye on that & make sure it is.
> > > > > > Thanks for the sanity check! 🙂
> > > > > > Doug.
> > > > > >
> > > > > > On 28 November 2011 12:40, doug livesey [biot023@gmail.com](mailto:biot023@gmail.com) wrote:
> > > > > >
> > > > > > > Hi -- it's a new install of ES, configured to use the (new for this
> > > > > > > install) data and log directories /var/data/elasticsearch-0.18.4/ and
> > > > > > > /var/log/elasticsearch-0.18.4/
> > > > > > > It also reported this same error when I first uncompressed the
> > > > > > > tarball and ran it with the defaults.
> > > > > > > I have had another version of ES on this machine (under Snow
> > > > > > > Leopard), which used /var/data/elasticsearch/ and /var/log/elasticsearch/,
> > > > > > > but I thought that the installs were self-contained, and therefore
> > > > > > > shouldn't interfere with each other?
> > > > > > > Maybe I could try a totally fresh install -- could anyone advise me
> > > > > > > on what files to delete to achieve this? I thought it would just be the
> > > > > > > elasticsearch directory, and any that I'd specified separately.
> > > > > > > Thanks,
> > > > > > > Doug.
> > > > > > >
> > > > > > > On 28 November 2011 11:22, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote:
> > > > > > >
> > > > > > > > Is that only your machine? There seems to be 2 nodes there, is that
> > > > > > > > what there should be? Its not a Java issue, more seems like a change in the
> > > > > > > > data location, or maybe something got deleted? Need more info as to the
> > > > > > > > amount of nodes in the cluster, and gist the cluster state.
> > > > > > > >
> > > > > > > > On Mon, Nov 28, 2011 at 1:01 PM, doug livesey [biot023@gmail.com](mailto:biot023@gmail.com)wrote:
> > > > > > > >
> > > > > > > > > Hi -- I have a new install of elasticsearch on my dev machine
> > > > > > > > > after upgrading to OSX Lion.
> > > > > > > > > Now, when I try to start elasticsearch, and check the cluster
> > > > > > > > > health, I get this:
> > > > > > > > >
> > > > > > > > > {
> > > > > > > > > "cluster\_name" : "elasticsearch",
> > > > > > > > > "status" : "red",
> > > > > > > > > "timed\_out" : false,
> > > > > > > > > "number\_of\_nodes" : 2,
> > > > > > > > > "number\_of\_data\_nodes" : 2,
> > > > > > > > > "active\_primary\_shards" : 7,
> > > > > > > > > "active\_shards" : 14,
> > > > > > > > > "relocating\_shards" : 0,
> > > > > > > > > "initializing\_shards" : 0,
> > > > > > > > > "unassigned\_shards" : 6
> > > > > > > > > }
> > > > > > > > >
> > > > > > > > > It stays at these values indefinitely. I've looked in the logs,
> > > > > > > > > but there's no hint of any errors in there.
> > > > > > > > > Can anyone offer any advice as to how to investigate this further?
> > > > > > > > > It's the basic elasticsearch install started up with
> > > > > > > > > bin/elasticsearch, so should be working, as far as I can tell.
> > > > > > > > > I guess, with my machine being upgraded to Lion, this could be a
> > > > > > > > > java issue?
> > > > > > > > > But I'm rather out of my depth with java.
> > > > > > > > > Incidentally, I tried to use my previous install of ES (0.17.5) to
> > > > > > > > > see if that still worked, and that also had unassigned shards, but was
> > > > > > > > > typically in status yellow.
> > > > > > > > > Thanks,
> > > > > > > > > Doug.
---
### Author:  [@doug\_livesey](https://discuss.elastic.co/u/doug_livesey)
#### Post date: [November 29, 2011, 10:25am UTC](https://discuss.elastic.co/t/new-install-of-elasticsearch-on-lion-status-red-unassigned-shards-nothing-in-the-logs/5989/11 "2011-11-29T10:25:15Z")
So I went through the config file and set the number of shards to 1 and the
number of replicas to 0, and that seems to have fixed it.
I use quite a large local index, so I may set the number of shards back up
to 10 or so, but for now that's working nicely.
I also changed the name of the node to "Susan Sarandon" because of that
vampire film she was in with Catherine Deneuve, but I doubt that's had any
effect on this issue. 😉
Cheers for all your help,
Doug.
On 29 November 2011 10:15, doug livesey [biot023@gmail.com](mailto:biot023@gmail.com) wrote:
> Right, so is there something I should change in my config?
> Maybe get rid of the number of replicas? I don't have a network at home --
> just my computer and the wifi router, so I guess that's why shards aren't
> getting assigned.
>
> On 29 November 2011 07:03, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote:
>
> > Now you have a single node, not two (at home). So I think you are joining
> > another node started in the network at home. The reason why you have 10
> > shards unassigned and yellow state is because you have indices that are
> > created with number\_of\_replicas set to 1, but, since you have just a single
> > node, it makes not sense to allocate both shard copies on the same node.
> >
> > On Tue, Nov 29, 2011 at 2:26 AM, doug livesey [biot023@gmail.com](mailto:biot023@gmail.com) wrote:
> >
> > > Hi -- only just spotted this reply, sorry -- I was at choir practice! 🙂
> > > Now I'm at home, and the only computer around is mine. I've just started
> > > the service with the -f option, and this is the output I get:
> > >
> > > [2011-11-29 00:19:41,576][INFO][node] [Storm,
> > > Susan] {0.18.4}[1806]: initializing ...
> > > [2011-11-29 00:19:41,589][INFO][plugins] [Storm,
> > > Susan] loaded , sites
> > > [2011-11-29 00:19:44,291][INFO][node] [Storm,
> > > Susan] {0.18.4}[1806]: initialized
> > > [2011-11-29 00:19:44,303][INFO][node] [Storm,
> > > Susan] {0.18.4}[1806]: starting ...
> > > [2011-11-29 00:19:44,413][INFO][transport] [Storm,
> > > Susan] bound\_address {inet[/0.0.0.0:9300]}, publish\_address {inet[/
> > > 192.168.0.2:9300]}
> > > [2011-11-29 00:19:47,512][INFO][cluster.service] [Storm,
> > > Susan] new\_master [Storm,
> > > Susan][v8UXExqiQxesxSoj8StQTg][inet[/192.168.0.2:9300]], reason:
> > > zen-disco-join (elected\_as\_master)
> > > [2011-11-29 00:19:47,565][INFO][discovery] [Storm,
> > > Susan] elasticsearch/v8UXExqiQxesxSoj8StQTg
> > > [2011-11-29 00:19:47,674][INFO][http] [Storm,
> > > Susan] bound\_address {inet[/0.0.0.0:9200]}, publish\_address {inet[/
> > > 192.168.0.2:9200]}
> > > [2011-11-29 00:19:47,675][INFO][node] [Storm,
> > > Susan] {0.18.4}[1806]: started
> > > [2011-11-29 00:19:48,425][INFO][gateway] [Storm,
> > > Susan] recovered [2] indices into cluster\_state
> > >
> > > When I check the health of my cluster, I get this:
> > >
> > > {
> > > "cluster\_name" : "elasticsearch",
> > > "status" : "yellow",
> > > "timed\_out" : false,
> > > "number\_of\_nodes" : 1,
> > > "number\_of\_data\_nodes" : 1,
> > > "active\_primary\_shards" : 10,
> > > "active\_shards" : 10,
> > > "relocating\_shards" : 0,
> > > "initializing\_shards" : 0,
> > > "unassigned\_shards" : 10
> > > }
> > >
> > > Could it be expecting another server, there?
> > > I'm afraid I'm quite at a loss as to how to investigate this further, so
> > > really appreciate your help, thanks.
> > > Doug.
> > >
> > > On 28 November 2011 18:25, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote:
> > >
> > > > Check the logs, see where the second node is coming from (it will show
> > > > you the IP for it). Maybe someone else is running ES in your network. You
> > > > can disable multicast discovery in the configuration.
> > > >
> > > > On Mon, Nov 28, 2011 at 3:30 PM, doug livesey [biot023@gmail.com](mailto:biot023@gmail.com)wrote:
> > > >
> > > > > Yeah, something's up -- it's being very slow.
> > > > > I get this with ps:
> > > > >
> > > > > $ ps aux | grep elastic
> > > > > douglivesey 340 0.1 3.8 3765632 318788 s000 S+ 12:45pm
> > > > > 1:05.07 /usr/bin/java -Xms256m -Xmx1g -Xss128k -XX:+UseParNewGC
> > > > > -XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -XX:SurvivorRatio=8
> > > > > -XX:MaxTenuringThreshold=1 -XX:CMSInitiatingOccupancyFraction=75
> > > > > -XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError
> > > > > -Delasticsearch -Des.path.home=/Users/douglivesey/bin/elasticsearch-0.18.4
> > > > > -Des-foreground=yes -cp
> > > > > :/Users/douglivesey/bin/elasticsearch-0.18.4/lib/_:/Users/douglivesey/bin/elasticsearch-0.18.4/lib/sigar/_
> > > > > org.elasticsearch.bootstrap.Elasticsearch
> > > > >
> > > > > And the health report is:
> > > > >
> > > > > {
> > > > > "cluster\_name" : "elasticsearch",
> > > > > "status" : "green",
> > > > > "timed\_out" : false,
> > > > > "number\_of\_nodes" : 2,
> > > > > "number\_of\_data\_nodes" : 2,
> > > > > "active\_primary\_shards" : 10,
> > > > > "active\_shards" : 20,
> > > > > "relocating\_shards" : 0,
> > > > > "initializing\_shards" : 0,
> > > > > "unassigned\_shards" : 0
> > > > > }
> > > > >
> > > > > Which is green, but (as you say) seems to think that I have 2 nodes.
> > > > > Is there something I can do in the config to stop this? I've not
> > > > > explicitly set any node counts.
> > > > >
> > > > > On 28 November 2011 12:57, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote:
> > > > >
> > > > > > Something was still strange in your setup, since it reported that
> > > > > > there were two instances running, and I think, based on your feedback, that
> > > > > > you expect only one to run? Just do ps -ef | grep elasticsearch and check
> > > > > > how many instances you have...
> > > > > >
> > > > > > On Mon, Nov 28, 2011 at 2:51 PM, doug livesey [biot023@gmail.com](mailto:biot023@gmail.com)wrote:
> > > > > >
> > > > > > > Hi -- I deleted all data and log files, and restarted my machine,
> > > > > > > and we seem to be green, now.
> > > > > > > I'm re-indexing all my items, and it seems to be running slower than
> > > > > > > it did, but I'll keep an eye on that & make sure it is.
> > > > > > > Thanks for the sanity check! 🙂
> > > > > > > Doug.
> > > > > > >
> > > > > > > On 28 November 2011 12:40, doug livesey [biot023@gmail.com](mailto:biot023@gmail.com) wrote:
> > > > > > >
> > > > > > > > Hi -- it's a new install of ES, configured to use the (new for this
> > > > > > > > install) data and log directories /var/data/elasticsearch-0.18.4/ and
> > > > > > > > /var/log/elasticsearch-0.18.4/
> > > > > > > > It also reported this same error when I first uncompressed the
> > > > > > > > tarball and ran it with the defaults.
> > > > > > > > I have had another version of ES on this machine (under Snow
> > > > > > > > Leopard), which used /var/data/elasticsearch/ and /var/log/elasticsearch/,
> > > > > > > > but I thought that the installs were self-contained, and therefore
> > > > > > > > shouldn't interfere with each other?
> > > > > > > > Maybe I could try a totally fresh install -- could anyone advise me
> > > > > > > > on what files to delete to achieve this? I thought it would just be the
> > > > > > > > elasticsearch directory, and any that I'd specified separately.
> > > > > > > > Thanks,
> > > > > > > > Doug.
> > > > > > > >
> > > > > > > > On 28 November 2011 11:22, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote:
> > > > > > > >
> > > > > > > > > Is that only your machine? There seems to be 2 nodes there, is
> > > > > > > > > that what there should be? Its not a Java issue, more seems like a change
> > > > > > > > > in the data location, or maybe something got deleted? Need more info as to
> > > > > > > > > the amount of nodes in the cluster, and gist the cluster state.
> > > > > > > > >
> > > > > > > > > On Mon, Nov 28, 2011 at 1:01 PM, doug livesey [biot023@gmail.com](mailto:biot023@gmail.com)wrote:
> > > > > > > > >
> > > > > > > > > > Hi -- I have a new install of elasticsearch on my dev machine
> > > > > > > > > > after upgrading to OSX Lion.
> > > > > > > > > > Now, when I try to start elasticsearch, and check the cluster
> > > > > > > > > > health, I get this:
> > > > > > > > > >
> > > > > > > > > > {
> > > > > > > > > > "cluster\_name" : "elasticsearch",
> > > > > > > > > > "status" : "red",
> > > > > > > > > > "timed\_out" : false,
> > > > > > > > > > "number\_of\_nodes" : 2,
> > > > > > > > > > "number\_of\_data\_nodes" : 2,
> > > > > > > > > > "active\_primary\_shards" : 7,
> > > > > > > > > > "active\_shards" : 14,
> > > > > > > > > > "relocating\_shards" : 0,
> > > > > > > > > > "initializing\_shards" : 0,
> > > > > > > > > > "unassigned\_shards" : 6
> > > > > > > > > > }
> > > > > > > > > >
> > > > > > > > > > It stays at these values indefinitely. I've looked in the logs,
> > > > > > > > > > but there's no hint of any errors in there.
> > > > > > > > > > Can anyone offer any advice as to how to investigate this further?
> > > > > > > > > > It's the basic elasticsearch install started up with
> > > > > > > > > > bin/elasticsearch, so should be working, as far as I can tell.
> > > > > > > > > > I guess, with my machine being upgraded to Lion, this could be a
> > > > > > > > > > java issue?
> > > > > > > > > > But I'm rather out of my depth with java.
> > > > > > > > > > Incidentally, I tried to use my previous install of ES (0.17.5)
> > > > > > > > > > to see if that still worked, and that also had unassigned shards, but was
> > > > > > > > > > typically in status yellow.
> > > > > > > > > > Thanks,
> > > > > > > > > > Doug.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 3:47am UTC](https://discuss.elastic.co/t/new-install-of-elasticsearch-on-lion-status-red-unassigned-shards-nothing-in-the-logs/5989/12 "2017-07-06T03:47:07Z")