Hello!
I have added you to contributors role.
Please make sure to read
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
Regards,
--
Ilya Kasnacheev
чт, 1 апр. 2021 г. в 16:27, Игорь Гусев :
>
> Hi all!
> I am Igor Gusev, and I am an experienced technical writer. I am lear
Hi Nikita,
Welcome to the community! We've been waiting for professionals like you for
a while ;)
Sharing extra resources:
- Our documentation contribution process, you're welcome to suggest
changes:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Document
- Our Slack chann
Hi Nikita,
Welcome to the community! Any help with the documentation is extremely
valuable.
I've added you to the Contributors group in Jira - you should be able to
assign tickets to yourself now.
-Val
On Thu, Dec 3, 2020 at 7:46 AM Никита Сафонов
wrote:
> Hi everyone!
> My name is Nikita Saf
Hello Semyon,
Welcome to Apache Ignite Community!
I added your account to the contributors list. Now you can assign
tickets to yourself. Do not hesitate to ask if you need any
assistance.
Please check this page out for commonly asked questions pertaining to
the contribution process https://ignit
Hello Denis,
We are planning to migrate to Apache Ignite, we have created POC for our
system with Ignite and working well so want to contribute in development.
Thanks,
Prashant Rahulkar.
On Tue, 17 Dec 2019 at 01:25, Denis Magda wrote:
> Prashant,
>
> What brought you to Ignite folks? Do you al
Prashant,
What brought you to Ignite folks? Do you already use it internally and
would like to improve contributing?
-
Denis
On Sun, Dec 15, 2019 at 11:48 PM Prashant Rahulkar <
prashantrahul...@gmail.com> wrote:
> Hello Dmitriy ,
>
> Thanks for your clarification, definitely our employee wil
Hello Dmitriy ,
Thanks for your clarification, definitely our employee will contribute with
riEquaiton.com official mail id.
Thanks,
Prashant Rahulkar.
On Sat, 14 Dec 2019 at 18:34, Dmitriy Pavlov wrote:
> Hi Prashant,
>
> Thank you for your interest in Apache Ignite. And I hope the Ignite
>
Hi Prashant,
Thank you for your interest in Apache Ignite. And I hope the Ignite
community would be glad to work with new contributors.
Just one note: A company can not contribute to an Apache project, but your
employee(s) can contribute as an individual. Similar is true for
management, an employ
Hello Everyone,
I have started software firm in India, with complete motivation to focus on
open source technologies, so as a part of company policy we will star to
contribute in this project with our company name.
Thanks,
PrashantR.
s.com<http://www.t-systems.ru/>
>>
>>
>>
>> -Original Message-
>> From: Ilya Kasnacheev
>> Sent: Thursday, December 12, 2019 5:25 PM
>> To: dev
>> Subject: Re: joining
>>
>>
>>
>> Hello!
>>
essage-
> From: Ilya Kasnacheev
> Sent: Thursday, December 12, 2019 5:25 PM
> To: dev
> Subject: Re: joining
>
>
>
> Hello!
>
>
>
> I will need an Apache JIRA username to add you to contributors. Can you
> provide it?
>
>
>
> Regards,
p://www.t-systems.ru/>
-Original Message-
From: Ilya Kasnacheev
Sent: Thursday, December 12, 2019 5:25 PM
To: dev
Subject: Re: joining
Hello!
I will need an Apache JIRA username to add you to contributors. Can you provide
it?
Regards,
--
Ilya Kasnacheev
чт, 12 дек. 201
Hello!
I will need an Apache JIRA username to add you to contributors. Can you
provide it?
Regards,
--
Ilya Kasnacheev
чт, 12 дек. 2019 г. в 17:20, :
> Hi everyone,
> I'd like to participate in this project!
>
> Best regards,
>
> T-Systems RUS
> Point of Production
> Roman Koriakov
> Softwar
gt;>>>>>> it seems that you can use
> >>>>>>>>>>>> PluginProvider#validateNewNode(org.apache.ignite.cluster.ClusterNode,
> >>>>>>>>>>>> java.io.Serializable) method. Does it fit for your needs?
> >>>>>>>
discussion was moved in private channel. The problem
I'm trying to solve is described below in the thread. The security
plugin in my case stores and analyzesinfo about a node that failed to join.
Regards,
Mikhail.
-------- Forwarded Message
Subject:Re: Joining node validatio
to no decision yet. As I mentioned above
> >>>>>>>>>>> this
> >>>>>>>>>>> event is disabled by default and no node will receive this event
> >>>>>>>>>>> without
> >>>>>>
lve is described below in the thread. The security
plugin in my case stores and analyzesinfo about a node that failed to join.
Regards,
Mikhail.
-------- Forwarded Message
Subject:Re: Joining node validation failure event.
Date: Thu, 21 Nov 2019 21:43:33 +0300
From: Mikha
;>>>>> publishing a new event too. But I'm concerned about the acceptance
> >>>>>>>>> of
> >>>>>>>>> that solution. Maybe it can be solved some other way? I will
> >>>>>>>>> apprecia
zesinfo about a node that failed to join.
Regards,
Mikhail.
Forwarded Message ----
Subject:Re: Joining node validation failure event.
Date: Thu, 21 Nov 2019 21:43:33 +0300
From: Mikhail Petrov
To: Andrey Gura
Hi, Andrey.
In my task security plugin running on
ache/ignite/pull/7057
>>>>>>>>
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>>
>>>>>>>> Mikhail.
>>>>>>>>
>>>>>>>> On 02.12.2019 10:38, Ivan Pavlukhin wrote:
>
gt; Regards,
> >>>>>>
> >>>>>> Mikhail.
> >>>>>>
> >>>>>> On 02.12.2019 10:38, Ivan Pavlukhin wrote:
> >>>>>>> Mikhail, Andrey,
> >>>>>>>
> >>>>>>&
cision here? As for me, it sounds useful
>>>>>>> to expose node join failure details somehow. The thing to decide on is
>>>>>>> a mechanism to expose it. Unfortunately, immediately have no idea
>>>>>>> better than using events.
>>>>
e on is
> >>>>> a mechanism to expose it. Unfortunately, immediately have no idea
> >>>>> better than using events.
> >>>>>
> >>>>>> What is purpose of the special cluster wide event? Node is not joined
> >&
olve is described below in the thread. The security
plugin in my case stores and analyzesinfo about a node that failed to join.
Regards,
Mikhail.
Forwarded Message ----
Subject:Re: Joining node validation failure event.
Date: Thu, 21 Nov 2019 21:43:33 +0300
From: Mikha
nodes should know something about this
> >>>> node?
> >>> Was this question answered? I suppose that at least coordinator will
> >>> receive the event, will not it?
> >>>
> >>> чт, 28 нояб. 2019 г. в 10:10, Mikhail Petrov :
> >&g
the thread. The security
plugin in my case stores and analyzesinfo about a node that failed to join.
Regards,
Mikhail.
Forwarded Message ----
Subject:Re: Joining node validation failure event.
Date: Thu, 21 Nov 2019 21:43:33 +0300
From: Mikhail Petrov
To: Andrey Gu
.
> >>
> >> I'm sorry that the discussion was moved in private channel. The problem
> >> I'm trying to solve is described below in the thread. The security
> >> plugin in my case stores and analyzesinfo about a node that failed to join.
> >>
> &
gards,
Mikhail.
Forwarded Message
Subject:Re: Joining node validation failure event.
Date: Thu, 21 Nov 2019 21:43:33 +0300
From: Mikhail Petrov
To: Andrey Gura
Hi, Andrey.
In my task security plugin running on the coordinator must locally
handle the situation when some no
t; I'm sorry that the discussion was moved in private channel. The problem
> I'm trying to solve is described below in the thread. The security
> plugin in my case stores and analyzesinfo about a node that failed to join.
>
>
> Regards,
>
> Mikhail.
>
>
>
> --
--
Subject: Re: Joining node validation failure event.
Date: Thu, 21 Nov 2019 21:43:33 +0300
From: Mikhail Petrov
To: Andrey Gura
Hi, Andrey.
In my task security plugin running on the coordinator must locally
handle the situation when some node is trying to join the topology
Hi Mikhail,
Interesting topic. Could you please shed some light how a node
validation failure can be handled? Immediately cannot imagine how one
can handle it.
чт, 21 нояб. 2019 г. в 14:17, Mikhail Petrov :
>
> Hi, Andrey.
>
> I take part in the development of a custom security plugin for Apache
Hi, Andrey.
I take part in the development of a custom security plugin for Apache
Ignite. There is an information security requirement for which node
joining failures due to invalid configuration must be handled by the
plugin.
This is where my case comes from. Are there any objections to the
Hi, Mikhail!
Could you please describe the case for this new event?
On Wed, Nov 20, 2019 at 12:45 PM Mikhail Petrov wrote:
>
> Hello, Igniters.
>
> There is a case which requires to handle joining node validation failure
> in Ignite components and obtain information of the node that tried to
> j
Mandhir,
Click on “subscribe” reference that is in the dev list row and send a message
to the address pop up:
https://ignite.apache.org/community/resources.html#mail-lists
-
Denis
> On May 4, 2017, at 7:20 AM, Mandhir Gidda wrote:
>
> SUBSCRIBE
To send message to coordinator we need establish new connection, it is
preferably to use existing connections. Actually we tested this approach,
and on large clusters (> 200 nodes) it did not give start time improvments.
Thanks
On Wed, Apr 26, 2017 at 1:06 PM, ALEKSEY KUZNETSOV wrote:
> Hi, Ign
On Wed, Apr 26, 2017 at 1:06 PM, ALEKSEY KUZNETSOV wrote:
> Hi, Igntrs!
> When new node joins topology, it sends join TcpDiscoveryJoinRequestMessage
> to arbitrary node N1.
> If N1 is not coordinator, then it will resend to all nodes.
>
> Why doesn't N1 send the message directly to coordinator ?
36 matches
Mail list logo
