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 join and the reason for the failure. Now, as I see, there is no way to do it. I propose to implement a new event -- NodeValidationFailedEvent -- and record it in case the validation fails. I have created Tiket [1] and PR [2], which shows an example of implementation. Could anyone take a look at it, please? [1] https://issues.apache.org/jira/browse/IGNITE-12380 [2] https://github.com/apache/ignite/pull/7057 |
Hi, Mikhail!
Could you please describe the case for this new event? On Wed, Nov 20, 2019 at 12:45 PM Mikhail Petrov <[hidden email]> 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 > join and the reason for the failure. Now, as I see, there is no way to > do it. I propose to implement a new event -- NodeValidationFailedEvent > -- and record it in case the validation fails. I have created Tiket [1] > and PR [2], which shows an example of implementation. Could anyone take > a look at it, please? > > [1] https://issues.apache.org/jira/browse/IGNITE-12380 > > [2] https://github.com/apache/ignite/pull/7057 > |
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 proposed approach? Regards, Mikhail. On 20.11.2019 19:38, Andrey Gura wrote: > Hi, Mikhail! > > Could you please describe the case for this new event? > > On Wed, Nov 20, 2019 at 12:45 PM Mikhail Petrov <[hidden email]> 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 >> join and the reason for the failure. Now, as I see, there is no way to >> do it. I propose to implement a new event -- NodeValidationFailedEvent >> -- and record it in case the validation fails. I have created Tiket [1] >> and PR [2], which shows an example of implementation. Could anyone take >> a look at it, please? >> >> [1] https://issues.apache.org/jira/browse/IGNITE-12380 >> >> [2] https://github.com/apache/ignite/pull/7057 >> |
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 <[hidden email]>: > > 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 > proposed approach? > > Regards, > Mikhail. > > On 20.11.2019 19:38, Andrey Gura wrote: > > Hi, Mikhail! > > > > Could you please describe the case for this new event? > > > > On Wed, Nov 20, 2019 at 12:45 PM Mikhail Petrov <[hidden email]> 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 > >> join and the reason for the failure. Now, as I see, there is no way to > >> do it. I propose to implement a new event -- NodeValidationFailedEvent > >> -- and record it in case the validation fails. I have created Tiket [1] > >> and PR [2], which shows an example of implementation. Could anyone take > >> a look at it, please? > >> > >> [1] https://issues.apache.org/jira/browse/IGNITE-12380 > >> > >> [2] https://github.com/apache/ignite/pull/7057 > >> -- Best regards, Ivan Pavlukhin |
Free forum by Nabble | Edit this page |