You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Alexandre Rafalovitch (JIRA)" <ji...@apache.org> on 2018/06/22 13:30:00 UTC
[jira] [Resolved] (SOLR-12512) New Drive Change for existing Solr
Installation Setup
[ https://issues.apache.org/jira/browse/SOLR-12512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexandre Rafalovitch resolved SOLR-12512.
------------------------------------------
Resolution: Invalid
Fix Version/s: (was: 6.4.3)
This is not a bug/feature for Solr, but a configuration issue for your system. You are already getting help on the mailing list, which is the correct approach.
> New Drive Change for existing Solr Installation Setup
> -----------------------------------------------------
>
> Key: SOLR-12512
> URL: https://issues.apache.org/jira/browse/SOLR-12512
> Project: Solr
> Issue Type: Test
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Affects Versions: 6.4.2
> Reporter: Srinivas M
> Priority: Blocker
> Labels: features
>
> Hi Solr Team,
> As part of Solr project the installation setup and instances(including clustered solr, zk services and indexing jobs schedulers) is available in Windows 'E:\ ' drive in production environment. As business needs to remove the E:\ drive, going forward D:\ drive will be used and operational.
> Is there any possible solution/steps for the moving existing solr installation setup from 'E' drive to 'D' Drive(New Drive) without any impact to the existing application(it should not create re indexing again)
> Please let us know your suggestions/solutions.
> Your earliest help will be appreciated!!
> Thanks,
> Srinivas
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org