Re: [jira] [Updated] (IGNITE-12033) Callbacks from striped pool due to async/await may hang cluster
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, 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 :
> > 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,
> 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 :
> >> > 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
>
Re: [jira] [Updated] (IGNITE-10279) Control.sh utility unify options naming format
How to unsubscribe these jira emails.
Please help me..
On Wed, 15 Jul, 2020, 4:05 pm Ilya Kasnacheev (Jira),
wrote:
>
> [
> https://issues.apache.org/jira/browse/IGNITE-10279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>
> Ilya Kasnacheev updated IGNITE-10279:
> -
> Component/s: control.sh
>
> > Control.sh utility unify options naming format
> > --
> >
> > Key: IGNITE-10279
> > URL: https://issues.apache.org/jira/browse/IGNITE-10279
> > Project: Ignite
> > Issue Type: Improvement
> > Components: control.sh
> >Affects Versions: 2.6
> >Reporter: Sergey Antonov
> >Assignee: Sergey Antonov
> >Priority: Major
> > Fix For: 2.8
> >
> >
> > Now we have options in several styles:
> > {noformat}
> > --ping-interval
> > {noformat}
> > {noformat}
> > --skipZeros
> > {noformat}
> > I think, we must unify options naming format and we should use linux
> like format, i.e. {{--word1-word2}}
> >
>
>
>
> --
> This message was sent by Atlassian Jira
> (v8.3.4#803005)
>
Re: [DISCUSSION] Complete Discontinuation of IGFS and Hadoop Accelerator
Hi, Could you please help me to unsubscribe all these ignite mails. I have unsubscribed it, but still I am getting lot of emails Could you please help me.. On Wed, 22 Jul, 2020, 9:45 pm Anton Kalashnikov, wrote: > Sorry, I was mistaken, we can not leave these methods because at least > FileSystemConfiguration and HadoopConfiguration require corresponded > classes that were deleted. So I think we should just remove it right now. > > -- > Best regards, > Anton Kalashnikov > > > > 22.07.2020, 18:56, "Anton Kalashnikov" : > > Hi, > > > > All of these methods are from IgniteConfiguration: > > Hadoop configuration: > > - HadoopConfiguration getHadoopConfiguration() > > - IgniteConfiguration setHadoopConfiguration(HadoopConfiguration > hadoopCfg) > > > > IGFS (Ignite In-Memory File System) configurations: > > - FileSystemConfiguration[] getFileSystemConfiguration > > - IgniteConfiguration > setFileSystemConfiguration(FileSystemConfiguration... igfsCfg) > > > > thread pool size that will be used to process outgoing IGFS messages: > > - IgniteConfiguration setIgfsThreadPoolSize(int poolSize) > > - int getIgfsThreadPoolSize() > > > > Of course, I can leave these methods intact but they will be doing > nothing so API formally wouldn't be changed but, in fact, features would be > removed. Does it make sense? I don't think so and in my opinion, perhaps it > is ok to remove these methods right now if we are ready to remove these > features right now. (but again, if there are some concerns about it, I can > easily to leave these methods with empty implementation) > > > > -- > > Best regards, > > Anton Kalashnikov > > > > 22.07.2020, 17:47, "Denis Magda" : > >> Hi Alex, > >> > >> It's been a year since we voted to discontinue this integration [1] > and it > >> wasn't removed from the source code earlier only because of the > internal > >> dependencies with the ML component. Now all the dependencies are gone > and > >> Ignite 2.9 is the right version to finish the discontinuation process. > It > >> would make sense to wait for Ignite 3.0 only there are some breaking > >> changes in the APIs that will stay in Ignite. > >> > >> @Anton Kalashnikov , you mentioned that > you > >> removed some methods from the configuration. Could you please list them > >> here? Are they Hadoop-specific or generic? > >> > >> [1] > >> > http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Complete-Discontinuation-of-IGFS-and-Hadoop-Accelerator-td42405.html > >> > >> - > >> Denis > >> > >> On Wed, Jul 22, 2020 at 1:52 AM Alex Plehanov > > >> wrote: > >> > >>> Guys, > >>> > >>> Any updates here? Looks like we still don't have a consensus about > release > >>> version for this patch (already mention it in the release thread). > >>> Currently, the ticket is still targeted to 2.9. > >>> > >>> ср, 15 июл. 2020 г. в 00:40, Denis Magda : > >>> > >>> > I don't think it's required to wait until Ignite 3.0 to make this > happen. > >>> > If I'm not mistaken, we stopped releasing Hadoop binaries and > sources a > >>> > long time ago (at least you can't longer find them on the downloads > >>> page). > >>> > Also, we removed all the mentioning from the documentation and > website. > >>> > Nobody complained or requested for a maintenance release since > that time. > >>> > Thus, I would remove the integration in 2.9. If anybody shows up > later > >>> then > >>> > they can use the sources in the 2.8 branch and do whatever they > want. > >>> > > >>> > - > >>> > Denis > >>> > > >>> > > >>> > On Thu, Jul 9, 2020 at 3:52 AM Pavel Tupitsyn < > ptupit...@apache.org> > >>> > wrote: > >>> > > >>> > > We are breaking backwards compatibility, > >>> > > so this can be only done for Ignite 3.0, am I right? > >>> > > > >>> > > On Thu, Jul 9, 2020 at 1:46 PM Anton Kalashnikov < > kaa@yandex.ru> > >>> > > wrote: > >>> > > > >>> > > > Hi everyone, > >>> > > > > >>> > > > The task of removal IGFS and Hadoop accelerator is ready to > review.( > >>> > > > https://issues.apache.org/jira/browse/IGNITE-11942) > >>> > > > I've already asked some guys to take a look at it but if > somebody > >>> > > familiar > >>> > > > with this part of code, feel free to take a look at the changes > >>> > > > too(especially scripts changes). > >>> > > > > >>> > > > I also think it is good to decide which release it should be > planned > >>> > on. > >>> > > > This task planned for 2.9 right now but I should notice that > first of > >>> > all > >>> > > > there are a lot of changes and secondly there are some changes > in > >>> > public > >>> > > > API(removed some methods from configuration). So maybe it > makes sense > >>> > to > >>> > > > move this ticket to the next release. What do you think? > >>> > > > > >>> > > > -- > >>> > > > Best regards, > >>> > > > Anton Kalashnikov > >>> > > > > >>> > > > > >>> > > > 10.02.2020, 15:45, "Alexey Zinoviev" : > >>> > > > >
Re: [jira] [Updated] (IGNITE-12033) Callbacks from striped pool due to async/await may hang cluster
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, 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 :
> > 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
>
Re: [jira] [Updated] (IGNITE-12033) Callbacks from striped pool due to async/await may hang cluster
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),
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)
>
Re: Help with ignite cluster
I am able to see Topology snapshot in my logs as ver=23 servers=2 offheap=93 gb heap=120 gb I am able see 2 severs. Still we are facing the issue. Could you please help me on this issue. On Thu, 4 Jun, 2020, 5:34 pm Ilya Kasnacheev, wrote: > Hello! > > I think that your nodes were not able to discover each other and formed two > clusters. > > Can you find "Topology snapshot" messages from their logs, share those with > us? > > Regards, > -- > Ilya Kasnacheev > > > чт, 4 июн. 2020 г. в 13:28, C Ravikiran : > > > Hi Team, > > > > Initially my application running with single node. > > > > Recently added one more node in to the cluster and my application is > > working with two nodes without issues and also fetching data in cache IDs > > also. > > > > But today one node was down which was runnig intially. > > > > Newly added node was running fine. > > > > But we are not able to see the data from newly added node. > > > > Two nodes sync has not done properly. > > > > We are using ignite 2.6 version > > > > Cache mode: partitioned, FULL_SYNC > > > > Could you please help me on this. > > Ignite ui i am getting below error: > > Fail to find data nodes for cache: * > > > > Thanks in advance > > advanc. e > > >
Re: Help with ignite cluster
Thank you for the response. I have one cluster and two nodes. Both nodes I am able to see ignite UI. Still I am facing the same problem. Could please let me know, any configuration I have missed. On Thu, 4 Jun, 2020, 5:34 pm Ilya Kasnacheev, wrote: > Hello! > > I think that your nodes were not able to discover each other and formed two > clusters. > > Can you find "Topology snapshot" messages from their logs, share those with > us? > > Regards, > -- > Ilya Kasnacheev > > > чт, 4 июн. 2020 г. в 13:28, C Ravikiran : > > > Hi Team, > > > > Initially my application running with single node. > > > > Recently added one more node in to the cluster and my application is > > working with two nodes without issues and also fetching data in cache IDs > > also. > > > > But today one node was down which was runnig intially. > > > > Newly added node was running fine. > > > > But we are not able to see the data from newly added node. > > > > Two nodes sync has not done properly. > > > > We are using ignite 2.6 version > > > > Cache mode: partitioned, FULL_SYNC > > > > Could you please help me on this. > > Ignite ui i am getting below error: > > Fail to find data nodes for cache: * > > > > Thanks in advance > > advanc. e > > >
Help with ignite cluster
Hi Team, Initially my application running with single node. Recently added one more node in to the cluster and my application is working with two nodes without issues and also fetching data in cache IDs also. But today one node was down which was runnig intially. Newly added node was running fine. But we are not able to see the data from newly added node. Two nodes sync has not done properly. We are using ignite 2.6 version Cache mode: partitioned, FULL_SYNC Could you please help me on this. Ignite ui i am getting below error: Fail to find data nodes for cache: * Thanks in advance advanc. e
Ignite Migration 2.6 to 2.8
Hi Team, Currently my project is ignite 2.6 version. 2.6 configuration in my project is below. JVM_OPTS= -Xms2g Xmx32g But in 2.8 is little different, JVM_OPTS = -Xms1g Xmx32g In 2.8 also Shall I update the same configuration like 2.6. If change is, is there any problem I will get On Fri 8 May, 2020, 12:20 PM C Ravikiran, wrote: >
Re: Out of memory error in ignite 1.6
Last 2 years there is no code changes. Our application is running in only one node. Our daily data is around 10GB, as our scheduler is removing old data. Our application users also less. Why we got suddenly, these memory leakage problem, when there is no application code change. Problem we are getting only in production environment. We are not getting the same Error in UAT environment, we are using same configuration. On Sat 9 May, 2020, 12:23 AM Denis Magda, wrote: > You need to get to the bottom of why JVM fails with the OOM on your cluster > nodes. An ignite node is no more than a Java application and you can start > investigating the issue using standard methods. For now, I can only share > some useful pointers: > >- > > https://apacheignite.readme.io/docs/jvm-and-system-tuning#debugging-memory-usage-issues-and-gc-pauses >- https://www.toptal.com/java/hunting-memory-leaks-in-java > > Once you pinpoint the memory leak and confirm the leak is caused by Ignite > internal objects, then send us a note. > > Also, ensure that you simply didn't exhaust all available memory. It might > happen that you store more data in Ignite than before and there is no > capacity available. In this case, just scale out, add more nodes to the > cluster. > > - > Denis > > > On Fri, May 8, 2020 at 11:46 AM C Ravikiran > wrote: > > > I am new to ignite, if you need any details please let me know, I will > > check and provide those details. > > > > I need proper justification, if I need to upgrade to new version. > > > > Suddenly we are getting OOM error, after 2 years. > > > > Every day we are removing all old cache ids and adding new cache ids > > > > Our heap size is 32 GB. > > > > > > > > > > > > A > > > > > > On Sat 9 May, 2020, 12:06 AM Denis Magda, wrote: > > > > > You just stated that experienced OOM issues with no details for > > suggestions > > > or help with troubleshooting. Take heap dumps, analyze GC logs, etc: > > > > > > > > > https://apacheignite.readme.io/docs/jvm-and-system-tuning#debugging-memory-usage-issues-and-gc-pauses > > > > > > - > > > Denis > > > > > > > > > On Fri, May 8, 2020 at 11:31 AM C Ravikiran < > itsmeravikira...@gmail.com> > > > wrote: > > > > > > > Is this problem will be solved, if I upgraded to 2.8 version. > > > > > > > > > > > > On Fri 8 May, 2020, 10:02 PM Ilya Kasnacheev, < > > ilya.kasnach...@gmail.com > > > > > > > > wrote: > > > > > > > > > Hello! > > > > > > > > > > I don't think you will find much expertise on Ignite 1.x here. I > > > > recommend > > > > > upgrading it to 2.8 eventually. > > > > > > > > > > Regards, > > > > > -- > > > > > Ilya Kasnacheev > > > > > > > > > > > > > > > пт, 8 мая 2020 г. в 09:57, C Ravikiran >: > > > > > > > > > > > Hi Team, > > > > > > > > > > > > Our application is running past 2 year onwards, there was no > > problem > > > > with > > > > > > ignite. > > > > > > Suddenly last 2 week onwards, we are getting out of memory error > in > > > > > ignite. > > > > > > > > > > > > There was no code changes in last 2 years. > > > > > > > > > > > > If we restart the ignite, our memory gradually increasing and we > > are > > > > > > getting out of memory error. > > > > > > > > > > > > Every day we will remove all the previous cache ids, and create > new > > > > cach > > > > > > ids. > > > > > > We have only one se of cache ids, but still our heap size is > > > gradually > > > > > > increasing. > > > > > > > > > > > > 1) why we got this problem suddenly. > > > > > > 2) any remediation for this problem > > > > > > 3) is this problem will be solved, if we upgraded to new version. > > > > > > > > > > > > Regards, > > > > > > Ravikiran c > > > > > > > > > > > > > > > > > > > > >
Re: Out of memory error in ignite 1.6
I am new to ignite, if you need any details please let me know, I will check and provide those details. I need proper justification, if I need to upgrade to new version. Suddenly we are getting OOM error, after 2 years. Every day we are removing all old cache ids and adding new cache ids Our heap size is 32 GB. A On Sat 9 May, 2020, 12:06 AM Denis Magda, wrote: > You just stated that experienced OOM issues with no details for suggestions > or help with troubleshooting. Take heap dumps, analyze GC logs, etc: > > https://apacheignite.readme.io/docs/jvm-and-system-tuning#debugging-memory-usage-issues-and-gc-pauses > > - > Denis > > > On Fri, May 8, 2020 at 11:31 AM C Ravikiran > wrote: > > > Is this problem will be solved, if I upgraded to 2.8 version. > > > > > > On Fri 8 May, 2020, 10:02 PM Ilya Kasnacheev, > > > wrote: > > > > > Hello! > > > > > > I don't think you will find much expertise on Ignite 1.x here. I > > recommend > > > upgrading it to 2.8 eventually. > > > > > > Regards, > > > -- > > > Ilya Kasnacheev > > > > > > > > > пт, 8 мая 2020 г. в 09:57, C Ravikiran : > > > > > > > Hi Team, > > > > > > > > Our application is running past 2 year onwards, there was no problem > > with > > > > ignite. > > > > Suddenly last 2 week onwards, we are getting out of memory error in > > > ignite. > > > > > > > > There was no code changes in last 2 years. > > > > > > > > If we restart the ignite, our memory gradually increasing and we are > > > > getting out of memory error. > > > > > > > > Every day we will remove all the previous cache ids, and create new > > cach > > > > ids. > > > > We have only one se of cache ids, but still our heap size is > gradually > > > > increasing. > > > > > > > > 1) why we got this problem suddenly. > > > > 2) any remediation for this problem > > > > 3) is this problem will be solved, if we upgraded to new version. > > > > > > > > Regards, > > > > Ravikiran c > > > > > > > > > >
Re: Out of memory error in ignite 1.6
Is this problem will be solved, if I upgraded to 2.8 version. On Fri 8 May, 2020, 10:02 PM Ilya Kasnacheev, wrote: > Hello! > > I don't think you will find much expertise on Ignite 1.x here. I recommend > upgrading it to 2.8 eventually. > > Regards, > -- > Ilya Kasnacheev > > > пт, 8 мая 2020 г. в 09:57, C Ravikiran : > > > Hi Team, > > > > Our application is running past 2 year onwards, there was no problem with > > ignite. > > Suddenly last 2 week onwards, we are getting out of memory error in > ignite. > > > > There was no code changes in last 2 years. > > > > If we restart the ignite, our memory gradually increasing and we are > > getting out of memory error. > > > > Every day we will remove all the previous cache ids, and create new cach > > ids. > > We have only one se of cache ids, but still our heap size is gradually > > increasing. > > > > 1) why we got this problem suddenly. > > 2) any remediation for this problem > > 3) is this problem will be solved, if we upgraded to new version. > > > > Regards, > > Ravikiran c > > >
Out of memory error in ignite 1.6
Hi Team, Our application is running past 2 year onwards, there was no problem with ignite. Suddenly last 2 week onwards, we are getting out of memory error in ignite. There was no code changes in last 2 years. If we restart the ignite, our memory gradually increasing and we are getting out of memory error. Every day we will remove all the previous cache ids, and create new cach ids. We have only one se of cache ids, but still our heap size is gradually increasing. 1) why we got this problem suddenly. 2) any remediation for this problem 3) is this problem will be solved, if we upgraded to new version. Regards, Ravikiran c
