Thank you, Shalin.
Here is the Jira https://issues.apache.org/jira/browse/SOLR-12585
On Mon, Jul 23, 2018 at 11:21 PM, Shalin Shekhar Mangar <
shalinman...@gmail.com> wrote:
> Can you please open a Jira issue? I don't think we handle DNS problems very
> well during startup. Thanks.
>
> On Tue,
Can you please open a Jira issue? I don't think we handle DNS problems very
well during startup. Thanks.
On Tue, Jul 24, 2018 at 2:31 AM Susheel Kumar wrote:
> Something messed up with DNS which resulted into unknown host exception for
> one the machines in our env and caused Solr to throw the
Something messed up with DNS which resulted into unknown host exception for
one the machines in our env and caused Solr to throw the above exception
Eric, I have the Solr configured using service installation script and
the ZK_HOST entry in
And how do you start Solr? Do you use the entire 3-node ensemble address?
On Mon, Jul 23, 2018 at 12:55 PM, Michael Braun wrote:
> Per the exception, this looks like a network / DNS resolution issue,
> independent of Solr and Zookeeper code:
>
> Caused by: org.apache.solr.common.SolrException:
>
Per the exception, this looks like a network / DNS resolution issue,
independent of Solr and Zookeeper code:
Caused by: org.apache.solr.common.SolrException:
java.net.UnknownHostException: ditsearch001.es.com: Name or service not
known
Is this address actually resolvable at the time?
On Mon,
In usual circumstances when one Zookeeper goes down while others 2 are up,
Solr continues to operate but when one of the ZK machine was not reachable
with ping returning below results, Solr count't starts. See stack trace
below
ping: cannot resolve ditsearch001.es.com: Unknown host
Setup: Solr
