Barbara Pruijn commented on GEODE-5053:

The precondition of the use of this -force option is that you have exported 
your configuration and data (the configuration matches the data that you have 
exported). And then when you do a force import, the configuration and data that 
you import are in synch.

This is an advanced option, not meant for the beginner.

Maybe we should add a reaffirming question: "Are you sure? Your configuration 
needs to be consistent with the data that you will import. Y/n".

When this option is run in a script, you should know what you are doing.

> 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: docs, 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

Reply via email to