incubator-blur-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aaron McCurry <>
Subject Re: cluster - tableuri configuration
Date Fri, 24 Apr 2015 16:16:24 GMT
Perhaps we should make the controllers that need to carry out cluster
specific operations route to a shard server in the given cluster.  They way
they don't need to have the same write permissions and shard cluster
knowledge as the shard servers.  What do you think?


On Thu, Apr 23, 2015 at 3:03 PM, Tim Williams <> wrote:

> I think the writings on the wall that the future of blur deployments
> will be in a managed environment vs the current
> self-managed-script-based deployments.  I'm thinking Yarn, Cloudera
> Manager, etc.  With some changes to the startup scripts this isn't so
> bad but one small challenge is the default table uri which is
> currently configured via  I'm wondering if
> there's a downside to just sticking that in ZK when the cluster first
> gets registered (e.g. BlurUtil.setupZookeeper()) ?  That way
> controller's of a different cluster (I know they don't really "belong"
> to the cluster) need only a ZK connection to front different shard
> clusters.
> Thoughts?
> --tim

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message