I’m a little confused here. Are you unloading/copying/creating the core on
master?
I’ll assume so since I can’t really think of how doing this on one of the other
cores would make sense…..
I’m having a hard time wrapping my head around the use-case. You’re
“delivering a new index”, which I take to mean you’re building a completely new
index somewhere else.
But you’re also updating the target index. What’s the relationship between the
index you’re “delivering” and the update sent while the core is unloaded? Are
the updates _already_ in the index you’re delivering or would you expect them
to be in the new index? Or are they just lost? Or does the indexing program
resend them after the core is created?
The unloaded core should not have any open index writers though. What I’m
guessing is that updates are coming in before the unload is complete. Instead
of a sleep, have you tried specifying the async parameter and waiting until
REQUESTSTATUS tells you the unload is complete?
Best,
Erick
> On Nov 30, 2020, at 7:41 AM, elisabeth benoit
> wrote:
>
> Hello all,
>
> We are using solr 7.3.1, with master and slave config.
>
> When we deliver a new index we unload the core, with option delete data dir
> = true, then recreate the data folder and copy the new index files into
> that folder before sending solr a command to recreate the core (with the
> same name).
>
> But we have, at the same time, some batches indexing non stop the core we
> just unloaded, and it happens quite frequently that we have an error at
> this point, the copy cannot be done, and I guess it is because of a
> write.lock file created by a solr index writer in the index directory.
>
> Is it possible, when unloading the core, to stop / kill index writer? I've
> tried including a sleep after the unload and before recreation of the index
> folder, it seems to work but I was wondering if a better solution exists.
>
> Best regards,
> Elisabeth
