[GitHub] [accumulo-website] dlmarion commented on a diff in pull request #367: update upgrade instructions to include prop conversion

[GitBox <gi...@apache.org>]

dlmarion commented on code in PR #367:
URL: https://github.com/apache/accumulo-website/pull/367#discussion_r1014092570


##########
_docs-2/administration/upgrading.md:
##########
@@ -38,6 +56,60 @@ will then need to transfer the contents of the current individual files to this
 **Warning**: Upgrading a previously encrypted instance is not supported as the implementation
 and properties have changed.
 
+## Upgrading from 2.0 to 2.1
+
+Note, the process fro upgrading to 2.1 assumes that you have already upgraded to 2.0.  Upgrading from a version prior 

Review Comment:
   ```suggestion
   Note, the process for upgrading to 2.1 assumes that you have already upgraded to 2.0.  Upgrading from a version prior 
   ```



##########
_docs-2/administration/upgrading.md:
##########
@@ -38,6 +56,60 @@ will then need to transfer the contents of the current individual files to this
 **Warning**: Upgrading a previously encrypted instance is not supported as the implementation
 and properties have changed.
 
+## Upgrading from 2.0 to 2.1
+
+Note, the process fro upgrading to 2.1 assumes that you have already upgraded to 2.0.  Upgrading from a version prior 
+to 2.0 may work, but is unsupported and untested.  The basic idea is to: 

Review Comment:
   This statement doesn't agree with the upgrading from 1.10.



##########
_docs-2/administration/upgrading.md:
##########
@@ -38,6 +56,60 @@ will then need to transfer the contents of the current individual files to this
 **Warning**: Upgrading a previously encrypted instance is not supported as the implementation
 and properties have changed.
 
+## Upgrading from 2.0 to 2.1

Review Comment:
   Should the title here be "Upgrading from 1.10 or 2.0 to 2.1"? Upgrading from 1.10 is supported and tested IIRC



##########
_docs-2/administration/upgrading.md:
##########
@@ -38,6 +56,60 @@ will then need to transfer the contents of the current individual files to this
 **Warning**: Upgrading a previously encrypted instance is not supported as the implementation
 and properties have changed.
 
+## Upgrading from 2.0 to 2.1
+
+Note, the process fro upgrading to 2.1 assumes that you have already upgraded to 2.0.  Upgrading from a version prior 
+to 2.0 may work, but is unsupported and untested.  The basic idea is to: 
+
+- install and configure 2.1. See ({% durl /in-depth-installation%}) for configuration information
+- stop Accumulo 2.0
+- update your environment to point to 2.1 executable path.
+- (optional) create a ZooKeeper snapshot
+- (optional) run the configuration upgrade utility
+- start Accumulo 2.1
+
+The particular order for your installation may differ depending on how you choose to install Accumulo. You may want
+to stop Accumlo first if your installation is going to over-write your current installation.  The important part is that
+Accumulo 2.1 manager does not start running before the 2.1 configuration is in place for all of your nodes and if you
+want to run the optional steps to create a ZooKeeper snapshot and run the configuration update stand-alone utility.
+
+### Create ZooKeeper snapshot (optional)

Review Comment:
   ```suggestion
   ### Create ZooKeeper snapshot (optional, but recommended)
   ```



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@accumulo.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org