Hi Alex, The issue is not related to GC all the time. i have attached the another gc and server log. GC looks good.
I am running my vertx-hazelcast application (which establishes ignite jdbc connection internally) inside kubernetes. Do you recommend any configurations for kubernetes ? Thanks, Anil On 28 June 2017 at 14:03, Anil <[email protected]> wrote: > HI Alex, > > Your sample program is working. i have compared the configuration and > every thing looks good. > > The only problem i see is something related to amount of data exports. All > other services working fine without any issue. > > I have attached the logs of two export client nodes. please let me know if > you see any issue. thanks. > > Thanks, > Anil > > On 24 June 2017 at 14:46, afedotov <[email protected]> wrote: > >> Hi, please provide full logs for all the nodes. >> Please add -Xms=1G to the client's VM options. >> >> Please try the code I attached before with exactly the same config for a >> server and a client that was mentioned in the message. If you see that it >> works in your environment then compare the config to the one of yours >> step-by-step. >> >> Kind regards, >> Alex >> >> >> 23 июня 2017 г. 12:48 PM пользователь "Anil [via Apache Ignite Users]" >> <[hidden >> email] <http:///user/SendEmail.jtp?type=node&node=14071&i=0>> написал: >> >>> Socket closed is the very frequent. May i now which causes the following >>> exception ? thanks, >>> >>> Some more log - >>> >>> >>> 2017-06-23 02:33:34 488 ERROR TcpDiscoverySpi:495 - Failed to send >>> message: TcpDiscoveryClientHeartbeatMessage >>> [super=TcpDiscoveryAbstractMessage [sndNodeId=null, >>> id=a71a444dc51-9956f95a-3bf9-4777-9431-cda0df43ff7d, >>> verifierNodeId=null, topVer=0, pendingIdx=0, failedNodes=null, >>> isClient=true]] >>> java.net.SocketException: Socket is closed >>> at java.net.Socket.getSendBufferSize(Socket.java:1215) >>> at org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.socketSt >>> ream(TcpDiscoverySpi.java:1254) >>> at org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.writeToS >>> ocket(TcpDiscoverySpi.java:1366) >>> at org.apache.ignite.spi.discovery.tcp.ClientImpl$SocketWriter. >>> body(ClientImpl.java:1095) >>> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.ja >>> va:62) >>> >>> >>> Thanks, >>> Anil >>> >>> On 23 June 2017 at 15:14, Anil <[hidden email] >>> <http:///user/SendEmail.jtp?type=node&node=14058&i=0>> wrote: >>> >>>> HI Alex, >>>> >>>> i tried XX:G1NewSizePercent=30 and ignite client is getting restarted >>>> very frequently, for each export operation. >>>> >>>> -Xmx6144m -XX:MetaspaceSize=512m -XX:+UnlockExperimentalVMOptions >>>> -XX:G1NewSizePercent=30 -XX:+UseTLAB -XX:+UseG1GC -XX:MaxGCPauseMillis=500 >>>> -XX:+ScavengeBeforeFullGC -XX:+DisableExplicitGC >>>> -Xloggc:C:/Anil/gc-client.log -XX:+HeapDumpOnOutOfMemoryError >>>> -XX:+PrintGCCause -XX:+PrintGCDetails -XX:+PrintAdaptiveSizePolicy >>>> -XX:+PrintGCTimeStamps -XX:+PrintGCDateStamps -XX:+HeapDumpAfterFullGC >>>> -XX:+ScavengeBeforeFullGC -XX:+DisableExplicitGC -XX:+AlwaysPreTouch >>>> -XX:+PrintFlagsFinal -XX:HeapDumpPath=C:/Anil/heapdump-client.hprof >>>> >>>> i have attached the gc logs and application logs >>>> >>>> I am not sure what is causing the ignite client restart for every >>>> restart. >>>> >>>> Do you have any suggestions ? please advice. >>>> >>>> Thanks, >>>> Anil >>>> >>>> >>>> On 21 June 2017 at 09:23, Anil <[hidden email] >>>> <http:///user/SendEmail.jtp?type=node&node=14058&i=1>> wrote: >>>> >>>>> Thanks Alex. I will test it in my local and share the results. >>>>> >>>>> Did you get a chance to look at the Jdbc driver's next() issue ? >>>>> Thanks. >>>>> >>>>> Thanks, >>>>> Anil >>>>> >>>> >>>> >>> >>> >>> ------------------------------ >>> If you reply to this email, your message will be added to the discussion >>> below: >>> http://apache-ignite-users.70518.x6.nabble.com/High-heap-on- >>> ignite-client-tp13594p14058.html >>> To start a new topic under Apache Ignite Users, email [hidden email] >>> <http:///user/SendEmail.jtp?type=node&node=14071&i=1> >>> To unsubscribe from Apache Ignite Users, click here. >>> NAML >>> <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> >>> >> >> ------------------------------ >> View this message in context: Re: High heap on ignite client >> <http://apache-ignite-users.70518.x6.nabble.com/High-heap-on-ignite-client-tp13594p14071.html> >> Sent from the Apache Ignite Users mailing list archive >> <http://apache-ignite-users.70518.x6.nabble.com/> at Nabble.com. >> > >
gc-client.log
Description: Binary data
server.log
Description: Binary data
