[jira] [Commented] (IGNITE-17034) Thin 3.0: Rename JDBC packages and classes to separate them from Ignite SQL API
[ https://issues.apache.org/jira/browse/IGNITE-17034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17542212#comment-17542212 ] Vladimir Ermakov commented on IGNITE-17034: --- LGTM > Thin 3.0: Rename JDBC packages and classes to separate them from Ignite SQL > API > --- > > Key: IGNITE-17034 > URL: https://issues.apache.org/jira/browse/IGNITE-17034 > Project: Ignite > Issue Type: Improvement > Components: jdbc, sql, thin client >Affects Versions: 3.0.0-alpha4 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > Time Spent: 10m > Remaining Estimate: 0h > > Rename client operation names, request handlers, and their packages from Sql > to Jdbc. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-17034) Thin 3.0: Rename JDBC packages and classes to separate them from Ignite SQL API
[ https://issues.apache.org/jira/browse/IGNITE-17034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17542207#comment-17542207 ] Igor Sapego commented on IGNITE-17034: -- Looks good to me > Thin 3.0: Rename JDBC packages and classes to separate them from Ignite SQL > API > --- > > Key: IGNITE-17034 > URL: https://issues.apache.org/jira/browse/IGNITE-17034 > Project: Ignite > Issue Type: Improvement > Components: jdbc, sql, thin client >Affects Versions: 3.0.0-alpha4 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > Time Spent: 10m > Remaining Estimate: 0h > > Rename client operation names, request handlers, and their packages from Sql > to Jdbc. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17034) Thin 3.0: Rename JDBC packages and classes to separate them from Ignite SQL API
Pavel Tupitsyn created IGNITE-17034: --- Summary: Thin 3.0: Rename JDBC packages and classes to separate them from Ignite SQL API Key: IGNITE-17034 URL: https://issues.apache.org/jira/browse/IGNITE-17034 Project: Ignite Issue Type: Improvement Components: jdbc, sql, thin client Affects Versions: 3.0.0-alpha4 Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: 3.0.0-alpha5 Rename client operation names, request handlers, and their packages from Sql to Jdbc. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17031) Stabilize the test StopCalciteModuleTest#testStopQueryOnNodeStop
[
https://issues.apache.org/jira/browse/IGNITE-17031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-17031:
--
Labels: ignite-3 (was: )
> Stabilize the test StopCalciteModuleTest#testStopQueryOnNodeStop
>
>
> Key: IGNITE-17031
> URL: https://issues.apache.org/jira/browse/IGNITE-17031
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 3.0.0-alpha4
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha5
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The test is periodically fails with error
> {code}
> org.opentest4j.AssertionFailedError: Unexpected type ==> expected:
> but
> was:
> at
> org.junit.jupiter.api.AssertInstanceOf.assertInstanceOf(AssertInstanceOf.java:51)
> at
> org.junit.jupiter.api.AssertInstanceOf.assertInstanceOf(AssertInstanceOf.java:35)
> at
> org.junit.jupiter.api.Assertions.assertInstanceOf(Assertions.java:3539)
> at
> org.apache.ignite.internal.sql.engine.StopCalciteModuleTest.lambda$testStopQueryOnNodeStop$7(StopCalciteModuleTest.java:231)
> at
> java.base/java.util.concurrent.CompletableFuture.uniExceptionally(CompletableFuture.java:986)
> at
> java.base/java.util.concurrent.CompletableFuture.uniExceptionallyStage(CompletableFuture.java:1004)
> at
> java.base/java.util.concurrent.CompletableFuture.exceptionally(CompletableFuture.java:2307)
> at
> org.apache.ignite.internal.sql.engine.StopCalciteModuleTest.testStopQueryOnNodeStop(StopCalciteModuleTest.java:228)
> ...
> {code}
> *Root cause*:
> {{ExecutionServiceImpl#stop}} doesn't await of the end of asynchronous close
> query cursors.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (IGNITE-11998) Fix DataPageScan for fragmented pages.
[
https://issues.apache.org/jira/browse/IGNITE-11998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17542075#comment-17542075
]
Maxim Muzafarov commented on IGNITE-11998:
--
The following notes must also be considered:
- the {{cacheId}} is not always been written to the data pages the
investigation required here;
- we can create a new FragmentedDataPageIO layer to identify the pages with
tails (a pageIo migration required);
> Fix DataPageScan for fragmented pages.
> --
>
> Key: IGNITE-11998
> URL: https://issues.apache.org/jira/browse/IGNITE-11998
> Project: Ignite
> Issue Type: Bug
>Reporter: Ivan Bessonov
>Assignee: Maxim Muzafarov
>Priority: Critical
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Fragmented pages crash JVM when accessed by DataPageScan scanner/query
> optimized scanner. It happens when scanner accesses data in later chunk in
> fragmented entry but treats it like the first one, expecting length of the
> payload, which is absent and replaced with raw entry data.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-17033) Move ignite-aop to the Ignite Extensions
[ https://issues.apache.org/jira/browse/IGNITE-17033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-17033: - Issue Type: Task (was: Improvement) > Move ignite-aop to the Ignite Extensions > > > Key: IGNITE-17033 > URL: https://issues.apache.org/jira/browse/IGNITE-17033 > Project: Ignite > Issue Type: Task >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.14 > > > The ignite-aop module must be moved to the Ignite Extension since it has not > been updated for a few years and it is not configured on TC for running tests. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17033) Move ignite-aop to the Ignite Extensions
Maxim Muzafarov created IGNITE-17033: Summary: Move ignite-aop to the Ignite Extensions Key: IGNITE-17033 URL: https://issues.apache.org/jira/browse/IGNITE-17033 Project: Ignite Issue Type: Improvement Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Fix For: 2.14 The ignite-aop module must be moved to the Ignite Extension since it has not been updated for a few years and it is not configured on TC for running tests. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Comment Edited] (IGNITE-16936) Incorrect DML syntax error message contains sensitive information
[ https://issues.apache.org/jira/browse/IGNITE-16936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17542069#comment-17542069 ] Yury Gerzhedovich edited comment on IGNITE-16936 at 5/25/22 2:12 PM: - [~AldoRaine] the GNITE-17001 about not only for 'Duplicate key during INSERT' event, please check patch for the ticket and description. was (Author: jooger): [~AldoRaine] the GNITE-17001 not only 'Duplicate key during INSERT', please check patch for the ticket and description. > Incorrect DML syntax error message contains sensitive information > - > > Key: IGNITE-16936 > URL: https://issues.apache.org/jira/browse/IGNITE-16936 > Project: Ignite > Issue Type: Bug >Reporter: Luchnikov Alexander >Priority: Major > Labels: ise > Attachments: > IGNITE-16936_Ignore_IGNITE_TO_STRING_INCLUDE_SENSITIVE_in_wrong_syntax_DML_error_message_-.patch > > > Incorrect DML syntax error message contains sensitive information. > Regardless of the value of IGNITE_TO_STRING_INCLUDE_SENSITIVE. > Reproducer > [^IGNITE-16936_Ignore_IGNITE_TO_STRING_INCLUDE_SENSITIVE_in_wrong_syntax_DML_error_message_-.patch] > show what SENSITIVE contains in message. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-16936) Incorrect DML syntax error message contains sensitive information
[ https://issues.apache.org/jira/browse/IGNITE-16936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17542069#comment-17542069 ] Yury Gerzhedovich commented on IGNITE-16936: [~AldoRaine] the GNITE-17001 not only 'Duplicate key during INSERT', please check patch for the ticket and description. > Incorrect DML syntax error message contains sensitive information > - > > Key: IGNITE-16936 > URL: https://issues.apache.org/jira/browse/IGNITE-16936 > Project: Ignite > Issue Type: Bug >Reporter: Luchnikov Alexander >Priority: Major > Labels: ise > Attachments: > IGNITE-16936_Ignore_IGNITE_TO_STRING_INCLUDE_SENSITIVE_in_wrong_syntax_DML_error_message_-.patch > > > Incorrect DML syntax error message contains sensitive information. > Regardless of the value of IGNITE_TO_STRING_INCLUDE_SENSITIVE. > Reproducer > [^IGNITE-16936_Ignore_IGNITE_TO_STRING_INCLUDE_SENSITIVE_in_wrong_syntax_DML_error_message_-.patch] > show what SENSITIVE contains in message. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (IGNITE-17031) Stabilize the test StopCalciteModuleTest#testStopQueryOnNodeStop
[
https://issues.apache.org/jira/browse/IGNITE-17031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov resolved IGNITE-17031.
---
Resolution: Fixed
Merged to
[main|https://github.com/apache/ignite-3/commit/d9d7ba2c5132584d8eca77bee76f159364fd58b1]
> Stabilize the test StopCalciteModuleTest#testStopQueryOnNodeStop
>
>
> Key: IGNITE-17031
> URL: https://issues.apache.org/jira/browse/IGNITE-17031
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 3.0.0-alpha4
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Major
> Fix For: 3.0.0-alpha5
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The test is periodically fails with error
> {code}
> org.opentest4j.AssertionFailedError: Unexpected type ==> expected:
> but
> was:
> at
> org.junit.jupiter.api.AssertInstanceOf.assertInstanceOf(AssertInstanceOf.java:51)
> at
> org.junit.jupiter.api.AssertInstanceOf.assertInstanceOf(AssertInstanceOf.java:35)
> at
> org.junit.jupiter.api.Assertions.assertInstanceOf(Assertions.java:3539)
> at
> org.apache.ignite.internal.sql.engine.StopCalciteModuleTest.lambda$testStopQueryOnNodeStop$7(StopCalciteModuleTest.java:231)
> at
> java.base/java.util.concurrent.CompletableFuture.uniExceptionally(CompletableFuture.java:986)
> at
> java.base/java.util.concurrent.CompletableFuture.uniExceptionallyStage(CompletableFuture.java:1004)
> at
> java.base/java.util.concurrent.CompletableFuture.exceptionally(CompletableFuture.java:2307)
> at
> org.apache.ignite.internal.sql.engine.StopCalciteModuleTest.testStopQueryOnNodeStop(StopCalciteModuleTest.java:228)
> ...
> {code}
> *Root cause*:
> {{ExecutionServiceImpl#stop}} doesn't await of the end of asynchronous close
> query cursors.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-17032) Apache Ignite Docker container does not run correctly if image is run in read only file system mode
[ https://issues.apache.org/jira/browse/IGNITE-17032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petar Tonkovic updated IGNITE-17032: Description: When following the Kubernetes deployment tutorials (online: https://ignite.apache.org/docs/latest/installation/kubernetes/azure-deployment, youtube: [https://youtu.be/38YgdAOs038]), trying to run the official docker image () with the --read-only flag is causing errors: /opt/ignite/apache-ignite/bin/include/functions.sh: line 52: cannot create temp file for here-document: Read-only file system /opt/ignite/apache-ignite/bin/include/functions.sh: line 85: [: -lt: unary operator expected2022-05-25T14:27:34.504369604+02:00 Since most managed company Kubernetes clusters enforce this read-only flag as a security requirement, it would be good to look into these errors. Later on, we get the following error on starting up: class org.apache.ignite.IgniteException: Failed to instantiate Spring XML application context (make sure all classes used in Spring configuration are present at CLASSPATH) [springUrl=file:/ignite/config/node-configuration.xml] at org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:1135) at org.apache.ignite.Ignition.start(Ignition.java:356) at org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:365) Caused by: class org.apache.ignite.IgniteCheckedException: Failed to instantiate Spring XML application context (make sure all classes used in Spring configuration are present at CLASSPATH) [springUrl=file:/ignite/config/node-configuration.xml] at org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.applicationContext(IgniteSpringHelperImpl.java:364) at org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.loadConfigurations(IgniteSpringHelperImpl.java:102) at org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.loadConfigurations(IgniteSpringHelperImpl.java:96) at org.apache.ignite.internal.IgnitionEx.loadConfigurations(IgnitionEx.java:729)2022-05-25T14:27:34.916588365+02:00 at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:930) at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:839)2022-05-25T14:27:34.916609431+02:00 at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:709)2022-05-25T14:27:34.916622089+02:00 at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:678)2022-05-25T14:27:34.916636146+02:00 at org.apache.ignite.Ignition.start(Ignition.java:353)2022-05-25T14:27:34.916650122+02:00 ... 1 more2022-05-25T14:27:34.916671644+02:00 Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.apache.ignite.configuration.IgniteConfiguration#0' defined in URL [file:/ignite/config/node-configuration.xml|file://ignite/config/node-configuration.xml]: Cannot create inner bean 'org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi#56ef9176' of type [org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi] while setting bean property 'discoverySpi'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi#56ef9176' defined in URL [file:/ignite/config/node-configuration.xml|file://ignite/config/node-configuration.xml]: Cannot create inner bean 'org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder#13805618' of type [org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder] while setting bean property 'ipFinder'; nested exception is org.springframework.beans.factory.CannotLoadBeanClassException: Cannot find class [org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder] for bean with name 'org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder#13805618' defined in URL [file:/ignite/config/node-configuration.xml|file://ignite/config/node-configuration.xml]; nested exception is java.lang.ClassNotFoundException: org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:389) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:127) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1702) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1447) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:593) at
[jira] [Commented] (IGNITE-16306) snaptree-based in-memory storage
[ https://issues.apache.org/jira/browse/IGNITE-16306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17542064#comment-17542064 ] Ivan Bessonov commented on IGNITE-16306: [~sergeychugunov] sure, with great pleasure! > snaptree-based in-memory storage > > > Key: IGNITE-16306 > URL: https://issues.apache.org/jira/browse/IGNITE-16306 > Project: Ignite > Issue Type: Improvement >Affects Versions: 3.0.0-alpha3 >Reporter: Ivan Bessonov >Assignee: Aleksandr Polovtcev >Priority: Major > Labels: iep-74, ignite-3 > > Until a full-fledged MV store is implemented we can implement in-memory > storage on a snaptree library [1] that represents a concurrent AVL tree with > support of snapshots. > In this ticket we need to integrate the library with our existing storage > APIs (refine API if necessary), integrate its snapshot API with Raft > snapshots and provide configuration if necessary. > [1] https://github.com/nbronson/snaptree -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (IGNITE-16306) snaptree-based in-memory storage
[ https://issues.apache.org/jira/browse/IGNITE-16306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov resolved IGNITE-16306. Resolution: Won't Fix > snaptree-based in-memory storage > > > Key: IGNITE-16306 > URL: https://issues.apache.org/jira/browse/IGNITE-16306 > Project: Ignite > Issue Type: Improvement >Affects Versions: 3.0.0-alpha3 >Reporter: Ivan Bessonov >Assignee: Aleksandr Polovtcev >Priority: Major > Labels: iep-74, ignite-3 > > Until a full-fledged MV store is implemented we can implement in-memory > storage on a snaptree library [1] that represents a concurrent AVL tree with > support of snapshots. > In this ticket we need to integrate the library with our existing storage > APIs (refine API if necessary), integrate its snapshot API with Raft > snapshots and provide configuration if necessary. > [1] https://github.com/nbronson/snaptree -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-16306) snaptree-based in-memory storage
[ https://issues.apache.org/jira/browse/IGNITE-16306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17542063#comment-17542063 ] Sergey Chugunov commented on IGNITE-16306: -- [~ibessonov] , this ticket doesn't seem relevant to me as in-memory PageMemory implementation is already ported to ignite-3 codebase. Could you please close it as an owner of that task? > snaptree-based in-memory storage > > > Key: IGNITE-16306 > URL: https://issues.apache.org/jira/browse/IGNITE-16306 > Project: Ignite > Issue Type: Improvement >Affects Versions: 3.0.0-alpha3 >Reporter: Ivan Bessonov >Assignee: Aleksandr Polovtcev >Priority: Major > Labels: iep-74, ignite-3 > > Until a full-fledged MV store is implemented we can implement in-memory > storage on a snaptree library [1] that represents a concurrent AVL tree with > support of snapshots. > In this ticket we need to integrate the library with our existing storage > APIs (refine API if necessary), integrate its snapshot API with Raft > snapshots and provide configuration if necessary. > [1] https://github.com/nbronson/snaptree -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17032) Apache Ignite Docker container does not run correctly if image is run in read only file system mode
[ https://issues.apache.org/jira/browse/IGNITE-17032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petar Tonkovic updated IGNITE-17032: Description: When following the Kubernetes deployment tutorials (online: [https://ignite.apache.org/docs/latest/logging], youtube: [https://youtu.be/38YgdAOs038]), trying to run the official docker image () with the --read-only flag is causing errors: /opt/ignite/apache-ignite/bin/include/functions.sh: line 52: cannot create temp file for here-document: Read-only file system /opt/ignite/apache-ignite/bin/include/functions.sh: line 85: [: -lt: unary operator expected2022-05-25T14:27:34.504369604+02:00 Since most managed company Kubernetes clusters enforce this read-only flag as a security requirement, it would be good to look into these errors. Later on, we get the following error on starting up: class org.apache.ignite.IgniteException: Failed to instantiate Spring XML application context (make sure all classes used in Spring configuration are present at CLASSPATH) [springUrl=file:/ignite/config/node-configuration.xml] at org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:1135) at org.apache.ignite.Ignition.start(Ignition.java:356) at org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:365) Caused by: class org.apache.ignite.IgniteCheckedException: Failed to instantiate Spring XML application context (make sure all classes used in Spring configuration are present at CLASSPATH) [springUrl=file:/ignite/config/node-configuration.xml] at org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.applicationContext(IgniteSpringHelperImpl.java:364) at org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.loadConfigurations(IgniteSpringHelperImpl.java:102) at org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.loadConfigurations(IgniteSpringHelperImpl.java:96) at org.apache.ignite.internal.IgnitionEx.loadConfigurations(IgnitionEx.java:729)2022-05-25T14:27:34.916588365+02:00 at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:930) at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:839)2022-05-25T14:27:34.916609431+02:00 at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:709)2022-05-25T14:27:34.916622089+02:00 at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:678)2022-05-25T14:27:34.916636146+02:00 at org.apache.ignite.Ignition.start(Ignition.java:353)2022-05-25T14:27:34.916650122+02:00 ... 1 more2022-05-25T14:27:34.916671644+02:00 Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.apache.ignite.configuration.IgniteConfiguration#0' defined in URL [file:/ignite/config/node-configuration.xml|file://ignite/config/node-configuration.xml]: Cannot create inner bean 'org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi#56ef9176' of type [org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi] while setting bean property 'discoverySpi'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi#56ef9176' defined in URL [file:/ignite/config/node-configuration.xml|file://ignite/config/node-configuration.xml]: Cannot create inner bean 'org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder#13805618' of type [org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder] while setting bean property 'ipFinder'; nested exception is org.springframework.beans.factory.CannotLoadBeanClassException: Cannot find class [org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder] for bean with name 'org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder#13805618' defined in URL [file:/ignite/config/node-configuration.xml|file://ignite/config/node-configuration.xml]; nested exception is java.lang.ClassNotFoundException: org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:389) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:127) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1702) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1447) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:593) at
[jira] [Updated] (IGNITE-17032) Apache Ignite Docker container does not run correctly if image is run in read only file system mode
[ https://issues.apache.org/jira/browse/IGNITE-17032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petar Tonkovic updated IGNITE-17032: Description: When following the Kubernetes deployment tutorials (online: [https://ignite.apache.org/docs/latest/logging], youtube: [https://youtu.be/38YgdAOs038]) Trying to run the official docker image () with the --read-only flag is causing errors: /opt/ignite/apache-ignite/bin/include/functions.sh: line 52: cannot create temp file for here-document: Read-only file system /opt/ignite/apache-ignite/bin/include/functions.sh: line 85: [: -lt: unary operator expected2022-05-25T14:27:34.504369604+02:00 Since most managed company Kubernetes clusters enforce this read-only flag as a security requirement, it would be good to look into these errors. Later on, we get the following error on starting up: class org.apache.ignite.IgniteException: Failed to instantiate Spring XML application context (make sure all classes used in Spring configuration are present at CLASSPATH) [springUrl=file:/ignite/config/node-configuration.xml] at org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:1135) at org.apache.ignite.Ignition.start(Ignition.java:356) at org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:365) Caused by: class org.apache.ignite.IgniteCheckedException: Failed to instantiate Spring XML application context (make sure all classes used in Spring configuration are present at CLASSPATH) [springUrl=file:/ignite/config/node-configuration.xml] at org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.applicationContext(IgniteSpringHelperImpl.java:364) at org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.loadConfigurations(IgniteSpringHelperImpl.java:102) at org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.loadConfigurations(IgniteSpringHelperImpl.java:96) at org.apache.ignite.internal.IgnitionEx.loadConfigurations(IgnitionEx.java:729)2022-05-25T14:27:34.916588365+02:00 at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:930) at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:839)2022-05-25T14:27:34.916609431+02:00 at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:709)2022-05-25T14:27:34.916622089+02:00 at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:678)2022-05-25T14:27:34.916636146+02:00 at org.apache.ignite.Ignition.start(Ignition.java:353)2022-05-25T14:27:34.916650122+02:00 ... 1 more2022-05-25T14:27:34.916671644+02:00 Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.apache.ignite.configuration.IgniteConfiguration#0' defined in URL [file:/ignite/config/node-configuration.xml|file://ignite/config/node-configuration.xml]: Cannot create inner bean 'org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi#56ef9176' of type [org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi] while setting bean property 'discoverySpi'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi#56ef9176' defined in URL [file:/ignite/config/node-configuration.xml|file://ignite/config/node-configuration.xml]: Cannot create inner bean 'org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder#13805618' of type [org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder] while setting bean property 'ipFinder'; nested exception is org.springframework.beans.factory.CannotLoadBeanClassException: Cannot find class [org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder] for bean with name 'org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder#13805618' defined in URL [file:/ignite/config/node-configuration.xml|file://ignite/config/node-configuration.xml]; nested exception is java.lang.ClassNotFoundException: org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:389) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:127) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1702) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1447) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:593) at
[jira] [Updated] (IGNITE-17032) Apache Ignite Docker container does not run correctly if image is run in read only file system mode
[ https://issues.apache.org/jira/browse/IGNITE-17032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petar Tonkovic updated IGNITE-17032: Description: When following the Kubernetes deployment tutorials (online:https://ignite.apache.org/docs/latest/logging, youtube:https://youtu.be/38YgdAOs038) Trying to run the official docker image () with the --read-only flag is causing errors: /opt/ignite/apache-ignite/bin/include/functions.sh: line 52: cannot create temp file for here-document: Read-only file system /opt/ignite/apache-ignite/bin/include/functions.sh: line 85: [: -lt: unary operator expected2022-05-25T14:27:34.504369604+02:00 Since most managed company Kubernetes clusters enforce this read-only flag as a security requirement, it would be good to look into these errors. Later on, we get the following error on starting up: class org.apache.ignite.IgniteException: Failed to instantiate Spring XML application context (make sure all classes used in Spring configuration are present at CLASSPATH) [springUrl=file:/ignite/config/node-configuration.xml] at org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:1135) at org.apache.ignite.Ignition.start(Ignition.java:356) at org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:365) Caused by: class org.apache.ignite.IgniteCheckedException: Failed to instantiate Spring XML application context (make sure all classes used in Spring configuration are present at CLASSPATH) [springUrl=file:/ignite/config/node-configuration.xml] at org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.applicationContext(IgniteSpringHelperImpl.java:364) at org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.loadConfigurations(IgniteSpringHelperImpl.java:102) at org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.loadConfigurations(IgniteSpringHelperImpl.java:96) at org.apache.ignite.internal.IgnitionEx.loadConfigurations(IgnitionEx.java:729)2022-05-25T14:27:34.916588365+02:00 at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:930) at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:839)2022-05-25T14:27:34.916609431+02:00 at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:709)2022-05-25T14:27:34.916622089+02:00 at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:678)2022-05-25T14:27:34.916636146+02:00 at org.apache.ignite.Ignition.start(Ignition.java:353)2022-05-25T14:27:34.916650122+02:00 ... 1 more2022-05-25T14:27:34.916671644+02:00 Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.apache.ignite.configuration.IgniteConfiguration#0' defined in URL [file:/ignite/config/node-configuration.xml|file://ignite/config/node-configuration.xml]: Cannot create inner bean 'org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi#56ef9176' of type [org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi] while setting bean property 'discoverySpi'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi#56ef9176' defined in URL [file:/ignite/config/node-configuration.xml|file://ignite/config/node-configuration.xml]: Cannot create inner bean 'org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder#13805618' of type [org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder] while setting bean property 'ipFinder'; nested exception is org.springframework.beans.factory.CannotLoadBeanClassException: Cannot find class [org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder] for bean with name 'org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder#13805618' defined in URL [file:/ignite/config/node-configuration.xml|file://ignite/config/node-configuration.xml]; nested exception is java.lang.ClassNotFoundException: org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:389) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:127) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1702) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1447) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:593) at
[jira] [Updated] (IGNITE-17032) Apache Ignite Docker container does not run correctly if image is run in read only file system mode
[ https://issues.apache.org/jira/browse/IGNITE-17032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petar Tonkovic updated IGNITE-17032: Description: Trying to run the official docker image () with the --read-only flag is causing errors: /opt/ignite/apache-ignite/bin/include/functions.sh: line 52: cannot create temp file for here-document: Read-only file system /opt/ignite/apache-ignite/bin/include/functions.sh: line 85: [: -lt: unary operator expected2022-05-25T14:27:34.504369604+02:00 Since most managed company Kubernetes clusters enforce this read-only flag as a security requirement, it would be good to look into these errors. Later on, we get the following error on starting up: class org.apache.ignite.IgniteException: Failed to instantiate Spring XML application context (make sure all classes used in Spring configuration are present at CLASSPATH) [springUrl=file:/ignite/config/node-configuration.xml] at org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:1135) at org.apache.ignite.Ignition.start(Ignition.java:356) at org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:365) Caused by: class org.apache.ignite.IgniteCheckedException: Failed to instantiate Spring XML application context (make sure all classes used in Spring configuration are present at CLASSPATH) [springUrl=file:/ignite/config/node-configuration.xml] at org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.applicationContext(IgniteSpringHelperImpl.java:364) at org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.loadConfigurations(IgniteSpringHelperImpl.java:102) at org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.loadConfigurations(IgniteSpringHelperImpl.java:96) at org.apache.ignite.internal.IgnitionEx.loadConfigurations(IgnitionEx.java:729)2022-05-25T14:27:34.916588365+02:00 at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:930) at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:839)2022-05-25T14:27:34.916609431+02:00 at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:709)2022-05-25T14:27:34.916622089+02:00 at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:678)2022-05-25T14:27:34.916636146+02:00 at org.apache.ignite.Ignition.start(Ignition.java:353)2022-05-25T14:27:34.916650122+02:00 ... 1 more2022-05-25T14:27:34.916671644+02:00 Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.apache.ignite.configuration.IgniteConfiguration#0' defined in URL [file:/ignite/config/node-configuration.xml]: Cannot create inner bean 'org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi#56ef9176' of type [org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi] while setting bean property 'discoverySpi'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi#56ef9176' defined in URL [file:/ignite/config/node-configuration.xml]: Cannot create inner bean 'org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder#13805618' of type [org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder] while setting bean property 'ipFinder'; nested exception is org.springframework.beans.factory.CannotLoadBeanClassException: Cannot find class [org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder] for bean with name 'org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder#13805618' defined in URL [file:/ignite/config/node-configuration.xml]; nested exception is java.lang.ClassNotFoundException: org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:389) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:127) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1702) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1447) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:593) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:516)2022-05-25T14:27:34.916861927+02:00 at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:324)2022-05-25T14:27:34.916874946+02:00 at
[jira] [Updated] (IGNITE-17032) Apache Ignite Docker container does not run correctly if image is run in read only file system mode
[ https://issues.apache.org/jira/browse/IGNITE-17032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petar Tonkovic updated IGNITE-17032: Description: Trying to run the official docker image () with the --read-only flag is causing errors: /opt/ignite/apache-ignite/bin/include/functions.sh: line 52: cannot create temp file for here-document: Read-only file system /opt/ignite/apache-ignite/bin/include/functions.sh: line 85: [: -lt: unary operator expected2022-05-25T14:27:34.504369604+02:00 Since most managed company Kubernetes clusters enforce this read-only flag as a security requirement, it would be good to look into these errors. Later on, we get the following error on starting up: class org.apache.ignite.IgniteException: Failed to instantiate Spring XML application context (make sure all classes used in Spring configuration are present at CLASSPATH) [springUrl=file:/ignite/config/node-configuration.xml] at org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:1135) at org.apache.ignite.Ignition.start(Ignition.java:356) at org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:365) Caused by: class org.apache.ignite.IgniteCheckedException: Failed to instantiate Spring XML application context (make sure all classes used in Spring configuration are present at CLASSPATH) [springUrl=file:/ignite/config/node-configuration.xml] at org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.applicationContext(IgniteSpringHelperImpl.java:364) at org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.loadConfigurations(IgniteSpringHelperImpl.java:102) at org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.loadConfigurations(IgniteSpringHelperImpl.java:96) at org.apache.ignite.internal.IgnitionEx.loadConfigurations(IgnitionEx.java:729)2022-05-25T14:27:34.916588365+02:00 at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:930) at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:839)2022-05-25T14:27:34.916609431+02:00 at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:709)2022-05-25T14:27:34.916622089+02:00 at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:678)2022-05-25T14:27:34.916636146+02:00 at org.apache.ignite.Ignition.start(Ignition.java:353)2022-05-25T14:27:34.916650122+02:00 ... 1 more2022-05-25T14:27:34.916671644+02:00 Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.apache.ignite.configuration.IgniteConfiguration#0' defined in URL [file:/ignite/config/node-configuration.xml|file://ignite/config/node-configuration.xml]: Cannot create inner bean 'org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi#56ef9176' of type [org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi] while setting bean property 'discoverySpi'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi#56ef9176' defined in URL [file:/ignite/config/node-configuration.xml|file://ignite/config/node-configuration.xml]: Cannot create inner bean 'org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder#13805618' of type [org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder] while setting bean property 'ipFinder'; nested exception is org.springframework.beans.factory.CannotLoadBeanClassException: Cannot find class [org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder] for bean with name 'org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder#13805618' defined in URL [file:/ignite/config/node-configuration.xml|file://ignite/config/node-configuration.xml]; nested exception is java.lang.ClassNotFoundException: org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:389) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:127) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1702) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1447) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:593) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:516)2022-05-25T14:27:34.916861927+02:00 at
[jira] [Created] (IGNITE-17032) Apache Ignite Docker container does not run correctly if image is run in read only file system mode
Petar Tonkovic created IGNITE-17032: --- Summary: Apache Ignite Docker container does not run correctly if image is run in read only file system mode Key: IGNITE-17032 URL: https://issues.apache.org/jira/browse/IGNITE-17032 Project: Ignite Issue Type: Bug Components: build Affects Versions: 2.13 Reporter: Petar Tonkovic Trying to run the official docker image () with the --read-only flag is causing errors: /opt/ignite/apache-ignite/bin/include/functions.sh: line 52: cannot create temp file for here-document: Read-only file system /opt/ignite/apache-ignite/bin/include/functions.sh: line 85: [: -lt: unary operator expected2022-05-25T14:27:34.504369604+02:00 Since most managed company Kubernetes clusters enforce this read-only flag as a security requirement, it would be good to look into these errors. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17031) Stabilize the test StopCalciteModuleTest#testStopQueryOnNodeStop
[
https://issues.apache.org/jira/browse/IGNITE-17031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-17031:
--
Description:
The test is periodically fails with error
{code}
org.opentest4j.AssertionFailedError: Unexpected type ==> expected:
but
was:
at
org.junit.jupiter.api.AssertInstanceOf.assertInstanceOf(AssertInstanceOf.java:51)
at
org.junit.jupiter.api.AssertInstanceOf.assertInstanceOf(AssertInstanceOf.java:35)
at
org.junit.jupiter.api.Assertions.assertInstanceOf(Assertions.java:3539)
at
org.apache.ignite.internal.sql.engine.StopCalciteModuleTest.lambda$testStopQueryOnNodeStop$7(StopCalciteModuleTest.java:231)
at
java.base/java.util.concurrent.CompletableFuture.uniExceptionally(CompletableFuture.java:986)
at
java.base/java.util.concurrent.CompletableFuture.uniExceptionallyStage(CompletableFuture.java:1004)
at
java.base/java.util.concurrent.CompletableFuture.exceptionally(CompletableFuture.java:2307)
at
org.apache.ignite.internal.sql.engine.StopCalciteModuleTest.testStopQueryOnNodeStop(StopCalciteModuleTest.java:228)
...
{code}
*Root cause*:
{{ExecutionServiceImpl#stop}} doesn't await of the end of asynchronous close
query cursors.
was:The test is periodically fails.
> Stabilize the test StopCalciteModuleTest#testStopQueryOnNodeStop
>
>
> Key: IGNITE-17031
> URL: https://issues.apache.org/jira/browse/IGNITE-17031
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 3.0.0-alpha4
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Major
> Fix For: 3.0.0-alpha5
>
>
> The test is periodically fails with error
> {code}
> org.opentest4j.AssertionFailedError: Unexpected type ==> expected:
> but
> was:
> at
> org.junit.jupiter.api.AssertInstanceOf.assertInstanceOf(AssertInstanceOf.java:51)
> at
> org.junit.jupiter.api.AssertInstanceOf.assertInstanceOf(AssertInstanceOf.java:35)
> at
> org.junit.jupiter.api.Assertions.assertInstanceOf(Assertions.java:3539)
> at
> org.apache.ignite.internal.sql.engine.StopCalciteModuleTest.lambda$testStopQueryOnNodeStop$7(StopCalciteModuleTest.java:231)
> at
> java.base/java.util.concurrent.CompletableFuture.uniExceptionally(CompletableFuture.java:986)
> at
> java.base/java.util.concurrent.CompletableFuture.uniExceptionallyStage(CompletableFuture.java:1004)
> at
> java.base/java.util.concurrent.CompletableFuture.exceptionally(CompletableFuture.java:2307)
> at
> org.apache.ignite.internal.sql.engine.StopCalciteModuleTest.testStopQueryOnNodeStop(StopCalciteModuleTest.java:228)
> ...
> {code}
> *Root cause*:
> {{ExecutionServiceImpl#stop}} doesn't await of the end of asynchronous close
> query cursors.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (IGNITE-17031) Stabilize the test StopCalciteModuleTest#testStopQueryOnNodeStop
Taras Ledkov created IGNITE-17031: - Summary: Stabilize the test StopCalciteModuleTest#testStopQueryOnNodeStop Key: IGNITE-17031 URL: https://issues.apache.org/jira/browse/IGNITE-17031 Project: Ignite Issue Type: Bug Components: sql Affects Versions: 3.0.0-alpha4 Reporter: Taras Ledkov Assignee: Taras Ledkov Fix For: 3.0.0-alpha5 The test is periodically fails. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17015) Perform rebalance on node recovery before join
[
https://issues.apache.org/jira/browse/IGNITE-17015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-17015:
-
Epic Link: IGNITE-16362
> Perform rebalance on node recovery before join
> ---
>
> Key: IGNITE-17015
> URL: https://issues.apache.org/jira/browse/IGNITE-17015
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Chudov
>Priority: Major
> Labels: ignite-3
>
> For now, there is only one condition for distributed recovery completion -
> it's meta storage catch-up (see {{
> org.apache.ignite.internal.recovery.RecoveryCompletionFutureFactory#create }}
> ). During recovery raft groups for tables start. So, rebalance is able to
> start during recovery and we can just wait for it in recovery completion
> future.
> Rebalance should be performed for those tables which assignments are
> up-to-date with the cluster, i.e. it should start after meta storage catch-up.
> Rebalance should be considered as completed after successful read from local
> node. It can be implemented after implementation of consistent read from
> backups (see IGNITE-16767), which incapsulates following logic: consistent
> read is possible either when local raft log is replicated and consistent with
> leader, i.e. local index and leader index are the same, or when read with
> safe-time* is successul.
> *Safe-time is some timestamp. All updates which have less or equal timestamp
> than safe-time are already replicated on this node.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (IGNITE-17030) Automatic restart after Maintenance Mode completion
Sergey Chugunov created IGNITE-17030: Summary: Automatic restart after Maintenance Mode completion Key: IGNITE-17030 URL: https://issues.apache.org/jira/browse/IGNITE-17030 Project: Ignite Issue Type: Improvement Components: control.sh, persistence Reporter: Sergey Chugunov Maintenance Mode, though being a valuable piece of functionality, requires too much manual intervention from the end-user, which makes managing Ignite cluster inconvenient in environments like K8. This behavior could be improved in the following way: * For maintenance tasks, which execution starts automatically upon entering Maintenance Mode, automatic restart is performed to get back to normal operations. It worth mentioning that it doesn't matter whether these tasks are requested by the user or created automatically because of internal errors. * For maintenance tasks requiring user intervention nothing changes: only user can decide that the task is finished, than it's up to the users as well to decide when to restart the node. This behavior should be reflected in documentation. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17026) Add the 2.13 version to compatibility tests
[ https://issues.apache.org/jira/browse/IGNITE-17026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-17026: - Fix Version/s: 2.14 > Add the 2.13 version to compatibility tests > --- > > Key: IGNITE-17026 > URL: https://issues.apache.org/jira/browse/IGNITE-17026 > Project: Ignite > Issue Type: Task >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > Add the 2.13 version to compatibility tests -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (IGNITE-17026) Add the 2.13 version to compatibility tests
[ https://issues.apache.org/jira/browse/IGNITE-17026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita resolved IGNITE-17026. -- Resolution: Fixed Merged into the master. [~xtern], thanks for the review. > Add the 2.13 version to compatibility tests > --- > > Key: IGNITE-17026 > URL: https://issues.apache.org/jira/browse/IGNITE-17026 > Project: Ignite > Issue Type: Task >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Add the 2.13 version to compatibility tests -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-17026) Add the 2.13 version to compatibility tests
[
https://issues.apache.org/jira/browse/IGNITE-17026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17542013#comment-17542013
]
Ignite TC Bot commented on IGNITE-17026:
{panel:title=Branch: [pull/10034/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}PDS 2{color} [[tests 0 TIMEOUT , Exit Code
|https://ci2.ignite.apache.org/viewLog.html?buildId=6452499]]
{panel}
{panel:title=Branch: [pull/10034/head] Base: [master] : New Tests
(8)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}PDS (Compatibility){color} [[tests
8|https://ci2.ignite.apache.org/viewLog.html?buildId=6451366]]
* {color:#013220}IgniteCompatibilityBasicTestSuite:
IndexTypesCompatibilityTest.testQueryOldIndex[ver=2.13.0] - PASSED{color}
* {color:#013220}IgniteCompatibilityBasicTestSuite:
InlineJavaObjectCompatibilityTest.testQueryOldInlinedIndex[ver=2.13.0,
cfgInlineSize=true] - PASSED{color}
* {color:#013220}IgniteCompatibilityBasicTestSuite:
InlineJavaObjectCompatibilityTest.testQueryOldInlinedIndex[ver=2.13.0,
cfgInlineSize=false] - PASSED{color}
* {color:#013220}IgniteCompatibilityBasicTestSuite:
PersistenceBasicCompatibilityTest.testNodeStartByOldVersionPersistenceData[version=2.13.0]
- PASSED{color}
* {color:#013220}IgniteCompatibilityBasicTestSuite:
JdbcThinCompatibilityTest.testCurrentClientToOldServer[Version 2.13.0] -
PASSED{color}
* {color:#013220}IgniteCompatibilityBasicTestSuite:
JdbcThinCompatibilityTest.testOldClientToCurrentServer[Version 2.13.0] -
PASSED{color}
* {color:#013220}IgniteCompatibilityBasicTestSuite:
JavaThinCompatibilityTest.testCurrentClientToOldServer[Version 2.13.0] -
PASSED{color}
* {color:#013220}IgniteCompatibilityBasicTestSuite:
JavaThinCompatibilityTest.testOldClientToCurrentServer[Version 2.13.0] -
PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=6451338buildTypeId=IgniteTests24Java8_RunAll]
> Add the 2.13 version to compatibility tests
> ---
>
> Key: IGNITE-17026
> URL: https://issues.apache.org/jira/browse/IGNITE-17026
> Project: Ignite
> Issue Type: Task
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Add the 2.13 version to compatibility tests
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-16888) Update Ignite dependency: lz4
[ https://issues.apache.org/jira/browse/IGNITE-16888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-16888: - Fix Version/s: 2.14 > Update Ignite dependency: lz4 > - > > Key: IGNITE-16888 > URL: https://issues.apache.org/jira/browse/IGNITE-16888 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Major > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > Update lz4 dependency 1.5.0 to 1.8.0 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (IGNITE-17025) Remove the ability to manually set INLINE_SIZE for types with a fixed length
[
https://issues.apache.org/jira/browse/IGNITE-17025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Izhikov reassigned IGNITE-17025:
Assignee: Nikolay Izhikov
> Remove the ability to manually set INLINE_SIZE for types with a fixed length
>
>
> Key: IGNITE-17025
> URL: https://issues.apache.org/jira/browse/IGNITE-17025
> Project: Ignite
> Issue Type: Improvement
>Reporter: Luchnikov Alexander
>Assignee: Nikolay Izhikov
>Priority: Minor
> Labels: ise
> Attachments: InlineIndexTest1.patch
>
>
> The reproducer ( [^InlineIndexTest1.patch] ) shows index.bin size growing
> when INLINE_SIZE increases when creating indexes on fixed length fields.The
> negative point is that a place is reserved that does not carry any profit.
> As a solution. When trying to build an index on a field with a fixed length
> type, do not allow this. The value of INLINE_SIZE for such types is
> calculated automatically. And display a WARN level message about it.
> To see the size of index.bin, run the
> {code:java}
> du -sh IGNITE_HOME/db/node*/*INLINE*/* | grep index.bin"
> {code}
> after running the reproducer.
> {code:java}
> 36K BIGINT_INLINE10/index.bin
> 320K BIGINT_INLINE100/index.bin
> 128K INT_INLINE10/index.bin
> 324K INT_INLINE100/index.bin
> 64K NUMBER_INLINE10/index.bin
> 64K NUMBER_INLINE100/index.bin
> 128K VARCHAR_INLINE10/index.bin
> 256K VARCHAR_INLINE100/index.bin
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (IGNITE-11998) Fix DataPageScan for fragmented pages.
[
https://issues.apache.org/jira/browse/IGNITE-11998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17541980#comment-17541980
]
Maxim Muzafarov commented on IGNITE-11998:
--
h4. The inital proposal
Currently, during a full scan of a cache group partition (SqlQuery or
ScanQuery) all the data is read though the partition B-Tree and this in turn
leads to the _n(log n)_ complexity. For such a queries it may be necessary to
read all the data by sequential pages read directly from the partition file
which has the _n_ complexity and also the sequential file reads has some
benefits instead of random access file reads.
h4. The main issue
Accoring to the [Ignite Multi-Tier Storage - under the
hood|https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Multi-Tier+Storage+-+under+the+hood#IgniteMultiTierStorageunderthehood-Longobjects]
long objects are splitted on the several pages. For the pages which are
contain an entry tail there is no any dedicated page attribute or page header
flag to identify such a pages, however, such a pages have a link to an other
fragment or a entry head. These pages may only be accessed from the page which
contain the entry head.
h4. Current solution and benchmarks
_The double loop over the all partition pages. _
During the first loop we are reading all the pages and collecting references to
the other pages (reading entries are performed from the head to tail, writing
entries are preformed from the tail to head). On the second loop we are
building the list of pages that doesn't have a references on itself - and these
are the pages that containing the entries headers to be read.
||Data Page Scan||true||false||
|IgniteDataPageScanBenchmark|148848|179228|
|IgniteDataPageScanBenchmark|186917|166980|
|IgniteDataPageScanBenchmark|197114|175667|
h4. Possible solutions
An additional analysis and investigation required to perform the full partition
scan using only the one loop. We need to identify the fragmented pages with
entries tails:
- for such a pages we can write the {{freeSpace}}, {{directCounter}},
{{indirectCounter}} e.g. {{-1}} value (currently it's zero) and here we need
check the pds compatibility.
- almost the same issue with identifying fragmented pages are here -
IGNITE-12510
> Fix DataPageScan for fragmented pages.
> --
>
> Key: IGNITE-11998
> URL: https://issues.apache.org/jira/browse/IGNITE-11998
> Project: Ignite
> Issue Type: Bug
>Reporter: Ivan Bessonov
>Assignee: Maxim Muzafarov
>Priority: Critical
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Fragmented pages crash JVM when accessed by DataPageScan scanner/query
> optimized scanner. It happens when scanner accesses data in later chunk in
> fragmented entry but treats it like the first one, expecting length of the
> payload, which is absent and replaced with raw entry data.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-16984) [Native Persistence 3.0] Porting a checkpoint and related code, part 4
[ https://issues.apache.org/jira/browse/IGNITE-16984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko updated IGNITE-16984: - Description: Before implementing the new checkpoint algorithm, you need to port the checkpoint code from 2.0 . Need to port: * *org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointManager* Also finalize all tests related to *org.apache.ignite.internal.pagememory.persistence.PageMemoryImpl* and fix all *TODO: IGNITE-16984*. was:Before implementing the new checkpoint algorithm, you need to port the checkpoint code from 2.0 . > [Native Persistence 3.0] Porting a checkpoint and related code, part 4 > -- > > Key: IGNITE-16984 > URL: https://issues.apache.org/jira/browse/IGNITE-16984 > Project: Ignite > Issue Type: Task >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > Time Spent: 10m > Remaining Estimate: 0h > > Before implementing the new checkpoint algorithm, you need to port the > checkpoint code from 2.0 . > Need to port: > * > *org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointManager* > Also finalize all tests related to > *org.apache.ignite.internal.pagememory.persistence.PageMemoryImpl* and fix > all *TODO: IGNITE-16984*. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (IGNITE-16965) SQL API: Implement synchronous SQL API.
[ https://issues.apache.org/jira/browse/IGNITE-16965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov reassigned IGNITE-16965: - Assignee: Taras Ledkov > SQL API: Implement synchronous SQL API. > --- > > Key: IGNITE-16965 > URL: https://issues.apache.org/jira/browse/IGNITE-16965 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Mashenkov >Assignee: Taras Ledkov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > > Implement session and session builder interfaces (excl. async/reactive) > Implement statement and statement builder (excl. prepared) > Implement client-server protocol, messages and integrate it with the query > engine. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (IGNITE-17013) Implement failure handling for changePeerAsync invocation regarding rebalance algorithm
[
https://issues.apache.org/jira/browse/IGNITE-17013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirza Aliev reassigned IGNITE-17013:
Assignee: Mirza Aliev
> Implement failure handling for changePeerAsync invocation regarding rebalance
> algorithm
> -
>
> Key: IGNITE-17013
> URL: https://issues.apache.org/jira/browse/IGNITE-17013
> Project: Ignite
> Issue Type: Task
>Reporter: Mirza Aliev
>Assignee: Mirza Aliev
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha5
>
>
> According to the relalance algorithm
> https://github.com/apache/ignite-3/blob/main/modules/table/tech-notes/rebalance.md
> after leader node receives an updating of a pending key, it starts a raft
> group reconfiguration by calling {{RaftGroupService#changePeersAsync}} which
> returns future, that can be completed exceptionally. We should provide the
> way to retry {{RaftGroupService#changePeersAsync}} invocation, with some
> throttling, and in case of failure cancel the current rebalance.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
