RE: Error:data-streamer-stripe....Timed out while waiting for schema update.
Hi Siva, Nodes started on local machine require more than 80% of physical RAM whatcan lead to significant slowdown due to swapping (please decrease JVM heapsize, data region size or checkpoint buffer size) [required=78152MB,available=65535MB] According to the warning, you don’t have enough heap size (65 MB). Try increasing it and check the result. From: sivaSent: Thursday, January 14, 2021 7:21 AMTo: user@ignite.apache.orgSubject: Error:data-streamer-stripeTimed out while waiting for schema update. Hi,I have .Net ClientServer Ignite Application.I am using DataStreamer to loaddata into ignite caches. while loading data client node getting stop with stackoverflow message .Andon server node displaying message on console likeError:data-streamer-stripeTimed out while waiting for schema update. And while again starting client node getting the following message onconsole. Nodes started on local machine require more than 80% of physical RAM whatcan lead to significant slowdown due to swapping (please decrease JVM heapsize, data region size or checkpoint buffer size) [required=78152MB,available=65535MB] what might be the issue and how to solve? Any other inform needed please let me know.Thanks. --Sent from: http://apache-ignite-users.70518.x6.nabble.com/
RE: Error:data-streamer-stripe....Timed out while waiting for schema update.
Hi, I am using these options to increase size -J-Xms6000m -J-Xmx6m while i am trying to increase heap size and on start again it's showing required size more everytime. first time running exe: # IgnitePersistenceApp.exe -J-Xms5000m -J-Xmx5m -J-XX:+UseParNewGC -J-XX:+AlwaysPreTouch -J-XX:+DisableExplicitGC -J-XX:MaxMetaspaceSize=2048m -springConfigUrl="server-config.xml" --console warning: Nodes started on local machine require more than 80% of physical RAM what can lead to significant slowdown due to swapping (please decrease JVM heap size, data region size or checkpoint buffer size) [required=78152MB, available=65535MB] Second time increased and running exe: # IgnitePersistenceApp.exe -J-Xms6000m -J-Xmx6m -J-XX:+UseParNewGC -J-XX:+AlwaysPreTouch -J-XX:+DisableExplicitGC -J-XX:MaxMetaspaceSize=2048m -springConfigUrl="server-config.xml" --console warning: Nodes started on local machine require more than 80% of physical RAM what can lead to significant slowdown due to swapping (please decrease JVM heap size, data region size or checkpoint buffer size) [required=87819MB, available=65535MB] every time it's keep increasing required size. Am i doing wrong? Thanks. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Error:data-streamer-stripe....Timed out while waiting for schema update.
Hi Siva, Please check your ignite configuration file and dataStorageConfiguration section not required at client side. Thanks & Regards, Charlin On Fri, 15 Jan 2021 at 10:33, siva wrote: > Hi, > I am using these options to increase size > -J-Xms6000m -J-Xmx6m > > while i am trying to increase heap size and on start again it's showing > required size more everytime. > > first time running exe: > # IgnitePersistenceApp.exe -J-Xms5000m -J-Xmx5m -J-XX:+UseParNewGC > -J-XX:+AlwaysPreTouch -J-XX:+DisableExplicitGC -J-XX:MaxMetaspaceSize=2048m > -springConfigUrl="server-config.xml" --console > > warning: > Nodes started on local machine require more than 80% of physical RAM what > can lead to significant slowdown due to swapping (please decrease JVM heap > size, data region size or checkpoint buffer size) [required=78152MB, > available=65535MB] > > Second time increased and running exe: > # IgnitePersistenceApp.exe -J-Xms6000m -J-Xmx6m -J-XX:+UseParNewGC > -J-XX:+AlwaysPreTouch -J-XX:+DisableExplicitGC -J-XX:MaxMetaspaceSize=2048m > -springConfigUrl="server-config.xml" --console > > warning: > Nodes started on local machine require more than 80% of physical RAM what > can lead to significant slowdown due to swapping (please decrease JVM heap > size, data region size or checkpoint buffer size) [required=87819MB, > available=65535MB] > > every time it's keep increasing required size. > Am i doing wrong? > Thanks. > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
Re: Error:data-streamer-stripe....Timed out while waiting for schema update.
Hi, I am providing size at server side by passing arguments.Not client side. Warning is showing while starting client. Here is the my server side start command # IgnitePersistenceApp.exe -J-Xms6000m -J-Xmx6m -J-XX:+UseParNewGC -J-XX:+AlwaysPreTouch -J-XX:+DisableExplicitGC -J-XX:MaxMetaspaceSize=2048m -springConfigUrl="server-config.xml" --console And using defaultDataRegionConfiguration.here is the dataStorageConfiguration section of server configuartion Thanks. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Error:data-streamer-stripe....Timed out while waiting for schema update.
Hello! If you're on .Net please make sure to explicitly register the types that you use, otherwise you can see this "schema update" locking. new BinaryConfiguration { TypeConfigurations = new List { new BinaryTypeConfiguration(typeof (Address)), new BinaryTypeConfiguration(typeof (TestModel)) } }; (then set it to IgniteConfiguration.BinaryConfiguration) Especially if you're using DataStreamer and not Cache API. If that does not help, please provide a reproducer project which demonstrates the issue. Regards, -- Ilya Kasnacheev чт, 14 янв. 2021 г. в 07:21, siva : > Hi, > I have .Net ClientServer Ignite Application.I am using DataStreamer to load > data into ignite caches. > > while loading data client node getting stop with stackoverflow message .And > on server node displaying message on console like > Error:data-streamer-stripeTimed out while waiting for schema update. > > > And while again starting client node getting the following message on > console. > > Nodes started on local machine require more than 80% of physical RAM what > can lead to significant slowdown due to swapping (please decrease JVM heap > size, data region size or checkpoint buffer size) [required=78152MB, > available=65535MB] > > what might be the issue and how to solve? > > Any other inform needed please let me know. > Thanks. > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >