[ 
https://issues.apache.org/jira/browse/GEODE-5053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16436297#comment-16436297
 ] 

Barbara Pruijn commented on GEODE-5053:
---------------------------------------

Since there is a use case where specific configuration gets added to the 
cluster before
{code:java}
import cluster-configuration{code}
is called, we need to have the option to wipe out any existing configuration 
when importing a preferred configuration.

The proposal is to add the option -force: 
{code:java}
import cluster-configuration --force{code}

The behavior of the -force is that any existing configuration on the cluster 
will be replaced with the configuration provided in the import command.

> Import and export should be supported with full cluster running
> ---------------------------------------------------------------
>
>                 Key: GEODE-5053
>                 URL: https://issues.apache.org/jira/browse/GEODE-5053
>             Project: Geode
>          Issue Type: Improvement
>          Components: gfsh, management
>    Affects Versions: 1.4.0, 1.5.0
>            Reporter: Pulkit Chandra
>            Priority: Major
>
> We want to provide support to export /import config and data. We dont have 
> the ability to just run locators and not servers as we use BOSH to manage 
> Geode, which is required for `import` today
> **Why** : As a operator if data contained in Geode is important, I would like 
> to ensure I can back it up. Use cases range from ensuring your data doesnt 
> get lost to migrating your data to another cluster.
> **How**: `Import` and `export` command should be the way to go
> **Limitations**: Cant have locators running and servers not running. Full 
> cluster would be running before import is called. We can do rolling restart, 
> if that is needed.
>  
> its related to the issue https://issues.apache.org/jira/browse/GEODE-4893



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to