[IGNITE-19086] Fix NullPointerException on building indexes if the number of replicas is more than one

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0.0-beta2
• Labels: ignite-3
• Epic Link: Dynamic indexes creation
• Assignee: Kirill Tkalenko
• Reporter: Kirill Tkalenko
• Reviewer: Aleksandr Polovtsev
• Created: 21/Mar/23 19:07
• Updated: 20/Apr/23 12:02
• Resolved: 20/Apr/23 12:02

Description

Fix NullPointerException on building indexes if the number of replicas is more than one. Fall is not stable.

Caused by: java.lang.NullPointerException
	at org.apache.ignite.internal.sql.engine.schema.IgniteTableImpl.lambda$insertAll$2(IgniteTableImpl.java:417)
	at java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:642)
	at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
	at java.base/java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2073)
	at org.apache.ignite.internal.replicator.ReplicaService.lambda$sendToReplica$2(ReplicaService.java:147)
	at java.base/java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:930)
	at java.base/java.util.concurrent.CompletableFuture$UniHandle.tryFire(CompletableFuture.java:907)
	at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
	at java.base/java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2073)
	at org.apache.ignite.network.DefaultMessagingService.onInvokeResponse(DefaultMessagingService.java:363)
	at org.apache.ignite.network.DefaultMessagingService.onMessage(DefaultMessagingService.java:328)
	at org.apache.ignite.network.DefaultMessagingService.lambda$onMessage$3(DefaultMessagingService.java:306)
	... 3 more

Issue Links

• links to: GitHub Pull Request #1963