To unsubscribe you need to send any message to issues-unsubscr...@ignite.apache.org address and follow instructions sent in a response.
2020-07-22 20:25 GMT+03:00, C Ravikiran <itsmeravikira...@gmail.com>: > Thank you for your email. > Could me help me, how to unsubscribe from iss...@ignite.apache.org > > > > > > > On Wed, 22 Jul, 2020, 10:40 pm Ivan Pavlukhin, <vololo...@gmail.com> wrote: > >> Hi Ravikiran C, >> >> Could you please provide all "To:" addresses from a particular JIRA >> notification email? >> >> Might it be the case that you are subscribed to >> iss...@ignite.apache.org? If so you should unsubscribe from it as >> well. >> >> 2020-07-22 16:42 GMT+03:00, C Ravikiran <itsmeravikira...@gmail.com>: >> > I have not participated any of the jira issues. >> > I am getting lot emails related to jira. >> > >> > How to unsubscribe all. >> > >> > On Wed, 22 Jul, 2020, 3:37 pm Ivan Pavlukhin, <vololo...@gmail.com> >> wrote: >> > >> >> Hi Ravikiran C, >> >> >> >> JIRA sends emails about issue updates to participants. I guess >> >> clicking "Stop watching this issue" on a particular issue in JIRA can >> >> help here. >> >> >> >> 2020-07-22 12:41 GMT+03:00, C Ravikiran <itsmeravikira...@gmail.com>: >> >> > HI Team, >> >> > >> >> > I have unsubscribed ignite users, still i am getting below emails. >> >> > >> >> > Could you please help me to unsubscribe all these emails? >> >> > >> >> > Regards, >> >> > Ravikiran C >> >> > >> >> > On Wed, 22 Jul, 2020, 12:04 pm Aleksey Plekhanov (Jira), < >> >> j...@apache.org> >> >> > wrote: >> >> > >> >> >> >> >> >> [ >> >> >> >> >> >> https://issues.apache.org/jira/browse/IGNITE-12033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel >> >> >> ] >> >> >> >> >> >> Aleksey Plekhanov updated IGNITE-12033: >> >> >> --------------------------------------- >> >> >> Fix Version/s: (was: 2.9) >> >> >> 2.10 >> >> >> >> >> >> > Callbacks from striped pool due to async/await may hang cluster >> >> >> > --------------------------------------------------------------- >> >> >> > >> >> >> > Key: IGNITE-12033 >> >> >> > URL: >> >> https://issues.apache.org/jira/browse/IGNITE-12033 >> >> >> > Project: Ignite >> >> >> > Issue Type: Bug >> >> >> > Components: cache, platforms >> >> >> > Affects Versions: 2.7.5 >> >> >> > Reporter: Ilya Kasnacheev >> >> >> > Priority: Critical >> >> >> > Fix For: 2.10 >> >> >> > >> >> >> > >> >> >> > Discussed on dev-list: >> >> >> > >> >> >> >> >> >> http://apache-ignite-developers.2346864.n4.nabble.com/Re-EXTERNAL-Re-Replace-or-Put-after-PutAsync-causes-Ignite-to-hang-td42921.html >> >> >> > *Must use the public pool for callbacks as the most obvious >> >> >> > step.* >> >> >> > ---- >> >> >> > >> >> >> >> >> >> http://apache-ignite-users.70518.x6.nabble.com/Replace-or-Put-after-PutAsync-causes-Ignite-to-hang-td27871.html#a28051 >> >> >> > There's a reproducer project. Long story short, .Net can invoke >> >> >> > cache >> >> >> operations with future callbacks, which will be invoked from >> >> >> striped >> >> >> pool. >> >> >> If such callbacks are to use cache operations, those will be >> >> >> possibly >> >> >> sheduled to the same stripe and cause a deadlock. >> >> >> > The code is very simple: >> >> >> > {code} >> >> >> > Console.WriteLine("PutAsync"); >> >> >> > await cache.PutAsync(1, "Test"); >> >> >> > Console.WriteLine("Replace"); >> >> >> > cache.Replace(1, "Testing"); // Hangs here >> >> >> > Console.WriteLine("Wait"); >> >> >> > await Task.Delay(Timeout.Infinite); >> >> >> > {code} >> >> >> > async/await should absolutely not allow any client code to be run >> >> >> > from >> >> >> stripes. >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> >> This message was sent by Atlassian Jira >> >> >> (v8.3.4#803005) >> >> >> >> >> > >> >> >> >> >> >> -- >> >> >> >> Best regards, >> >> Ivan Pavlukhin >> >> >> > >> >> >> -- >> >> Best regards, >> Ivan Pavlukhin >> > -- Best regards, Ivan Pavlukhin
