Hello,ignite community.

I use muiti thred to write data to ignite's same table.The table is in
memory.I open streaming mode by using 'SET STREAMING ON ORDERED;' before my
write,and use 'SET STREAMING OFF;' to flush data.I found that these threads
may all wait on condition and never ends.

Here is the thread dump for one write thread:
"XXXXX" #708 daemon prio=5 os_prio=0 tid=0x00007f5ec800d800 nid=0xbea
waiting on condition [0x00007f5d01825000]
   java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:178)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:141)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection$StreamState.executeBatch(JdbcThinConnection.java:935)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection$StreamState.close0(JdbcThinConnection.java:987)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection$StreamState.close(JdbcThinConnection.java:977)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.executeNative(JdbcThinConnection.java:185)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:190)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
at com.zaxxer.hikari.pool.ProxyStatement.execute(ProxyStatement.java:95)
at
com.zaxxer.hikari.pool.HikariProxyStatement.execute(HikariProxyStatement.java)
...
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

I think these threads run in trouble after GridFutureAdapter calls 
LockSupport.park().

Do u have any ideas about such situation?How can I get rid of such trouble?




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Reply via email to