exceptionfactory commented on PR #6779: URL: https://github.com/apache/nifi/pull/6779#issuecomment-1375670809
> It looks like a `ConfigMap` is created for each component that requires state management. Do you have any concern about the size of state (in bytes) that may be written to any one `ConfigMap`? > > The [maximum size of a ConfigMap is 1MiB](https://kubernetes.io/docs/concepts/configuration/configmap/#:~:text=The%20data%20stored%20in%20a,separate%20database%20or%20file%20service.). Do you anticipate any compatibility issues where a use case would work with Zookeeper but would not work with ConfigMaps? Thanks for the feedback @michael81877. The standard ZooKeeper node storage is also [limited to 1 MB](https://zookeeper.apache.org/doc/r3.8.0/apidocs/zookeeper-server/org/apache/zookeeper/ZooKeeper.html#create-java.lang.String-byte:A-java.util.List-org.apache.zookeeper.CreateMode-), so the standard size limits of a Kubernetes ConfigMap align well with current behavior. With that background and similar size limitations, I do not expect any compatibility issues based on size limitations. It is possible that other behavioral nuances could surface as a result of these alternative State Management and Leader Election implementations. -- 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: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
