Issue with patch: https://issues.apache.org/jira/browse/IGNITE-10513
On 12/3/18 17:43, Dmitry Lazurkin wrote:
> OK. I have found steps to reproduce.
>
> For reproducing we need Ignite with slow disk. Or I known how to
> emulate slow hard disk:
>
> Add to partitions cycle in
> GridCacheDatabaseShar
OK. I have found steps to reproduce.
For reproducing we need Ignite with slow disk. Or I known how to emulate
slow hard disk:
Add to partitions cycle in
GridCacheDatabaseSharedManager#restorePartitionStates:
//...
for (int i = 0; i < grp.affinity().partitions(); i++) {
Hello.
I use version 2.6.0#20180710-sha1:669feacc and I can not reproduce this
issue. I have seen it at least 2 times, and I don't have full log =/ .
My cluster has lazy disk so restoration of partition states is too slow.
So I think there is race condition between ClientImpl and call of
TcpDisco
Hello.
I use version 2.6.0#20180710-sha1:669feacc and I can not reproduce this
issue. I have seen it at least 2 times, and I don't have full log =/ .
My cluster has lazy disk so restoration of partition states is too slow.
So I think there is race condition between ClientImpl and call of
TcpDisco
Hi,
The interesting (and disappointing) part is the NPE:
java.lang.NullPointerException: null
at
org.apache.ignite.spi.discovery.tcp.ClientImpl.sendJoinRequest(ClientImpl.java:666)
at
org.apache.ignite.spi.discovery.tcp.ClientImpl.joinTopology(ClientImpl.java:546)
at
org.ap
