Hi,
The community has just voted to phase out Ignite Web Console:
https://issues.apache.org/jira/browse/IGNITE-13038
GridGain's version of Web Console incorporates all the features of Ignite
counterpart and should support the feature you are checking out. Feel free
to switch to that tool or
Hi - Just checking if this feature of naming a cluster from the web console
has been added now? If yes how do we do it?
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Kirill Tkalenko created IGNITE-12162:
Summary: Add the cluster name to the promt message "--deactivate"
the control.sh
Key: IGNITE-12162
URL: https://issues.apache.org/jira/browse/IG
The system properties are a blackbox that few of the users are aware about. How
do we decide where a property should go? Any rule for that?
—
Denis
> On Oct 12, 2017, at 1:43 AM, Alexey Goncharuk <alexey.goncha...@gmail.com>
> wrote:
>
> The same way as if one nod
The same way as if one node had cluster name in configuration and the other
did not - they should not discover each other.
2017-10-12 11:40 GMT+03:00 Alexey Kuznetsov <akuznet...@apache.org>:
> Alexey,
>
> How we would handle situation if first node has one name in sys props a
Alexey,
How we would handle situation if first node has one name in sys props and
second has another name or does not have any name?
On Thu, Oct 12, 2017 at 3:19 PM, Alexey Goncharuk <
alexey.goncha...@gmail.com> wrote:
> Personally, I would still add an ability to set cluster
Personally, I would still add an ability to set cluster name via the system
property because in some cases this may be convenient (starting multiple
clusters with the same configuration from ignite.sh, embedded deployments
when configuration change is not available).
--AG
2017-10-11 14:13 GMT+03
Alexey Kuznetsov created IGNITE-6597:
Summary: Add cluster name to IgniteConfiguration
Key: IGNITE-6597
URL: https://issues.apache.org/jira/browse/IGNITE-6597
Project: Ignite
Issue Type
Created issue: https://issues.apache.org/jira/browse/IGNITE-6597
On Wed, Oct 11, 2017 at 5:21 PM, Sasha Belyak <rtsfo...@gmail.com> wrote:
> Cluster name - yes
> Limit cluster building by cluster name - yes
> env/system property - no, let's add cluster name to ignite configurati
Cluster name - yes
Limit cluster building by cluster name - yes
env/system property - no, let's add cluster name to ignite configuration.
2017-10-11 17:08 GMT+07:00 Dmitry Pavlov <dpavlov@gmail.com>:
> I like this idea too. Some imdg have such feature and allow to limit
> clus
I like this idea too. Some imdg have such feature and allow to limit
cluster building only within cluster name.
ср, 11 окт. 2017 г. в 12:38, Alexey Kuznetsov <akuznet...@apache.org>:
> Hi,
>
> I'd like to up this thread for discussion.
>
> It seems that cluster name could be
ey Kuznetsov <akuznet...@apache.org>
> wrote:
>
> > Hi,
> >
> > I'd like to up this thread for discussion.
> >
> > It seems that cluster name could be very useful together with multicast
> > discovery - do not accept nodes with different clu
Alex,
Agree. Looks like a useful feature, especially for testing purposes.
On Wed, Oct 11, 2017 at 12:38 PM, Alexey Kuznetsov <akuznet...@apache.org>
wrote:
> Hi,
>
> I'd like to up this thread for discussion.
>
> It seems that cluster name could be very useful to
Hi,
I'd like to up this thread for discussion.
It seems that cluster name could be very useful together with multicast
discovery - do not accept nodes with different cluster name.
By default, let's set cluster name to "DEFAULT_CLUSTER".
Thoughts?
On Fri, Mar 17, 2017 at 12:30 A
, then we automatically assign the
timestamp of the first node or some UUID as a cluster name.
Thoughts?
D.
On Thu, Mar 16, 2017 at 5:01 AM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Alexey,
>
> Cluster doesn't know about the console, but web agent does,
t;
> > > 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
> > >
>
e 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 <dsetrak...@apache.org>:
> >
> > > I am
gt; 2017-03-16 4:21 GMT+03:00 Dmitriy Setrakyan <dsetrak...@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"?
> &
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 <dsetrak...@apache.org>:
> I am OK with having a cluster na
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 <akuznet...@apache.org>
wrote:
> Igniters,
>
> I'm planning
"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
21 matches
Mail list logo
