Re: Joining in

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

Joining in

Hi all! I am Igor Gusev, and I am an experienced technical writer. I am learning in-memory processing technologies and would be glad to contribute to the community. Please give me access to Apache Ignite Jira. My JIRA ID is igusev.   Thanks in advance! Igor

Re: Joining the community

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

Re: Joining the community

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

Joining the community

Hi everyone! My name is Nikita Safonov, I am a professional technical writer. Since I am familiar with in-memory processing technology and deeply interested in its emerging nature, I would be glad to contribute to the community. I kindly request to grant me access to the Apache Ignite JIRA. My

[jira] [Created] (IGNITE-13567) TcpDiscoverySpi: incorrect value of the joiningNodeClient flag for the joining client

Amelchev Nikita created IGNITE-13567: Summary: TcpDiscoverySpi: incorrect value of the joiningNodeClient flag for the joining client Key: IGNITE-13567 URL: https://issues.apache.org/jira/browse/IGNITE-13567

[jira] [Created] (IGNITE-13346) “Joining persistence node to in-memory cluster couldn't be allowed” Verification is too strict

YuJue Li created IGNITE-13346: - Summary: “Joining persistence node to in-memory cluster couldn't be allowed” Verification is too strict Key: IGNITE-13346 URL: https://issues.apache.org/jira/browse/IGNITE-13346

Re: i'm joining the community for contribution

/jira/browse/IGNITE-13040 task > to me or advise some another task for beginners > i can work with SQL, Spring related tasks > > -- Forwarded message - > From: Aleksey Kurinov > Date: Mon, Jun 8, 2020 at 8:35 AM > Subject: i'm joining the community for contribution &

Fwd: i'm joining the community for contribution

, 2020 at 8:35 AM Subject: i'm joining the community for contribution To: Hello I'm Aleksei Kurinov, Software Developer from Epam Systems company. I'd like to contribute to the Ignite project. I'm a java developer but never contributed to open source projects. I'd like to familiar with the process

i'm joining the community for contribution

Hello I'm Aleksei Kurinov, Software Developer from Epam Systems company. I'd like to contribute to the Ignite project. I'm a java developer but never contributed to open source projects. I'd like to familiar with the process so for starting I'd prefer to work on some trivial task for beginners my

[jira] [Created] (IGNITE-13054) Prevent nodes with stale data joining the active topology.

Alexey Scherbakov created IGNITE-13054: -- Summary: Prevent nodes with stale data joining the active topology. Key: IGNITE-13054 URL: https://issues.apache.org/jira/browse/IGNITE-13054 Project

Re: Joining Ignite ASF

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

Joining Ignite ASF

Hello! I would like to start contributing, could you please add me to contributors list? My login for https://issues.apache.org/ is sdanilov. Kind regards, Semyon Danilov.

Re: joining

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

Re: joining

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

Re: joining

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

Re: joining

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

Re: joining

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.

Re: joining

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! >>

Re: joining

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,

RE: joining

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

Re: joining

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 >

joining

Hi everyone, I'd like to participate in this project! Best regards, T-Systems RUS Point of Production Roman Koriakov Software Developer Kirova 11, Voronezh, Russia Tel: + 7 473 200 15 30 E-mail: roman.koria...@t-systems.com

Re: Joining node validation failure event.

pull/7057/files > >>> > >>> вт, 3 дек. 2019 г. в 14:32, Mikhail Petrov : > >>>> Nikolay, Ivan, > >>>> > >>>> I understood the possible problem. It seems that it can be solved using > >>>> EventStorageSpi which starts bef

Re: Joining node validation failure event.

eryManager. As for me, ClusterNode is enough. It contains all info about joining node including its attributes. Discovery events such as (join/left/failed) are connected with a topology version change. In my case that not happens and may be misleading. That's why the new event type was chosen.

Re: Joining node validation failure event.

iles > > > > вт, 3 дек. 2019 г. в 14:32, Mikhail Petrov : > >> Nikolay, Ivan, > >> > >> I understood the possible problem. It seems that it can be solved using > >> EventStorageSpi which starts before DiscoveryManager. > >> > >> As for

