Will Berkeley has uploaded this change for review. ( http://gerrit.cloudera.org:8080/10962
Change subject: [java] Add extra info about using multiple clients ...................................................................... [java] Add extra info about using multiple clients The AsyncKuduClient and KuduClient are meant to map 1-1 with Kudu clusters used by an application. In particular, an application shouldn't make more than one client per cluster. This patch adds a note to this effect to the AsyncKuduClient javadoc. Additionally, some use cases require using multiple clients in multiple applications running on the same machine. For example, to provide very strict classpath isolation, or to run applications on different JVM versions, or even for extra security by isolating different data flows in different processes. In this case, I've seen client instances put pressure on thread limits on machines with a lot of cores because the AsyncKuduClient starts at least (2 * #cpu) threads for a netty threadpool. This patch also adds advice to adjust the netty worker count to help users with this case. Change-Id: I34242862ee6d806b74d7717399e5fd0260dece89 --- M java/kudu-client/src/main/java/org/apache/kudu/client/AsyncKuduClient.java 1 file changed, 10 insertions(+), 2 deletions(-) git pull ssh://gerrit.cloudera.org:29418/kudu refs/changes/62/10962/1 -- To view, visit http://gerrit.cloudera.org:8080/10962 To unsubscribe, visit http://gerrit.cloudera.org:8080/settings Gerrit-Project: kudu Gerrit-Branch: master Gerrit-MessageType: newchange Gerrit-Change-Id: I34242862ee6d806b74d7717399e5fd0260dece89 Gerrit-Change-Number: 10962 Gerrit-PatchSet: 1 Gerrit-Owner: Will Berkeley <[email protected]>
