You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Pulkit Chandra (JIRA)" <ji...@apache.org> on 2018/03/20 17:28:00 UTC

[jira] [Commented] (GEODE-4893) import cluster configuration command shuts down the existing servers

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

Pulkit Chandra commented on GEODE-4893:
---------------------------------------

The use case we would like to go after is

As a Operator, When I am upgrading Geode Clusters

I want to backup and restore my config and data using `export cluster-config` command and `import cluster-config` command

So that I can derisk my upgrades, In case rolling upgrade fails I can restore using these files to fill an empty cluster.

> import cluster configuration command shuts down the existing servers
> --------------------------------------------------------------------
>
>                 Key: GEODE-4893
>                 URL: https://issues.apache.org/jira/browse/GEODE-4893
>             Project: Geode
>          Issue Type: Bug
>          Components: configuration, docs, gfsh
>    Affects Versions: 1.4.0
>            Reporter: Jinmei Liao
>            Priority: Major
>
> `import cluster-configuration --zip-file-name=...` in a cluster which has locator and servers (Server has no application regions defined yet). the server is shutdown without any message in the logs as to why the server was shutdown. Gfsh says import was successful.
> On manual restart of the server I can see that the config was actually imported successfully.
>  
> We had added the feature that user can do an {{import cluster-configuration --zip-file-name=...}} without shutting down the vanilla servers, and the servers cache would just bounce. This feature needs to be re-hashed out.



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