Thanks again for the information Shawn. 1) The long running process I told earlier was about Backup. I have written a custom BackupHandler to backup the index files to a Cloud storage following the ReplicationHandler class. I’m just wondering how does switching between transient state affect such processes. Does ReplicationHandler not get affected if a replication job is in progress and Solr decided to unload this core in between the process.
Thanks, Shashank On 3/29/17, 4:41 PM, "Shawn Heisey" <apa...@elyograg.org> wrote: >On 3/29/2017 4:50 PM, Shashank Pedamallu wrote: >> Thank you very much for the response. Is there no definite way of >> ensuring that Solr does not switch transient states by an api? Like >> solrCore.open() and solrCore.close()? > >I am not aware of any way to tell Solr to NOT unload a core when all of >the following conditions have been met: > >1) Another transient core must be loaded because it has been accessed. >2) The core in question has been marked transient. >3) The transientCacheSize has already been reached. >4) The core in question is the one with the earliest timestamp. > >I checked the code, but could not determine whether the oldest core is >decided by core load time or by core access time. My guess is that it is >decided by the load time, because this is the option that would have the >best performance. > >If it's important that this core never gets unloaded, then you'll want >to remove the transient property. > >Thanks, >Shawn >
