You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@storm.apache.org by "Jungtaek Lim (JIRA)" <ji...@apache.org> on 2018/02/06 08:09:00 UTC
[jira] [Updated] (STORM-2938) Share CuratorFramework instance in a
process (daemons/worker)
[ https://issues.apache.org/jira/browse/STORM-2938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jungtaek Lim updated STORM-2938:
--------------------------------
Priority: Minor (was: Major)
> Share CuratorFramework instance in a process (daemons/worker)
> -------------------------------------------------------------
>
> Key: STORM-2938
> URL: https://issues.apache.org/jira/browse/STORM-2938
> Project: Apache Storm
> Issue Type: Improvement
> Components: storm-client, storm-server
> Reporter: Jungtaek Lim
> Priority: Minor
>
> According to Curator web site, each process (nimbus, supervisor, worker, etc.) can share singleton curator framework instance per ZK cluster since it's thread-safe.
> [http://curator.apache.org/curator-framework/]
> {quote}CuratorFrameworks are allocated using the CuratorFrameworkFactory which provides both factory methods and a builder for creating instances. IMPORTANT: CuratorFramework instances are fully thread-safe. You should share one CuratorFramework per ZooKeeper cluster in your application.
> {quote}
> We are using Curator 4.0 both master and 1.x branch, hence we are good to apply this.
> We already applied this for Nimbus via STORM-2901. This issue is to track the efforts for other processes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)