[jira] [Resolved] (IGNITE-15678) CPP: Build ODBC installers using cmake
[ https://issues.apache.org/jira/browse/IGNITE-15678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky resolved IGNITE-15678. -- Resolution: Fixed [~isapego] Thanks for review, merged > CPP: Build ODBC installers using cmake > -- > > Key: IGNITE-15678 > URL: https://issues.apache.org/jira/browse/IGNITE-15678 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Daschinsky >Assignee: Ivan Daschinsky >Priority: Major > Fix For: 2.12 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-15686) TableExample and KeyValueBinaryViewExample fail with NPE
[
https://issues.apache.org/jira/browse/IGNITE-15686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego reassigned IGNITE-15686:
Assignee: Igor Sapego
> TableExample and KeyValueBinaryViewExample fail with NPE
>
>
> Key: IGNITE-15686
> URL: https://issues.apache.org/jira/browse/IGNITE-15686
> Project: Ignite
> Issue Type: Bug
> Components: examples
>Reporter: Valentin Kulichenko
>Assignee: Igor Sapego
>Priority: Blocker
> Labels: ignite-3
> Fix For: 3.0.0-alpha3
>
>
> {noformat}
> Exception in thread "main" java.util.concurrent.CompletionException: class
> org.apache.ignite.internal.manager.ListenerRemovedException:
> java.lang.NullPointerException
> at
> java.base/java.util.concurrent.CompletableFuture.reportJoin(CompletableFuture.java:412)
> at
> java.base/java.util.concurrent.CompletableFuture.join(CompletableFuture.java:2108)
> at
> org.apache.ignite.internal.table.distributed.TableManager.createTable(TableManager.java:382)
> at
> org.apache.ignite.example.table.TableExample.main(TableExample.java:65)
> Caused by: class org.apache.ignite.internal.manager.ListenerRemovedException:
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.manager.Producer.removeListener(Producer.java:65)
> at
> org.apache.ignite.internal.table.distributed.TableManager.lambda$createTableAsync$10(TableManager.java:489)
> at
> java.base/java.util.concurrent.CompletableFuture.uniExceptionally(CompletableFuture.java:986)
> at
> java.base/java.util.concurrent.CompletableFuture$UniExceptionally.tryFire(CompletableFuture.java:970)
> at
> java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
> at
> java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1769)
> at
> java.base/java.util.concurrent.CompletableFuture$AsyncSupply.exec(CompletableFuture.java:1756)
> at
> java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290)
> at
> java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1016)
> at
> java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1665)
> at
> java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1598)
> at
> java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:183)
> Caused by: class org.apache.ignite.lang.IgniteInternalCheckedException:
> java.lang.NullPointerException
> ... 11 more
> Caused by: java.util.concurrent.CompletionException:
> java.lang.NullPointerException
> at
> java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:314)
> at
> java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:319)
> at
> java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1766)
> ... 6 more
> Caused by: java.lang.NullPointerException
> at
> org.apache.ignite.configuration.schemas.table.TableNode.partitions(Unknown
> Source)
> at
> org.apache.ignite.internal.table.distributed.TableManager.lambda$createTableAsync$8(TableManager.java:464)
> at
> org.apache.ignite.internal.configuration.tree.NamedListNode.create(NamedListNode.java:131)
> at
> org.apache.ignite.internal.table.distributed.TableManager.lambda$createTableAsync$9(TableManager.java:452)
> at
> org.apache.ignite.internal.configuration.DynamicConfiguration$1.descend(DynamicConfiguration.java:88)
> at
> org.apache.ignite.configuration.schemas.table.TablesNode.construct(Unknown
> Source)
> at
> org.apache.ignite.internal.configuration.DynamicConfiguration$1.descend(DynamicConfiguration.java:90)
> at
> org.apache.ignite.internal.configuration.SuperRoot.construct(SuperRoot.java:137)
> at
> org.apache.ignite.internal.configuration.DynamicConfiguration$1.descend(DynamicConfiguration.java:90)
> at
> org.apache.ignite.internal.configuration.ConfigurationChanger.lambda$changeInternally$1(ConfigurationChanger.java:376)
> at
> java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1764)
> ... 6 more
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15681) SLF4J header is printed out in CLI
[
https://issues.apache.org/jira/browse/IGNITE-15681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-15681:
-
Fix Version/s: 3.0.0-alpha3
> SLF4J header is printed out in CLI
> --
>
> Key: IGNITE-15681
> URL: https://issues.apache.org/jira/browse/IGNITE-15681
> Project: Ignite
> Issue Type: Bug
>Reporter: Valentin Kulichenko
>Priority: Major
> Labels: ignite-3, ignite-3-cli-tool
> Fix For: 3.0.0-alpha3
>
>
> Currently, every CLI command has the following output at the very beginning:
> {noformat}
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
> details.
> {noformat}
> This output is unnecessary and should be removed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15602) Add KubernetesConnectionConfiguration.DiscoveryPort property
[ https://issues.apache.org/jira/browse/IGNITE-15602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raymond Wilson updated IGNITE-15602: Release Note: This patch adds a DiscoveryPort configuration item in the Kubernetes configuration to allow an Ignite node running on Kubernetes to target a particular Ignite grid. (was: This patch adds a DiscoveryPort configuration item in the Kubernetes configuration to allow an Ignite running on Kubernetes to target a particular Ignite grid.) > Add KubernetesConnectionConfiguration.DiscoveryPort property > > > Key: IGNITE-15602 > URL: https://issues.apache.org/jira/browse/IGNITE-15602 > Project: Ignite > Issue Type: Improvement > Components: general >Affects Versions: 2.8.1, 2.10, 2.9.1, 2.11 >Reporter: Raymond Wilson >Assignee: Raymond Wilson >Priority: Minor > Labels: Kubernetes > Fix For: 2.12 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > The TcpDiscoveryKubernetesIpFinder hard wires the port passed to the > KubernetesServiceAddressResolver to 0, rather than a configurable > DiscoveryPort specified in KubernetesConnectionConfiguration. This means if > there is a client to more than one grid deployed to Kubernetes, that client > can only see one of the grids due to the port being hard wired to 0 causing > it to use the default port to locate the grid to join. > > KubernetesConnectionConfiguration should define a property, DiscoveryPort, > which the Ignite Kubernetes finder can use to locate a grid deployed in > Kubernetes. > This work item makes the following changes: > * Adds a DiscoveryPort property to KubernetesConnectionConfiguration > * Passes that DiscoveryPort configuration value to the > KubernetesServiceAddressResolver > > I have added a related documentation ticket here: > https://issues.apache.org/jira/browse/IGNITE-15630 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-15687) Unable to start more than one node on a single server
Valentin Kulichenko created IGNITE-15687:
Summary: Unable to start more than one node on a single server
Key: IGNITE-15687
URL: https://issues.apache.org/jira/browse/IGNITE-15687
Project: Ignite
Issue Type: Bug
Components: persistence
Reporter: Valentin Kulichenko
Fix For: 3.0.0-alpha3
If I try to start two server nodes on my laptop from the CLI tool, the second
fails to start with the following error:
{noformat}
Oct 05, 2021 5:13:06 PM org.apache.ignite.lang.IgniteLogger error
SEVERE: Unable to start node=[node-2].
class org.apache.ignite.lang.IgniteInternalException: While lock file:
work/vault/LOCK: Resource temporarily unavailable
at
org.apache.ignite.internal.vault.persistence.PersistentVaultService.start(PersistentVaultService.java:103)
at
org.apache.ignite.internal.vault.VaultManager.start(VaultManager.java:50)
at
org.apache.ignite.internal.app.IgniteImpl.doStartComponent(IgniteImpl.java:385)
at org.apache.ignite.internal.app.IgniteImpl.start(IgniteImpl.java:238)
at
org.apache.ignite.internal.app.IgnitionImpl.doStart(IgnitionImpl.java:142)
at
org.apache.ignite.internal.app.IgnitionImpl.start(IgnitionImpl.java:72)
at org.apache.ignite.app.IgniteCliRunner.main(IgniteCliRunner.java:59)
Caused by: org.rocksdb.RocksDBException: While lock file: work/vault/LOCK:
Resource temporarily unavailable
at org.rocksdb.RocksDB.open(Native Method)
at org.rocksdb.RocksDB.open(RocksDB.java:251)
at
org.apache.ignite.internal.vault.persistence.PersistentVaultService.start(PersistentVaultService.java:100)
... 6 more
Oct 05, 2021 5:13:06 PM org.apache.ignite.lang.IgniteLogger error
SEVERE: Unable to stop
component=[org.apache.ignite.internal.vault.VaultManager@1a1da881] within
node=[node-2]
java.lang.NullPointerException
at
org.apache.ignite.internal.vault.persistence.PersistentVaultService.close(PersistentVaultService.java:121)
at
org.apache.ignite.internal.vault.VaultManager.stop(VaultManager.java:56)
at
org.apache.ignite.internal.app.IgniteImpl.doStopNode(IgniteImpl.java:418)
at org.apache.ignite.internal.app.IgniteImpl.start(IgniteImpl.java:292)
at
org.apache.ignite.internal.app.IgnitionImpl.doStart(IgnitionImpl.java:142)
at
org.apache.ignite.internal.app.IgnitionImpl.start(IgnitionImpl.java:72)
at org.apache.ignite.app.IgniteCliRunner.main(IgniteCliRunner.java:59)
Exception in thread "main" class org.apache.ignite.lang.IgniteException: Unable
to start node=[node-2].
at
org.apache.ignite.internal.app.IgnitionImpl.doStart(IgnitionImpl.java:147)
at
org.apache.ignite.internal.app.IgnitionImpl.start(IgnitionImpl.java:72)
at org.apache.ignite.app.IgniteCliRunner.main(IgniteCliRunner.java:59)
Caused by: class org.apache.ignite.lang.IgniteException: Unable to start
node=[node-2].
at org.apache.ignite.internal.app.IgniteImpl.start(IgniteImpl.java:294)
at
org.apache.ignite.internal.app.IgnitionImpl.doStart(IgnitionImpl.java:142)
... 2 more
Caused by: class org.apache.ignite.lang.IgniteInternalException: While lock
file: work/vault/LOCK: Resource temporarily unavailable
at
org.apache.ignite.internal.vault.persistence.PersistentVaultService.start(PersistentVaultService.java:103)
at
org.apache.ignite.internal.vault.VaultManager.start(VaultManager.java:50)
at
org.apache.ignite.internal.app.IgniteImpl.doStartComponent(IgniteImpl.java:385)
at org.apache.ignite.internal.app.IgniteImpl.start(IgniteImpl.java:238)
... 3 more
Caused by: org.rocksdb.RocksDBException: While lock file: work/vault/LOCK:
Resource temporarily unavailable
at org.rocksdb.RocksDB.open(Native Method)
at org.rocksdb.RocksDB.open(RocksDB.java:251)
at
org.apache.ignite.internal.vault.persistence.PersistentVaultService.start(PersistentVaultService.java:100)
... 6 more
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-15686) TableExample and KeyValueBinaryViewExample fail with NPE
Valentin Kulichenko created IGNITE-15686:
Summary: TableExample and KeyValueBinaryViewExample fail with NPE
Key: IGNITE-15686
URL: https://issues.apache.org/jira/browse/IGNITE-15686
Project: Ignite
Issue Type: Bug
Components: examples
Reporter: Valentin Kulichenko
Fix For: 3.0.0-alpha3
{noformat}
Exception in thread "main" java.util.concurrent.CompletionException: class
org.apache.ignite.internal.manager.ListenerRemovedException:
java.lang.NullPointerException
at
java.base/java.util.concurrent.CompletableFuture.reportJoin(CompletableFuture.java:412)
at
java.base/java.util.concurrent.CompletableFuture.join(CompletableFuture.java:2108)
at
org.apache.ignite.internal.table.distributed.TableManager.createTable(TableManager.java:382)
at
org.apache.ignite.example.table.TableExample.main(TableExample.java:65)
Caused by: class org.apache.ignite.internal.manager.ListenerRemovedException:
java.lang.NullPointerException
at
org.apache.ignite.internal.manager.Producer.removeListener(Producer.java:65)
at
org.apache.ignite.internal.table.distributed.TableManager.lambda$createTableAsync$10(TableManager.java:489)
at
java.base/java.util.concurrent.CompletableFuture.uniExceptionally(CompletableFuture.java:986)
at
java.base/java.util.concurrent.CompletableFuture$UniExceptionally.tryFire(CompletableFuture.java:970)
at
java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
at
java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1769)
at
java.base/java.util.concurrent.CompletableFuture$AsyncSupply.exec(CompletableFuture.java:1756)
at
java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290)
at
java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1016)
at
java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1665)
at
java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1598)
at
java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:183)
Caused by: class org.apache.ignite.lang.IgniteInternalCheckedException:
java.lang.NullPointerException
... 11 more
Caused by: java.util.concurrent.CompletionException:
java.lang.NullPointerException
at
java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:314)
at
java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:319)
at
java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1766)
... 6 more
Caused by: java.lang.NullPointerException
at
org.apache.ignite.configuration.schemas.table.TableNode.partitions(Unknown
Source)
at
org.apache.ignite.internal.table.distributed.TableManager.lambda$createTableAsync$8(TableManager.java:464)
at
org.apache.ignite.internal.configuration.tree.NamedListNode.create(NamedListNode.java:131)
at
org.apache.ignite.internal.table.distributed.TableManager.lambda$createTableAsync$9(TableManager.java:452)
at
org.apache.ignite.internal.configuration.DynamicConfiguration$1.descend(DynamicConfiguration.java:88)
at
org.apache.ignite.configuration.schemas.table.TablesNode.construct(Unknown
Source)
at
org.apache.ignite.internal.configuration.DynamicConfiguration$1.descend(DynamicConfiguration.java:90)
at
org.apache.ignite.internal.configuration.SuperRoot.construct(SuperRoot.java:137)
at
org.apache.ignite.internal.configuration.DynamicConfiguration$1.descend(DynamicConfiguration.java:90)
at
org.apache.ignite.internal.configuration.ConfigurationChanger.lambda$changeInternally$1(ConfigurationChanger.java:376)
at
java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1764)
... 6 more
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-15685) Examples should be renamed
Valentin Kulichenko created IGNITE-15685:
Summary: Examples should be renamed
Key: IGNITE-15685
URL: https://issues.apache.org/jira/browse/IGNITE-15685
Project: Ignite
Issue Type: Bug
Components: examples
Reporter: Valentin Kulichenko
Assignee: Valentin Kulichenko
Fix For: 3.0.0-alpha3
The Ignite 3 Table API changed, so current example names look inconsistent.
Need to rename:
* {{TableExample}} to {{RecordViewExample}}.
* {{KeyValueBinaryViewExample}} to {{KeyValueViewExample}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15685) Examples should be renamed
[
https://issues.apache.org/jira/browse/IGNITE-15685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-15685:
-
Priority: Blocker (was: Major)
> Examples should be renamed
> --
>
> Key: IGNITE-15685
> URL: https://issues.apache.org/jira/browse/IGNITE-15685
> Project: Ignite
> Issue Type: Bug
> Components: examples
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Blocker
> Labels: ignite-3
> Fix For: 3.0.0-alpha3
>
>
> The Ignite 3 Table API changed, so current example names look inconsistent.
> Need to rename:
> * {{TableExample}} to {{RecordViewExample}}.
> * {{KeyValueBinaryViewExample}} to {{KeyValueViewExample}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-15683) CLI tool says 'Can't start the node' even though the node is successfully started
[
https://issues.apache.org/jira/browse/IGNITE-15683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko reassigned IGNITE-15683:
Assignee: Valentin Kulichenko
> CLI tool says 'Can't start the node' even though the node is successfully
> started
> -
>
> Key: IGNITE-15683
> URL: https://issues.apache.org/jira/browse/IGNITE-15683
> Project: Ignite
> Issue Type: Bug
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Blocker
> Labels: ignite-3, ignite-3-cli-tool
> Fix For: 3.0.0-alpha3
>
>
> {{ignite node start}} command fails with the following message even though
> the node actually starts:
> {code}
> Starting a new Ignite node...
> Can't start the node. Read logs for details:
> /Users/vkulichenko/GridGain/ignite-3/target/apache-ignite-3.0.0-alpha3/ignite-log/node-1.log
> {code}
> Looks like this happens because there is the following line in the log:
> {noformat}
> Oct 05, 2021 3:41:45 PM org.apache.ignite.lang.IgniteLogger
> logInternalExceptional
> {noformat}
> The tool treats it as a failure because of this condition (see
> {{NodeManager}} class):
> {code}
> else if (content.contains("Exception"))
> throw new IgniteCLIException("Can't start the node. Read logs for
> details: " + file);
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15684) Issues with the SqlJdbcExample
[
https://issues.apache.org/jira/browse/IGNITE-15684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-15684:
-
Component/s: sql
> Issues with the SqlJdbcExample
> --
>
> Key: IGNITE-15684
> URL: https://issues.apache.org/jira/browse/IGNITE-15684
> Project: Ignite
> Issue Type: Bug
> Components: examples, sql
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Blocker
> Labels: ignite-3
> Fix For: 3.0.0-alpha3
>
>
> The new {{SqlJdbcExample}} doesn't work in a standalone project.
> Specifically, there are two issues:
> # Path to the config file is incorrect which prevents the server node from
> starting. The path should be the same as in other examples.
> # JDBC driver can't be found, because {{ignite-client}} dependency is not
> included.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-15684) Issues with the SqlJdbcExample
[
https://issues.apache.org/jira/browse/IGNITE-15684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko reassigned IGNITE-15684:
Assignee: Valentin Kulichenko
> Issues with the SqlJdbcExample
> --
>
> Key: IGNITE-15684
> URL: https://issues.apache.org/jira/browse/IGNITE-15684
> Project: Ignite
> Issue Type: Bug
> Components: examples
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Blocker
> Labels: ignite-3
> Fix For: 3.0.0-alpha3
>
>
> The new {{SqlJdbcExample}} doesn't work in a standalone project.
> Specifically, there are two issues:
> # Path to the config file is incorrect which prevents the server node from
> starting. The path should be the same as in other examples.
> # JDBC driver can't be found, because {{ignite-client}} dependency is not
> included.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15684) Issues with the SqlJdbcExample
[
https://issues.apache.org/jira/browse/IGNITE-15684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-15684:
-
Labels: ignite-3 (was: ignite-3 ignite-3-cli-tool)
> Issues with the SqlJdbcExample
> --
>
> Key: IGNITE-15684
> URL: https://issues.apache.org/jira/browse/IGNITE-15684
> Project: Ignite
> Issue Type: Bug
> Components: examples
>Reporter: Valentin Kulichenko
>Priority: Blocker
> Labels: ignite-3
> Fix For: 3.0.0-alpha3
>
>
> The new {{SqlJdbcExample}} doesn't work in a standalone project.
> Specifically, there are two issues:
> # Path to the config file is incorrect which prevents the server node from
> starting. The path should be the same as in other examples.
> # JDBC driver can't be found, because {{ignite-client}} dependency is not
> included.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-15684) Issues with the SqlJdbcExample
Valentin Kulichenko created IGNITE-15684:
Summary: Issues with the SqlJdbcExample
Key: IGNITE-15684
URL: https://issues.apache.org/jira/browse/IGNITE-15684
Project: Ignite
Issue Type: Bug
Components: examples
Reporter: Valentin Kulichenko
Fix For: 3.0.0-alpha3
The new {{SqlJdbcExample}} doesn't work in a standalone project. Specifically,
there are two issues:
# Path to the config file is incorrect which prevents the server node from
starting. The path should be the same as in other examples.
# JDBC driver can't be found, because {{ignite-client}} dependency is not
included.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15683) CLI tool says 'Can't start the node' even though the node is successfully started
[
https://issues.apache.org/jira/browse/IGNITE-15683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17424730#comment-17424730
]
Valentin Kulichenko commented on IGNITE-15683:
--
As a side, there is one more issue with this condition: it doesn't force the
tool to kill the external process (like we do in case of a timeout). As a
short-term solution, I think we can simply remove this condition - if something
goes wrong, the tool will just wait for the timeout and kill the process if
needed.
> CLI tool says 'Can't start the node' even though the node is successfully
> started
> -
>
> Key: IGNITE-15683
> URL: https://issues.apache.org/jira/browse/IGNITE-15683
> Project: Ignite
> Issue Type: Bug
>Reporter: Valentin Kulichenko
>Priority: Blocker
> Labels: ignite-3, ignite-3-cli-tool
> Fix For: 3.0.0-alpha3
>
>
> {{ignite node start}} command fails with the following message even though
> the node actually starts:
> {code}
> Starting a new Ignite node...
> Can't start the node. Read logs for details:
> /Users/vkulichenko/GridGain/ignite-3/target/apache-ignite-3.0.0-alpha3/ignite-log/node-1.log
> {code}
> Looks like this happens because there is the following line in the log:
> {noformat}
> Oct 05, 2021 3:41:45 PM org.apache.ignite.lang.IgniteLogger
> logInternalExceptional
> {noformat}
> The tool treats it as a failure because of this condition (see
> {{NodeManager}} class):
> {code}
> else if (content.contains("Exception"))
> throw new IgniteCLIException("Can't start the node. Read logs for
> details: " + file);
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15682) Verbose output produced by 'ignite init' and 'ignite module add' commands
[
https://issues.apache.org/jira/browse/IGNITE-15682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-15682:
-
Priority: Blocker (was: Major)
> Verbose output produced by 'ignite init' and 'ignite module add' commands
> -
>
> Key: IGNITE-15682
> URL: https://issues.apache.org/jira/browse/IGNITE-15682
> Project: Ignite
> Issue Type: Bug
>Reporter: Valentin Kulichenko
>Priority: Blocker
> Labels: ignite-3, ignite-3-cli-tool
> Fix For: 3.0.0-alpha3
>
>
> {{ignite init}} and {{ignite module add}} commands started to output a lot of
> unnecessary logging information (see a sample below). This output should be
> removed from the console output.
> {noformat}
> Installing org.apache.ignite:ignite-runner:3.0.0-alpha3...
> Oct 05, 2021 3:38:20 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: :: resolving dependencies ::
> org.apache.ignite#installer-envelope;working
> Oct 05, 2021 3:38:20 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: confs: [default]
> |>
> | 1%Oct 05, 2021 3:38:22 PM
> org.apache.ignite.lang.IgniteLogger logInternal
> INFO: found org.apache.ignite#ignite-runner;3.0.0-alpha3 in
> /content/repositories/orgapacheignite-1527
> |=>
> | 2%Oct 05, 2021 3:38:24 PM
> org.apache.ignite.lang.IgniteLogger logInternal
> INFO: found org.apache.ignite#ignite-configuration;3.0.0-alpha3 in
> /content/repositories/orgapacheignite-1527
> |==>
> | 3%Oct 05, 2021 3:38:25 PM
> org.apache.ignite.lang.IgniteLogger logInternal
> INFO: found org.apache.ignite#ignite-bytecode;3.0.0-alpha3 in
> /content/repositories/orgapacheignite-1527
> |===>
> | 4%Oct 05, 2021 3:38:26 PM
> org.apache.ignite.lang.IgniteLogger logInternal
> INFO: found org.jetbrains#annotations;20.1.0 in central
> |>
> | 5%Oct 05, 2021 3:38:27 PM
> org.apache.ignite.lang.IgniteLogger logInternal
> INFO: found org.ow2.asm#asm;9.0 in central
> |=>
> | 6%Oct 05, 2021 3:38:28 PM
> org.apache.ignite.lang.IgniteLogger logInternal
> INFO: found org.ow2.asm#asm-tree;9.0 in central
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-15683) CLI tool says 'Can't start the node' even though the node is successfully started
Valentin Kulichenko created IGNITE-15683:
Summary: CLI tool says 'Can't start the node' even though the node
is successfully started
Key: IGNITE-15683
URL: https://issues.apache.org/jira/browse/IGNITE-15683
Project: Ignite
Issue Type: Bug
Reporter: Valentin Kulichenko
Fix For: 3.0.0-alpha3
{{ignite node start}} command fails with the following message even though the
node actually starts:
{code}
Starting a new Ignite node...
Can't start the node. Read logs for details:
/Users/vkulichenko/GridGain/ignite-3/target/apache-ignite-3.0.0-alpha3/ignite-log/node-1.log
{code}
Looks like this happens because there is the following line in the log:
{noformat}
Oct 05, 2021 3:41:45 PM org.apache.ignite.lang.IgniteLogger
logInternalExceptional
{noformat}
The tool treats it as a failure because of this condition (see {{NodeManager}}
class):
{code}
else if (content.contains("Exception"))
throw new IgniteCLIException("Can't start the node. Read logs for details:
" + file);
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15683) CLI tool says 'Can't start the node' even though the node is successfully started
[
https://issues.apache.org/jira/browse/IGNITE-15683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-15683:
-
Priority: Blocker (was: Major)
> CLI tool says 'Can't start the node' even though the node is successfully
> started
> -
>
> Key: IGNITE-15683
> URL: https://issues.apache.org/jira/browse/IGNITE-15683
> Project: Ignite
> Issue Type: Bug
>Reporter: Valentin Kulichenko
>Priority: Blocker
> Labels: ignite-3, ignite-3-cli-tool
> Fix For: 3.0.0-alpha3
>
>
> {{ignite node start}} command fails with the following message even though
> the node actually starts:
> {code}
> Starting a new Ignite node...
> Can't start the node. Read logs for details:
> /Users/vkulichenko/GridGain/ignite-3/target/apache-ignite-3.0.0-alpha3/ignite-log/node-1.log
> {code}
> Looks like this happens because there is the following line in the log:
> {noformat}
> Oct 05, 2021 3:41:45 PM org.apache.ignite.lang.IgniteLogger
> logInternalExceptional
> {noformat}
> The tool treats it as a failure because of this condition (see
> {{NodeManager}} class):
> {code}
> else if (content.contains("Exception"))
> throw new IgniteCLIException("Can't start the node. Read logs for
> details: " + file);
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15682) Verbose output produced by 'ignite init' and 'ignite module add' commands
[
https://issues.apache.org/jira/browse/IGNITE-15682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-15682:
-
Fix Version/s: 3.0.0-alpha3
> Verbose output produced by 'ignite init' and 'ignite module add' commands
> -
>
> Key: IGNITE-15682
> URL: https://issues.apache.org/jira/browse/IGNITE-15682
> Project: Ignite
> Issue Type: Bug
>Reporter: Valentin Kulichenko
>Priority: Major
> Labels: ignite-3, ignite-3-cli-tool
> Fix For: 3.0.0-alpha3
>
>
> {{ignite init}} and {{ignite module add}} commands started to output a lot of
> unnecessary logging information (see a sample below). This output should be
> removed from the console output.
> {noformat}
> Installing org.apache.ignite:ignite-runner:3.0.0-alpha3...
> Oct 05, 2021 3:38:20 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: :: resolving dependencies ::
> org.apache.ignite#installer-envelope;working
> Oct 05, 2021 3:38:20 PM org.apache.ignite.lang.IgniteLogger logInternal
> INFO: confs: [default]
> |>
> | 1%Oct 05, 2021 3:38:22 PM
> org.apache.ignite.lang.IgniteLogger logInternal
> INFO: found org.apache.ignite#ignite-runner;3.0.0-alpha3 in
> /content/repositories/orgapacheignite-1527
> |=>
> | 2%Oct 05, 2021 3:38:24 PM
> org.apache.ignite.lang.IgniteLogger logInternal
> INFO: found org.apache.ignite#ignite-configuration;3.0.0-alpha3 in
> /content/repositories/orgapacheignite-1527
> |==>
> | 3%Oct 05, 2021 3:38:25 PM
> org.apache.ignite.lang.IgniteLogger logInternal
> INFO: found org.apache.ignite#ignite-bytecode;3.0.0-alpha3 in
> /content/repositories/orgapacheignite-1527
> |===>
> | 4%Oct 05, 2021 3:38:26 PM
> org.apache.ignite.lang.IgniteLogger logInternal
> INFO: found org.jetbrains#annotations;20.1.0 in central
> |>
> | 5%Oct 05, 2021 3:38:27 PM
> org.apache.ignite.lang.IgniteLogger logInternal
> INFO: found org.ow2.asm#asm;9.0 in central
> |=>
> | 6%Oct 05, 2021 3:38:28 PM
> org.apache.ignite.lang.IgniteLogger logInternal
> INFO: found org.ow2.asm#asm-tree;9.0 in central
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-15682) Verbose output produced by 'ignite init' and 'ignite module add' commands
Valentin Kulichenko created IGNITE-15682:
Summary: Verbose output produced by 'ignite init' and 'ignite
module add' commands
Key: IGNITE-15682
URL: https://issues.apache.org/jira/browse/IGNITE-15682
Project: Ignite
Issue Type: Bug
Reporter: Valentin Kulichenko
{{ignite init}} and {{ignite module add}} commands started to output a lot of
unnecessary logging information (see a sample below). This output should be
removed from the console output.
{noformat}
Installing org.apache.ignite:ignite-runner:3.0.0-alpha3...
Oct 05, 2021 3:38:20 PM org.apache.ignite.lang.IgniteLogger logInternal
INFO: :: resolving dependencies :: org.apache.ignite#installer-envelope;working
Oct 05, 2021 3:38:20 PM org.apache.ignite.lang.IgniteLogger logInternal
INFO: confs: [default]
|>
| 1%Oct 05, 2021 3:38:22 PM org.apache.ignite.lang.IgniteLogger
logInternal
INFO: found org.apache.ignite#ignite-runner;3.0.0-alpha3 in
/content/repositories/orgapacheignite-1527
|=>
| 2%Oct 05, 2021 3:38:24 PM org.apache.ignite.lang.IgniteLogger
logInternal
INFO: found org.apache.ignite#ignite-configuration;3.0.0-alpha3 in
/content/repositories/orgapacheignite-1527
|==>
| 3%Oct 05, 2021 3:38:25 PM org.apache.ignite.lang.IgniteLogger
logInternal
INFO: found org.apache.ignite#ignite-bytecode;3.0.0-alpha3 in
/content/repositories/orgapacheignite-1527
|===>
| 4%Oct 05, 2021 3:38:26 PM org.apache.ignite.lang.IgniteLogger
logInternal
INFO: found org.jetbrains#annotations;20.1.0 in central
|>
| 5%Oct 05, 2021 3:38:27 PM org.apache.ignite.lang.IgniteLogger
logInternal
INFO: found org.ow2.asm#asm;9.0 in central
|=>
| 6%Oct 05, 2021 3:38:28 PM org.apache.ignite.lang.IgniteLogger
logInternal
INFO: found org.ow2.asm#asm-tree;9.0 in central
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-15681) SLF4J header is printed out in CLI
Valentin Kulichenko created IGNITE-15681:
Summary: SLF4J header is printed out in CLI
Key: IGNITE-15681
URL: https://issues.apache.org/jira/browse/IGNITE-15681
Project: Ignite
Issue Type: Bug
Reporter: Valentin Kulichenko
Currently, every CLI command has the following output at the very beginning:
{noformat}
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
details.
{noformat}
This output is unnecessary and should be removed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15547) QueryTypeDescriptorImpl: Accept Classes/Enums extending an Interface which is used as cache indexed field
[
https://issues.apache.org/jira/browse/IGNITE-15547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17424714#comment-17424714
]
Ignite TC Bot commented on IGNITE-15547:
{panel:title=Branch: [pull/9427/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9427/head] Base: [master] : New Tests
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Cache 5{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=6211753]]
* {color:#013220}IgniteCacheWithIndexingTestSuite:
EnumClassImplementingIndexedInterfaceTest.testInsertTableVarColumns -
PASSED{color}
* {color:#013220}IgniteCacheWithIndexingTestSuite:
EnumClassImplementingIndexedInterfaceTest.testInsertValueVarColumns -
PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6211795&buildTypeId=IgniteTests24Java8_RunAll]
> QueryTypeDescriptorImpl: Accept Classes/Enums extending an Interface which is
> used as cache indexed field
> -
>
> Key: IGNITE-15547
> URL: https://issues.apache.org/jira/browse/IGNITE-15547
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.10
>Reporter: Andrian Boscanean
>Assignee: Andrian Boscanean
>Priority: Major
> Fix For: 2.12
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Currently Classes/Enums that extend an interface which is used as Indexed
> field are not allowed.
> Example
> @QuerySqlField(index = true)
> private TestInterface testInterface;
> --
> enum TestEnum1 implements TestInterface
> { VALUE_1, VALUE_2, VALUE_3 }
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15538) Starting node via CLI can lead to NullPointerException
[
https://issues.apache.org/jira/browse/IGNITE-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17424589#comment-17424589
]
Vyacheslav Koptilin commented on IGNITE-15538:
--
Hello [~maliev],
Could you please take a look?
> Starting node via CLI can lead to NullPointerException
> --
>
> Key: IGNITE-15538
> URL: https://issues.apache.org/jira/browse/IGNITE-15538
> Project: Ignite
> Issue Type: Bug
>Reporter: Kirill Gusakov
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha3
>
>
> Trying to start a new node via CLI without specifying metastorage raft group
> may lead to the following exception:
> {code:java}
> Exception in thread "main" class org.apache.ignite.lang.IgniteException:
> Unable to start node=[new1].
> at org.apache.ignite.internal.app.IgniteImpl.start(IgniteImpl.java:293)
> at
> org.apache.ignite.internal.app.IgnitionImpl.doStart(IgnitionImpl.java:141)
> at
> org.apache.ignite.internal.app.IgnitionImpl.start(IgnitionImpl.java:72)
> at org.apache.ignite.app.IgniteCliRunner.main(IgniteCliRunner.java:59)
> Caused by: java.lang.NullPointerException
> at
> org.apache.ignite.raft.jraft.rpc.impl.RaftGroupServiceImpl.sendWithRetry(RaftGroupServiceImpl.java:456)
> at
> org.apache.ignite.raft.jraft.rpc.impl.RaftGroupServiceImpl.refreshLeader(RaftGroupServiceImpl.java:202)
> at
> org.apache.ignite.raft.jraft.rpc.impl.RaftGroupServiceImpl.start(RaftGroupServiceImpl.java:158)
> at org.apache.ignite.internal.raft.Loza.prepareRaftGroup(Loza.java:99)
> at
> org.apache.ignite.internal.metastorage.MetaStorageManager.start(MetaStorageManager.java:167)
> at
> org.apache.ignite.internal.app.IgniteImpl.doStartComponent(IgniteImpl.java:384)
> at org.apache.ignite.internal.app.IgniteImpl.start(IgniteImpl.java:278)
> {code}
> Also, trying to start a new node without a configuration file (which is
> optional) results in NullPointerException:
> {code:java}
> Exception in thread "main" java.lang.NullPointerException
> at org.apache.ignite.app.IgniteCliRunner.main(IgniteCliRunner.java:59)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15538) Starting node via CLI can lead to NullPointerException
[
https://issues.apache.org/jira/browse/IGNITE-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17424588#comment-17424588
]
Vyacheslav Koptilin commented on IGNITE-15538:
--
Looks like, the first NPE is already fixed by IGNITE-15027
> Starting node via CLI can lead to NullPointerException
> --
>
> Key: IGNITE-15538
> URL: https://issues.apache.org/jira/browse/IGNITE-15538
> Project: Ignite
> Issue Type: Bug
>Reporter: Kirill Gusakov
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha3
>
>
> Trying to start a new node via CLI without specifying metastorage raft group
> may lead to the following exception:
> {code:java}
> Exception in thread "main" class org.apache.ignite.lang.IgniteException:
> Unable to start node=[new1].
> at org.apache.ignite.internal.app.IgniteImpl.start(IgniteImpl.java:293)
> at
> org.apache.ignite.internal.app.IgnitionImpl.doStart(IgnitionImpl.java:141)
> at
> org.apache.ignite.internal.app.IgnitionImpl.start(IgnitionImpl.java:72)
> at org.apache.ignite.app.IgniteCliRunner.main(IgniteCliRunner.java:59)
> Caused by: java.lang.NullPointerException
> at
> org.apache.ignite.raft.jraft.rpc.impl.RaftGroupServiceImpl.sendWithRetry(RaftGroupServiceImpl.java:456)
> at
> org.apache.ignite.raft.jraft.rpc.impl.RaftGroupServiceImpl.refreshLeader(RaftGroupServiceImpl.java:202)
> at
> org.apache.ignite.raft.jraft.rpc.impl.RaftGroupServiceImpl.start(RaftGroupServiceImpl.java:158)
> at org.apache.ignite.internal.raft.Loza.prepareRaftGroup(Loza.java:99)
> at
> org.apache.ignite.internal.metastorage.MetaStorageManager.start(MetaStorageManager.java:167)
> at
> org.apache.ignite.internal.app.IgniteImpl.doStartComponent(IgniteImpl.java:384)
> at org.apache.ignite.internal.app.IgniteImpl.start(IgniteImpl.java:278)
> {code}
> Also, trying to start a new node without a configuration file (which is
> optional) results in NullPointerException:
> {code:java}
> Exception in thread "main" java.lang.NullPointerException
> at org.apache.ignite.app.IgniteCliRunner.main(IgniteCliRunner.java:59)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15538) Starting node via CLI can lead to NullPointerException
[
https://issues.apache.org/jira/browse/IGNITE-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-15538:
-
Description:
Trying to start a new node via CLI without specifying metastorage raft group
may lead to the following exception:
{code:java}
Exception in thread "main" class org.apache.ignite.lang.IgniteException: Unable
to start node=[new1].
at org.apache.ignite.internal.app.IgniteImpl.start(IgniteImpl.java:293)
at
org.apache.ignite.internal.app.IgnitionImpl.doStart(IgnitionImpl.java:141)
at
org.apache.ignite.internal.app.IgnitionImpl.start(IgnitionImpl.java:72)
at org.apache.ignite.app.IgniteCliRunner.main(IgniteCliRunner.java:59)
Caused by: java.lang.NullPointerException
at
org.apache.ignite.raft.jraft.rpc.impl.RaftGroupServiceImpl.sendWithRetry(RaftGroupServiceImpl.java:456)
at
org.apache.ignite.raft.jraft.rpc.impl.RaftGroupServiceImpl.refreshLeader(RaftGroupServiceImpl.java:202)
at
org.apache.ignite.raft.jraft.rpc.impl.RaftGroupServiceImpl.start(RaftGroupServiceImpl.java:158)
at org.apache.ignite.internal.raft.Loza.prepareRaftGroup(Loza.java:99)
at
org.apache.ignite.internal.metastorage.MetaStorageManager.start(MetaStorageManager.java:167)
at
org.apache.ignite.internal.app.IgniteImpl.doStartComponent(IgniteImpl.java:384)
at org.apache.ignite.internal.app.IgniteImpl.start(IgniteImpl.java:278)
{code}
Also, trying to start a new node without a configuration file (which is
optional) results in NullPointerException:
{code:java}
Exception in thread "main" java.lang.NullPointerException
at org.apache.ignite.app.IgniteCliRunner.main(IgniteCliRunner.java:59)
{code}
was:
{code:java}
Exception in thread "main" class org.apache.ignite.lang.IgniteException: Unable
to start node=[new1].
at org.apache.ignite.internal.app.IgniteImpl.start(IgniteImpl.java:293)
at
org.apache.ignite.internal.app.IgnitionImpl.doStart(IgnitionImpl.java:141)
at
org.apache.ignite.internal.app.IgnitionImpl.start(IgnitionImpl.java:72)
at org.apache.ignite.app.IgniteCliRunner.main(IgniteCliRunner.java:59)
Caused by: java.lang.NullPointerException
at
org.apache.ignite.raft.jraft.rpc.impl.RaftGroupServiceImpl.sendWithRetry(RaftGroupServiceImpl.java:456)
at
org.apache.ignite.raft.jraft.rpc.impl.RaftGroupServiceImpl.refreshLeader(RaftGroupServiceImpl.java:202)
at
org.apache.ignite.raft.jraft.rpc.impl.RaftGroupServiceImpl.start(RaftGroupServiceImpl.java:158)
at org.apache.ignite.internal.raft.Loza.prepareRaftGroup(Loza.java:99)
at
org.apache.ignite.internal.metastorage.MetaStorageManager.start(MetaStorageManager.java:167)
at
org.apache.ignite.internal.app.IgniteImpl.doStartComponent(IgniteImpl.java:384)
at org.apache.ignite.internal.app.IgniteImpl.start(IgniteImpl.java:278)
{code}
> Starting node via CLI can lead to NullPointerException
> --
>
> Key: IGNITE-15538
> URL: https://issues.apache.org/jira/browse/IGNITE-15538
> Project: Ignite
> Issue Type: Bug
>Reporter: Kirill Gusakov
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha3
>
>
> Trying to start a new node via CLI without specifying metastorage raft group
> may lead to the following exception:
> {code:java}
> Exception in thread "main" class org.apache.ignite.lang.IgniteException:
> Unable to start node=[new1].
> at org.apache.ignite.internal.app.IgniteImpl.start(IgniteImpl.java:293)
> at
> org.apache.ignite.internal.app.IgnitionImpl.doStart(IgnitionImpl.java:141)
> at
> org.apache.ignite.internal.app.IgnitionImpl.start(IgnitionImpl.java:72)
> at org.apache.ignite.app.IgniteCliRunner.main(IgniteCliRunner.java:59)
> Caused by: java.lang.NullPointerException
> at
> org.apache.ignite.raft.jraft.rpc.impl.RaftGroupServiceImpl.sendWithRetry(RaftGroupServiceImpl.java:456)
> at
> org.apache.ignite.raft.jraft.rpc.impl.RaftGroupServiceImpl.refreshLeader(RaftGroupServiceImpl.java:202)
> at
> org.apache.ignite.raft.jraft.rpc.impl.RaftGroupServiceImpl.start(RaftGroupServiceImpl.java:158)
> at org.apache.ignite.internal.raft.Loza.prepareRaftGroup(Loza.java:99)
> at
> org.apache.ignite.internal.metastorage.MetaStorageManager.start(MetaStorageManager.java:167)
> at
> org.apache.ignite.internal.app.IgniteImpl.doStartComponent(IgniteImpl.java:384)
> at org.apache.ignite.internal.app.IgniteImpl.start(IgniteImpl.java:278)
> {code}
> Also, trying to start a new node without a configuration file (which is
> optional) results in NullPointerException:
> {code:java}
> Exception in thread "main" java.lang.NullPointerExcep
[jira] [Updated] (IGNITE-15538) Starting node via CLI can lead to NullPointerException
[
https://issues.apache.org/jira/browse/IGNITE-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-15538:
-
Summary: Starting node via CLI can lead to NullPointerException (was: NPE
when starting node from CLI)
> Starting node via CLI can lead to NullPointerException
> --
>
> Key: IGNITE-15538
> URL: https://issues.apache.org/jira/browse/IGNITE-15538
> Project: Ignite
> Issue Type: Bug
>Reporter: Kirill Gusakov
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha3
>
>
> {code:java}
> Exception in thread "main" class org.apache.ignite.lang.IgniteException:
> Unable to start node=[new1].
> at org.apache.ignite.internal.app.IgniteImpl.start(IgniteImpl.java:293)
> at
> org.apache.ignite.internal.app.IgnitionImpl.doStart(IgnitionImpl.java:141)
> at
> org.apache.ignite.internal.app.IgnitionImpl.start(IgnitionImpl.java:72)
> at org.apache.ignite.app.IgniteCliRunner.main(IgniteCliRunner.java:59)
> Caused by: java.lang.NullPointerException
> at
> org.apache.ignite.raft.jraft.rpc.impl.RaftGroupServiceImpl.sendWithRetry(RaftGroupServiceImpl.java:456)
> at
> org.apache.ignite.raft.jraft.rpc.impl.RaftGroupServiceImpl.refreshLeader(RaftGroupServiceImpl.java:202)
> at
> org.apache.ignite.raft.jraft.rpc.impl.RaftGroupServiceImpl.start(RaftGroupServiceImpl.java:158)
> at org.apache.ignite.internal.raft.Loza.prepareRaftGroup(Loza.java:99)
> at
> org.apache.ignite.internal.metastorage.MetaStorageManager.start(MetaStorageManager.java:167)
> at
> org.apache.ignite.internal.app.IgniteImpl.doStartComponent(IgniteImpl.java:384)
> at org.apache.ignite.internal.app.IgniteImpl.start(IgniteImpl.java:278)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15678) CPP: Build ODBC installers using cmake
[
https://issues.apache.org/jira/browse/IGNITE-15678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17424582#comment-17424582
]
Ignite TC Bot commented on IGNITE-15678:
{panel:title=Branch: [pull/9470/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}[Check Code Style]{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6211661]]
{panel}
{panel:title=Branch: [pull/9470/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *-> Run :: CPP*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6211666&buildTypeId=IgniteTests24Java8_RunCpp]
> CPP: Build ODBC installers using cmake
> --
>
> Key: IGNITE-15678
> URL: https://issues.apache.org/jira/browse/IGNITE-15678
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ivan Daschinsky
>Assignee: Ivan Daschinsky
>Priority: Major
> Fix For: 2.12
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15397) Use named thread pools
[ https://issues.apache.org/jira/browse/IGNITE-15397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-15397: - Ignite Flags: (was: Docs Required,Release Notes Required) > Use named thread pools > -- > > Key: IGNITE-15397 > URL: https://issues.apache.org/jira/browse/IGNITE-15397 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Mashenkov >Priority: Major > Labels: ignite-3, tech-debt > Fix For: 3.0.0-alpha3 > > > I've found numerous usage of NioEventLoopGroup() that creates threads with > meaningless names like "nioEventLoopGroup-X-X". > Debuging thread leakage is very hard when default names are used. > Let's force thread pools with meaningful names. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15680) testChangePeersChaosWithSnapshot is flaky
[
https://issues.apache.org/jira/browse/IGNITE-15680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirza Aliev updated IGNITE-15680:
-
Description:
testChangePeersChaosWithSnapshot is started to fall with a timeout, in logs we
can see:
{noformat}
[19:51:41]W: [org.apache.ignite:ignite-raft] 2021-10-04
19:51:41:503 +0300
[ERROR][%172.17.0.7:5010%JRaft-Common-Executor-0][LocalSnapshotCopier] Fail to
start copy job
[19:51:41]W: [org.apache.ignite:ignite-raft]
java.nio.channels.ClosedByInterruptException
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:199)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/sun.nio.ch.FileChannelImpl.endBlocking(FileChannelImpl.java:162)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/sun.nio.ch.FileChannelImpl.force(FileChannelImpl.java:465)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.util.Utils.fsync(Utils.java:408)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.io.MessageFile.save(MessageFile.java:94)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotMetaTable.saveToFile(LocalSnapshotMetaTable.java:133)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotWriter.sync(LocalSnapshotWriter.java:103)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotCopier.copyFile(LocalSnapshotCopier.java:197)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotCopier.internalCopy(LocalSnapshotCopier.java:123)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotCopier.startCopy(LocalSnapshotCopier.java:100)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/java.lang.Thread.run(Thread.java:834)
{noformat}
Seems, that jraft snapshotting mechanism couldn't start to copy for some
reason. After that
There is a chance that the problem has appeared after this temporary solution
https://issues.apache.org/jira/browse/IGNITE-15663
was:
testChangePeersChaosWithSnapshot is started to fall with a timeout, in logs we
can see:
{noformat}
[19:51:41]W: [org.apache.ignite:ignite-raft] 2021-10-04
19:51:41:503 +0300
[ERROR][%172.17.0.7:5010%JRaft-Common-Executor-0][LocalSnapshotCopier] Fail to
start copy job
[19:51:41]W: [org.apache.ignite:ignite-raft]
java.nio.channels.ClosedByInterruptException
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:199)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/sun.nio.ch.FileChannelImpl.endBlocking(FileChannelImpl.java:162)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/sun.nio.ch.FileChannelImpl.force(FileChannelImpl.java:465)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.util.Utils.fsync(Utils.java:408)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.io.MessageFile.save(MessageFile.java:94)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotMetaTable.saveToFile(LocalSnapshotMetaTable.java:133)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotWriter.sync(LocalSnapshotWriter.java:103)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotCopier.copyFile(LocalSnapshotCopier.java:197)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotCopier.
[jira] [Updated] (IGNITE-15680) testChangePeersChaosWithSnapshot is flaky
[
https://issues.apache.org/jira/browse/IGNITE-15680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirza Aliev updated IGNITE-15680:
-
Description:
testChangePeersChaosWithSnapshot is started to fall with a timeout, in logs we
can see:
{noformat}
[19:51:41]W: [org.apache.ignite:ignite-raft] 2021-10-04
19:51:41:503 +0300
[ERROR][%172.17.0.7:5010%JRaft-Common-Executor-0][LocalSnapshotCopier] Fail to
start copy job
[19:51:41]W: [org.apache.ignite:ignite-raft]
java.nio.channels.ClosedByInterruptException
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:199)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/sun.nio.ch.FileChannelImpl.endBlocking(FileChannelImpl.java:162)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/sun.nio.ch.FileChannelImpl.force(FileChannelImpl.java:465)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.util.Utils.fsync(Utils.java:408)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.io.MessageFile.save(MessageFile.java:94)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotMetaTable.saveToFile(LocalSnapshotMetaTable.java:133)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotWriter.sync(LocalSnapshotWriter.java:103)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotCopier.copyFile(LocalSnapshotCopier.java:197)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotCopier.internalCopy(LocalSnapshotCopier.java:123)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotCopier.startCopy(LocalSnapshotCopier.java:100)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/java.lang.Thread.run(Thread.java:834)
{noformat}
Seems, that raft snapshotting mechanism couldn't start to copy for some
reason. After that
There is a chance that the problem has appeared after this temporary solution
https://issues.apache.org/jira/browse/IGNITE-15663
was:
testChangePeersChaosWithSnapshot is started to fall with a timeout, in logs we
can see
{noformat}
[19:51:41]W: [org.apache.ignite:ignite-raft] 2021-10-04
19:51:41:503 +0300
[ERROR][%172.17.0.7:5010%JRaft-Common-Executor-0][LocalSnapshotCopier] Fail to
start copy job
[19:51:41]W: [org.apache.ignite:ignite-raft]
java.nio.channels.ClosedByInterruptException
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:199)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/sun.nio.ch.FileChannelImpl.endBlocking(FileChannelImpl.java:162)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/sun.nio.ch.FileChannelImpl.force(FileChannelImpl.java:465)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.util.Utils.fsync(Utils.java:408)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.io.MessageFile.save(MessageFile.java:94)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotMetaTable.saveToFile(LocalSnapshotMetaTable.java:133)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotWriter.sync(LocalSnapshotWriter.java:103)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotCopier.copyFile(LocalSnapshotCopier.java:197)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotCopier.i
[jira] [Updated] (IGNITE-15680) testChangePeersChaosWithSnapshot is flaky
[
https://issues.apache.org/jira/browse/IGNITE-15680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirza Aliev updated IGNITE-15680:
-
Description:
testChangePeersChaosWithSnapshot is started to fall with a timeout, in logs we
can see
{noformat}
[19:51:41]W: [org.apache.ignite:ignite-raft] 2021-10-04
19:51:41:503 +0300
[ERROR][%172.17.0.7:5010%JRaft-Common-Executor-0][LocalSnapshotCopier] Fail to
start copy job
[19:51:41]W: [org.apache.ignite:ignite-raft]
java.nio.channels.ClosedByInterruptException
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:199)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/sun.nio.ch.FileChannelImpl.endBlocking(FileChannelImpl.java:162)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/sun.nio.ch.FileChannelImpl.force(FileChannelImpl.java:465)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.util.Utils.fsync(Utils.java:408)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.io.MessageFile.save(MessageFile.java:94)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotMetaTable.saveToFile(LocalSnapshotMetaTable.java:133)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotWriter.sync(LocalSnapshotWriter.java:103)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotCopier.copyFile(LocalSnapshotCopier.java:197)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotCopier.internalCopy(LocalSnapshotCopier.java:123)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotCopier.startCopy(LocalSnapshotCopier.java:100)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/java.lang.Thread.run(Thread.java:834)
{noformat}
seems, that raft snapshotting mechanism couldn't start to copy for some reason.
There is a chance that the problem has appeared after this temporary solution
https://issues.apache.org/jira/browse/IGNITE-15663
was:
testChangePeersChaosWithSnapshot is started to fall with a timeout, in logs we
can see
{noformat}
[19:51:41]W: [org.apache.ignite:ignite-raft] 2021-10-04
19:51:41:503 +0300
[ERROR][%172.17.0.7:5010%JRaft-Common-Executor-0][LocalSnapshotCopier] Fail to
start copy job
[19:51:41]W: [org.apache.ignite:ignite-raft]
java.nio.channels.ClosedByInterruptException
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:199)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/sun.nio.ch.FileChannelImpl.endBlocking(FileChannelImpl.java:162)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/sun.nio.ch.FileChannelImpl.force(FileChannelImpl.java:465)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.util.Utils.fsync(Utils.java:408)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.io.MessageFile.save(MessageFile.java:94)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotMetaTable.saveToFile(LocalSnapshotMetaTable.java:133)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotWriter.sync(LocalSnapshotWriter.java:103)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotCopier.copyFile(LocalSnapshotCopier.java:197)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotCopier.internalCopy(L
[jira] [Updated] (IGNITE-15680) testChangePeersChaosWithSnapshot is flaky
[
https://issues.apache.org/jira/browse/IGNITE-15680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirza Aliev updated IGNITE-15680:
-
Attachment: _Integration_Tests_Integration_Tests_3419.log.zip
> testChangePeersChaosWithSnapshot is flaky
> -
>
> Key: IGNITE-15680
> URL: https://issues.apache.org/jira/browse/IGNITE-15680
> Project: Ignite
> Issue Type: Improvement
>Reporter: Mirza Aliev
>Priority: Major
> Labels: ignite-3
> Attachments: _Integration_Tests_Integration_Tests_3419.log.zip
>
>
> testChangePeersChaosWithSnapshot is started to fall with a timeout, in logs
> we can see
> {noformat}
> [19:51:41]W: [org.apache.ignite:ignite-raft] 2021-10-04
> 19:51:41:503 +0300
> [ERROR][%172.17.0.7:5010%JRaft-Common-Executor-0][LocalSnapshotCopier] Fail
> to start copy job
> [19:51:41]W: [org.apache.ignite:ignite-raft]
> java.nio.channels.ClosedByInterruptException
> [19:51:41]W: [org.apache.ignite:ignite-raft]at
> java.base/java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:199)
> [19:51:41]W: [org.apache.ignite:ignite-raft]at
> java.base/sun.nio.ch.FileChannelImpl.endBlocking(FileChannelImpl.java:162)
> [19:51:41]W: [org.apache.ignite:ignite-raft]at
> java.base/sun.nio.ch.FileChannelImpl.force(FileChannelImpl.java:465)
> [19:51:41]W: [org.apache.ignite:ignite-raft]at
> org.apache.ignite.raft.jraft.util.Utils.fsync(Utils.java:408)
> [19:51:41]W: [org.apache.ignite:ignite-raft]at
> org.apache.ignite.raft.jraft.storage.io.MessageFile.save(MessageFile.java:94)
> [19:51:41]W: [org.apache.ignite:ignite-raft]at
> org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotMetaTable.saveToFile(LocalSnapshotMetaTable.java:133)
> [19:51:41]W: [org.apache.ignite:ignite-raft]at
> org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotWriter.sync(LocalSnapshotWriter.java:103)
> [19:51:41]W: [org.apache.ignite:ignite-raft]at
> org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotCopier.copyFile(LocalSnapshotCopier.java:197)
> [19:51:41]W: [org.apache.ignite:ignite-raft]at
> org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotCopier.internalCopy(LocalSnapshotCopier.java:123)
> [19:51:41]W: [org.apache.ignite:ignite-raft]at
> org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotCopier.startCopy(LocalSnapshotCopier.java:100)
> [19:51:41]W: [org.apache.ignite:ignite-raft]at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> [19:51:41]W: [org.apache.ignite:ignite-raft]at
> java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> [19:51:41]W: [org.apache.ignite:ignite-raft]at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> [19:51:41]W: [org.apache.ignite:ignite-raft]at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> [19:51:41]W: [org.apache.ignite:ignite-raft]at
> java.base/java.lang.Thread.run(Thread.java:834)
> {noformat}
>
> seems, that raft snapshotting mechanism couldn't start to copy for some
> reason.
>
> There is a chance that the problem has appeared after this temporary solution
> https://issues.apache.org/jira/browse/IGNITE-15663
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15680) testChangePeersChaosWithSnapshot is flaky
[
https://issues.apache.org/jira/browse/IGNITE-15680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirza Aliev updated IGNITE-15680:
-
Description:
testChangePeersChaosWithSnapshot is started to fall with a timeout, in logs we
can see
{noformat}
[19:51:41]W: [org.apache.ignite:ignite-raft] 2021-10-04
19:51:41:503 +0300
[ERROR][%172.17.0.7:5010%JRaft-Common-Executor-0][LocalSnapshotCopier] Fail to
start copy job
[19:51:41]W: [org.apache.ignite:ignite-raft]
java.nio.channels.ClosedByInterruptException
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:199)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/sun.nio.ch.FileChannelImpl.endBlocking(FileChannelImpl.java:162)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/sun.nio.ch.FileChannelImpl.force(FileChannelImpl.java:465)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.util.Utils.fsync(Utils.java:408)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.io.MessageFile.save(MessageFile.java:94)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotMetaTable.saveToFile(LocalSnapshotMetaTable.java:133)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotWriter.sync(LocalSnapshotWriter.java:103)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotCopier.copyFile(LocalSnapshotCopier.java:197)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotCopier.internalCopy(LocalSnapshotCopier.java:123)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotCopier.startCopy(LocalSnapshotCopier.java:100)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/java.lang.Thread.run(Thread.java:834)
{noformat}
seems, that raft snapshotting mechanism couldn't start to copy for some reason.
There is a chance that the problem has appeared after this temporary solution
https://issues.apache.org/jira/browse/IGNITE-15663
was:
testChangePeersChaosWithSnapshot is started to fall with a timeout, in logs we
can see
{noformat}
[19:51:41]W: [org.apache.ignite:ignite-raft] 2021-10-04
19:51:41:503 +0300
[ERROR][%172.17.0.7:5010%JRaft-Common-Executor-0][LocalSnapshotCopier] Fail to
start copy job
[19:51:41]W: [org.apache.ignite:ignite-raft]
java.nio.channels.ClosedByInterruptException
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:199)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/sun.nio.ch.FileChannelImpl.endBlocking(FileChannelImpl.java:162)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/sun.nio.ch.FileChannelImpl.force(FileChannelImpl.java:465)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.util.Utils.fsync(Utils.java:408)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.io.MessageFile.save(MessageFile.java:94)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotMetaTable.saveToFile(LocalSnapshotMetaTable.java:133)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotWriter.sync(LocalSnapshotWriter.java:103)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotCopier.copyFile(LocalSnapshotCopier.java:197)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotCopier.internalCopy
[jira] [Updated] (IGNITE-15680) testChangePeersChaosWithSnapshot is flaky
[
https://issues.apache.org/jira/browse/IGNITE-15680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirza Aliev updated IGNITE-15680:
-
Description:
testChangePeersChaosWithSnapshot is started to fall with a timeout, in logs we
can see
{noformat}
[19:51:41]W: [org.apache.ignite:ignite-raft] 2021-10-04
19:51:41:503 +0300
[ERROR][%172.17.0.7:5010%JRaft-Common-Executor-0][LocalSnapshotCopier] Fail to
start copy job
[19:51:41]W: [org.apache.ignite:ignite-raft]
java.nio.channels.ClosedByInterruptException
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:199)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/sun.nio.ch.FileChannelImpl.endBlocking(FileChannelImpl.java:162)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/sun.nio.ch.FileChannelImpl.force(FileChannelImpl.java:465)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.util.Utils.fsync(Utils.java:408)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.io.MessageFile.save(MessageFile.java:94)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotMetaTable.saveToFile(LocalSnapshotMetaTable.java:133)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotWriter.sync(LocalSnapshotWriter.java:103)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotCopier.copyFile(LocalSnapshotCopier.java:197)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotCopier.internalCopy(LocalSnapshotCopier.java:123)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotCopier.startCopy(LocalSnapshotCopier.java:100)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
[19:51:41]W: [org.apache.ignite:ignite-raft]at
java.base/java.lang.Thread.run(Thread.java:834)
{noformat}
seems, that raft snapshotting mechanism couldn't start to copy for some reason.
There is a chance that the problem has appeared after this temporary solution
https://issues.apache.org/jira/browse/IGNITE-15663
was:
testChangePeersChaosWithSnapshot is started to fall with a timeout, in logs we
can see
{noformat}
[19:51:41]W: [org.apache.ignite:ignite-raft] 2021-10-04 19:51:41:503
+0300 [ERROR][%172.17.0.7:5010%JRaft-Common-Executor-0][LocalSnapshotCopier]
Fail to start copy job[19:51:41]W: [org.apache.ignite:ignite-raft]
java.nio.channels.ClosedByInterruptException[19:51:41]W:
[org.apache.ignite:ignite-raft]at
java.base/java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:199)[19:51:41]W:
[org.apache.ignite:ignite-raft]at
java.base/sun.nio.ch.FileChannelImpl.endBlocking(FileChannelImpl.java:162)[19:51:41]W:
[org.apache.ignite:ignite-raft]at
java.base/sun.nio.ch.FileChannelImpl.force(FileChannelImpl.java:465)[19:51:41]W:
[org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.util.Utils.fsync(Utils.java:408)[19:51:41]W:
[org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.io.MessageFile.save(MessageFile.java:94)[19:51:41]W:
[org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotMetaTable.saveToFile(LocalSnapshotMetaTable.java:133)[19:51:41]W:
[org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotWriter.sync(LocalSnapshotWriter.java:103)[19:51:41]W:
[org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotCopier.copyFile(LocalSnapshotCopier.java:197)[19:51:41]W:
[org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotCopier.internalCopy(LocalSnapshotCopier.java:123)[19:51:41]W:
[org.apache.ignite:ignite
[jira] [Created] (IGNITE-15680) testChangePeersChaosWithSnapshot is flaky
Mirza Aliev created IGNITE-15680:
Summary: testChangePeersChaosWithSnapshot is flaky
Key: IGNITE-15680
URL: https://issues.apache.org/jira/browse/IGNITE-15680
Project: Ignite
Issue Type: Improvement
Reporter: Mirza Aliev
testChangePeersChaosWithSnapshot is started to fall with a timeout, in logs we
can see
{noformat}
[19:51:41]W: [org.apache.ignite:ignite-raft] 2021-10-04 19:51:41:503
+0300 [ERROR][%172.17.0.7:5010%JRaft-Common-Executor-0][LocalSnapshotCopier]
Fail to start copy job[19:51:41]W: [org.apache.ignite:ignite-raft]
java.nio.channels.ClosedByInterruptException[19:51:41]W:
[org.apache.ignite:ignite-raft]at
java.base/java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:199)[19:51:41]W:
[org.apache.ignite:ignite-raft]at
java.base/sun.nio.ch.FileChannelImpl.endBlocking(FileChannelImpl.java:162)[19:51:41]W:
[org.apache.ignite:ignite-raft]at
java.base/sun.nio.ch.FileChannelImpl.force(FileChannelImpl.java:465)[19:51:41]W:
[org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.util.Utils.fsync(Utils.java:408)[19:51:41]W:
[org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.io.MessageFile.save(MessageFile.java:94)[19:51:41]W:
[org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotMetaTable.saveToFile(LocalSnapshotMetaTable.java:133)[19:51:41]W:
[org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotWriter.sync(LocalSnapshotWriter.java:103)[19:51:41]W:
[org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotCopier.copyFile(LocalSnapshotCopier.java:197)[19:51:41]W:
[org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotCopier.internalCopy(LocalSnapshotCopier.java:123)[19:51:41]W:
[org.apache.ignite:ignite-raft]at
org.apache.ignite.raft.jraft.storage.snapshot.local.LocalSnapshotCopier.startCopy(LocalSnapshotCopier.java:100)[19:51:41]W:
[org.apache.ignite:ignite-raft]at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)[19:51:41]W:
[org.apache.ignite:ignite-raft]at
java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)[19:51:41]W:
[org.apache.ignite:ignite-raft]at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)[19:51:41]W:
[org.apache.ignite:ignite-raft]at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)[19:51:41]W:
[org.apache.ignite:ignite-raft]at
java.base/java.lang.Thread.run(Thread.java:834){noformat}
seems, that raft snapshotting mechanism couldn't start to copy for some reason.
There is a chance that the problem has appeared after this temporary solution
https://issues.apache.org/jira/browse/IGNITE-15663
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14794) Add JMX command and metrics for automatic snapshot restore operation.
[
https://issues.apache.org/jira/browse/IGNITE-14794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-14794:
--
Description:
Add JMX command to restore a cache group from the snapshot.
Suggested methods
{code:java}
@MXBeanDescription("Restore cluster-wide snapshot.")
public void restoreSnapshot(
@MXBeanParameter(name = "snpName", description = "Snapshot name.")
String name,
@MXBeanParameter(name = "cacheGroupNames", description = "Optional
comma-separated list of cache group names.") String cacheGroupNames);
@MXBeanDescription("Cancel previously started snapshot restore operation.")
public void cancelSnapshotRestore(@MXBeanParameter(name = "snpName",
description = "Snapshot name.") String name);
{code}
Since the automatic snapshot restore operation can take a long time, we must be
able to track its progress using metrics.
Suggested metrics:
{noformat}
start time
partitions (processed/total)
bytes (processed/total)
end time
{noformat}
Suggested status command output.
[in progress]
{noformat}
Restore operation for snapshot "snapshot_25052021" is still in progress
(requestId=0e2d8c06-d44a-4ade-91bf-2b84b367499a).
Progress: 100% completed (66/66 partitions, 3.8/3.8 MB)
Started: 2021-10-05 15:47:47.942
Cache groups: default
Node test1: 100% completed (33/33 partitions, 1.9/1.9 MB)
Node test0: 100% completed (33/33 partitions, 1.9/1.9 MB)
{noformat}
[error]
{noformat}
Restore operation for snapshot "snapshot_25052021" failed
(requestId=b9b312f5-ba34-40e9-bb94-35daacd552c0).
Error: Operation has been canceled by the user.
Started: 2021-10-05 15:51:52.255
Finished: 2021-10-05 15:51:52.782
Cache groups: default
Node test1: 100% completed (33/33 partitions, 1.9/1.9 MB)
Node test0: 100% completed (33/33 partitions, 1.9/1.9 MB){noformat}
[finished]
{noformat}
Restore operation for snapshot "snapshot_25052021" completed successfully
(requestId=6adeea86-1ee2-4664-8d7d-3383a484a00a).
Progress: 100% completed (66/66 partitions, 3.8/3.8 MB)
Started: 2021-10-05 15:53:03.352
Finished: 2021-10-05 15:53:03.443
Cache groups: default
Node test1: 100% completed (33/33 partitions, 1.9/1.9 MB)
Node test0: 100% completed (33/33 partitions, 1.9/1.9 MB){noformat}
[missing snapshot name]
{noformat}
No information about restoring snapshot "snapshot_MISSING" is
available.{noformat}
was:
Add JMX command to restore a cache group from the snapshot.
Suggested methods
{code:java}
@MXBeanDescription("Restore cluster-wide snapshot.")
public void restoreSnapshot(
@MXBeanParameter(name = "snpName", description = "Snapshot name.")
String name,
@MXBeanParameter(name = "cacheGroupNames", description = "Optional
comma-separated list of cache group names.") String cacheGroupNames);
@MXBeanDescription("Cancel previously started snapshot restore operation.")
public void cancelSnapshotRestore(@MXBeanParameter(name = "snpName",
description = "Snapshot name.") String name);
{code}
Since the automatic snapshot restore operation can take a long time, we must be
able to track its progress using metrics.
Suggested metrics:
{noformat}
start time
partitions (processed/total)
bytes (processed/total)
end time
{noformat}
Suggested status command output.
[in progress]
{noformat}
Restore operation for snapshot "snapshot_25052021" is still in progress
(requestId=0e2d8c06-d44a-4ade-91bf-2b84b367499a).
Progress: 100% completed (66/66 partitions, 3.8/3.8 MB)
Started: 2021-10-05 15:47:47.942
Cache groups: default
Node 11faec83-a304-48f7-aac7-e67bf881: 100% completed (33/33 partitions,
1.9/1.9 MB)
Node 99066100-890f-41a3-b0cd-4a3d5960: 100% completed (33/33 partitions,
1.9/1.9 MB)
{noformat}
[error]
{noformat}
Restore operation for snapshot "snapshot_25052021" failed
(requestId=b9b312f5-ba34-40e9-bb94-35daacd552c0).
Error: Operation has been canceled by the user.
Started: 2021-10-05 15:51:52.255
Finished: 2021-10-05 15:51:52.782
Cache groups: default
Node e3c8d45b-2ccd-43ba-81ab-ea3bb9e1: 100% completed (33/33 partitions,
1.9/1.9 MB)
Node 884cd446-38c2-4538-9dcd-81509eb0: 100% completed (33/33 partitions,
1.9/1.9 MB){noformat}
[finished]
{noformat}
Restore operation for snapshot "snapshot_25052021" completed successfully
(requestId=6adeea86-1ee2-4664-8d7d-3383a484a00a).
Progress: 100% completed (66/66 partitions, 3.8/3.8 MB)
Started: 2021-10-05 15:53:03.352
Finished: 2021-10-05 15:53:03.443
Cache groups: default
Node cc69e33f-de95-42b4-99af-86cf8391: 100% completed (33/33 partitions,
1.9/1.9 MB)
Node b4f3bb36-aef3-4813-a3e9-9f777360: 100% completed (33/33 partitions,
1.9/1.9 MB){noformat}
[missing snapshot name]
{noformat}
No information about restoring snapshot "snapshot_MISSING" is
available.{noformat}
> Add JMX command and metrics for automatic s
[jira] [Updated] (IGNITE-14794) Add JMX command and metrics for automatic snapshot restore operation.
[
https://issues.apache.org/jira/browse/IGNITE-14794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-14794:
--
Description:
Add JMX command to restore a cache group from the snapshot.
Suggested methods
{code:java}
@MXBeanDescription("Restore cluster-wide snapshot.")
public void restoreSnapshot(
@MXBeanParameter(name = "snpName", description = "Snapshot name.")
String name,
@MXBeanParameter(name = "cacheGroupNames", description = "Optional
comma-separated list of cache group names.") String cacheGroupNames);
@MXBeanDescription("Cancel previously started snapshot restore operation.")
public void cancelSnapshotRestore(@MXBeanParameter(name = "snpName",
description = "Snapshot name.") String name);
{code}
Since the automatic snapshot restore operation can take a long time, we must be
able to track its progress using metrics.
Suggested metrics:
{noformat}
start time
partitions (processed/total)
bytes (processed/total)
end time
{noformat}
Suggested status command output.
[in progress]
{noformat}
Restore operation for snapshot "snapshot_25052021" is still in progress
(requestId=0e2d8c06-d44a-4ade-91bf-2b84b367499a).
Progress: 100% completed (66/66 partitions, 3.8/3.8 MB)
Started: 2021-10-05 15:47:47.942
Cache groups: default
Node 11faec83-a304-48f7-aac7-e67bf881: 100% completed (33/33 partitions,
1.9/1.9 MB)
Node 99066100-890f-41a3-b0cd-4a3d5960: 100% completed (33/33 partitions,
1.9/1.9 MB)
{noformat}
[error]
{noformat}
Restore operation for snapshot "snapshot_25052021" failed
(requestId=b9b312f5-ba34-40e9-bb94-35daacd552c0).
Error: Operation has been canceled by the user.
Started: 2021-10-05 15:51:52.255
Finished: 2021-10-05 15:51:52.782
Cache groups: default
Node e3c8d45b-2ccd-43ba-81ab-ea3bb9e1: 100% completed (33/33 partitions,
1.9/1.9 MB)
Node 884cd446-38c2-4538-9dcd-81509eb0: 100% completed (33/33 partitions,
1.9/1.9 MB){noformat}
[finished]
{noformat}
Restore operation for snapshot "snapshot_25052021" completed successfully
(requestId=6adeea86-1ee2-4664-8d7d-3383a484a00a).
Progress: 100% completed (66/66 partitions, 3.8/3.8 MB)
Started: 2021-10-05 15:53:03.352
Finished: 2021-10-05 15:53:03.443
Cache groups: default
Node cc69e33f-de95-42b4-99af-86cf8391: 100% completed (33/33 partitions,
1.9/1.9 MB)
Node b4f3bb36-aef3-4813-a3e9-9f777360: 100% completed (33/33 partitions,
1.9/1.9 MB){noformat}
[missing snapshot name]
{noformat}
No information about restoring snapshot "snapshot_MISSING" is
available.{noformat}
was:
Add JMX command to restore a cache group from the snapshot.
Suggested methods
{code:java}
@MXBeanDescription("Restore cluster-wide snapshot.")
public void restoreSnapshot(
@MXBeanParameter(name = "snpName", description = "Snapshot name.")
String name,
@MXBeanParameter(name = "cacheGroupNames", description = "Optional
comma-separated list of cache group names.") String cacheGroupNames);
@MXBeanDescription("Cancel previously started snapshot restore operation.")
public void cancelSnapshotRestore(@MXBeanParameter(name = "snpName",
description = "Snapshot name.") String name);
{code}
Since the automatic snapshot restore operation can take a long time, we must be
able to track its progress using metrics.
Suggested metrics:
{noformat}
start time
partitions (processed/total)
bytes (processed/total)
end time
{noformat}
Suggested status command output.
[in progress]
{noformat}
Restore operation for snapshot "snapshot_25052021" is still in progress
(requestId=0e2d8c06-d44a-4ade-91bf-2b84b367499a). Progress: 100% completed
(66/66 partitions, 3.8/3.8 MB)
Started: 2021-10-05 15:47:47.942
Cache groups: default Node 11faec83-a304-48f7-aac7-e67bf881: 100%
completed (33/33 partitions, 1.9/1.9 MB)
Node 99066100-890f-41a3-b0cd-4a3d5960: 100% completed (33/33 partitions,
1.9/1.9 MB)Command [SNAPSHOT] finished with code: 0{noformat}
[finished]
{noformat}
Restore operation for snapshot "snapshot_25052021" completed successfully
(requestId=6adeea86-1ee2-4664-8d7d-3383a484a00a). Progress: 100% completed
(66/66 partitions, 3.8/3.8 MB)
Started: 2021-10-05 15:53:03.352
Finished: 2021-10-05 15:53:03.443
Cache groups: default Node cc69e33f-de95-42b4-99af-86cf8391: 100%
completed (33/33 partitions, 1.9/1.9 MB)
Node b4f3bb36-aef3-4813-a3e9-9f777360: 100% completed (33/33 partitions,
1.9/1.9 MB){noformat}
[missing snapshot name]
{noformat}
No information about restoring snapshot "snapshot_MISSING" is
available.{noformat}
[error]
{noformat}
Restore operation for snapshot "snapshot_25052021" failed
(requestId=b9b312f5-ba34-40e9-bb94-35daacd552c0). Error: Operation has been
canceled by the user.
Started: 2021-10-05 15:51:52.255
Finished: 2021-10-05 15:51:52.782
Cache groups: default Node e3c8d4
[jira] [Updated] (IGNITE-14794) Add JMX command and metrics for automatic snapshot restore operation.
[
https://issues.apache.org/jira/browse/IGNITE-14794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-14794:
--
Description:
Add JMX command to restore a cache group from the snapshot.
Suggested methods
{code:java}
@MXBeanDescription("Restore cluster-wide snapshot.")
public void restoreSnapshot(
@MXBeanParameter(name = "snpName", description = "Snapshot name.")
String name,
@MXBeanParameter(name = "cacheGroupNames", description = "Optional
comma-separated list of cache group names.") String cacheGroupNames);
@MXBeanDescription("Cancel previously started snapshot restore operation.")
public void cancelSnapshotRestore(@MXBeanParameter(name = "snpName",
description = "Snapshot name.") String name);
{code}
Since the automatic snapshot restore operation can take a long time, we must be
able to track its progress using metrics.
Suggested metrics:
{noformat}
start time
partitions (processed/total)
bytes (processed/total)
end time
{noformat}
Suggested status command output.
[in progress]
{noformat}
Restore operation for snapshot "snapshot_25052021" is still in progress
(requestId=0e2d8c06-d44a-4ade-91bf-2b84b367499a). Progress: 100% completed
(66/66 partitions, 3.8/3.8 MB)
Started: 2021-10-05 15:47:47.942
Cache groups: default Node 11faec83-a304-48f7-aac7-e67bf881: 100%
completed (33/33 partitions, 1.9/1.9 MB)
Node 99066100-890f-41a3-b0cd-4a3d5960: 100% completed (33/33 partitions,
1.9/1.9 MB)Command [SNAPSHOT] finished with code: 0{noformat}
[finished]
{noformat}
Restore operation for snapshot "snapshot_25052021" completed successfully
(requestId=6adeea86-1ee2-4664-8d7d-3383a484a00a). Progress: 100% completed
(66/66 partitions, 3.8/3.8 MB)
Started: 2021-10-05 15:53:03.352
Finished: 2021-10-05 15:53:03.443
Cache groups: default Node cc69e33f-de95-42b4-99af-86cf8391: 100%
completed (33/33 partitions, 1.9/1.9 MB)
Node b4f3bb36-aef3-4813-a3e9-9f777360: 100% completed (33/33 partitions,
1.9/1.9 MB){noformat}
[missing snapshot name]
{noformat}
No information about restoring snapshot "snapshot_MISSING" is
available.{noformat}
[error]
{noformat}
Restore operation for snapshot "snapshot_25052021" failed
(requestId=b9b312f5-ba34-40e9-bb94-35daacd552c0). Error: Operation has been
canceled by the user.
Started: 2021-10-05 15:51:52.255
Finished: 2021-10-05 15:51:52.782
Cache groups: default Node e3c8d45b-2ccd-43ba-81ab-ea3bb9e1: 100%
completed (33/33 partitions, 1.9/1.9 MB)
Node 884cd446-38c2-4538-9dcd-81509eb0: 100% completed (33/33 partitions,
1.9/1.9 MB){noformat}
was:
Add JMX command to restore a cache group from the snapshot.
Suggested methods
{code:java}
@MXBeanDescription("Restore cluster-wide snapshot.")
public void restoreSnapshot(
@MXBeanParameter(name = "snpName", description = "Snapshot name.")
String name,
@MXBeanParameter(name = "cacheGroupNames", description = "Optional
comma-separated list of cache group names.") String cacheGroupNames);
@MXBeanDescription("Cancel previously started snapshot restore operation.")
public void cancelSnapshotRestore(@MXBeanParameter(name = "snpName",
description = "Snapshot name.") String name);
{code}
Since the automatic snapshot restore operation can take a long time, we must be
able to track its progress using metrics.
Suggested metrics:
{noformat}
start time
total partitions
copied partitions
end time
{noformat}
> Add JMX command and metrics for automatic snapshot restore operation.
> --
>
> Key: IGNITE-14794
> URL: https://issues.apache.org/jira/browse/IGNITE-14794
> Project: Ignite
> Issue Type: Improvement
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: iep-43
> Fix For: 2.12
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Add JMX command to restore a cache group from the snapshot.
> Suggested methods
> {code:java}
> @MXBeanDescription("Restore cluster-wide snapshot.")
> public void restoreSnapshot(
> @MXBeanParameter(name = "snpName", description = "Snapshot name.")
> String name,
> @MXBeanParameter(name = "cacheGroupNames", description = "Optional
> comma-separated list of cache group names.") String cacheGroupNames);
> @MXBeanDescription("Cancel previously started snapshot restore
> operation.")
> public void cancelSnapshotRestore(@MXBeanParameter(name = "snpName",
> description = "Snapshot name.") String name);
> {code}
> Since the automatic snapshot restore operation can take a long time, we must
> be able to track its progress using metrics.
> Suggested metrics:
> {noformat}
> start time
> partitions (processed/total)
> bytes (process
[jira] [Commented] (IGNITE-15678) CPP: Build ODBC installers using cmake
[ https://issues.apache.org/jira/browse/IGNITE-15678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17424458#comment-17424458 ] Igor Sapego commented on IGNITE-15678: -- [~ivandasch] looks good to me > CPP: Build ODBC installers using cmake > -- > > Key: IGNITE-15678 > URL: https://issues.apache.org/jira/browse/IGNITE-15678 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Daschinsky >Assignee: Ivan Daschinsky >Priority: Major > Fix For: 2.12 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15027) Node fails to start with IndexOutOfBoundsException if metastorage nodes do not exist
[
https://issues.apache.org/jira/browse/IGNITE-15027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-15027:
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> Node fails to start with IndexOutOfBoundsException if metastorage nodes do
> not exist
>
>
> Key: IGNITE-15027
> URL: https://issues.apache.org/jira/browse/IGNITE-15027
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha2
>Reporter: Valentin Kulichenko
>Assignee: Mirza Aliev
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha3
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> If a node is started with this config...
> {code}
> {
> "node": {
> "metastorageNodes": [
> "node-0", "node-1", "node-2"
> ]
> },
> "network": {
> "port": 3344,
> "netClusterNodes": [
> "localhost:3344"
> ]
> }
> }
> {code}
> but with a name that is not present in {{metastorageNodes}}...
> {code}
> IgnitionManager.start("other-name",
> Files.readString(Path.of("config/ignite-config.json")))
> {code}
> it fails with {{IndexOutOfBoundsException}}:
> {noformat}
> INFO: Started replication server [node=ClusterNode
> [id=4640f6cd-f2c2-4fcf-9261-560b55190894, name=example-node,
> host=192.168.2.190, port=3344]]
> Exception in thread "main" java.lang.IndexOutOfBoundsException: Index 0 out
> of bounds for length 0
> at
> java.base/jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:64)
> at
> java.base/jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:70)
> at
> java.base/jdk.internal.util.Preconditions.checkIndex(Preconditions.java:248)
> at java.base/java.util.Objects.checkIndex(Objects.java:373)
> at java.base/java.util.ArrayList.get(ArrayList.java:426)
> at org.apache.ignite.internal.raft.Loza.startRaftGroup(Loza.java:76)
> at
> org.apache.ignite.internal.metastorage.MetaStorageManager.(MetaStorageManager.java:133)
> at
> org.apache.ignite.internal.app.IgnitionImpl.start(IgnitionImpl.java:145)
> at org.apache.ignite.app.IgnitionManager.start(IgnitionManager.java:45)
> at
> org.apache.ignite.example.table.TableExample.main(TableExample.java:29)
> {noformat}
> Should instead fail with a meaningful error message.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15027) Node fails to start with IndexOutOfBoundsException if metastorage nodes do not exist
[
https://issues.apache.org/jira/browse/IGNITE-15027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-15027:
-
Labels: ignite-3 (was: )
> Node fails to start with IndexOutOfBoundsException if metastorage nodes do
> not exist
>
>
> Key: IGNITE-15027
> URL: https://issues.apache.org/jira/browse/IGNITE-15027
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha2
>Reporter: Valentin Kulichenko
>Assignee: Mirza Aliev
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha3
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> If a node is started with this config...
> {code}
> {
> "node": {
> "metastorageNodes": [
> "node-0", "node-1", "node-2"
> ]
> },
> "network": {
> "port": 3344,
> "netClusterNodes": [
> "localhost:3344"
> ]
> }
> }
> {code}
> but with a name that is not present in {{metastorageNodes}}...
> {code}
> IgnitionManager.start("other-name",
> Files.readString(Path.of("config/ignite-config.json")))
> {code}
> it fails with {{IndexOutOfBoundsException}}:
> {noformat}
> INFO: Started replication server [node=ClusterNode
> [id=4640f6cd-f2c2-4fcf-9261-560b55190894, name=example-node,
> host=192.168.2.190, port=3344]]
> Exception in thread "main" java.lang.IndexOutOfBoundsException: Index 0 out
> of bounds for length 0
> at
> java.base/jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:64)
> at
> java.base/jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:70)
> at
> java.base/jdk.internal.util.Preconditions.checkIndex(Preconditions.java:248)
> at java.base/java.util.Objects.checkIndex(Objects.java:373)
> at java.base/java.util.ArrayList.get(ArrayList.java:426)
> at org.apache.ignite.internal.raft.Loza.startRaftGroup(Loza.java:76)
> at
> org.apache.ignite.internal.metastorage.MetaStorageManager.(MetaStorageManager.java:133)
> at
> org.apache.ignite.internal.app.IgnitionImpl.start(IgnitionImpl.java:145)
> at org.apache.ignite.app.IgnitionManager.start(IgnitionManager.java:45)
> at
> org.apache.ignite.example.table.TableExample.main(TableExample.java:29)
> {noformat}
> Should instead fail with a meaningful error message.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15658) Merge resolve Calcite tickets to 3.0
[ https://issues.apache.org/jira/browse/IGNITE-15658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-15658: - Labels: ignite-3 (was: ) > Merge resolve Calcite tickets to 3.0 > > > Key: IGNITE-15658 > URL: https://issues.apache.org/jira/browse/IGNITE-15658 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Yury Gerzhedovich >Priority: Major > Labels: ignite-3 > > We have a bunch of resolved tickets related to Calcite and merged only to > Ignite 2.x repo. > Need to find all such tickets use the filter [project=Ignite and labels > in(calcite3-required) and labels not > in(calcite2-required)|https://issues.apache.org/jira/issues/?jql=project%3DIgnite%20and%20labels%20in(calcite3-required)%20and%20labels%20not%20in(calcite2-required)%20] > merge into 3.0 repo and remove calcite3-required label for merged tickets. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15654) Calcite engine. Fix the test HashAggregateExecutionTest#countOfEmptyWithRewind
[
https://issues.apache.org/jira/browse/IGNITE-15654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-15654:
-
Labels: calcite2-required calcite3-required ignite-3 (was:
calcite2-required calcite3-required)
> Calcite engine. Fix the test HashAggregateExecutionTest#countOfEmptyWithRewind
> --
>
> Key: IGNITE-15654
> URL: https://issues.apache.org/jira/browse/IGNITE-15654
> Project: Ignite
> Issue Type: Improvement
>Reporter: Taras Ledkov
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Labels: calcite2-required, calcite3-required, ignite-3
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The test {{HashAggregateExecutionTest#countOfEmptyWithRewind}} uses
> aggregates without specified groups.
> The test fails with:
> {code}
> class org.apache.ignite.IgniteException: Unexpected exception
> at
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionContext.lambda$execute$0(ExecutionContext.java:309)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.QueryTaskExecutorImpl.lambda$execute$0(QueryTaskExecutorImpl.java:68)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: java.lang.ClassCastException: class [Ljava.lang.Object; cannot be
> cast to class java.lang.Comparable ([Ljava.lang.Object; and
> java.lang.Comparable are in module java.base of loader 'bootstrap')
> at
> java.base/java.util.PriorityQueue.siftUpComparable(PriorityQueue.java:659)
> at java.base/java.util.PriorityQueue.siftUp(PriorityQueue.java:655)
> at java.base/java.util.PriorityQueue.offer(PriorityQueue.java:346)
> at java.base/java.util.PriorityQueue.add(PriorityQueue.java:327)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.rel.SortNode.push(SortNode.java:92)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.rel.HashAggregateNode.flush(HashAggregateNode.java:188)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.rel.HashAggregateNode.end(HashAggregateNode.java:142)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.rel.ScanNode.push(ScanNode.java:127)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionContext.lambda$execute$0(ExecutionContext.java:304)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15654) Calcite engine. Fix the test HashAggregateExecutionTest#countOfEmptyWithRewind
[
https://issues.apache.org/jira/browse/IGNITE-15654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-15654:
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> Calcite engine. Fix the test HashAggregateExecutionTest#countOfEmptyWithRewind
> --
>
> Key: IGNITE-15654
> URL: https://issues.apache.org/jira/browse/IGNITE-15654
> Project: Ignite
> Issue Type: Improvement
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Major
> Labels: calcite2-required, calcite3-required
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The test {{HashAggregateExecutionTest#countOfEmptyWithRewind}} uses
> aggregates without specified groups.
> The test fails with:
> {code}
> class org.apache.ignite.IgniteException: Unexpected exception
> at
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionContext.lambda$execute$0(ExecutionContext.java:309)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.QueryTaskExecutorImpl.lambda$execute$0(QueryTaskExecutorImpl.java:68)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: java.lang.ClassCastException: class [Ljava.lang.Object; cannot be
> cast to class java.lang.Comparable ([Ljava.lang.Object; and
> java.lang.Comparable are in module java.base of loader 'bootstrap')
> at
> java.base/java.util.PriorityQueue.siftUpComparable(PriorityQueue.java:659)
> at java.base/java.util.PriorityQueue.siftUp(PriorityQueue.java:655)
> at java.base/java.util.PriorityQueue.offer(PriorityQueue.java:346)
> at java.base/java.util.PriorityQueue.add(PriorityQueue.java:327)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.rel.SortNode.push(SortNode.java:92)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.rel.HashAggregateNode.flush(HashAggregateNode.java:188)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.rel.HashAggregateNode.end(HashAggregateNode.java:142)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.rel.ScanNode.push(ScanNode.java:127)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionContext.lambda$execute$0(ExecutionContext.java:304)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-15654) Calcite engine. Fix the test HashAggregateExecutionTest#countOfEmptyWithRewind
[
https://issues.apache.org/jira/browse/IGNITE-15654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin reassigned IGNITE-15654:
Assignee: Vyacheslav Koptilin (was: Taras Ledkov)
> Calcite engine. Fix the test HashAggregateExecutionTest#countOfEmptyWithRewind
> --
>
> Key: IGNITE-15654
> URL: https://issues.apache.org/jira/browse/IGNITE-15654
> Project: Ignite
> Issue Type: Improvement
>Reporter: Taras Ledkov
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Labels: calcite2-required, calcite3-required
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The test {{HashAggregateExecutionTest#countOfEmptyWithRewind}} uses
> aggregates without specified groups.
> The test fails with:
> {code}
> class org.apache.ignite.IgniteException: Unexpected exception
> at
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionContext.lambda$execute$0(ExecutionContext.java:309)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.QueryTaskExecutorImpl.lambda$execute$0(QueryTaskExecutorImpl.java:68)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: java.lang.ClassCastException: class [Ljava.lang.Object; cannot be
> cast to class java.lang.Comparable ([Ljava.lang.Object; and
> java.lang.Comparable are in module java.base of loader 'bootstrap')
> at
> java.base/java.util.PriorityQueue.siftUpComparable(PriorityQueue.java:659)
> at java.base/java.util.PriorityQueue.siftUp(PriorityQueue.java:655)
> at java.base/java.util.PriorityQueue.offer(PriorityQueue.java:346)
> at java.base/java.util.PriorityQueue.add(PriorityQueue.java:327)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.rel.SortNode.push(SortNode.java:92)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.rel.HashAggregateNode.flush(HashAggregateNode.java:188)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.rel.HashAggregateNode.end(HashAggregateNode.java:142)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.rel.ScanNode.push(ScanNode.java:127)
> at
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionContext.lambda$execute$0(ExecutionContext.java:304)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15633) Add custom leftover node detection mechanism to TC
[ https://issues.apache.org/jira/browse/IGNITE-15633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-15633: - Labels: ignite-3 (was: ) > Add custom leftover node detection mechanism to TC > -- > > Key: IGNITE-15633 > URL: https://issues.apache.org/jira/browse/IGNITE-15633 > Project: Ignite > Issue Type: Task >Reporter: Petr Ivanov >Assignee: Petr Ivanov >Priority: Major > Labels: ignite-3 > > Sometimes after test runs, unattended Ignite nodes can left running, which > can affect next test runs on the same agent. > We should: > * detect and destroy such process after tests > * fail build if there were processes with Ignite nodes left after the test > (to inform developer that test is leaking) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15677) ODBC: DSN can not be created by DataSource manager
[
https://issues.apache.org/jira/browse/IGNITE-15677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17424417#comment-17424417
]
Ignite TC Bot commented on IGNITE-15677:
{panel:title=Branch: [pull/9469/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}[Check Code Style]{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6211219]]
{panel}
{panel:title=Branch: [pull/9469/head] Base: [master] : New Tests
(2032)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Platform C++ CMake (Win x64 / Debug){color} [[tests
1022|https://ci.ignite.apache.org/viewLog.html?buildId=6211222]]
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite: SelectTwoValues
- PASSED{color}
* {color:#013220}IgniteOdbcTest: SqlNumericFunctionTestSuite:
TestNumericFunctionFloor - PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
SelectSingleValue - PASSED{color}
* {color:#013220}IgniteOdbcTest: SqlNumericFunctionTestSuite:
TestNumericFunctionLog - PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
CreateTableInsertSelect - PASSED{color}
* {color:#013220}IgniteOdbcTest: SqlDateTimeFunctionTestSuite: TestCurrentDate
- PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
SelectTwoValuesInDifferentOrder - PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForCacheNodes -
PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForClientNodes -
PASSED{color}
* {color:#013220}IgniteCoreTest: CacheQueryTestSuite:
TestFieldsQueryByteArrayInsertSelect - PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForDaemons -
PASSED{color}
... and 1011 new tests
{color:#8b}Platform C++ (Win x64 / Debug){color} [[tests
1010|https://ci.ignite.apache.org/viewLog.html?buildId=6211215]]
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite: SelectTwoValues
- PASSED{color}
* {color:#013220}IgniteOdbcTest: SqlNumericFunctionTestSuite:
TestNumericFunctionFloor - PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
SelectSingleValue - PASSED{color}
* {color:#013220}IgniteOdbcTest: SqlNumericFunctionTestSuite:
TestNumericFunctionLog - PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
CreateTableInsertSelect - PASSED{color}
* {color:#013220}IgniteOdbcTest: SqlDateTimeFunctionTestSuite: TestCurrentDate
- PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
SelectTwoValuesInDifferentOrder - PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForCacheNodes -
PASSED{color}
* {color:#013220}IgniteCoreTest: CacheQueryTestSuite:
TestFieldsQueryByteArrayInsertSelect - PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForClientNodes -
PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForDaemons -
PASSED{color}
... and 999 new tests
{panel}
[TeamCity *-> Run :: CPP*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6211224&buildTypeId=IgniteTests24Java8_RunCpp]
> ODBC: DSN can not be created by DataSource manager
> --
>
> Key: IGNITE-15677
> URL: https://issues.apache.org/jira/browse/IGNITE-15677
> Project: Ignite
> Issue Type: Bug
> Components: odbc
>Affects Versions: 2.11
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
> Fix For: 2.12
>
> Attachments: image-2021-04-29-03-33-21-267.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> DSN for Apache Ignite ODBC driver can not be created using odbcad32.exe if
> built by CMake. The error message is attached.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14358) Regression when referencing aliased constant from derived table
[
https://issues.apache.org/jira/browse/IGNITE-14358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17424403#comment-17424403
]
Ignite TC Bot commented on IGNITE-14358:
{panel:title=Branch: [pull/9441/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9441/head] Base: [master] : New Tests
(12)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Queries 1{color} [[tests
12|https://ci.ignite.apache.org/viewLog.html?buildId=6209813]]
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridSubqueryJoinOptimizerSelfTest.testOptimizationAliasUnion - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridSubqueryJoinOptimizerSelfTest.testOptimizationLeftJoinWhereFalse3 -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridSubqueryJoinOptimizerSelfTest.testOptimizationLeftJoinWhereFalse2 -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridSubqueryJoinOptimizerSelfTest.testOptimizationConstant2 - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridSubqueryJoinOptimizerSelfTest.testOptimizationConstant1 - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridSubqueryJoinOptimizerSelfTest.testOptimizationAlias2 - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridSubqueryJoinOptimizerSelfTest.testOptimizationAlias1 - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridSubqueryJoinOptimizerSelfTest.testOptimizationCaseWhen - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridSubqueryJoinOptimizerSelfTest.testOptimizationCastFunction - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridSubqueryJoinOptimizerSelfTest.testOptimizationLeftJoinWhereFalse -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
GridSubqueryJoinOptimizerSelfTest.testOptimizationAlias4 - PASSED{color}
... and 1 new tests
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6209835&buildTypeId=IgniteTests24Java8_RunAll]
> Regression when referencing aliased constant from derived table
> ---
>
> Key: IGNITE-14358
> URL: https://issues.apache.org/jira/browse/IGNITE-14358
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.10
>Reporter: Lukas Eder
>Assignee: Vladimir Ermakov
>Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> This used to work in 2.9.1 but no longer does in 2.10.0:
>
> {code:java}
> CREATE TABLE t (i int PRIMARY KEY, j int);
> INSERT INTO t VALUES (1, 1);
> SELECT u.x
> FROM (
> SELECT 1 AS x
> FROM t
> ) u;
> {code}
>
> The error I'm getting is:
> {noformat}
> SQL Error [1001] [42000]: Failed to parse query. Column "U__Z0.X" not found;
> SQL statement:
> SELECT
> U__Z0.X
> FROM PUBLIC.T U__Z0 [42122-197]{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15412) Configuration registry: add ability to retreive distributed value
[
https://issues.apache.org/jira/browse/IGNITE-15412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-15412:
-
Issue Type: Improvement (was: Epic)
> Configuration registry: add ability to retreive distributed value
> ---
>
> Key: IGNITE-15412
> URL: https://issues.apache.org/jira/browse/IGNITE-15412
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexander Lapin
>Assignee: Aleksandr Polovtcev
>Priority: Major
> Labels: iep-55, ignite-3
> Fix For: 3.0.0-alpha3
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In some cases it's required to retrieve configuration distributed value.
> Currently we use meta storage manager interface for this purpose and cause
> configuration registry hides the keys the code of the distributed property
> retrieval looks horrible:
>
> {code:java}
> //TODO This is an egregious violation of encapsulation. Current approach has
> to be revisited.
> private Set tableNamesConfigured() {
> IgniteBiTuple range = toRange(new
> ByteArray(PUBLIC_PREFIX));
> Set tableNames = new HashSet<>();
> try (Cursor cursor = metaStorageMgr.range(range.get1(),
> range.get2())) {
> while (cursor.hasNext()) {
> Entry entry = cursor.next();
> List keySplit =
> ConfigurationUtil.split(entry.key().toString());
> if (keySplit.size() == 5 &&
> NamedListNode.NAME.equals(keySplit.get(4)))
> tableNames.add(ByteUtils.fromBytes(entry.value()).toString());
> }
> }
> catch (Exception e) {
> LOG.error("Can't get table names.", e);
> }
> return tableNames;
> }
> {code}
> Let's refactor it by adding distributedValue() (concrete name of the method
> is up to an implementator) to ConfigurationProperty. That will allow to
> simplify distributed retrieval:
> {code:java}
> private Set tableNamesConfigured() {
> return new
> HashSet<>(clusterCfgMgr.configurationRegistry().getConfiguration(TablesConfiguration.KEY).tables().
> distirbuteValue().namedListKeys());
> }
> {code}
> Internally distributedValue() should fetch corresponding key->val from the
> meta storage without applying this value to local state updating
> localRoots.version etc.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15412) Configuration registry: add ability to retreive distributed value
[
https://issues.apache.org/jira/browse/IGNITE-15412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-15412:
-
Issue Type: Epic (was: Improvement)
> Configuration registry: add ability to retreive distributed value
> ---
>
> Key: IGNITE-15412
> URL: https://issues.apache.org/jira/browse/IGNITE-15412
> Project: Ignite
> Issue Type: Epic
>Reporter: Alexander Lapin
>Assignee: Aleksandr Polovtcev
>Priority: Major
> Labels: iep-55, ignite-3
> Fix For: 3.0.0-alpha3
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In some cases it's required to retrieve configuration distributed value.
> Currently we use meta storage manager interface for this purpose and cause
> configuration registry hides the keys the code of the distributed property
> retrieval looks horrible:
>
> {code:java}
> //TODO This is an egregious violation of encapsulation. Current approach has
> to be revisited.
> private Set tableNamesConfigured() {
> IgniteBiTuple range = toRange(new
> ByteArray(PUBLIC_PREFIX));
> Set tableNames = new HashSet<>();
> try (Cursor cursor = metaStorageMgr.range(range.get1(),
> range.get2())) {
> while (cursor.hasNext()) {
> Entry entry = cursor.next();
> List keySplit =
> ConfigurationUtil.split(entry.key().toString());
> if (keySplit.size() == 5 &&
> NamedListNode.NAME.equals(keySplit.get(4)))
> tableNames.add(ByteUtils.fromBytes(entry.value()).toString());
> }
> }
> catch (Exception e) {
> LOG.error("Can't get table names.", e);
> }
> return tableNames;
> }
> {code}
> Let's refactor it by adding distributedValue() (concrete name of the method
> is up to an implementator) to ConfigurationProperty. That will allow to
> simplify distributed retrieval:
> {code:java}
> private Set tableNamesConfigured() {
> return new
> HashSet<>(clusterCfgMgr.configurationRegistry().getConfiguration(TablesConfiguration.KEY).tables().
> distirbuteValue().namedListKeys());
> }
> {code}
> Internally distributedValue() should fetch corresponding key->val from the
> meta storage without applying this value to local state updating
> localRoots.version etc.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15161) Implement component's stop
[ https://issues.apache.org/jira/browse/IGNITE-15161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-15161: - Epic Name: Component's stop (was: Implement component's stop) > Implement component's stop > -- > > Key: IGNITE-15161 > URL: https://issues.apache.org/jira/browse/IGNITE-15161 > Project: Ignite > Issue Type: Epic >Reporter: Alexander Lapin >Assignee: Alexander Lapin >Priority: Major > Labels: ignite-3 > Original Estimate: 120h > Time Spent: 10m > Remaining Estimate: 119h 50m > > During the work on https://issues.apache.org/jira/browse/IGNITE-15278, the > general flow of the components start and stop was introduced. > It is needed to implement a stop mechanism for every component. > The main points that should be considered during the implementation of > component's stop: > * All threads should be stopped properly > * All Executors should be shutdown > * All public methods should be guarded by read lock, stop should be done > using write lock. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15161) Implement component's stop
[ https://issues.apache.org/jira/browse/IGNITE-15161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-15161: - Epic Name: Implement component's stop > Implement component's stop > -- > > Key: IGNITE-15161 > URL: https://issues.apache.org/jira/browse/IGNITE-15161 > Project: Ignite > Issue Type: Epic >Reporter: Alexander Lapin >Assignee: Alexander Lapin >Priority: Major > Labels: ignite-3 > Original Estimate: 120h > Time Spent: 10m > Remaining Estimate: 119h 50m > > During the work on https://issues.apache.org/jira/browse/IGNITE-15278, the > general flow of the components start and stop was introduced. > It is needed to implement a stop mechanism for every component. > The main points that should be considered during the implementation of > component's stop: > * All threads should be stopped properly > * All Executors should be shutdown > * All public methods should be guarded by read lock, stop should be done > using write lock. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15679) InlineIndex should store enum as int and not as POJO
[ https://issues.apache.org/jira/browse/IGNITE-15679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Timonin updated IGNITE-15679: Summary: InlineIndex should store enum as int and not as POJO (was: Inline should store enum as int and not as POJO) > InlineIndex should store enum as int and not as POJO > > > Key: IGNITE-15679 > URL: https://issues.apache.org/jira/browse/IGNITE-15679 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Timonin >Assignee: Maksim Timonin >Priority: Major > > Investigate opportunity for optimal storing enum in inlines for faster > comparison. > Currently enum stores as POJO, and equal elements compares with comparing > BinaryObject arrays (also, it looks like the comparison doesn't use > intrinsics). > Looks like we can easily can store it as int using Enum.ordering(). > > BUT, H2 supports enum, but Ignite doesn't use it for some reason. Investigate > why. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-15679) Inline should store enum as int and not as POJO
Maksim Timonin created IGNITE-15679: --- Summary: Inline should store enum as int and not as POJO Key: IGNITE-15679 URL: https://issues.apache.org/jira/browse/IGNITE-15679 Project: Ignite Issue Type: New Feature Reporter: Maksim Timonin Assignee: Maksim Timonin Investigate opportunity for optimal storing enum in inlines for faster comparison. Currently enum stores as POJO, and equal elements compares with comparing BinaryObject arrays (also, it looks like the comparison doesn't use intrinsics). Looks like we can easily can store it as int using Enum.ordering(). BUT, H2 supports enum, but Ignite doesn't use it for some reason. Investigate why. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15161) Implement component's stop
[ https://issues.apache.org/jira/browse/IGNITE-15161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-15161: - Issue Type: Epic (was: Bug) > Implement component's stop > -- > > Key: IGNITE-15161 > URL: https://issues.apache.org/jira/browse/IGNITE-15161 > Project: Ignite > Issue Type: Epic >Reporter: Alexander Lapin >Assignee: Alexander Lapin >Priority: Major > Labels: ignite-3 > Original Estimate: 120h > Time Spent: 10m > Remaining Estimate: 119h 50m > > During the work on https://issues.apache.org/jira/browse/IGNITE-15278, the > general flow of the components start and stop was introduced. > It is needed to implement a stop mechanism for every component. > The main points that should be considered during the implementation of > component's stop: > * All threads should be stopped properly > * All Executors should be shutdown > * All public methods should be guarded by read lock, stop should be done > using write lock. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15662) It is impossible to add a test-jar dependency to the CLI module
[
https://issues.apache.org/jira/browse/IGNITE-15662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Petr Ivanov updated IGNITE-15662:
-
Fix Version/s: 3.0.0-alpha3
> It is impossible to add a test-jar dependency to the CLI module
> ---
>
> Key: IGNITE-15662
> URL: https://issues.apache.org/jira/browse/IGNITE-15662
> Project: Ignite
> Issue Type: Task
>Reporter: Aleksandr Polovtcev
>Assignee: Petr Ivanov
>Priority: Minor
> Labels: ignite-3
> Fix For: 3.0.0-alpha3
>
> Time Spent: 3h 10m
> Remaining Estimate: 0h
>
> h2. Steps to reproduce
> 1. Add a {{test-jar}} dependency to the {{pom.xml}} of the {{ignite-cli}}
> module, for example:
> {code:java}
>
> org.apache.ignite
> ignite-core
> test
> test-jar
> {code}
> 2. Run the following command from the repository root:
> {code:java}
> mvn package -Dmaven.test.skip -Dmaven.all-checks.skip
> {code}
> h2. Expected behavior
> The project is built successfully.
> h2. Actual behavior
> The project cannot be built and the following error appears:
> {code:java}
> [ERROR] Failed to execute goal on project ignite-cli: Could not resolve
> dependencies for project org.apache.ignite:ignite-cli:jar:3.0.0-SNAPSHOT:
> Could not find artifact
> org.apache.ignite:ignite-core:jar:tests:3.0.0-SNAPSHOT in apache.snapshots
> (https://repository.apache.org/snapshots) -> [Help 1]
> {code}
> h2. Supposed cause
> {{ignite-cli}} module uses the {{maven-antrun-plugin}} to create a
> self-executing JAR. This plugin requires the test dependencies to be present
> during the {{package}} execution phase (see the [source
> code|https://github.com/apache/maven-antrun-plugin/blob/master/src/main/java/org/apache/maven/plugins/antrun/AntRunMojo.java#L67]),
> which are not created because of the {{maven.test.skip}} flag.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-15637) CPP: Remove vs project files
[ https://issues.apache.org/jira/browse/IGNITE-15637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky reassigned IGNITE-15637: Assignee: Ivan Daschinsky > CPP: Remove vs project files > > > Key: IGNITE-15637 > URL: https://issues.apache.org/jira/browse/IGNITE-15637 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Daschinsky >Assignee: Ivan Daschinsky >Priority: Major > Fix For: 2.12 > > > Since CMake build are fully functional, CMake is supported on VS2015, VS2017 > and VS2019 out of the box and CMake can generate project files as is, let's > remove old vs projects. > Moreover, if you want to build old vs project, bundled with ignite, it should > be updated (manually or by script) in order to be built on modern VS -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15677) ODBC: DSN can not be created by DataSource manager
[ https://issues.apache.org/jira/browse/IGNITE-15677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky updated IGNITE-15677: - Fix Version/s: 2.12 > ODBC: DSN can not be created by DataSource manager > -- > > Key: IGNITE-15677 > URL: https://issues.apache.org/jira/browse/IGNITE-15677 > Project: Ignite > Issue Type: Bug > Components: odbc >Affects Versions: 2.11 >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Major > Fix For: 2.12 > > Attachments: image-2021-04-29-03-33-21-267.png > > Time Spent: 10m > Remaining Estimate: 0h > > DSN for Apache Ignite ODBC driver can not be created using odbcad32.exe if > built by CMake. The error message is attached. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15678) CPP: Build ODBC installers using cmake
[ https://issues.apache.org/jira/browse/IGNITE-15678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky updated IGNITE-15678: - Fix Version/s: (was: 2.11) 2.12 > CPP: Build ODBC installers using cmake > -- > > Key: IGNITE-15678 > URL: https://issues.apache.org/jira/browse/IGNITE-15678 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Daschinsky >Assignee: Ivan Daschinsky >Priority: Major > Fix For: 2.12 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15678) CPP: Build ODBC installers using cmake
[ https://issues.apache.org/jira/browse/IGNITE-15678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky updated IGNITE-15678: - Fix Version/s: 2.11 > CPP: Build ODBC installers using cmake > -- > > Key: IGNITE-15678 > URL: https://issues.apache.org/jira/browse/IGNITE-15678 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Daschinsky >Assignee: Ivan Daschinsky >Priority: Major > Fix For: 2.11 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-15678) CPP: Build ODBC installers using cmake
Ivan Daschinsky created IGNITE-15678: Summary: CPP: Build ODBC installers using cmake Key: IGNITE-15678 URL: https://issues.apache.org/jira/browse/IGNITE-15678 Project: Ignite Issue Type: Improvement Reporter: Ivan Daschinsky Assignee: Ivan Daschinsky -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15677) ODBC: DSN can not be created by DataSource manager
[ https://issues.apache.org/jira/browse/IGNITE-15677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17424373#comment-17424373 ] Ivan Daschinsky commented on IGNITE-15677: -- Looks good to me. > ODBC: DSN can not be created by DataSource manager > -- > > Key: IGNITE-15677 > URL: https://issues.apache.org/jira/browse/IGNITE-15677 > Project: Ignite > Issue Type: Bug > Components: odbc >Affects Versions: 2.11 >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Major > Attachments: image-2021-04-29-03-33-21-267.png > > Time Spent: 10m > Remaining Estimate: 0h > > DSN for Apache Ignite ODBC driver can not be created using odbcad32.exe if > built by CMake. The error message is attached. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-15547) QueryTypeDescriptorImpl: Accept Classes/Enums extending an Interface which is used as cache indexed field
[
https://issues.apache.org/jira/browse/IGNITE-15547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17424359#comment-17424359
]
Maksim Timonin edited comment on IGNITE-15547 at 10/5/21, 8:46 AM:
---
[~andrian.boscanean] hi! This patch looks good to me, I've put some minor
comments on the PR page, please have a look.
[~andrian.boscanean] I do have concerns about performance of using enums in
indexes. Using POJO (enum will be considered as POJO) in indexes is possible,
but there are tread offs, and the main one is speed of comparison of equal
elements (yes, comparison of non-equal elements is pretty fast, but in case of
equality of POJO items in index there are additional checks and they aren't
optimal). As I understand there are a lot of equal elements in your case, as
you want use enum. So, I'd suggest you to test performance of your case. If
results won't be OK, it may be faster to use INT instead of ENUM.
was (Author: timonin.maksim):
[~andrian.boscanean] hi! This patch looks good to me, I've put some minor
comments on the PR page, please have a look.
[~andrian.boscanean] , changes your suggest will work. But I do have concerns
about performance of using enums in indexes. Using POJO (enum will be
considered as POJO) in indexes is possible, but there are tread offs, and the
main one is speed of comparison of equal elements (yes, comparison of non-equal
elements is pretty fast, but in case of equality of POJO items in index there
are additional checks and they aren't optimal). As I understand there are a lot
of equal elements in your case, as you want use enum. So, I'd suggest you to
test performance of your case. If results won't be OK, it may be faster to use
INT instead of ENUM.
> QueryTypeDescriptorImpl: Accept Classes/Enums extending an Interface which is
> used as cache indexed field
> -
>
> Key: IGNITE-15547
> URL: https://issues.apache.org/jira/browse/IGNITE-15547
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.10
>Reporter: Andrian Boscanean
>Assignee: Andrian Boscanean
>Priority: Major
> Fix For: 2.12
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Currently Classes/Enums that extend an interface which is used as Indexed
> field are not allowed.
> Example
> @QuerySqlField(index = true)
> private TestInterface testInterface;
> --
> enum TestEnum1 implements TestInterface
> { VALUE_1, VALUE_2, VALUE_3 }
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-15547) QueryTypeDescriptorImpl: Accept Classes/Enums extending an Interface which is used as cache indexed field
[
https://issues.apache.org/jira/browse/IGNITE-15547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17424359#comment-17424359
]
Maksim Timonin edited comment on IGNITE-15547 at 10/5/21, 8:40 AM:
---
[~andrian.boscanean] hi! This patch looks good to me, I've put some minor
comments on the PR page, please have a look.
[~andrian.boscanean] , changes your suggest will work. But I do have concerns
about performance of using enums in indexes. Using POJO (enum will be
considered as POJO) in indexes is possible, but there are tread offs, and the
main one is speed of comparison of equal elements (yes, comparison of non-equal
elements is pretty fast, but in case of equality of POJO items in index there
are additional checks and they aren't optimal). As I understand there are a lot
of equal elements in your case, as you want use enum. So, I'd suggest you to
test performance of your case. If results won't be OK, it may be faster to use
INT instead of ENUM.
was (Author: timonin.maksim):
[~andrian.boscanean] hi! This patch looks good to me, I've put some minor
comments on the PR page, please have a look.
[~andrian.boscanean] , changes your suggest will work. But I do have concerns
about performance of using enums in indexes. Using POJO (enum will be
considered as POJO) in indexes is possible, but there are tread offs, and the
main one is speed of comparison of equal elements (yes, comparison of non-equal
elements is pretty fast, but in case of equality of POJO items in index there
are additional checks and they aren't optimal). As I understand there are a lot
of equal elements in your case, as you want use enum. So, I'd suggest you to
test performance of your case. If results won't be OK, it will be much faster
to store INT instead of ENUM.
> QueryTypeDescriptorImpl: Accept Classes/Enums extending an Interface which is
> used as cache indexed field
> -
>
> Key: IGNITE-15547
> URL: https://issues.apache.org/jira/browse/IGNITE-15547
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.10
>Reporter: Andrian Boscanean
>Assignee: Andrian Boscanean
>Priority: Major
> Fix For: 2.12
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Currently Classes/Enums that extend an interface which is used as Indexed
> field are not allowed.
> Example
> @QuerySqlField(index = true)
> private TestInterface testInterface;
> --
> enum TestEnum1 implements TestInterface
> { VALUE_1, VALUE_2, VALUE_3 }
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15547) QueryTypeDescriptorImpl: Accept Classes/Enums extending an Interface which is used as cache indexed field
[
https://issues.apache.org/jira/browse/IGNITE-15547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17424359#comment-17424359
]
Maksim Timonin commented on IGNITE-15547:
-
[~andrian.boscanean] hi! This patch looks good to me, I've put some minor
comments on the PR page, please have a look.
[~andrian.boscanean] , changes your suggest will work. But I do have concerns
about performance of using enums in indexes. Using POJO (enum will be
considered as POJO) in indexes is possible, but there are tread offs, and the
main one is speed of comparison of equal elements (yes, comparison of non-equal
elements is pretty fast, but in case of equality of POJO items in index there
are additional checks and they aren't optimal). As I understand there are a lot
of equal elements in your case, as you want use enum. So, I'd suggest you to
test performance of your case. If results won't be OK, it will be much faster
to store INT instead of ENUM.
> QueryTypeDescriptorImpl: Accept Classes/Enums extending an Interface which is
> used as cache indexed field
> -
>
> Key: IGNITE-15547
> URL: https://issues.apache.org/jira/browse/IGNITE-15547
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.10
>Reporter: Andrian Boscanean
>Assignee: Andrian Boscanean
>Priority: Major
> Fix For: 2.12
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Currently Classes/Enums that extend an interface which is used as Indexed
> field are not allowed.
> Example
> @QuerySqlField(index = true)
> private TestInterface testInterface;
> --
> enum TestEnum1 implements TestInterface
> { VALUE_1, VALUE_2, VALUE_3 }
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15677) ODBC: DSN can not be created by DataSource manager
[ https://issues.apache.org/jira/browse/IGNITE-15677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-15677: - Attachment: image-2021-04-29-03-33-21-267.png > ODBC: DSN can not be created by DataSource manager > -- > > Key: IGNITE-15677 > URL: https://issues.apache.org/jira/browse/IGNITE-15677 > Project: Ignite > Issue Type: Bug > Components: odbc >Affects Versions: 2.11 >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Major > Attachments: image-2021-04-29-03-33-21-267.png > > > DSN for Apache Ignite ODBC driver can not be created using odbcad32.exe if > built by CMake. The error message is attached. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-15677) ODBC: DSN can not be created by DataSource manager
Igor Sapego created IGNITE-15677: Summary: ODBC: DSN can not be created by DataSource manager Key: IGNITE-15677 URL: https://issues.apache.org/jira/browse/IGNITE-15677 Project: Ignite Issue Type: Bug Components: odbc Affects Versions: 2.11 Reporter: Igor Sapego Assignee: Igor Sapego Attachments: image-2021-04-29-03-33-21-267.png DSN for Apache Ignite ODBC driver can not be created using odbcad32.exe if built by CMake. The error message is attached. -- This message was sent by Atlassian Jira (v8.3.4#803005)
