les. So at that point, the index is gone.
I'd love to prevent this from happening a third time. It's super baffling.
Any ideas?
Mike
On Tue, Jun 20, 2017 at 12:38 PM Mike Lissner <
mliss...@michaeljaylissner.com> wrote:
> Thanks for the suggestions everybody.
>
>
e SWAP index functionality, so the
above is just in case somebody wants to try to track this down. I'll
probably take those logs offline after a week or two.
Mike
On Tue, Jun 20, 2017 at 7:20 AM Shawn Heisey wrote:
> On 6/14/2017 12:26 PM, Mike Lissner wrote:
> > We are replacing
s <
> hastings.recurs...@gmail.com>
> wrote:
>
> > I dont have an answer to why the folder got cleared, however i am
> wondering
> > why you arent using basic replication to do this exact same thing, since
> > solr will natively take care of all this for you with no
We are replacing a drive mounted at /old with one mounted at /new. Our
index currently lives on /old, and our plan was to:
1. Create a new index on /new
2. Reindex from our database so that the new index on /new is properly
populated.
3. Stop solr.
4. Symlink /old to /new (Solr now looks for the i
Hi all,
I've had a rotten day today because of Solr. I want to share my experience
and perhaps see if we can do something to fix this particular situation in
the future.
Solr currently has two ways to get grouped results (so far!). You can
either use Result Grouping or you can use the Collapsing
Thanks for the replies. I made the changes so that the external file field
is loaded per:
On Fri, Oct 7, 2016 at 8:18 PM Erick Erickson
wrote:
> What you haven't mentioned is how often you add new docs. Is it once a
> day? Steadily
> from 8:00 to 17:00?
>
Alas, it's a steady trickle during business hours. We're ingesting court
documents as they're posted on court websites, then sendi
On Sat, Oct 8, 2016 at 8:46 AM Shawn Heisey wrote:
> Most soft commit
> > documentation talks about setting up soft commits with of
> about a
> > second.
>
> IMHO any documentation that recommends autoSoftCommit with a maxTime of
> one second is bad documentation, and needs to be fixed. Where h
I have an index of about 4M documents with an external file field
configured to do boosting based on pagerank scores of each document. The
pagerank file is about 93MB as of today -- it's pretty big.
Each day, I add about 1,000 new documents to the index, and I need them to
be available as soon as
