Moving shards is done via replication. Replication accepts an index from another SolrCore, and it cares nothing about what data directory it lived in. It only cares about it's local data directory - it will merge/replace into it's local data directory. It will retrieve the index data through http calls. The data directory is a local property for each SolrCore and other nodes in the cloud do not need to know about it.
- Mark On Jan 22, 2013, at 11:33 AM, Otis Gospodnetic <otis.gospodne...@gmail.com> wrote: > Thanks Markus. Yes, I'm after the actual, physical directory on the local > FS (local to wherever the shard lives). > > Is this information in index.properties reliable? Can't shards be moved > around in the cluster, say when a node that had some shard fails? When > this happens, is the new index directory for the shard(s) that got moved > updated in that index.properties? > > Thanks, > Otis > -- > Solr & ElasticSearch Support > http://sematext.com/ > > > > > > On Tue, Jan 22, 2013 at 10:44 AM, Markus Jelsma > <markus.jel...@openindex.io>wrote: > >> Hi Otis, >> >> I assume you're talking about the actual index directory? This is recorded >> in the index.properties file in the dataDir. >> >> Cheers, >> >> >> -----Original message----- >>> From:Otis Gospodnetic <otis.gospodne...@gmail.com> >>> Sent: Tue 22-Jan-2013 16:39 >>> To: solr-user@lucene.apache.org >>> Subject: Shard index dir paths in Cluster state JSON? >>> >>> Hi, >>> >>> I noticed Cluster state JSON doesn't include information about physical >>> directory for each shard in the cluster. Is there a reason for that? >> This >>> info is present in Solr Admin pages, but should it not be present in >>> Cluster state in ZK? >>> >>> Thanks, >>> Otis >>> -- >>> Solr & ElasticSearch Support >>> http://sematext.com/ >>> >>
