Bug 961317
Summary: | [CLI] HELP of some commands should to be changed | ||
---|---|---|---|
Product: | [JBoss] JBoss Data Grid 6 | Reporter: | Vitalii Chepeliuk <vchepeli> |
Component: | Server | Assignee: | Tristan Tarrant <ttarrant> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Martin Gencur <mgencur> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.1.0 | CC: | jdg-bugs, myarboro, slaskawi |
Target Milestone: | CR1 | ||
Target Release: | 6.4.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-01-28 13:27:49 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Vitalii Chepeliuk
2013-05-09 12:08:45 UTC
Fixed upstream Vitalii Chepeliuk <vchepeli> made a comment on jira ISPN-3087 But still upgrade command USAGE should be fixed. <<some space alignment needed here on 3. element in list>> 3. Invoke the... CONTAINER COMMAND--------------------------------------------------------------- SYNOPSIS container [containername] DESCRIPTION Shows the available containers or selects a container to be used as default for CLI operations ARGUMENTS <<cachename>> !!! should be "containername" (optional) the name of the container to set as default for the following operations And usage of upgrade command<<<<<<<<<<<<<<<<<<< USAGE In order to perform a rolling upgrade of a HotRod cluster, the following steps must be taken 1. Configure and start a new cluster with a RemoteCacheStore pointing to the old cluster and the hotRodWrapping flag enabled 2. Configure all clients so that they will connect to the new cluster <<some space alignment needed here on 3. >> 3. Invoke the!!!<<<<<<<<<<<<<<<<<<<<<<<here some tabbing problem but if that is difficult to change we can omit it upgrade --dumpkeys command on the old cluster for all of the caches that need to be migrated 4. Invoke the upgrade --synchronize=hotrod command on the new cluster to ensure that all data is migrated from the old cluster to the new one 5. Invoke the upgrade --disconnectsource=hotrod command on the new cluster to disable the RemoteCacheStore used to migrate the data 6. Switch off the old cluster |