andyvuong opened a new pull request #1223: SOLR-14213: Configuring Solr Cloud 
to use Shared Storage
URL: https://github.com/apache/lucene-solr/pull/1223
 
 
   This is an initial PR that allows Solr Cloud to be configured to use shared 
storage or not. Prior to this, shared storage is "on" by default with 
components be lazily initialized as needed e.g. when a collection of type 
shared is created. This of course is difficult to do correctly. 
   
   The solution proposed by this PR is check for the presence of a 
<sharedStorage> section in solr.xml that indicates the user's intention to use 
shared storage and initiate the components on startup. This also sets the stage 
for future work we need to do to move some hard coded values into configurable 
parameters that would be specified in sharedStorage. See the JIRA for further 
discussion. 
   
   Changes:
   - solr.xml supports a bare-bone <sharedStorage></sharedStorage> section that 
should be added to enable shared storage on the cluster
   - If core discovery discovers a shared collection but the cluster is not 
shared storage enabled, this is considered a fatal error (user error) and solr 
will not start in stable state
   - Collections of type shared can only be created if the cluster is shared 
storage enabled (all shared functionality is already gated behind the presence 
of shared replicas within shared collections)
   - Added a test in SimpleSharedStorageCollectionTest to ensure proper feature 
gating
   - Refactored our test setup for anything using SolrCloudSharedStoreTestCase 
to automatically start a mini solr cluster with a solr.xml (added 
solr-sharedstorage.xml) containing the sharedStorage section. Also made a 
change moving the local FS client setup into this parent class  so that any 
extending test classes don't need to worry about setting the shared directory 
up unless they want to mock the client themselves

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to