ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Valentin Kulichenko <valentin.kuliche...@gmail.com>
Subject Re: Cluster name
Date Thu, 16 Mar 2017 10:57:34 GMT
Alexey,

How does the workflow look like? How do you add a cluster to this dropdown
on the console? I think that assigning a name should be part of this
process and should happen on the console itself.

Adding yet another "name" to configuration will only confuse users even
more.

-Val

On Thu, Mar 16, 2017 at 9:59 AM, Sergi Vladykin <sergi.vladykin@gmail.com>
wrote:

> I don't like to add anything like this into Ignite config. It is a problem
> of Web console how to name or rename different clusters for a user, but not
> Ignite cluster itself.
>
> Sergi
>
> 2017-03-16 4:21 GMT+03:00 Dmitriy Setrakyan <dsetrakyan@apache.org>:
>
> > I am OK with having a cluster name, but I would like us to generate one
> > automatically, if users do not define one explicitly. How about
> > "cluster_timestamp"?
> >
> > On Wed, Mar 15, 2017 at 5:38 PM, Alexey Kuznetsov <akuznetsov@apache.org
> >
> > wrote:
> >
> > > Igniters,
> > >
> > > I'm planning to start working on multi cluster support for Web Console
> > > in order to be able to execute SQL queries on different clusters just
> by
> > > selecting
> > > target cluster from drop-down.
> > >
> > > But Ignite does not have any cluster wide name.
> > >
> > > So, how about to add to Ignite (may be 2.0) property "Cluster Name" to
> > > Ignite configuration?
> > >
> > > Or as alternative way it could use "Mandatory User Defined Attribute".
> > >
> > > Node should be rejected to join cluster with different "Cluster Name"
> > >
> > >
> > > Thoughts?
> > >
> > > --
> > > Alexey Kuznetsov
> > >
> >
>

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