Re: Joining node validation failure event.

]). https://github.com/apache/ignite/pull/7057/files вт, 3 дек. 2019 г. в 14:32, Mikhail Petrov : Nikolay, Ivan, I understood the possible problem. It seems that it can be solved using EventStorageSpi which starts before DiscoveryManager. As for me, ClusterNode is enough. It contains all info about jo

Re: Joining node validation failure event.

the possible problem. It seems that it can be solved using > EventStorageSpi which starts before DiscoveryManager. > > As for me, ClusterNode is enough. It contains all info about joining > node including its attributes. > > Discovery events such as (join/left/failed) are conne

Re: Joining node validation failure event.

Nikolay, Ivan, I understood the possible problem. It seems that it can be solved using EventStorageSpi which starts before DiscoveryManager. As for me, ClusterNode is enough. It contains all info about joining node including its attributes. Discovery events such as (join/left/failed

Re: Joining node validation failure event.

ent? Actually such >>> event seems to fit naturally node join/left/failed events. >>> >>> вт, 3 дек. 2019 г. в 10:38, Mikhail Petrov : >>>> >>>> Hi Ivan. >>>> >>>> No other lifecycle events are needed in my case.

Re: Joining node validation failure event.

Hi Ivan. > >> > >> No other lifecycle events are needed in my case. > >> > >> We can register a listener in the security component's > >> GridComponent#onKernalStart method and listen locally to every failed > >> joining attempt. Am I missing something? &

Re: Joining node validation failure event.

o other lifecycle events are needed in my case. >> >> We can register a listener in the security component's >> GridComponent#onKernalStart method and listen locally to every failed >> joining attempt. Am I missing something? >> >> Regards, >> Mikhai

Re: Joining node validation failure event.

naturally node join/left/failed events. вт, 3 дек. 2019 г. в 10:38, Mikhail Petrov : > > Hi Ivan. > > No other lifecycle events are needed in my case. > > We can register a listener in the security component's > GridComponent#onKernalStart method and listen locally to every fai

Re: Joining node validation failure event.

Hi Ivan. No other lifecycle events are needed in my case. We can register a listener in the security component's GridComponent#onKernalStart method and listen locally to every failed joining attempt. Am I missing something? Regards, Mikhail. On 03.12.2019 8:48, Ivan Pavlukhin wrote

Re: Joining node validation failure event.

. 2019 г. в 18:09, Mikhail Petrov : > > Hi, Andrey. > > It doesn't influence on authentication or authorization process. There > is a security requirement that demands to notify some outer security > subsystems in a specific way when joining node validation failed in any >

Re: Joining node validation failure event.

Hi, Andrey. It doesn't influence on authentication or authorization process. There is a security requirement that demands to notify some outer security subsystems in a specific way when joining node validation failed in any Ignite component (e.g. GridCacheProcessor) not only

Re: Joining node validation failure event.

gt; Hi, Ivan. > > > Unfortunately, we came to no decision yet. As I mentioned above this > event is disabled by default and no node will receive this event without > an explicit subscription. In my case, that event is assumed to be used > on node locally to share joining no

Re: Joining node validation failure event.

Hi, Ivan. Unfortunately, we came to no decision yet. As I mentioned above this event is disabled by default and no node will receive this event without an explicit subscription. In my case, that event is assumed to be used on node locally to share joining node info between security

Re: Re: Joining node validation failure event.

. > > 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. > > > > Forward

Fwd: Re: Joining node validation failure event.

: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

Re: Joining node validation failure event.

n 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, > M

Re: Joining node validation failure event.

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

Re: Joining node validation failure event.

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

Joining node validation failure event.

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

[jira] [Created] (IGNITE-11852) Assertion errors when changing PME coordinator to locally joining node

Pavel Kovalenko created IGNITE-11852: Summary: Assertion errors when changing PME coordinator to locally joining node Key: IGNITE-11852 URL: https://issues.apache.org/jira/browse/IGNITE-11852

[jira] [Created] (IGNITE-11678) Forbidding joining persistence node to in-memory cluster

Anton Kalashnikov created IGNITE-11678: -- Summary: Forbidding joining persistence node to in-memory cluster Key: IGNITE-11678 URL: https://issues.apache.org/jira/browse/IGNITE-11678 Project

[jira] [Created] (IGNITE-11662) Wrong classloader is used to unmarshal joining node data

Oleksii Mohylin created IGNITE-11662: Summary: Wrong classloader is used to unmarshal joining node data Key: IGNITE-11662 URL: https://issues.apache.org/jira/browse/IGNITE-11662 Project: Ignite

[jira] [Created] (IGNITE-11521) Register listeners before joining the cluster

Lukas Polacek created IGNITE-11521: -- Summary: Register listeners before joining the cluster Key: IGNITE-11521 URL: https://issues.apache.org/jira/browse/IGNITE-11521 Project: Ignite Issue

[jira] [Created] (IGNITE-10912) Huge node join request discovery message slows down node joining and corresponding PME

Alexei Scherbakov created IGNITE-10912: -- Summary: Huge node join request discovery message slows down node joining and corresponding PME Key: IGNITE-10912 URL: https://issues.apache.org/jira/browse/IGNITE

[jira] [Created] (IGNITE-9501) Exclude newly joining nodes from exchange latch

Pavel Kovalenko created IGNITE-9501: --- Summary: Exclude newly joining nodes from exchange latch Key: IGNITE-9501 URL: https://issues.apache.org/jira/browse/IGNITE-9501 Project: Ignite

[jira] [Created] (IGNITE-8897) Node with longer BaselineHistory joining the cluster causes cluster stopping

Sergey Chugunov created IGNITE-8897: --- Summary: Node with longer BaselineHistory joining the cluster causes cluster stopping Key: IGNITE-8897 URL: https://issues.apache.org/jira/browse/IGNITE-8897

[jira] [Created] (IGNITE-8423) Control utility may block when joining node is watiting for partition map exchange

Alexey Goncharuk created IGNITE-8423: Summary: Control utility may block when joining node is watiting for partition map exchange Key: IGNITE-8423 URL: https://issues.apache.org/jira/browse/IGNITE-8423

[jira] [Created] (IGNITE-8372) Cluster metrics are reported incorrectly on joining node with ZK-based discovery

Sergey Chugunov created IGNITE-8372: --- Summary: Cluster metrics are reported incorrectly on joining node with ZK-based discovery Key: IGNITE-8372 URL: https://issues.apache.org/jira/browse/IGNITE-8372

[jira] [Created] (IGNITE-8364) Propagate deployed services to joining nodes

Denis Mekhanikov created IGNITE-8364: Summary: Propagate deployed services to joining nodes Key: IGNITE-8364 URL: https://issues.apache.org/jira/browse/IGNITE-8364 Project: Ignite Issue

[jira] [Created] (IGNITE-8193) Joining node data should be cleaned in some cases

Sergey Chugunov created IGNITE-8193: --- Summary: Joining node data should be cleaned in some cases Key: IGNITE-8193 URL: https://issues.apache.org/jira/browse/IGNITE-8193 Project: Ignite

[jira] [Created] (IGNITE-8006) Starting multiple caches inhibits exchange process on joining node

Vladislav Pyatkov created IGNITE-8006: - Summary: Starting multiple caches inhibits exchange process on joining node Key: IGNITE-8006 URL: https://issues.apache.org/jira/browse/IGNITE-8006 Project

[jira] [Created] (IGNITE-7794) Marshaller mappings are not saved to disk on joining nodes

Denis Mekhanikov created IGNITE-7794: Summary: Marshaller mappings are not saved to disk on joining nodes Key: IGNITE-7794 URL: https://issues.apache.org/jira/browse/IGNITE-7794 Project: Ignite

[GitHub] ignite pull request #3519: IGNITE-7693: Printing out session ids on joining ...

GitHub user shroman opened a pull request: https://github.com/apache/ignite/pull/3519 IGNITE-7693: Printing out session ids on joining via ZookeeperDiscove… …rySpi. You can merge this pull request into a Git repository by running: $ git pull https://github.com/shroman

[jira] [Created] (IGNITE-7693) New node joining via ZookeeperDiscoverySpi should print out its ZooKeeper sessionId

Sergey Chugunov created IGNITE-7693: --- Summary: New node joining via ZookeeperDiscoverySpi should print out its ZooKeeper sessionId Key: IGNITE-7693 URL: https://issues.apache.org/jira/browse/IGNITE-7693

[jira] [Created] (IGNITE-7137) Provide a way to switch off BaselineTopology validation of nodes joining the cluster

Sergey Chugunov created IGNITE-7137: --- Summary: Provide a way to switch off BaselineTopology validation of nodes joining the cluster Key: IGNITE-7137 URL: https://issues.apache.org/jira/browse/IGNITE-7137

[GitHub] ignite pull request #3036: IGNITE-6916: node joining with enabled pds and em...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3036 ---

[GitHub] ignite pull request #3036: IGNITE-6916: node joining with enabled pds and em...

GitHub user zstan opened a pull request: https://github.com/apache/ignite/pull/3036 IGNITE-6916: node joining with enabled pds and empty disc space cause… …s exchange to hang You can merge this pull request into a Git repository by running: $ git pull https://github.com

[jira] [Created] (IGNITE-6916) A node joining with enabled persistence and empty disc space causes exchange to hang.

Stanilovsky Evgeny created IGNITE-6916: -- Summary: A node joining with enabled persistence and empty disc space causes exchange to hang. Key: IGNITE-6916 URL: https://issues.apache.org/jira/browse/IGNITE-6916

[jira] [Created] (IGNITE-6695) Validation of joining node data consistency WRT the same data in grid

Sergey Chugunov created IGNITE-6695: --- Summary: Validation of joining node data consistency WRT the same data in grid Key: IGNITE-6695 URL: https://issues.apache.org/jira/browse/IGNITE-6695 Project

[jira] [Created] (IGNITE-6321) Nodes joining to active cluster remain in inactive state

Sergey Chugunov created IGNITE-6321: --- Summary: Nodes joining to active cluster remain in inactive state Key: IGNITE-6321 URL: https://issues.apache.org/jira/browse/IGNITE-6321 Project: Ignite

[jira] [Created] (IGNITE-5704) Do not allow cluster to be deactivated if the joining node does not complete start all components

Dmitriy Govorukhin created IGNITE-5704: -- Summary: Do not allow cluster to be deactivated if the joining node does not complete start all components Key: IGNITE-5704 URL: https://issues.apache.org/jira/browse

Re: Joining

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

Joining

SUBSCRIBE

Re: joining exchange

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

Re: joining exchange

> Why doesn't N1 send the message directly to coordinator ? > It think that the joining node sends its join-request message to the IP address that was provided by the IP Finder, possibly in the configuration. -- > > *Best Regards,* > > *Kuznetsov Aleksey* >

joining exchange

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 ? -- *Best Regards,* *Kuznetsov Aleksey*

[jira] [Created] (IGNITE-4679) Consistency checks and error tracking during node joining process

Sergey Chugunov created IGNITE-4679: --- Summary: Consistency checks and error tracking during node joining process Key: IGNITE-4679 URL: https://issues.apache.org/jira/browse/IGNITE-4679 Project

[jira] [Created] (IGNITE-4638) Share current DDL schema and pending DDL operations with joining nodes

Vladimir Ozerov created IGNITE-4638: --- Summary: Share current DDL schema and pending DDL operations with joining nodes Key: IGNITE-4638 URL: https://issues.apache.org/jira/browse/IGNITE-4638 Project

[jira] [Created] (IGNITE-4448) Implement correct affinity validation on joining topology.

Alexei Scherbakov created IGNITE-4448: - Summary: Implement correct affinity validation on joining topology. Key: IGNITE-4448 URL: https://issues.apache.org/jira/browse/IGNITE-4448 Project: Ignite

[jira] [Created] (IGNITE-4223) Joining node should fetch affinity for all caches using single message

Semen Boikov created IGNITE-4223: Summary: Joining node should fetch affinity for all caches using single message Key: IGNITE-4223 URL: https://issues.apache.org/jira/browse/IGNITE-4223 Project