ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anil <anilk...@gmail.com>
Subject Re: High heap on ignite client
Date Fri, 23 Jun 2017 09:47:55 GMT
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.socketStream(TcpDiscoverySpi.java:1254)
        at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.writeToSocket(TcpDiscoverySpi.java:1366)
        at
org.apache.ignite.spi.discovery.tcp.ClientImpl$SocketWriter.body(ClientImpl.java:1095)
        at
org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)


Thanks,
Anil

On 23 June 2017 at 15:14, Anil <anilklce@gmail.com> 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 <anilklce@gmail.com> 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
>>
>
>

Mime
View raw message