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

ASF GitHub Bot commented on GEODE-401:
--------------------------------------

GitHub user jinmeiliao opened a pull request:

    https://github.com/apache/incubator-geode/pull/67

    GEODE-401: upgrade log4j from 2.1 to 2.5. Remove our own configuratio…

    …n watcher since log4j now has an almost the same implementation.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jinmeiliao/incubator-geode feature/GEODE-401

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-geode/pull/67.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #67
    
----
commit ff34c46350bf1b06258c2b0af258dbd8732a91a7
Author: Jinmei Liao <[email protected]>
Date:   2016-01-06T17:02:44Z

    GEODE-401: upgrade log4j from 2.1 to 2.5. Remove our own configuration 
watcher since log4j now has an almost the same implementation.

----


> gfsh backup disk-store does not print offline members
> -----------------------------------------------------
>
>                 Key: GEODE-401
>                 URL: https://issues.apache.org/jira/browse/GEODE-401
>             Project: Geode
>          Issue Type: Bug
>          Components: persistence
>    Affects Versions: 1.0.0-incubating
>            Reporter: Karen Smoler Miller
>            Assignee: Jinmei Liao
>            Priority: Minor
>              Labels: gfsh
>
> Test environment has 3 servers running with 1 REPLICATE_PERSISTENT region.  
> Make a backup with all 3 servers online:
> {noformat}
> gfsh>backup disk-store --dir=/Users/kmiller/tryit/trybackup/mybackupdir
> The following disk stores were backed up successfully
>  Member  |                 UUID                 |                             
>  Directory                              | Host
> -------- | ------------------------------------ | 
> ------------------------------------------------------------------- | 
> ---------------------------------
> server2  | 49ec8158-fa55-4340-a20c-bc20d9d90bbb | 
> /Users/kmiller/tryit/trybackup/try2/server2/.                       | 
> pdx2-office-dhcp10.eng.vmware.com
> server1  | 4b6ef006-c585-48de-83a2-74f79199e2fa | 
> /Users/kmiller/tryit/trybackup/try1/server1/.                       | 
> pdx2-office-dhcp10.eng.vmware.com
> server3  | b9e6771e-ab84-4808-a081-6c0134144fd9 | 
> /Users/kmiller/tryit/trybackup/try3/server3/.                       | 
> pdx2-office-dhcp10.eng.vmware.com
> locator1 | 5bce95be-5bb6-4be6-adc2-aa18dde1c2b6 | 
> /Users/kmiller/tryit/trybackup/try1/locator1/ConfigDiskDir_locator1 | 
> pdx2-office-dhcp10.eng.vmware.com
> {noformat}
> Here's the output once server 3 is stopped.  Notice that there is no 
> indication that a backup was not taken for server 3's disk store, since 
> server 3 is offline.
> {noformat}
> gfsh>stop server --name=server3
> gfsh>backup disk-store --dir=/Users/kmiller/tryit/trybackup/mybackupdir
> The following disk stores were backed up successfully
>  Member  |                 UUID                 |                             
>  Directory                              | Host
> -------- | ------------------------------------ | 
> ------------------------------------------------------------------- | 
> ---------------------------------
> server2  | 49ec8158-fa55-4340-a20c-bc20d9d90bbb | 
> /Users/kmiller/tryit/trybackup/try2/server2/.                       | 
> pdx2-office-dhcp10.eng.vmware.com
> server1  | 4b6ef006-c585-48de-83a2-74f79199e2fa | 
> /Users/kmiller/tryit/trybackup/try1/server1/.                       | 
> pdx2-office-dhcp10.eng.vmware.com
> locator1 | 5bce95be-5bb6-4be6-adc2-aa18dde1c2b6 | 
> /Users/kmiller/tryit/trybackup/try1/locator1/ConfigDiskDir_locator1 | 
> pdx2-office-dhcp10.eng.vmware.com
> {noformat}
> There ought to be an additional line in this output that states that no 
> backup was made for server 3.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to