In the Solr Wiki, Shawn Heisey writes the following:
"Regardless of the number of nodes or available resources, SolrCloud begins
to have stability problems when the number of collections reaches the low
hundreds. With thousands of collections, any little problem or change to
the cluster can cause
Following up on this thread. It was finally determined that Solr was being
hard killed. The Windows service was not giving Solr enough time to shut
down and was hard killing it. We fixed this and have not had the issue
since.
On Tue, May 31, 2016 at 1:51 PM, Jon Drews wrote:
> I forgot to
I forgot to add that this is Apache Solr 5.3.1.
There are three collections, two of which have one shard and and the other
has 3-5 shards. Approximately 200,000 documents across all collections.
Jon Drews
jondrews.com
On Tue, May 31, 2016 at 12:15 PM, Jon Drews wrote:
> We have seen
We have seen the following error on four separate instances of Solr. The
result is that all or most shards go into "Down" state and do not recover
on restart of Solr.
I'm hoping one of you has some insight into what might be causing it as we
haven't been able to track down the issue or reproduce i
understanding-solr-soft
Jon Drews
jondrews.com
On Wed, May 18, 2016 at 3:55 AM, Per Steffensen wrote:
> Hi
>
> Solr 5.1.
> Someone in production in my organization claims that even though Solrs are
> shut down gracefully, there can be huge tlogs to replay when starting Solrs
> ag
It would be really neat if Grafana supported Solr. They recently added
Elasticsearch support and I'd hope some of that code could be reused for
Solr support.
If anyone else is interested in this, please voice your support on the
Feature Request here:
https://github.com/grafana/grafana/issues/4422
