Re: [External]Re: Cluster becomes unresponsive if multiple clients join at a time
Hello! I think the relevant ticket is https://issues.apache.org/jira/browse/IGNITE-9558 It is poorly documented, I believe the prime condition is that client node should not define any caches in its configuration. Regards, -- Ilya Kasnacheev чт, 22 апр. 2021 г. в 16:07, Kamlesh Joshi : > Thanks Ilya! > > > > I have observed PME related log entries in latest version as well. Does > this mean these ‘some conditions’ are not met? > > > > Can you elaborate on this please ? > > > > *Thanks and Regards,* > > *Kamlesh Joshi* > > > > *From:* Ilya Kasnacheev > *Sent:* 22 April 2021 16:24 > *To:* user@ignite.apache.org > *Subject:* Re: [External]Re: Cluster becomes unresponsive if multiple > clients join at a time > > > > The e-mail below is from an external source. Please do not open > attachments or click links from an unknown or suspicious origin. > > Hello! > > > > Yes, it should no longer be blocking assuming some conditions are met. > > > > Regards, > > -- > > Ilya Kasnacheev > > > > > > чт, 22 апр. 2021 г. в 08:26, Kamlesh Joshi : > > Hi Ilya, > > > > Yeah even that’s what we were suspecting, PME triggering might be causing > issue. We are using 2.7.6 version. > > So you are saying, in recent version i.e. 2.10.0 version don’t have > blocking global PME ? > > > > > > *Thanks and Regards,* > > *Kamlesh Joshi* > > > > *From:* Ilya Kasnacheev > *Sent:* 21 April 2021 20:12 > *To:* user@ignite.apache.org > *Subject:* [External]Re: Cluster becomes unresponsive if multiple clients > join at a time > > > > The e-mail below is from an external source. Please do not open > attachments or click links from an unknown or suspicious origin. > > Hello! > > > > What is the version used? Usually, adding a new thick client would trigger > a PME (a global blocking operation). In recent versions, they should be > able to join without exchange. > > > > You could use flavors of thin client if you need a massive number of those. > > > > Regards, > > -- > > Ilya Kasnacheev > > > > > > ср, 21 апр. 2021 г. в 14:40, Kamlesh Joshi : > > Hi Igniters, > > > > We have observed that if multiple clients (say around 50) are joining > within very short span of time, then cluster seemed unresponsive for > sometime causing entire cluster traffic to go down. > > Have anyone encountered this behaviour before? Any parameters to be > tweaked to avoid this? > > > > *Thanks and Regards,* > > *Kamlesh Joshi* > > > > > "*Confidentiality Warning*: This message and any attachments are intended > only for the use of the intended recipient(s), are confidential and may be > privileged. If you are not the intended recipient, you are hereby notified > that any review, re-transmission, conversion to hard copy, copying, > circulation or other use of this message and any attachments is strictly > prohibited. If you are not the intended recipient, please notify the sender > immediately by return email and delete this message and any attachments > from your system. > > *Virus Warning:* Although the company has taken reasonable precautions to > ensure no viruses are present in this email. The company cannot accept > responsibility for any loss or damage arising from the use of this email or > attachment." > > > "*Confidentiality Warning*: This message and any attachments are intended > only for the use of the intended recipient(s), are confidential and may be > privileged. If you are not the intended recipient, you are hereby notified > that any review, re-transmission, conversion to hard copy, copying, > circulation or other use of this message and any attachments is strictly > prohibited. If you are not the intended recipient, please notify the sender > immediately by return email and delete this message and any attachments > from your system. > > *Virus Warning:* Although the company has taken reasonable precautions to > ensure no viruses are present in this email. The company cannot accept > responsibility for any loss or damage arising from the use of this email or > attachment." > > > "*Confidentiality Warning*: This message and any attachments are intended > only for the use of the intended recipient(s), are confidential and may be > privileged. If you are not the intended recipient, you are hereby notified > that any review, re-transmission, conversion to hard copy, copying, > circulation or other use of this message and any attachments is strictly > prohibited. If you are not the intended recipient, please notify the sender > immediately by return email and delete this message and any attachments > from your system. > > *Virus Warning:* Although the company has taken reasonable precautions to > ensure no viruses are present in this email. The company cannot accept > responsibility for any loss or damage arising from the use of this email or > attachment." >
RE: [External]Re: Cluster becomes unresponsive if multiple clients join at a time
Thanks Ilya! I have observed PME related log entries in latest version as well. Does this mean these ‘some conditions’ are not met? Can you elaborate on this please ? Thanks and Regards, Kamlesh Joshi From: Ilya Kasnacheev Sent: 22 April 2021 16:24 To: user@ignite.apache.org Subject: Re: [External]Re: Cluster becomes unresponsive if multiple clients join at a time The e-mail below is from an external source. Please do not open attachments or click links from an unknown or suspicious origin. Hello! Yes, it should no longer be blocking assuming some conditions are met. Regards, -- Ilya Kasnacheev чт, 22 апр. 2021 г. в 08:26, Kamlesh Joshi mailto:kamlesh.jo...@ril.com>>: Hi Ilya, Yeah even that’s what we were suspecting, PME triggering might be causing issue. We are using 2.7.6 version. So you are saying, in recent version i.e. 2.10.0 version don’t have blocking global PME ? Thanks and Regards, Kamlesh Joshi From: Ilya Kasnacheev mailto:ilya.kasnach...@gmail.com>> Sent: 21 April 2021 20:12 To: user@ignite.apache.org<mailto:user@ignite.apache.org> Subject: [External]Re: Cluster becomes unresponsive if multiple clients join at a time The e-mail below is from an external source. Please do not open attachments or click links from an unknown or suspicious origin. Hello! What is the version used? Usually, adding a new thick client would trigger a PME (a global blocking operation). In recent versions, they should be able to join without exchange. You could use flavors of thin client if you need a massive number of those. Regards, -- Ilya Kasnacheev ср, 21 апр. 2021 г. в 14:40, Kamlesh Joshi mailto:kamlesh.jo...@ril.com>>: Hi Igniters, We have observed that if multiple clients (say around 50) are joining within very short span of time, then cluster seemed unresponsive for sometime causing entire cluster traffic to go down. Have anyone encountered this behaviour before? Any parameters to be tweaked to avoid this? Thanks and Regards, Kamlesh Joshi "Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s), are confidential and may be privileged. If you are not the intended recipient, you are hereby notified that any review, re-transmission, conversion to hard copy, copying, circulation or other use of this message and any attachments is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this message and any attachments from your system. Virus Warning: Although the company has taken reasonable precautions to ensure no viruses are present in this email. The company cannot accept responsibility for any loss or damage arising from the use of this email or attachment." "Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s), are confidential and may be privileged. If you are not the intended recipient, you are hereby notified that any review, re-transmission, conversion to hard copy, copying, circulation or other use of this message and any attachments is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this message and any attachments from your system. Virus Warning: Although the company has taken reasonable precautions to ensure no viruses are present in this email. The company cannot accept responsibility for any loss or damage arising from the use of this email or attachment." "Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s). are confidential and may be privileged. If you are not the intended recipient. you are hereby notified that any review. re-transmission. conversion to hard copy. copying. circulation or other use of this message and any attachments is strictly prohibited. If you are not the intended recipient. please notify the sender immediately by return email. and delete this message and any attachments from your system. Virus Warning: Although the company has taken reasonable precautions to ensure no viruses are present in this email. The company cannot accept responsibility for any loss or damage arising from the use of this email or attachment."
Re: [External]Re: Cluster becomes unresponsive if multiple clients join at a time
Hello! Yes, it should no longer be blocking assuming some conditions are met. Regards, -- Ilya Kasnacheev чт, 22 апр. 2021 г. в 08:26, Kamlesh Joshi : > Hi Ilya, > > > > Yeah even that’s what we were suspecting, PME triggering might be causing > issue. We are using 2.7.6 version. > > So you are saying, in recent version i.e. 2.10.0 version don’t have > blocking global PME ? > > > > > > *Thanks and Regards,* > > *Kamlesh Joshi* > > > > *From:* Ilya Kasnacheev > *Sent:* 21 April 2021 20:12 > *To:* user@ignite.apache.org > *Subject:* [External]Re: Cluster becomes unresponsive if multiple clients > join at a time > > > > The e-mail below is from an external source. Please do not open > attachments or click links from an unknown or suspicious origin. > > Hello! > > > > What is the version used? Usually, adding a new thick client would trigger > a PME (a global blocking operation). In recent versions, they should be > able to join without exchange. > > > > You could use flavors of thin client if you need a massive number of those. > > > > Regards, > > -- > > Ilya Kasnacheev > > > > > > ср, 21 апр. 2021 г. в 14:40, Kamlesh Joshi : > > Hi Igniters, > > > > We have observed that if multiple clients (say around 50) are joining > within very short span of time, then cluster seemed unresponsive for > sometime causing entire cluster traffic to go down. > > Have anyone encountered this behaviour before? Any parameters to be > tweaked to avoid this? > > > > *Thanks and Regards,* > > *Kamlesh Joshi* > > > > > "*Confidentiality Warning*: This message and any attachments are intended > only for the use of the intended recipient(s), are confidential and may be > privileged. If you are not the intended recipient, you are hereby notified > that any review, re-transmission, conversion to hard copy, copying, > circulation or other use of this message and any attachments is strictly > prohibited. If you are not the intended recipient, please notify the sender > immediately by return email and delete this message and any attachments > from your system. > > *Virus Warning:* Although the company has taken reasonable precautions to > ensure no viruses are present in this email. The company cannot accept > responsibility for any loss or damage arising from the use of this email or > attachment." > > > "*Confidentiality Warning*: This message and any attachments are intended > only for the use of the intended recipient(s), are confidential and may be > privileged. If you are not the intended recipient, you are hereby notified > that any review, re-transmission, conversion to hard copy, copying, > circulation or other use of this message and any attachments is strictly > prohibited. If you are not the intended recipient, please notify the sender > immediately by return email and delete this message and any attachments > from your system. > > *Virus Warning:* Although the company has taken reasonable precautions to > ensure no viruses are present in this email. The company cannot accept > responsibility for any loss or damage arising from the use of this email or > attachment." >
RE: [External]Re: Cluster becomes unresponsive if multiple clients join at a time
Hi Ilya, Yeah even that’s what we were suspecting, PME triggering might be causing issue. We are using 2.7.6 version. So you are saying, in recent version i.e. 2.10.0 version don’t have blocking global PME ? Thanks and Regards, Kamlesh Joshi From: Ilya Kasnacheev Sent: 21 April 2021 20:12 To: user@ignite.apache.org Subject: [External]Re: Cluster becomes unresponsive if multiple clients join at a time The e-mail below is from an external source. Please do not open attachments or click links from an unknown or suspicious origin. Hello! What is the version used? Usually, adding a new thick client would trigger a PME (a global blocking operation). In recent versions, they should be able to join without exchange. You could use flavors of thin client if you need a massive number of those. Regards, -- Ilya Kasnacheev ср, 21 апр. 2021 г. в 14:40, Kamlesh Joshi mailto:kamlesh.jo...@ril.com>>: Hi Igniters, We have observed that if multiple clients (say around 50) are joining within very short span of time, then cluster seemed unresponsive for sometime causing entire cluster traffic to go down. Have anyone encountered this behaviour before? Any parameters to be tweaked to avoid this? Thanks and Regards, Kamlesh Joshi "Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s), are confidential and may be privileged. If you are not the intended recipient, you are hereby notified that any review, re-transmission, conversion to hard copy, copying, circulation or other use of this message and any attachments is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this message and any attachments from your system. Virus Warning: Although the company has taken reasonable precautions to ensure no viruses are present in this email. The company cannot accept responsibility for any loss or damage arising from the use of this email or attachment." "Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s). are confidential and may be privileged. If you are not the intended recipient. you are hereby notified that any review. re-transmission. conversion to hard copy. copying. circulation or other use of this message and any attachments is strictly prohibited. If you are not the intended recipient. please notify the sender immediately by return email. and delete this message and any attachments from your system. Virus Warning: Although the company has taken reasonable precautions to ensure no viruses are present in this email. The company cannot accept responsibility for any loss or damage arising from the use of this email or attachment."
