: I recently set up Solr with distribution on a couple of servers. I just : learned that our network policies do not permit us to use SSH with : passphraseless keys, and the snappuller script uses SSH to examine the master : Solr instance's state before it pulls the newest index via rsync.
you may want to question/clarify this policy ... while it's generally a good idea to have a policy like this for *users* there's very little reason for it when you're dealing with "role users" ... accounts that exists solely to execute specific applications nad have limitited permissions. if you have a "solruser" with a passphraseless key, which only works on the specific machines running solr, and solruser can only read/write the specific files it needs to for replication, there's very little downside. : scripts, as required) to eliminate this dependency on SSH. I thought I ask the : list in case anyone has experience with this same situation or any insights : into the reasoning behind requiring SSH access to the master instance. i haven't looked at those scripts in a while, but i believe it's two fold: 1) get the name of hte most current snapshoot 2) notify the master which snapshot is being used (for the status page) -Hoss
