guozhangwang commented on a change in pull request #11184:
URL: https://github.com/apache/kafka/pull/11184#discussion_r690792216



##########
File path: docs/streams/upgrade-guide.html
##########
@@ -52,6 +52,15 @@ <h1>Upgrade Guide and API Changes</h1>
         <li> restart all new ({{fullDotVersion}}) application instances </li>
     </ul>
 
+    <p>
+        Since 3.0.0 release, Kafka Streams uses a newer RocksDB version which 
bumped its footer version persisted on files.
+        This means that old versioned RocksDB would not be able to recognize 
the bytes written by that newer versioned RocksDB,
+        and hence it is harder to downgrade Kafka Streams with version 3.0.0 
or newer to older versions in-flight.
+        Users need to wipe out the local RocksDB state stores written by the 
new versioned Kafka Streams before swapping in the
+        older versioned Kafka Streams bytecode, which when then restore the 
state stores with the old versioned footer from the

Review comment:
       ack.

##########
File path: docs/streams/upgrade-guide.html
##########
@@ -52,6 +52,15 @@ <h1>Upgrade Guide and API Changes</h1>
         <li> restart all new ({{fullDotVersion}}) application instances </li>
     </ul>
 
+    <p>
+        Since 3.0.0 release, Kafka Streams uses a newer RocksDB version which 
bumped its footer version persisted on files.

Review comment:
       Ack.

##########
File path: docs/streams/upgrade-guide.html
##########
@@ -52,6 +52,15 @@ <h1>Upgrade Guide and API Changes</h1>
         <li> restart all new ({{fullDotVersion}}) application instances </li>
     </ul>
 
+    <p>
+        Since 3.0.0 release, Kafka Streams uses a newer RocksDB version which 
bumped its footer version persisted on files.
+        This means that old versioned RocksDB would not be able to recognize 
the bytes written by that newer versioned RocksDB,

Review comment:
       Ack.




-- 
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: jira-unsubscr...@kafka.apache.org

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


Reply via email to