You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Sergey Uttsel (Jira)" <ji...@apache.org> on 2023/05/12 08:54:00 UTC
[jira] [Updated] (IGNITE-19466) Empty data nodes on table creation
[ https://issues.apache.org/jira/browse/IGNITE-19466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergey Uttsel updated IGNITE-19466:
-----------------------------------
Description:
h3. *Motivation*
After introducing data nodes from DistributionZoneManager on table creation it became possible that a table is created with an empty data nodes value and therefore with empty assignments. It causes an exceptions like
{code:java}
Caused by: java.lang.AssertionError
at org.apache.ignite.internal.raft.RaftGroupServiceImpl.randomNode(RaftGroupServiceImpl.java:680)
at org.apache.ignite.internal.raft.RaftGroupServiceImpl.randomNode(RaftGroupServiceImpl.java:667)
at org.apache.ignite.internal.raft.RaftGroupServiceImpl.refreshLeader(RaftGroupServiceImpl.java:222)
at org.apache.ignite.internal.raft.RaftGroupServiceImpl.start(RaftGroupServiceImpl.java:178) {code}
because there are an empty peers on RaftGroupServiceImpl#start. The proper solution when a table is created with empty peers but remains unusable until the data nodes for the zone is updated and RaftGroupServiceImpl is started with peers.
h3. *Definition of Done*
If the date nodes for the zone are empty, then create a table without a raft group.
was:
h3. *Motivation*
After introducing data nodes from DistributionZoneManager on table creation it became possible that a table is created with an empty data nodes value and therefore with empty assignments. It causes an exceptions like
Caused by: java.lang.AssertionError
at org.apache.ignite.internal.raft.RaftGroupServiceImpl.randomNode(RaftGroupServiceImpl.java:680)
at org.apache.ignite.internal.raft.RaftGroupServiceImpl.randomNode(RaftGroupServiceImpl.java:667)
at org.apache.ignite.internal.raft.RaftGroupServiceImpl.refreshLeader(RaftGroupServiceImpl.java:222)
at org.apache.ignite.internal.raft.RaftGroupServiceImpl.start(RaftGroupServiceImpl.java:178)
because there are an empty peers on RaftGroupServiceImpl#start. The proper solution when a table is created with empty peers but remains unusable until the data nodes for the zone is updated and RaftGroupServiceImpl is started with peers.
h3. *Definition of Done*
If the date nodes for the zone are empty, then create a table without a raft group.
> Empty data nodes on table creation
> ----------------------------------
>
> Key: IGNITE-19466
> URL: https://issues.apache.org/jira/browse/IGNITE-19466
> Project: Ignite
> Issue Type: Bug
> Reporter: Sergey Uttsel
> Priority: Major
> Labels: ignite-3
>
> h3. *Motivation*
> After introducing data nodes from DistributionZoneManager on table creation it became possible that a table is created with an empty data nodes value and therefore with empty assignments. It causes an exceptions like
> {code:java}
> Caused by: java.lang.AssertionError
> at org.apache.ignite.internal.raft.RaftGroupServiceImpl.randomNode(RaftGroupServiceImpl.java:680)
> at org.apache.ignite.internal.raft.RaftGroupServiceImpl.randomNode(RaftGroupServiceImpl.java:667)
> at org.apache.ignite.internal.raft.RaftGroupServiceImpl.refreshLeader(RaftGroupServiceImpl.java:222)
> at org.apache.ignite.internal.raft.RaftGroupServiceImpl.start(RaftGroupServiceImpl.java:178) {code}
> because there are an empty peers on RaftGroupServiceImpl#start. The proper solution when a table is created with empty peers but remains unusable until the data nodes for the zone is updated and RaftGroupServiceImpl is started with peers.
> h3. *Definition of Done*
> If the date nodes for the zone are empty, then create a table without a raft group.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)