Github user arunmahadevan commented on a diff in the pull request:
https://github.com/apache/storm/pull/1950#discussion_r123958025
--- Diff: docs/State-checkpointing.md ---
@@ -70,6 +70,46 @@ json config with the following properties.
}
}
```
+
+For Redis Cluster state this is a json config with the following
properties.
+
+```
+ {
+ "keyClass": "Optional fully qualified class name of the Key type.",
+ "valueClass": "Optional fully qualified class name of the Value type.",
+ "keySerializerClass": "Optional Key serializer implementation class.",
+ "valueSerializerClass": "Optional Value Serializer implementation
class.",
+ "jedisClusterConfig": {
+ "nodes": ["localhost:7379", "localhost:7380", "localhost:7381"],
+ "timeout": 2000,
+ "maxRedirections": 5
+ }
+ }
+```
+
+NOTE: If you used Redis state with Storm version 1.1.0 or earlier, you
would need to also migrate your state since the representation of state has
changed
+from Base64-encoded string to binary to reduce huge overhead. Storm
provides a migration tool to help, which is placed on `storm-redis-example`
module.
+
+Please download the source from download page or clone the project, and
type below command:
+
+```
+mvn clean install -DskipTests
+cd examples/storm-redis-examples
+<storm-installation-dir>/bin/storm jar target/storm-redis-examples-*.jar
org.apache.storm.redis.tools.Base64ToBinaryStateMigrationUtil [options]
+```
+
+Supported options are listed here:
+
+```
+ -d,--dbnum <arg> Redis DB number (default: 0)
+ -h,--host <arg> Redis hostname (default: localhost)
+ -n,--namespace <arg> REQUIRED the list of namespace to migrate.
+ -p,--port <arg> Redis port (default: 6379)
+ --password <arg> Redis password (default: no password)
+```
+
+You can provide multiple `namespace` options to migrate multiple
namespaces at once. Other options are not mandatory.
--- End diff --
May be better to show an example of the command with a couple of namespaces.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
