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, Jul
ld be sensitive to that.
> >
> > WARNING: haven't done this myself so don't have any examples to point
> to
> >
> > Best,
> > Erick
> >
> > On Tue, Jun 12, 2018 at 8:34 AM, Shawn Heisey
> wrote:
> >> On 6/12/2018 9:12 AM,
We have a case of a Solr Cloud cluster with different kinds of nodes - some
may have significant differences in hardware specs (50-100% more
HD/RAM/CPU, etc). Ideally nodes with increased resources could take on more
shard replicas.
It looks like the Collections API (
https://lucene.apache.org/sol
Believe this is reported in https://issues.apache.org/jira/browse/SOLR-10471
On Mon, Jan 29, 2018 at 2:55 PM, Markus Jelsma
wrote:
> Hello SG,
>
> The default in solr.in.sh is commented so it defaults to the value set in
> bin/solr, which is fifteen seconds. Just uncomment the setting in
> solr
I went ahead and resolved the jira - it was never seen again by us in later
versions of Solr. There are a number of bug fixes since the 6.2 release, so
I personally recommend updating!
On Wed, Nov 22, 2017 at 11:48 AM, Pushkar Raste
wrote:
> As mentioned in the JIRA, exception seems to be coming
Have you attached JVisualVM or a similar application to the process to
sample where the time is being spent? It can be very helpful for debugging
this sort of problem.
On Fri, Aug 18, 2017 at 12:37 PM, Joe Obernberger <
joseph.obernber...@gmail.com> wrote:
> Indexing about 15 million documents pe
Have you attached JVisualVM or a similar tool for sampling when Solr is
answering the requests with highlight? What relevant methods are coming up?
On Wed, Aug 9, 2017 at 11:26 AM, sasarun wrote:
> Hi Amrit,
>
> Thanks for the response. I did went through both and that is how I landed
> up
> wit
