[
https://issues.apache.org/jira/browse/SOLR-9554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15529863#comment-15529863
]
Mikhail Khludnev edited comment on SOLR-9554 at 9/28/16 2:43 PM:
-----------------------------------------------------------------
I make test really really mad. It synchronizes race to reproduce it. Note: to
reproduce the NPE failure you need to run it a few times \-Dtests.iters=10,
just because now {{shuffle(winner,looser)}} adds one more race.
Now we can think how to fix it, and it's worth to do.
But might be more important question how to avoid such _races in zoo_ once and
for all or detect them automatically. Can we prohibit writes to Zookeeper at
all?
was (Author: mkhludnev):
I make test really really mad. It synchronizes race to reproduce it. Note: to
reproduce the NPE failure you need to run it a few times \-Dtests.iters=10,
just because now {{shuffle(winner,looser)}} adds one more race.
Now we can think how to fix it, and it's a really good idea.
But might be more important question how to how to avoid such races in zoo once
and for all or detect them automatically. Can we prohibit writes to Zookeeper
at all?
> Multiple ManagedIndexSchemaFactory upgrades running simultaneously can clash,
> causing cores not to load
> -------------------------------------------------------------------------------------------------------
>
> Key: SOLR-9554
> URL: https://issues.apache.org/jira/browse/SOLR-9554
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Alan Woodward
> Attachments: SOLR-9554.patch, SOLR-9554.patch, SOLR-9554.patch,
> SOLR-9554.patch
>
>
> If a collection is created using a configset with a ManagedSchemaFactory but
> no managed-schema file, then multiple cores may try and convert the schema
> file simultaneously.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
