Re: Dumb Question on bouncing nodes
Reading the description of that issue, I don't think they're the same. Looking at the code... Yeah, that's only about moving primaries around. So is there a way to restart a node without it going to zero shards and then back again? -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/25b969c7-ac3a-414a-b4e4-070b95b4857c%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Compared to Solr (with Solr Cloud), what is the advantage(s) of Elasticsearch?
We use both SOLR and Elasticsearch at Chegg. The search for www.chegg.com is powered by SOLR, because that's done by the search team, who are are more hard-core search nerds, like XML instead of JSON, etc. They have one master and a whole bunch of slaves, and rebuild the master continuously. I wanted to switch to Elasticsearch for the eReader team, because we're constantly adding new eBooks to our catalog, so I needed something that clustered. We had a bunch of endless meetings discussing it. Ops wanted a zone-aware solution, which Solr Cloud, since its based on Zookeeper, couldn't do automatically. Plus realistically, only the search folks knew how to deal with Solr. I could deal with ES with just my team with partial attention. Elasticsearch could do the zone aware thing, so that's how I got Ops to sign up. Plus they were already using Logstash. But really, its because its much easier for me to administrate, and the clustering part just works on its own without needing zookeeper. Pierce -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/d871e8ad-8403-46cc-aa4b-942d7477604a%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Dumb Question on bouncing nodes
Q: Is using the automatic node naming where every time I bounce a node I get a new node name interfering with restarting from the local gateway? Q Background: So previously, I asked about bouncing nodes, because it seems that whenever I bounce a node, it has to regenerate the node from the other nodes in the cluster. Someone told me I needed to lock shard allocation, then bounce, because the problem was that the cluster was reallocating the shards off of the node, so then the node wouldn't just come back up from the local gateway. I've tried that, and it doesn't seem to work. What happens is when the instance shutdown, all of its shards go into "unallocated". Then when I startup the instance, the node comes up with zero shards until I unlock shard allocation. So the locking didn't seem to help. I'm wondering if the problem is because all of my nodes are named automatically using the marvel characters list, so essentially the node name changes each time. So the lock/unlock doesn't help, because the cluster is expecting a node with a specific name and when it doesn't find it, it initializes the node with no shards. Pierce -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/5a6401b1-d6a9-4aad-807f-01f4c47a63d7%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
