> There is no way to trigger snapshots taking through Solr's admin interface > now. Taking a snapshot is a very light-weight operation. It uses hard > links so each snapshot doesn't take up much additional disk space. If you [Wu, Daniel] It is not a concern on the snapshot performance. Rather, it is the data consistency requirement.
I was also suggesting a new feature to allow sending messages to Solr through http interface and a mechanism to handling the message on the Solr server; in this case, a message to trigger snapshooter script. It seems to me, a very useful feature to help simplify operational issues. > don't want to replicate your index while the big batch job is still > running, > you can disable snappuller on the slave while the batch job is running and > enable it after the batch job has completed. > [Wu, Daniel] Yes, it can be done that way but will not be as elegant. The Solr master can be well-known among the applications; however, the slaves could be anywhere. To turn off snapulling requires the knowledge of all the Solr slaves as well as timing of the indexing. It gets ugly when there are multiple environments (e.g. dev, qa, stage, production) and multiple indexes.
