lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jerome Yang <jey...@pivotal.io>
Subject Re: Reload schema or configs failed then drop index, can not recreate that index.
Date Fri, 25 Nov 2016 02:05:00 GMT
Thanks Erick!

On Fri, Nov 25, 2016 at 1:38 AM, Erick Erickson <erickerickson@gmail.com>
wrote:

> This is arguably a bug. I raised a JIRA, see:
>
>  https://issues.apache.org/jira/browse/SOLR-9799
>
> Managed schema is not necessary to show this problem, generically if
> you upload a bad config by whatever means, then
> RELOAD/DELETE/correct/CREATE it fails. The steps I outlined
> in the JIRA force the same replica to be created on the same Solr instance
> to insure it can be reproduced at will.
>
> In the meantime, you can keep from having to restart Solr by:
> - correcting the schema
> - pushing it to Zookeeper (managed schema API does this for you)
> - RELOAD the collection (do NOT delete it first).
>
> Since you can just RELOAD, I doubt this will be a high priority though.
>
> Thanks for reporting!
> Erick
>
>
> On Wed, Nov 23, 2016 at 6:37 PM, Jerome Yang <jeyang@pivotal.io> wrote:
> > It's solr 6.1, cloud mode.
> >
> > Please ignore the first message. Just take check my second email.
> >
> > I mean if I modify an existing collections's managed-schema and the
> > modification makes reload collection failed.
> > Then I delete the collection, and delete the configs from zookeeper.
> > After that upload an configs as the same name as before, and the
> > managed-schema is the not modified version.
> > Then recreate the collection, it will throw an error, "core already
> > exists". But actually it's not.
> > After restart the whole cluster, recreate collection will success.
> >
> > Regards,
> > Jerome
> >
> >
> > On Wed, Nov 23, 2016 at 3:26 PM, Erick Erickson <erickerickson@gmail.com
> >
> > wrote:
> >
> >> The mail server is pretty heavy-handed at deleting attachments, none of
> >> your
> >> (presumably) screenshots came through.
> >>
> >> You also haven't told us what version of Solr you're using.
> >>
> >> Best,
> >> Erick
> >>
> >> On Tue, Nov 22, 2016 at 6:25 PM, Jerome Yang <jeyang@pivotal.io> wrote:
> >> > Sorry, wrong message.
> >> > To correct.
> >> >
> >> > In cloud mode.
> >> >
> >> >    1. I created a collection called "test" and then modified the
> >> >    managed-schemaI, write something wrong, for example
> >> >    "<uniqueKey>id</WRONG>", then reload collection would failed.
> >> >    2. Then I drop the collection "test" and delete configs form
> >> zookeeper.
> >> >    It works fine. The collection is removed both from zookeeper and
> hard
> >> disk.
> >> >    3. Upload the right configs with the same name as before, try to
> >> create
> >> >    collection as name "test", it would failed and the error is "core
> >> with name
> >> >    '*' already exists". But actually not.
> >> >    4. The restart the whole cluster, do the create again, everything
> >> works
> >> >    fine.
> >> >
> >> >
> >> > I think when doing the delete collection, there's something still
> hold in
> >> > somewhere not deleted.
> >> > Please have a look
> >> >
> >> > Regards,
> >> > Jerome
> >> >
> >> > On Wed, Nov 23, 2016 at 10:16 AM, Jerome Yang <jeyang@pivotal.io>
> wrote:
> >> >
> >> >> Hi all,
> >> >>
> >> >>
> >> >> Here's my situation:
> >> >>
> >> >> In cloud mode.
> >> >>
> >> >>    1. I created a collection called "test" and then modified the
> >> >>    managed-schemaI got an error as shown in picture 2.
> >> >>    2. To get enough error message, I checked solr logs and get
> message
> >> >>    shown in picture 3.
> >> >>    3. If I corrected the managed-schema, everything would be fine.
> But I
> >> >>    dropped the index. The index couldn't be created it again, like
> >> picture 4.
> >> >>    I restarted gptext using "gptext-start -r" and recreated the
> index,
> >> it was
> >> >>    created successfully like picture 5.
> >> >>
> >> >>
> >>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message