[jira] [Assigned] (IGNITE-20426) Sync deprecated methods in the ClientCacheConfiguration
[
https://issues.apache.org/jira/browse/IGNITE-20426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev reassigned IGNITE-20426:
Assignee: Anastasia Iakimova (was: Nikita Amelchev)
> Sync deprecated methods in the ClientCacheConfiguration
> ---
>
> Key: IGNITE-20426
> URL: https://issues.apache.org/jira/browse/IGNITE-20426
> Project: Ignite
> Issue Type: Task
>Reporter: Nikita Amelchev
>Assignee: Anastasia Iakimova
>Priority: Minor
> Labels: ise
>
> The following properties are deprecated in {{CacheConfiguration}} but are
> still actual in {{ClientCacheConfiguration}}:
> * getDefaultLockTimeout
> * getRebalanceBatchSize
> * getRebalanceBatchesPrefetchCount
> * getRebalanceDelay
> * getRebalanceThrottle
> * getRebalanceTimeout
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-15647) -e parameter of sqlline command does not work properly
[
https://issues.apache.org/jira/browse/IGNITE-15647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17706998#comment-17706998
]
Ilya Kasnacheev commented on IGNITE-15647:
--
Thank you [~alex_pl]
> -e parameter of sqlline command does not work properly
> --
>
> Key: IGNITE-15647
> URL: https://issues.apache.org/jira/browse/IGNITE-15647
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.10
> Environment: CentOS7.8.2003
>Reporter: Anton Kondratev
>Assignee: Ilya Kasnacheev
>Priority: Critical
> Fix For: 2.15
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> SQL query specified in -e parameter of sqlline command does not get parsed
> properly and therefore not executed.
> I'm trying to use it like this:
> {code:java}
> ./sqlline.sh -u jdbc:ignite:thin://1.2.3.4 -n login -p password -e 'select *
> from \"sys\".\"tables\";'{code}
> and output is:
> {code:java}
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> include (Is a directory)
> Property "url" is required
> Property "url" is required
> from (No such file or directory)
> \"sys\".\"tables\"; (No such file or directory)
> Error: Failed to parse query. Syntax error in SQL statement "SELECT [*]";
> expected "TOP, LIMIT, DISTINCT, ALL, *, NOT, EXISTS, INTERSECTS"; SQL
> statement:
> select [42001-197] (state=42000,code=1001)
> java.sql.SQLException: Failed to parse query. Syntax error in SQL statement
> "SELECT [*]"; expected "TOP, LIMIT, DISTINCT, ALL, *, NOT, EXISTS,
> INTERSECTS"; SQL statement:
> select [42001-197]
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:1009)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:234)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:560)
> at sqlline.Commands.executeSingleQuery(Commands.java:1054)
> at sqlline.Commands.execute(Commands.java:1003)
> at sqlline.Commands.sql(Commands.java:967)
> at sqlline.SqlLine.dispatch(SqlLine.java:734)
> at sqlline.SqlLine.initArgs(SqlLine.java:449)
> at sqlline.SqlLine.begin(SqlLine.java:515)
> at sqlline.SqlLine.start(SqlLine.java:267)
> at sqlline.SqlLine.main(SqlLine.java:206)
> sqlline version 1.9.0{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-15647) -e parameter of sqlline command does not work properly
[
https://issues.apache.org/jira/browse/IGNITE-15647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17602229#comment-17602229
]
Ilya Kasnacheev commented on IGNITE-15647:
--
[~liyuj] please review.
> -e parameter of sqlline command does not work properly
> --
>
> Key: IGNITE-15647
> URL: https://issues.apache.org/jira/browse/IGNITE-15647
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.10
> Environment: CentOS7.8.2003
>Reporter: Anton Kondratev
>Assignee: Ilya Kasnacheev
>Priority: Critical
> Fix For: 2.15
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> SQL query specified in -e parameter of sqlline command does not get parsed
> properly and therefore not executed.
> I'm trying to use it like this:
> {code:java}
> ./sqlline.sh -u jdbc:ignite:thin://1.2.3.4 -n login -p password -e 'select *
> from \"sys\".\"tables\";'{code}
> and output is:
> {code:java}
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> include (Is a directory)
> Property "url" is required
> Property "url" is required
> from (No such file or directory)
> \"sys\".\"tables\"; (No such file or directory)
> Error: Failed to parse query. Syntax error in SQL statement "SELECT [*]";
> expected "TOP, LIMIT, DISTINCT, ALL, *, NOT, EXISTS, INTERSECTS"; SQL
> statement:
> select [42001-197] (state=42000,code=1001)
> java.sql.SQLException: Failed to parse query. Syntax error in SQL statement
> "SELECT [*]"; expected "TOP, LIMIT, DISTINCT, ALL, *, NOT, EXISTS,
> INTERSECTS"; SQL statement:
> select [42001-197]
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:1009)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:234)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:560)
> at sqlline.Commands.executeSingleQuery(Commands.java:1054)
> at sqlline.Commands.execute(Commands.java:1003)
> at sqlline.Commands.sql(Commands.java:967)
> at sqlline.SqlLine.dispatch(SqlLine.java:734)
> at sqlline.SqlLine.initArgs(SqlLine.java:449)
> at sqlline.SqlLine.begin(SqlLine.java:515)
> at sqlline.SqlLine.start(SqlLine.java:267)
> at sqlline.SqlLine.main(SqlLine.java:206)
> sqlline version 1.9.0{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (IGNITE-16617) Delete the sections related to FIRSTVALUE and LASTVALUE functions in the document
[ https://issues.apache.org/jira/browse/IGNITE-16617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev resolved IGNITE-16617. -- Resolution: Fixed > Delete the sections related to FIRSTVALUE and LASTVALUE functions in the > document > - > > Key: IGNITE-16617 > URL: https://issues.apache.org/jira/browse/IGNITE-16617 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.12 >Reporter: YuJue Li >Assignee: YuJue Li >Priority: Critical > Fix For: 2.13 > > Time Spent: 20m > Remaining Estimate: 0h > > [https://ignite.apache.org/docs/latest/sql-reference/aggregate-functions] > Ignite does not support these two functions, so community should delete the > related contents from the document. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-15958) Ignite修改账户密码不支持防爆力破解
[
https://issues.apache.org/jira/browse/IGNITE-15958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17446775#comment-17446775
]
Ilya Kasnacheev commented on IGNITE-15958:
--
If you have proper SSL you likely do not need login/password protection at all.
> Ignite修改账户密码不支持防爆力破解
>
>
> Key: IGNITE-15958
> URL: https://issues.apache.org/jira/browse/IGNITE-15958
> Project: Ignite
> Issue Type: Bug
> Components: security
>Affects Versions: 2.8.1
>Reporter: igniteForCrackTest
>Priority: Major
>
> Ignite使用sqlline.sh修改密码时不支持防爆力破解，如下：
> {code:java}
> sqlline.sh --verbose=true -u
> "jdbc:ignite:thin://${IGNITE_IP}:${CLIENT_CONNECT_PORT};user=${IGNITE_USER};password=${IGNITE_PASSWORD};ssl=true;sslProtocol=TLSv1.2"
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-15958) Ignite修改账户密码不支持防爆力破解
[
https://issues.apache.org/jira/browse/IGNITE-15958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17446725#comment-17446725
]
Ilya Kasnacheev commented on IGNITE-15958:
--
Did you enable TLS in ClientConnectorConfiguration? You might need to specify
key/trust stores on client and server, and not just ssl=true.
> Ignite修改账户密码不支持防爆力破解
>
>
> Key: IGNITE-15958
> URL: https://issues.apache.org/jira/browse/IGNITE-15958
> Project: Ignite
> Issue Type: Bug
> Components: security
>Affects Versions: 2.8.1
>Reporter: igniteForCrackTest
>Priority: Major
>
> Ignite使用sqlline.sh修改密码时不支持防爆力破解，如下：
> {code:java}
> sqlline.sh --verbose=true -u
> "jdbc:ignite:thin://${IGNITE_IP}:${CLIENT_CONNECT_PORT};user=${IGNITE_USER};password=${IGNITE_PASSWORD};ssl=true;sslProtocol=TLSv1.2"
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-15942) Add support for h2 1.4.200 version to Ignite and Spring Ignite Data packages
[ https://issues.apache.org/jira/browse/IGNITE-15942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17445470#comment-17445470 ] Ilya Kasnacheev commented on IGNITE-15942: -- I'm not sure it is feasible, I know that H2 has dropped some of APIs needed by Ignite integration. > Add support for h2 1.4.200 version to Ignite and Spring Ignite Data packages > > > Key: IGNITE-15942 > URL: https://issues.apache.org/jira/browse/IGNITE-15942 > Project: Ignite > Issue Type: Improvement >Reporter: Julius Kabugu >Priority: Major > > Today, when we create Ignite thick clients, the ignite client packages and > Spring Ignite Data require h2 database version 1.4.197. Upgrading to 1.4.200 > breaks the clients. However, h2 1.4.197 has been flagged by security scans > due to a number of vulnerabilities. > The request is to update Ignite client packages to use H2 database version > 1.4.200. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Issue Comment Deleted] (IGNITE-15647) -e parameter of sqlline command does not work properly
[
https://issues.apache.org/jira/browse/IGNITE-15647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev updated IGNITE-15647:
-
Comment: was deleted
(was: {panel:title=Branch: [pull/9536/head] Base: [master] : Possible Blockers
(8)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Windows){color} [[tests 1 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6243286]]
* exe: CacheTest.TestCacheWithExpiryPolicyOnUpdate - Test has low fail rate in
base branch 1,2% and is not flaky
{color:#d04437}Platform C++ CMake (Win x64 / Release){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6243279]]
* IgniteThinClientTest: CacheClientTestSuite: CacheClientRemoveAll - Test has
low fail rate in base branch 0,0% and is not flaky
{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6243226]]
* ZookeeperDiscoverySpiTestSuite1:
ZookeeperDiscoveryMiscTest.testSetConsistentId - Test has low fail rate in base
branch 0,0% and is not flaky
{color:#d04437}Cache 5{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6243248]]
* IgniteCacheTestSuite5:
GridExchangeFreeCellularSwitchTxContinuationTest.testAlreadyStartedTxsContinuationDuringAndAfterTheSwitch[Isolation
= PESSIMISTIC, Concurrency = READ_COMMITTED, Started from = BROKEN_CELL] -
Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Control Utility{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6243277]]
{color:#d04437}Java Client{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6243208]]
{color:#d04437}ZooKeeper (Discovery) 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6243227]]
* ZookeeperDiscoverySpiTestSuite2:
GridCachePartitionedNodeRestartTest.testRestartWithTxPutAllTenNodesTwoBackups -
Test has low fail rate in base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/9536/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6243287buildTypeId=IgniteTests24Java8_RunAll])
> -e parameter of sqlline command does not work properly
> --
>
> Key: IGNITE-15647
> URL: https://issues.apache.org/jira/browse/IGNITE-15647
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.10
> Environment: CentOS7.8.2003
>Reporter: Anton Kondratev
>Assignee: Ilya Kasnacheev
>Priority: Critical
> Fix For: 2.12
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> SQL query specified in -e parameter of sqlline command does not get parsed
> properly and therefore not executed.
> I'm trying to use it like this:
> {code:java}
> ./sqlline.sh -u jdbc:ignite:thin://1.2.3.4 -n login -p password -e 'select *
> from \"sys\".\"tables\";'{code}
> and output is:
> {code:java}
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> include (Is a directory)
> Property "url" is required
> Property "url" is required
> from (No such file or directory)
> \"sys\".\"tables\"; (No such file or directory)
> Error: Failed to parse query. Syntax error in SQL statement "SELECT [*]";
> expected "TOP, LIMIT, DISTINCT, ALL, *, NOT, EXISTS, INTERSECTS"; SQL
> statement:
> select [42001-197] (state=42000,code=1001)
> java.sql.SQLException: Failed to parse query. Syntax error in SQL statement
> "SELECT [*]"; expected "TOP, LIMIT, DISTINCT, ALL, *, NOT, EXISTS,
> INTERSECTS"; SQL statement:
> select [42001-197]
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:1009)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:234)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:560)
> at sqlline.Commands.executeSingleQuery(Commands.java:1054)
> at sqlline.Commands.execute(Commands.java:1003)
> at sqlline.Commands.sql(Commands.java:967)
> at sqlline.SqlLine.dispatch(SqlLine.java:734)
> at sqlline.SqlLine.initArgs(SqlLine.java:449)
> at sqlline.SqlLine.begin(SqlLine.java:515)
> at sqlline.SqlLine.start(SqlLine.java:267)
> at sqlline.SqlLine.main(SqlLine.java:206)
> sqlline version 1.9.0{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15647) -e parameter of sqlline command does not work properly
[
https://issues.apache.org/jira/browse/IGNITE-15647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17435069#comment-17435069
]
Ilya Kasnacheev commented on IGNITE-15647:
--
{code}
apache-ignite-2.13.0-SNAPSHOT-bin% bin/sqlline.sh --silent -u
jdbc:ignite:thin://127.0.0.1 -n login -p password -e 'select * from
sys.tables;'0:31
++--+++-++-+---+-+---+--+
| CACHE_GROUP_ID | CACHE_GROUP_NAME | CACHE_ID | CACHE_NAME | SCHEMA_NAME
| TABLE_NAME | AFFINITY_KEY_COLUMN | KEY_ALIAS | VALUE_ALIAS | KEY_TYPE_NAME
| VALUE_ |
++--+++-++-+---+-+---+--+
| -897948415 | SQL_PUBLIC_FOO | -897948415 | SQL_PUBLIC_FOO | PUBLIC
| FOO| | BAR | |
java.lang.Integer | SQL_PUBLIC_FOO_5f3ec4bc_ |
++--+++-++-+---+-+---+--+
{code}
> -e parameter of sqlline command does not work properly
> --
>
> Key: IGNITE-15647
> URL: https://issues.apache.org/jira/browse/IGNITE-15647
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.10
> Environment: CentOS7.8.2003
>Reporter: Anton Kondratev
>Assignee: Ilya Kasnacheev
>Priority: Critical
> Fix For: 2.12
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> SQL query specified in -e parameter of sqlline command does not get parsed
> properly and therefore not executed.
> I'm trying to use it like this:
> {code:java}
> ./sqlline.sh -u jdbc:ignite:thin://1.2.3.4 -n login -p password -e 'select *
> from \"sys\".\"tables\";'{code}
> and output is:
> {code:java}
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> include (Is a directory)
> Property "url" is required
> Property "url" is required
> from (No such file or directory)
> \"sys\".\"tables\"; (No such file or directory)
> Error: Failed to parse query. Syntax error in SQL statement "SELECT [*]";
> expected "TOP, LIMIT, DISTINCT, ALL, *, NOT, EXISTS, INTERSECTS"; SQL
> statement:
> select [42001-197] (state=42000,code=1001)
> java.sql.SQLException: Failed to parse query. Syntax error in SQL statement
> "SELECT [*]"; expected "TOP, LIMIT, DISTINCT, ALL, *, NOT, EXISTS,
> INTERSECTS"; SQL statement:
> select [42001-197]
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:1009)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:234)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:560)
> at sqlline.Commands.executeSingleQuery(Commands.java:1054)
> at sqlline.Commands.execute(Commands.java:1003)
> at sqlline.Commands.sql(Commands.java:967)
> at sqlline.SqlLine.dispatch(SqlLine.java:734)
> at sqlline.SqlLine.initArgs(SqlLine.java:449)
> at sqlline.SqlLine.begin(SqlLine.java:515)
> at sqlline.SqlLine.start(SqlLine.java:267)
> at sqlline.SqlLine.main(SqlLine.java:206)
> sqlline version 1.9.0{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-15647) -e parameter of sqlline command does not work properly
[
https://issues.apache.org/jira/browse/IGNITE-15647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17435069#comment-17435069
]
Ilya Kasnacheev edited comment on IGNITE-15647 at 10/27/21, 9:32 PM:
-
{code}
apache-ignite-2.13.0-SNAPSHOT-bin% bin/sqlline.sh --silent -u
jdbc:ignite:thin://127.0.0.1 -n login -p password -e 'select * from sys.tables;'
++--+++-++-+---+-+---+--+
| CACHE_GROUP_ID | CACHE_GROUP_NAME | CACHE_ID | CACHE_NAME | SCHEMA_NAME
| TABLE_NAME | AFFINITY_KEY_COLUMN | KEY_ALIAS | VALUE_ALIAS | KEY_TYPE_NAME
| VALUE_ |
++--+++-++-+---+-+---+--+
| -897948415 | SQL_PUBLIC_FOO | -897948415 | SQL_PUBLIC_FOO | PUBLIC
| FOO| | BAR | |
java.lang.Integer | SQL_PUBLIC_FOO_5f3ec4bc_ |
++--+++-++-+---+-+---+--+
{code}
was (Author: ilyak):
{code}
apache-ignite-2.13.0-SNAPSHOT-bin% bin/sqlline.sh --silent -u
jdbc:ignite:thin://127.0.0.1 -n login -p password -e 'select * from
sys.tables;'0:31
++--+++-++-+---+-+---+--+
| CACHE_GROUP_ID | CACHE_GROUP_NAME | CACHE_ID | CACHE_NAME | SCHEMA_NAME
| TABLE_NAME | AFFINITY_KEY_COLUMN | KEY_ALIAS | VALUE_ALIAS | KEY_TYPE_NAME
| VALUE_ |
++--+++-++-+---+-+---+--+
| -897948415 | SQL_PUBLIC_FOO | -897948415 | SQL_PUBLIC_FOO | PUBLIC
| FOO| | BAR | |
java.lang.Integer | SQL_PUBLIC_FOO_5f3ec4bc_ |
++--+++-++-+---+-+---+--+
{code}
> -e parameter of sqlline command does not work properly
> --
>
> Key: IGNITE-15647
> URL: https://issues.apache.org/jira/browse/IGNITE-15647
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.10
> Environment: CentOS7.8.2003
>Reporter: Anton Kondratev
>Assignee: Ilya Kasnacheev
>Priority: Critical
> Fix For: 2.12
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> SQL query specified in -e parameter of sqlline command does not get parsed
> properly and therefore not executed.
> I'm trying to use it like this:
> {code:java}
> ./sqlline.sh -u jdbc:ignite:thin://1.2.3.4 -n login -p password -e 'select *
> from \"sys\".\"tables\";'{code}
> and output is:
> {code:java}
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> include (Is a directory)
> Property "url" is required
> Property "url" is required
> from (No such file or directory)
> \"sys\".\"tables\"; (No such file or directory)
> Error: Failed to parse query. Syntax error in SQL statement "SELECT [*]";
> expected "TOP, LIMIT, DISTINCT, ALL, *, NOT, EXISTS, INTERSECTS"; SQL
> statement:
> select [42001-197] (state=42000,code=1001)
> java.sql.SQLException: Failed to parse query. Syntax error in SQL statement
> "SELECT [*]"; expected "TOP, LIMIT, DISTINCT, ALL, *, NOT, EXISTS,
> INTERSECTS"; SQL statement:
> select [42001-197]
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:1009)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:234)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:560)
> at sqlline.Commands.executeSingleQuery(Commands.java:1054)
> at sqlline.Commands.execute(Commands.java:1003)
> at sqlline.Commands.sql(Commands.java:967)
> at sqlline.SqlLine.dispatch(SqlLine.java:734)
> at sqlline.SqlLine.initArgs(SqlLine.java:449)
> at sqlline.SqlLine.begin(SqlLine.java:515)
> at sqlline.SqlLine.start(SqlLine.java:267)
> at sqlline.SqlLine.main(SqlLine.java:206)
> sqlline version
[jira] [Commented] (IGNITE-15647) -e parameter of sqlline command does not work properly
[
https://issues.apache.org/jira/browse/IGNITE-15647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17435070#comment-17435070
]
Ilya Kasnacheev commented on IGNITE-15647:
--
[~ant0nk] [~jooger] please review
> -e parameter of sqlline command does not work properly
> --
>
> Key: IGNITE-15647
> URL: https://issues.apache.org/jira/browse/IGNITE-15647
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.10
> Environment: CentOS7.8.2003
>Reporter: Anton Kondratev
>Assignee: Ilya Kasnacheev
>Priority: Critical
> Fix For: 2.12
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> SQL query specified in -e parameter of sqlline command does not get parsed
> properly and therefore not executed.
> I'm trying to use it like this:
> {code:java}
> ./sqlline.sh -u jdbc:ignite:thin://1.2.3.4 -n login -p password -e 'select *
> from \"sys\".\"tables\";'{code}
> and output is:
> {code:java}
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> include (Is a directory)
> Property "url" is required
> Property "url" is required
> from (No such file or directory)
> \"sys\".\"tables\"; (No such file or directory)
> Error: Failed to parse query. Syntax error in SQL statement "SELECT [*]";
> expected "TOP, LIMIT, DISTINCT, ALL, *, NOT, EXISTS, INTERSECTS"; SQL
> statement:
> select [42001-197] (state=42000,code=1001)
> java.sql.SQLException: Failed to parse query. Syntax error in SQL statement
> "SELECT [*]"; expected "TOP, LIMIT, DISTINCT, ALL, *, NOT, EXISTS,
> INTERSECTS"; SQL statement:
> select [42001-197]
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:1009)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:234)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:560)
> at sqlline.Commands.executeSingleQuery(Commands.java:1054)
> at sqlline.Commands.execute(Commands.java:1003)
> at sqlline.Commands.sql(Commands.java:967)
> at sqlline.SqlLine.dispatch(SqlLine.java:734)
> at sqlline.SqlLine.initArgs(SqlLine.java:449)
> at sqlline.SqlLine.begin(SqlLine.java:515)
> at sqlline.SqlLine.start(SqlLine.java:267)
> at sqlline.SqlLine.main(SqlLine.java:206)
> sqlline version 1.9.0{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15647) -e parameter of sqlline command does not work properly
[
https://issues.apache.org/jira/browse/IGNITE-15647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev updated IGNITE-15647:
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> -e parameter of sqlline command does not work properly
> --
>
> Key: IGNITE-15647
> URL: https://issues.apache.org/jira/browse/IGNITE-15647
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.10
> Environment: CentOS7.8.2003
>Reporter: Anton Kondratev
>Assignee: Ilya Kasnacheev
>Priority: Critical
> Fix For: 2.12
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> SQL query specified in -e parameter of sqlline command does not get parsed
> properly and therefore not executed.
> I'm trying to use it like this:
> {code:java}
> ./sqlline.sh -u jdbc:ignite:thin://1.2.3.4 -n login -p password -e 'select *
> from \"sys\".\"tables\";'{code}
> and output is:
> {code:java}
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> include (Is a directory)
> Property "url" is required
> Property "url" is required
> from (No such file or directory)
> \"sys\".\"tables\"; (No such file or directory)
> Error: Failed to parse query. Syntax error in SQL statement "SELECT [*]";
> expected "TOP, LIMIT, DISTINCT, ALL, *, NOT, EXISTS, INTERSECTS"; SQL
> statement:
> select [42001-197] (state=42000,code=1001)
> java.sql.SQLException: Failed to parse query. Syntax error in SQL statement
> "SELECT [*]"; expected "TOP, LIMIT, DISTINCT, ALL, *, NOT, EXISTS,
> INTERSECTS"; SQL statement:
> select [42001-197]
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:1009)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:234)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:560)
> at sqlline.Commands.executeSingleQuery(Commands.java:1054)
> at sqlline.Commands.execute(Commands.java:1003)
> at sqlline.Commands.sql(Commands.java:967)
> at sqlline.SqlLine.dispatch(SqlLine.java:734)
> at sqlline.SqlLine.initArgs(SqlLine.java:449)
> at sqlline.SqlLine.begin(SqlLine.java:515)
> at sqlline.SqlLine.start(SqlLine.java:267)
> at sqlline.SqlLine.main(SqlLine.java:206)
> sqlline version 1.9.0{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15349) Bugyard feedback #4: Fix code snippet on SQL transactions
[
https://issues.apache.org/jira/browse/IGNITE-15349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17428099#comment-17428099
]
Ilya Kasnacheev commented on IGNITE-15349:
--
I have cherry-picked it to 2.11
> Bugyard feedback #4: Fix code snippet on SQL transactions
> -
>
> Key: IGNITE-15349
> URL: https://issues.apache.org/jira/browse/IGNITE-15349
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.10, 2.11
>Reporter: Igor Gusev
>Assignee: Igor Gusev
>Priority: Major
> Labels: Documentation, documentation
> Fix For: 2.11
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> We need to fix [the second code
> snippet|https://ignite.apache.org/docs/latest/sql-reference/transactions#example]
> on SQL Transactions doc page:
>
> {code:java}
> BEGIN;
> INSERT INTO Person (id, name, city_id) VALUES (1, 'John Doe', 3);
> UPDATE City SET population = population + 1 WHERE id = 3;
> {code}
>
> This code snippet appears to be a duplicate of the preceding one and does not
> actually show how to "Roll back the changes...".
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15459) Bugyard feedback #5: Fix Kubernetes installation script
[ https://issues.apache.org/jira/browse/IGNITE-15459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17428098#comment-17428098 ] Ilya Kasnacheev commented on IGNITE-15459: -- I have cherry-picked it to 2.11 > Bugyard feedback #5: Fix Kubernetes installation script > --- > > Key: IGNITE-15459 > URL: https://issues.apache.org/jira/browse/IGNITE-15459 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.10, 2.11 >Reporter: Igor Gusev >Assignee: Igor Gusev >Priority: Major > Fix For: 2.11 > > Time Spent: 20m > Remaining Estimate: 0h > > We need to fix the code sample in [Creating ConfigMap for Node Configuration > File > |[https://ignite.apache.org/docs/latest/installation/kubernetes/gke-deployment#creating-configmap-for-node-configuration-file]] > section of kubernetes installation. > The code snippet does not include full example. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15461) Bugyard feedback #6: Specify that near-caches are not created on thin clients
[ https://issues.apache.org/jira/browse/IGNITE-15461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17428096#comment-17428096 ] Ilya Kasnacheev commented on IGNITE-15461: -- I have cherry-picked it to 2.11 > Bugyard feedback #6: Specify that near-caches are not created on thin clients > - > > Key: IGNITE-15461 > URL: https://issues.apache.org/jira/browse/IGNITE-15461 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Igor Gusev >Assignee: Igor Gusev >Priority: Major > Fix For: 2.11 > > Time Spent: 20m > Remaining Estimate: 0h > > Bugyard feedback 6 asks if near caches are available on thin clients. We > should specify that it only affects thick clients and servers on the near > cache page > https://ignite.apache.org/docs/latest/configuring-caches/near-cache. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15461) Bugyard feedback #6: Specify that near-caches are not created on thin clients
[ https://issues.apache.org/jira/browse/IGNITE-15461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17427201#comment-17427201 ] Ilya Kasnacheev commented on IGNITE-15461: -- Anything else needs to be done? Does it need to be propagated anywhere? > Bugyard feedback #6: Specify that near-caches are not created on thin clients > - > > Key: IGNITE-15461 > URL: https://issues.apache.org/jira/browse/IGNITE-15461 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Igor Gusev >Assignee: Igor Gusev >Priority: Major > Fix For: 2.11 > > Time Spent: 20m > Remaining Estimate: 0h > > Bugyard feedback 6 asks if near caches are available on thin clients. We > should specify that it only affects thick clients and servers on the near > cache page > https://ignite.apache.org/docs/latest/configuring-caches/near-cache. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15349) Bugyard feedback #4: Fix code snippet on SQL transactions
[
https://issues.apache.org/jira/browse/IGNITE-15349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17427198#comment-17427198
]
Ilya Kasnacheev commented on IGNITE-15349:
--
Please resolve if it was merged.
> Bugyard feedback #4: Fix code snippet on SQL transactions
> -
>
> Key: IGNITE-15349
> URL: https://issues.apache.org/jira/browse/IGNITE-15349
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.10, 2.11
>Reporter: Igor Gusev
>Assignee: Igor Gusev
>Priority: Major
> Labels: Documentation, documentation
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> We need to fix [the second code
> snippet|https://ignite.apache.org/docs/latest/sql-reference/transactions#example]
> on SQL Transactions doc page:
>
> {code:java}
> BEGIN;
> INSERT INTO Person (id, name, city_id) VALUES (1, 'John Doe', 3);
> UPDATE City SET population = population + 1 WHERE id = 3;
> {code}
>
> This code snippet appears to be a duplicate of the preceding one and does not
> actually show how to "Roll back the changes...".
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15459) Bugyard feedback #5: Fix Kubernetes installation script
[ https://issues.apache.org/jira/browse/IGNITE-15459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17427199#comment-17427199 ] Ilya Kasnacheev commented on IGNITE-15459: -- Please resolve and set version. > Bugyard feedback #5: Fix Kubernetes installation script > --- > > Key: IGNITE-15459 > URL: https://issues.apache.org/jira/browse/IGNITE-15459 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.10, 2.11 >Reporter: Igor Gusev >Assignee: Igor Gusev >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > We need to fix the code sample in [Creating ConfigMap for Node Configuration > File > |[https://ignite.apache.org/docs/latest/installation/kubernetes/gke-deployment#creating-configmap-for-node-configuration-file]] > section of kubernetes installation. > The code snippet does not include full example. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-15647) -e parameter of sqlline command does not work properly
[
https://issues.apache.org/jira/browse/IGNITE-15647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17425442#comment-17425442
]
Ilya Kasnacheev edited comment on IGNITE-15647 at 10/7/21, 9:47 AM:
[~jooger] not right now - you can reassign it if you want.
was (Author: ilyak):
[~jooger] not riguth now - you can reassign it if you want.
> -e parameter of sqlline command does not work properly
> --
>
> Key: IGNITE-15647
> URL: https://issues.apache.org/jira/browse/IGNITE-15647
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.10
> Environment: CentOS7.8.2003
>Reporter: Anton Kondratev
>Assignee: Ilya Kasnacheev
>Priority: Critical
> Fix For: 2.12
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> SQL query specified in -e parameter of sqlline command does not get parsed
> properly and therefore not executed.
> I'm trying to use it like this:
> {code:java}
> ./sqlline.sh -u jdbc:ignite:thin://1.2.3.4 -n login -p password -e 'select *
> from \"sys\".\"tables\";'{code}
> and output is:
> {code:java}
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> include (Is a directory)
> Property "url" is required
> Property "url" is required
> from (No such file or directory)
> \"sys\".\"tables\"; (No such file or directory)
> Error: Failed to parse query. Syntax error in SQL statement "SELECT [*]";
> expected "TOP, LIMIT, DISTINCT, ALL, *, NOT, EXISTS, INTERSECTS"; SQL
> statement:
> select [42001-197] (state=42000,code=1001)
> java.sql.SQLException: Failed to parse query. Syntax error in SQL statement
> "SELECT [*]"; expected "TOP, LIMIT, DISTINCT, ALL, *, NOT, EXISTS,
> INTERSECTS"; SQL statement:
> select [42001-197]
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:1009)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:234)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:560)
> at sqlline.Commands.executeSingleQuery(Commands.java:1054)
> at sqlline.Commands.execute(Commands.java:1003)
> at sqlline.Commands.sql(Commands.java:967)
> at sqlline.SqlLine.dispatch(SqlLine.java:734)
> at sqlline.SqlLine.initArgs(SqlLine.java:449)
> at sqlline.SqlLine.begin(SqlLine.java:515)
> at sqlline.SqlLine.start(SqlLine.java:267)
> at sqlline.SqlLine.main(SqlLine.java:206)
> sqlline version 1.9.0{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15647) -e parameter of sqlline command does not work properly
[
https://issues.apache.org/jira/browse/IGNITE-15647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17425442#comment-17425442
]
Ilya Kasnacheev commented on IGNITE-15647:
--
[~jooger] not riguth now - you can reassign it if you want.
> -e parameter of sqlline command does not work properly
> --
>
> Key: IGNITE-15647
> URL: https://issues.apache.org/jira/browse/IGNITE-15647
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.10
> Environment: CentOS7.8.2003
>Reporter: Anton Kondratev
>Assignee: Ilya Kasnacheev
>Priority: Critical
> Fix For: 2.12
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> SQL query specified in -e parameter of sqlline command does not get parsed
> properly and therefore not executed.
> I'm trying to use it like this:
> {code:java}
> ./sqlline.sh -u jdbc:ignite:thin://1.2.3.4 -n login -p password -e 'select *
> from \"sys\".\"tables\";'{code}
> and output is:
> {code:java}
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> include (Is a directory)
> Property "url" is required
> Property "url" is required
> from (No such file or directory)
> \"sys\".\"tables\"; (No such file or directory)
> Error: Failed to parse query. Syntax error in SQL statement "SELECT [*]";
> expected "TOP, LIMIT, DISTINCT, ALL, *, NOT, EXISTS, INTERSECTS"; SQL
> statement:
> select [42001-197] (state=42000,code=1001)
> java.sql.SQLException: Failed to parse query. Syntax error in SQL statement
> "SELECT [*]"; expected "TOP, LIMIT, DISTINCT, ALL, *, NOT, EXISTS,
> INTERSECTS"; SQL statement:
> select [42001-197]
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:1009)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:234)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:560)
> at sqlline.Commands.executeSingleQuery(Commands.java:1054)
> at sqlline.Commands.execute(Commands.java:1003)
> at sqlline.Commands.sql(Commands.java:967)
> at sqlline.SqlLine.dispatch(SqlLine.java:734)
> at sqlline.SqlLine.initArgs(SqlLine.java:449)
> at sqlline.SqlLine.begin(SqlLine.java:515)
> at sqlline.SqlLine.start(SqlLine.java:267)
> at sqlline.SqlLine.main(SqlLine.java:206)
> sqlline version 1.9.0{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15647) -e parameter of sqlline command does not work properly
[
https://issues.apache.org/jira/browse/IGNITE-15647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev updated IGNITE-15647:
-
Priority: Critical (was: Minor)
> -e parameter of sqlline command does not work properly
> --
>
> Key: IGNITE-15647
> URL: https://issues.apache.org/jira/browse/IGNITE-15647
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.10
> Environment: CentOS7.8.2003
>Reporter: Anton Kondratev
>Assignee: Ilya Kasnacheev
>Priority: Critical
> Fix For: 2.12
>
>
> SQL query specified in -e parameter of sqlline command does not get parsed
> properly and therefore not executed.
> I'm trying to use it like this:
> {code:java}
> ./sqlline.sh -u jdbc:ignite:thin://1.2.3.4 -n login -p password -e 'select *
> from \"sys\".\"tables\";'{code}
> and output is:
> {code:java}
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> include (Is a directory)
> Property "url" is required
> Property "url" is required
> from (No such file or directory)
> \"sys\".\"tables\"; (No such file or directory)
> Error: Failed to parse query. Syntax error in SQL statement "SELECT [*]";
> expected "TOP, LIMIT, DISTINCT, ALL, *, NOT, EXISTS, INTERSECTS"; SQL
> statement:
> select [42001-197] (state=42000,code=1001)
> java.sql.SQLException: Failed to parse query. Syntax error in SQL statement
> "SELECT [*]"; expected "TOP, LIMIT, DISTINCT, ALL, *, NOT, EXISTS,
> INTERSECTS"; SQL statement:
> select [42001-197]
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:1009)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:234)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:560)
> at sqlline.Commands.executeSingleQuery(Commands.java:1054)
> at sqlline.Commands.execute(Commands.java:1003)
> at sqlline.Commands.sql(Commands.java:967)
> at sqlline.SqlLine.dispatch(SqlLine.java:734)
> at sqlline.SqlLine.initArgs(SqlLine.java:449)
> at sqlline.SqlLine.begin(SqlLine.java:515)
> at sqlline.SqlLine.start(SqlLine.java:267)
> at sqlline.SqlLine.main(SqlLine.java:206)
> sqlline version 1.9.0{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-15647) -e parameter of sqlline command does not work properly
[
https://issues.apache.org/jira/browse/IGNITE-15647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev reassigned IGNITE-15647:
Assignee: Ilya Kasnacheev
> -e parameter of sqlline command does not work properly
> --
>
> Key: IGNITE-15647
> URL: https://issues.apache.org/jira/browse/IGNITE-15647
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.10
> Environment: CentOS7.8.2003
>Reporter: Anton Kondratev
>Assignee: Ilya Kasnacheev
>Priority: Minor
>
> SQL query specified in -e parameter of sqlline command does not get parsed
> properly and therefore not executed.
> I'm trying to use it like this:
> {code:java}
> ./sqlline.sh -u jdbc:ignite:thin://1.2.3.4 -n login -p password -e 'select *
> from \"sys\".\"tables\";'{code}
> and output is:
> {code:java}
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> include (Is a directory)
> Property "url" is required
> Property "url" is required
> from (No such file or directory)
> \"sys\".\"tables\"; (No such file or directory)
> Error: Failed to parse query. Syntax error in SQL statement "SELECT [*]";
> expected "TOP, LIMIT, DISTINCT, ALL, *, NOT, EXISTS, INTERSECTS"; SQL
> statement:
> select [42001-197] (state=42000,code=1001)
> java.sql.SQLException: Failed to parse query. Syntax error in SQL statement
> "SELECT [*]"; expected "TOP, LIMIT, DISTINCT, ALL, *, NOT, EXISTS,
> INTERSECTS"; SQL statement:
> select [42001-197]
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:1009)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:234)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:560)
> at sqlline.Commands.executeSingleQuery(Commands.java:1054)
> at sqlline.Commands.execute(Commands.java:1003)
> at sqlline.Commands.sql(Commands.java:967)
> at sqlline.SqlLine.dispatch(SqlLine.java:734)
> at sqlline.SqlLine.initArgs(SqlLine.java:449)
> at sqlline.SqlLine.begin(SqlLine.java:515)
> at sqlline.SqlLine.start(SqlLine.java:267)
> at sqlline.SqlLine.main(SqlLine.java:206)
> sqlline version 1.9.0{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15647) -e parameter of sqlline command does not work properly
[
https://issues.apache.org/jira/browse/IGNITE-15647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev updated IGNITE-15647:
-
Fix Version/s: 2.12
> -e parameter of sqlline command does not work properly
> --
>
> Key: IGNITE-15647
> URL: https://issues.apache.org/jira/browse/IGNITE-15647
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.10
> Environment: CentOS7.8.2003
>Reporter: Anton Kondratev
>Assignee: Ilya Kasnacheev
>Priority: Minor
> Fix For: 2.12
>
>
> SQL query specified in -e parameter of sqlline command does not get parsed
> properly and therefore not executed.
> I'm trying to use it like this:
> {code:java}
> ./sqlline.sh -u jdbc:ignite:thin://1.2.3.4 -n login -p password -e 'select *
> from \"sys\".\"tables\";'{code}
> and output is:
> {code:java}
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> Property "url" is required
> include (Is a directory)
> Property "url" is required
> Property "url" is required
> from (No such file or directory)
> \"sys\".\"tables\"; (No such file or directory)
> Error: Failed to parse query. Syntax error in SQL statement "SELECT [*]";
> expected "TOP, LIMIT, DISTINCT, ALL, *, NOT, EXISTS, INTERSECTS"; SQL
> statement:
> select [42001-197] (state=42000,code=1001)
> java.sql.SQLException: Failed to parse query. Syntax error in SQL statement
> "SELECT [*]"; expected "TOP, LIMIT, DISTINCT, ALL, *, NOT, EXISTS,
> INTERSECTS"; SQL statement:
> select [42001-197]
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:1009)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:234)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:560)
> at sqlline.Commands.executeSingleQuery(Commands.java:1054)
> at sqlline.Commands.execute(Commands.java:1003)
> at sqlline.Commands.sql(Commands.java:967)
> at sqlline.SqlLine.dispatch(SqlLine.java:734)
> at sqlline.SqlLine.initArgs(SqlLine.java:449)
> at sqlline.SqlLine.begin(SqlLine.java:515)
> at sqlline.SqlLine.start(SqlLine.java:267)
> at sqlline.SqlLine.main(SqlLine.java:206)
> sqlline version 1.9.0{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15388) Bump up the azure-storage-blob version
[
https://issues.apache.org/jira/browse/IGNITE-15388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17408293#comment-17408293
]
Ilya Kasnacheev commented on IGNITE-15388:
--
I'm afraid I don't have it any more.
> Bump up the azure-storage-blob version
> ---
>
> Key: IGNITE-15388
> URL: https://issues.apache.org/jira/browse/IGNITE-15388
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.11
>Reporter: Maxim Muzafarov
>Assignee: Pavel Pereslegin
>Priority: Blocker
> Fix For: 2.11
>
> Attachments: azure-storage-blob-2.13.0-deps.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The 12.0.0 azure-storage-blob is missed in the maven central repository [1].
> It's strictly recommended to update the dependency version to the 12.13.0
> version in the ignite-azure module.
>
> [https://github.com/Azure/azure-sdk-for-java/issues/23562#issuecomment-903183704]
>
> {code:java}
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 01:27 min
> [INFO] Finished at: 2021-08-25T22:40:58+03:00
> [INFO]
>
> [ERROR] Failed to execute goal on project ignite-azure: Could not
> resolve dependencies for project
> org.apache.ignite:ignite-azure:jar:2.12.0-SNAPSHOT: Failure to find
> com.azure:azure-storage-blob:jar:12.0.0 in
> https://repo.maven.apache.org/maven2 was cached in the local
> repository, resolution will not be reattempted until the update
> interval of central has elapsed or updates are forced -> [Help 1]
> {code}
> [1] [https://repo1.maven.org/maven2/com/azure/azure-storage-blob/12.0.0]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (IGNITE-15386) mvn clean compile failure
[ https://issues.apache.org/jira/browse/IGNITE-15386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev resolved IGNITE-15386. -- Resolution: Duplicate > mvn clean compile failure > - > > Key: IGNITE-15386 > URL: https://issues.apache.org/jira/browse/IGNITE-15386 > Project: Ignite > Issue Type: Bug > Components: spark >Affects Versions: 2.9.1 >Reporter: david.duan >Priority: Major > > It was failure when i use mvn command to package source code.The reason is > that pom.xml references some packages that are not in the repository -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-15387) mvn clean compile failure
[ https://issues.apache.org/jira/browse/IGNITE-15387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev resolved IGNITE-15387. -- Assignee: Ilya Kasnacheev Resolution: Invalid > mvn clean compile failure > - > > Key: IGNITE-15387 > URL: https://issues.apache.org/jira/browse/IGNITE-15387 > Project: Ignite > Issue Type: Bug > Components: spark >Affects Versions: 2.9.1 >Reporter: david.duan >Assignee: Ilya Kasnacheev >Priority: Critical > > It was failure when i use mvn command to package source code.The reason is > that pom.xml references some packages that are not in the repository -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15387) mvn clean compile failure
[ https://issues.apache.org/jira/browse/IGNITE-15387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17406307#comment-17406307 ] Ilya Kasnacheev commented on IGNITE-15387: -- You need to use older maven, since newer maven disallowed http repositories. I think it's a WONTFIX. > mvn clean compile failure > - > > Key: IGNITE-15387 > URL: https://issues.apache.org/jira/browse/IGNITE-15387 > Project: Ignite > Issue Type: Bug > Components: spark >Affects Versions: 2.9.1 >Reporter: david.duan >Priority: Critical > > It was failure when i use mvn command to package source code.The reason is > that pom.xml references some packages that are not in the repository -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-15368) s390x support to Apache Ignite TeamCity CI
[ https://issues.apache.org/jira/browse/IGNITE-15368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev reassigned IGNITE-15368: Assignee: Petr Ivanov > s390x support to Apache Ignite TeamCity CI > --- > > Key: IGNITE-15368 > URL: https://issues.apache.org/jira/browse/IGNITE-15368 > Project: Ignite > Issue Type: Wish >Affects Versions: 2.10 >Reporter: Anuja Jakhade >Assignee: Petr Ivanov >Priority: Major > > Hi, > I wanted to know details about the TeamCity CI used by Apache Ignite. > Is it possible to add s390x support to the CI? > I had raised a PR for adding s390x support in Travis. But got to know that > Travis is meant only for pull checks. > https://github.com/apache/ignite/pull/7931 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15368) s390x support to Apache Ignite TeamCity CI
[ https://issues.apache.org/jira/browse/IGNITE-15368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404402#comment-17404402 ] Ilya Kasnacheev commented on IGNITE-15368: -- [~vveider] can you please help with adding an agent? > s390x support to Apache Ignite TeamCity CI > --- > > Key: IGNITE-15368 > URL: https://issues.apache.org/jira/browse/IGNITE-15368 > Project: Ignite > Issue Type: Wish >Affects Versions: 2.10 >Reporter: Anuja Jakhade >Priority: Major > > Hi, > I wanted to know details about the TeamCity CI used by Apache Ignite. > Is it possible to add s390x support to the CI? > I had raised a PR for adding s390x support in Travis. But got to know that > Travis is meant only for pull checks. > https://github.com/apache/ignite/pull/7931 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15368) s390x support to Apache Ignite TeamCity CI
[ https://issues.apache.org/jira/browse/IGNITE-15368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404375#comment-17404375 ] Ilya Kasnacheev commented on IGNITE-15368: -- If you can donate access to s390x agent, I don't see why not. > s390x support to Apache Ignite TeamCity CI > --- > > Key: IGNITE-15368 > URL: https://issues.apache.org/jira/browse/IGNITE-15368 > Project: Ignite > Issue Type: Wish >Affects Versions: 2.10 >Reporter: Anuja Jakhade >Priority: Major > > Hi, > I wanted to know details about the TeamCity CI used by Apache Ignite. > Is it possible to add s390x support to the CI? > I had raised a PR for adding s390x support in Travis. But got to know that > Travis is meant only for pull checks. > https://issues.apache.org/jira/browse/IGNITE-15368 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-11298) TcpCommunicationSpi does not support TLSv1.3
[
https://issues.apache.org/jira/browse/IGNITE-11298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17402152#comment-17402152
]
Ilya Kasnacheev commented on IGNITE-11298:
--
But it's not my comment :) I've just posted it.
мопед не мой
> TcpCommunicationSpi does not support TLSv1.3
>
>
> Key: IGNITE-11298
> URL: https://issues.apache.org/jira/browse/IGNITE-11298
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.7
>Reporter: Ilya Kasnacheev
>Assignee: Vitaliy Biryukov
>Priority: Major
> Labels: Java11
> Fix For: 2.8
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When started on Java 11 we cannot form a secure cluster - Discovery will
> happily use the default TLSv1.3 but Communication will fail with its custom
> SSLEngine-using code.
> Need to fix that.
> Until that, nodes may be salvaged by setProtocol("TLSv1.2") on
> SslContextFactory, or by system property -Djdk.tls.client.protocols="TLSv1.2"
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-11298) TcpCommunicationSpi does not support TLSv1.3
[
https://issues.apache.org/jira/browse/IGNITE-11298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17401824#comment-17401824
]
Ilya Kasnacheev commented on IGNITE-11298:
--
I'm not the one who fixed it so no. But you can probably check out the commit.
> TcpCommunicationSpi does not support TLSv1.3
>
>
> Key: IGNITE-11298
> URL: https://issues.apache.org/jira/browse/IGNITE-11298
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.7
>Reporter: Ilya Kasnacheev
>Assignee: Vitaliy Biryukov
>Priority: Major
> Labels: Java11
> Fix For: 2.8
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When started on Java 11 we cannot form a secure cluster - Discovery will
> happily use the default TLSv1.3 but Communication will fail with its custom
> SSLEngine-using code.
> Need to fix that.
> Until that, nodes may be salvaged by setProtocol("TLSv1.2") on
> SslContextFactory, or by system property -Djdk.tls.client.protocols="TLSv1.2"
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12749) Unsupported operation exception on node stop if collisionspi not null
[
https://issues.apache.org/jira/browse/IGNITE-12749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17379185#comment-17379185
]
Ilya Kasnacheev commented on IGNITE-12749:
--
I don't think we need to define clear() for map, it should be recreated
Why is this still a problem [~antkr]?
> Unsupported operation exception on node stop if collisionspi not null
> -
>
> Key: IGNITE-12749
> URL: https://issues.apache.org/jira/browse/IGNITE-12749
> Project: Ignite
> Issue Type: Bug
>Reporter: Nikolay Izhikov
>Assignee: Yaroslav Molochkov
>Priority: Major
> Labels: newbie
> Time Spent: 50m
> Remaining Estimate: 0h
>
> If collision spi specified then on the node stop there are exception:
> {noformat}
> java.lang.UnsupportedOperationException
> at
> org.jsr166.ConcurrentLinkedHashMap.clear(ConcurrentLinkedHashMap.java:1542)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor.stop(GridJobProcessor.java:376)
> at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2697)
> at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2569)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2660)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2623)
> at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:339)
> at org.apache.ignite.Ignition.stop(Ignition.java:223)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:1316)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.stopAllGrids(GridAbstractTest.java:1361)
> {noformat}
> The issue in the next line:
> {code:java}
> public GridJobProcessor(GridKernalContext ctx) {
> // Collision manager is already started and is fully functional.
> jobAlwaysActivate = !ctx.collision().enabled();
> activeJobs = jobAlwaysActivate ? new ConcurrentHashMap GridJobWorker>() :
> new JobsMap(1024, 0.75f, 256);
> {code}
> We need replace JobsMap with the correct implementation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12401) Some Text Queries return repeated results
[ https://issues.apache.org/jira/browse/IGNITE-12401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17370634#comment-17370634 ] Ilya Kasnacheev commented on IGNITE-12401: -- Unfortunately, I'm not sure since I don't know rebalance process in-depth. Maybe [~Pavlukhin] can help? > Some Text Queries return repeated results > - > > Key: IGNITE-12401 > URL: https://issues.apache.org/jira/browse/IGNITE-12401 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.8 >Reporter: Ilya Kasnacheev >Assignee: Yuriy Shuliha >Priority: Critical > Time Spent: 10m > Remaining Estimate: 0h > > It came to my attention while checking for Range Queries support that we > don't actually check that found query results are the correct ones. > We were checking that we got some results, but not whether they were expected. > And voila, it turns out that Range Queries examples, as well as some other > test cases, will readily fail when run with such checks! A query will return > same value repeatedly, e.g. range query will return the "1" record twice, and > limited text query will return "14" record twice. > It didn't really occur on non-range queries before the introduction of limits. > I think we should not ship broken limit queries. Maybe also fix range > queries, if it's hard let's @Ignore them for now. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12911) B+Tree Corrupted exception when using a key extracted from a BinaryObject value object --- and SQL enabled.
[
https://issues.apache.org/jira/browse/IGNITE-12911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17369470#comment-17369470
]
Ilya Kasnacheev commented on IGNITE-12911:
--
LGTM now, please merge [~sergeychugunov]
> B+Tree Corrupted exception when using a key extracted from a BinaryObject
> value object --- and SQL enabled.
> ---
>
> Key: IGNITE-12911
> URL: https://issues.apache.org/jira/browse/IGNITE-12911
> Project: Ignite
> Issue Type: Bug
> Components: cache, sql
>Reporter: Alexander Korenshteyn
>Assignee: Sergey Chugunov
>Priority: Blocker
> Attachments: Employee.java, EmployeeId.java, ServerNode.java,
> image-2020-04-21-17-10-55-797.png, image-2020-04-21-17-11-31-242.png,
> image-2020-04-21-17-16-10-703.png, image-2020-04-21-17-16-29-107.png,
> image-2020-04-21-17-16-46-381.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If a key is part of the value like so:
> class key \{ ... }
> class value
> { private Key key getKey() }
> cache = ignite.cache()*.withKeepBinary()*
> the following scenario yields a B+ Tree exception:
> 1. *Enable SQL via annotations or QueryEntities.*
> key1= new Key()
> value1 = new Value(key1)
> cache.put(key1, value1)
> BinaryObject val2 = cache.get(key1)
> BinaryObject key2 = val2.field("key")
>
> *cache2.put(key2.toBuilder().build(), emp1); // OK!*
>
> *cache.put(key2, emp1); // CRASH!!! CorruptedTreeException: B+Tree
> iscorrupted ...*
> user list:
>
> [http://apache-ignite-users.70518.x6.nabble.com/Ignite-crashes-with-CorruptedTreeException-quot-B-Tree-is-corrupted-quot-on-a-composite-BinaryObjecto-tc32032.html]
> *Reproducer – attached*
>
> his happens because:
> CacheRowAdapter.readFullRow() reads the length
> *int len = PageUtils.getInt(addr,off)*
> *it returns 0 when val2.field("key") is used*
>
> *the data is written correctly in DataPageIO.writeDataPageIO():*
> !image-2020-04-21-17-16-46-381.png!
>
> *but read incorrectly in CacheRowAdapter.readFullRow()*
> !image-2020-04-21-17-16-29-107.png!
>
>
> Exception:
> [2020-04-17 11:24:33,475][ERROR][main][root] Critical system error detected.
> Will be handled accordingly to configured handler
> [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
> super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
> [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
> failureCtx=FailureContext [type=CRITICAL_ERROR, err=class
> o.a.i.i.processors.cache.persistence.tree.CorruptedTreeException: B+Tree is
> corrupted [pages(groupId, pageId)=[IgniteBiTuple [val1=1258113742,
> val2=844420635164673]], cacheId=1976096430, cacheName=EMPLOYEE,
> indexName=_key_PK, msg=Runtime failure on row: Row@2233cac0[ key:
> model.EmployeeId [idHash=1744523301, hash=674030145, employeeNumber=65348765,
> departmentNumber=123], val: model.Employee [idHash=382762227,
> hash=1627745429, firstName=John, lastName=Smith, id=model.EmployeeId
> [idHash=2021540695, hash=674030145, employeeNumber=65348765,
> departmentNumber=123]] ][ John, Smith
> class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> B+Tree is corrupted [pages(groupId, pageId)=[IgniteBiTuple [val1=1258113742,
> val2=844420635164673]], cacheId=1976096430, cacheName=EMPLOYEE,
> indexName=_key_PK, msg=Runtime failure on row: Row@2233cac0[ key:
> model.EmployeeId [idHash=1744523301, hash=674030145, employeeNumber=65348765,
> departmentNumber=123], val: model.Employee [idHash=382762227,
> hash=1627745429, firstName=John, lastName=Smith, id=model.EmployeeId
> [idHash=2021540695, hash=674030145, employeeNumber=65348765,
> departmentNumber=123]] ][ John, Smith ]]
> at
> org.apache.ignite.internal.processors.query.h2.database.H2Tree.corruptedTreeException(H2Tree.java:836)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2447)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putx(BPlusTree.java:2394)
> at
> org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.putx(H2TreeIndex.java:437)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.update(GridH2Table.java:756)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.store(IgniteH2Indexing.java:363)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.store(GridQueryProcessor.java:2016)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.store(GridCacheQueryManager.java:401)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishUpdate(IgniteCacheOffheapManagerImpl.java:2555)
> at
>
[jira] [Updated] (IGNITE-14753) Build via maven 3.8.1 fails
[ https://issues.apache.org/jira/browse/IGNITE-14753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-14753: - Ignite Flags: (was: Release Notes Required) > Build via maven 3.8.1 fails > > > Key: IGNITE-14753 > URL: https://issues.apache.org/jira/browse/IGNITE-14753 > Project: Ignite > Issue Type: Improvement > Components: general >Reporter: Ilya Korol >Assignee: Stanislav Lukyanov >Priority: Major > Labels: build > Fix For: 2.12 > > Time Spent: 1.5h > Remaining Estimate: 0h > > Building ignite with latest maven (3.8.1) fails due to http blocking policy. > https://maven.apache.org/docs/3.8.1/release-notes.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14753) Build via maven 3.8.1 fails
[ https://issues.apache.org/jira/browse/IGNITE-14753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-14753: - Labels: build (was: ) > Build via maven 3.8.1 fails > > > Key: IGNITE-14753 > URL: https://issues.apache.org/jira/browse/IGNITE-14753 > Project: Ignite > Issue Type: Improvement > Components: general >Reporter: Ilya Korol >Assignee: Stanislav Lukyanov >Priority: Major > Labels: build > Fix For: 2.12 > > Time Spent: 1.5h > Remaining Estimate: 0h > > Building ignite with latest maven (3.8.1) fails due to http blocking policy. > https://maven.apache.org/docs/3.8.1/release-notes.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12401) Some Text Queries return repeated results
[ https://issues.apache.org/jira/browse/IGNITE-12401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17367151#comment-17367151 ] Ilya Kasnacheev commented on IGNITE-12401: -- I don't think that we have fixed it. > Some Text Queries return repeated results > - > > Key: IGNITE-12401 > URL: https://issues.apache.org/jira/browse/IGNITE-12401 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.8 >Reporter: Ilya Kasnacheev >Assignee: Yuriy Shuliha >Priority: Critical > Time Spent: 10m > Remaining Estimate: 0h > > It came to my attention while checking for Range Queries support that we > don't actually check that found query results are the correct ones. > We were checking that we got some results, but not whether they were expected. > And voila, it turns out that Range Queries examples, as well as some other > test cases, will readily fail when run with such checks! A query will return > same value repeatedly, e.g. range query will return the "1" record twice, and > limited text query will return "14" record twice. > It didn't really occur on non-range queries before the introduction of limits. > I think we should not ship broken limit queries. Maybe also fix range > queries, if it's hard let's @Ignore them for now. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14856) "Failed to resolve class name" on server when cache with indexed types is defined on client
[
https://issues.apache.org/jira/browse/IGNITE-14856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17360880#comment-17360880
]
Ilya Kasnacheev commented on IGNITE-14856:
--
Java side LGTM; I have left just one small code conventions comment.
> "Failed to resolve class name" on server when cache with indexed types is
> defined on client
> ---
>
> Key: IGNITE-14856
> URL: https://issues.apache.org/jira/browse/IGNITE-14856
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Affects Versions: 2.10, 2.11
>Reporter: Ilya Kasnacheev
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Fix For: 2.11
>
> Attachments: IgniteMarshallerCacheSeparateDirectoryTest.java
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Please see attached reproducer test (
> org.apache.ignite.internal.processors.cache.IgniteMarshallerCacheSeparateDirectoryTest#testClientCcfgIndexedGetClosure)
> If an indexed types cache is defined on client node's configuration but not
> server, client may put values into cache but server cannot read them despite
> having class on its classpath:
> {code}
> [2021-06-09 16:00:33,611][ERROR][pub-#229%client%][GridJobWorker] Failed to
> execute job [jobId=7992cd0f971-749bd94c-cbeb-460d-a0d9-cba5d7a37739,
> ses=GridJobSessionImpl [ses=GridTaskSessionImpl
> [taskName=o.a.i.i.processors.cache.IgniteMarshallerCacheSeparateDirectoryTest$2,
> dep=LocalDeployment [super=GridDeployment [ts=1623243633290, depMode=SHARED,
> clsLdr=sun.misc.Launcher$AppClassLoader18b4aac2,
> clsLdrId=8092cd0f971-749bd94c-cbeb-460d-a0d9-cba5d7a37739, userVer=0,
> loc=true, sampleClsName=java.lang.String, pendingUndeploy=false,
> undeployed=false, usage=0]],
> taskClsName=o.a.i.i.processors.cache.IgniteMarshallerCacheSeparateDirectoryTest$2,
> sesId=6992cd0f971-749bd94c-cbeb-460d-a0d9-cba5d7a37739,
> startTime=1623243633569, endTime=9223372036854775807,
> taskNodeId=749bd94c-cbeb-460d-a0d9-cba5d7a37739,
> clsLdr=sun.misc.Launcher$AppClassLoader18b4aac2, closed=false,
> cpSpi=null, failSpi=null, loadSpi=null, usage=1, fullSup=false,
> internal=false, topPred=null, subjId=749bd94c-cbeb-460d-a0d9-cba5d7a37739,
> mapFut=IgniteFuture [orig=GridFutureAdapter [ignoreInterrupts=false,
> state=INIT, res=null, hash=1341412812]], execName=null],
> jobId=7992cd0f971-749bd94c-cbeb-460d-a0d9-cba5d7a37739]]
> class org.apache.ignite.IgniteException: class
> org.apache.ignite.IgniteCheckedException: Failed to resolve class name
> [platformId=0, platform=Java, typeId=1438082999]
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.execute(GridClosureProcessor.java:1849)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:590)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:7181)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:584)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:511)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: javax.cache.CacheException: class
> org.apache.ignite.IgniteCheckedException: Failed to resolve class name
> [platformId=0, platform=Java, typeId=1438082999]
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1265)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:2078)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.get(IgniteCacheProxyImpl.java:1105)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.get(GatewayProtectedCacheProxy.java:637)
> at
> org.apache.ignite.internal.processors.cache.IgniteMarshallerCacheSeparateDirectoryTest$2.call(IgniteMarshallerCacheSeparateDirectoryTest.java:188)
> at
> org.apache.ignite.internal.processors.cache.IgniteMarshallerCacheSeparateDirectoryTest$2.call(IgniteMarshallerCacheSeparateDirectoryTest.java:185)
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.execute(GridClosureProcessor.java:1846)
> ... 8 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to resolve
> class name [platformId=0, platform=Java, typeId=1438082999]
> at
>
[jira] [Comment Edited] (IGNITE-12911) B+Tree Corrupted exception when using a key extracted from a BinaryObject value object --- and SQL enabled.
[
https://issues.apache.org/jira/browse/IGNITE-12911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17351125#comment-17351125
]
Ilya Kasnacheev edited comment on IGNITE-12911 at 6/9/21, 3:01 PM:
---
Looks OK if you are going to mark the subKey case as known issue. Just move the
test to a different suite.
was (Author: ilyak):
Looks OK if you are going to mark the subKey case as known issue. Just move the
test to a different site.
> B+Tree Corrupted exception when using a key extracted from a BinaryObject
> value object --- and SQL enabled.
> ---
>
> Key: IGNITE-12911
> URL: https://issues.apache.org/jira/browse/IGNITE-12911
> Project: Ignite
> Issue Type: Bug
> Components: cache, sql
>Reporter: Alexander Korenshteyn
>Assignee: Sergey Chugunov
>Priority: Blocker
> Attachments: Employee.java, EmployeeId.java, ServerNode.java,
> image-2020-04-21-17-10-55-797.png, image-2020-04-21-17-11-31-242.png,
> image-2020-04-21-17-16-10-703.png, image-2020-04-21-17-16-29-107.png,
> image-2020-04-21-17-16-46-381.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If a key is part of the value like so:
> class key \{ ... }
> class value
> { private Key key getKey() }
> cache = ignite.cache()*.withKeepBinary()*
> the following scenario yields a B+ Tree exception:
> 1. *Enable SQL via annotations or QueryEntities.*
> key1= new Key()
> value1 = new Value(key1)
> cache.put(key1, value1)
> BinaryObject val2 = cache.get(key1)
> BinaryObject key2 = val2.field("key")
>
> *cache2.put(key2.toBuilder().build(), emp1); // OK!*
>
> *cache.put(key2, emp1); // CRASH!!! CorruptedTreeException: B+Tree
> iscorrupted ...*
> user list:
>
> [http://apache-ignite-users.70518.x6.nabble.com/Ignite-crashes-with-CorruptedTreeException-quot-B-Tree-is-corrupted-quot-on-a-composite-BinaryObjecto-tc32032.html]
> *Reproducer – attached*
>
> his happens because:
> CacheRowAdapter.readFullRow() reads the length
> *int len = PageUtils.getInt(addr,off)*
> *it returns 0 when val2.field("key") is used*
>
> *the data is written correctly in DataPageIO.writeDataPageIO():*
> !image-2020-04-21-17-16-46-381.png!
>
> *but read incorrectly in CacheRowAdapter.readFullRow()*
> !image-2020-04-21-17-16-29-107.png!
>
>
> Exception:
> [2020-04-17 11:24:33,475][ERROR][main][root] Critical system error detected.
> Will be handled accordingly to configured handler
> [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
> super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
> [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
> failureCtx=FailureContext [type=CRITICAL_ERROR, err=class
> o.a.i.i.processors.cache.persistence.tree.CorruptedTreeException: B+Tree is
> corrupted [pages(groupId, pageId)=[IgniteBiTuple [val1=1258113742,
> val2=844420635164673]], cacheId=1976096430, cacheName=EMPLOYEE,
> indexName=_key_PK, msg=Runtime failure on row: Row@2233cac0[ key:
> model.EmployeeId [idHash=1744523301, hash=674030145, employeeNumber=65348765,
> departmentNumber=123], val: model.Employee [idHash=382762227,
> hash=1627745429, firstName=John, lastName=Smith, id=model.EmployeeId
> [idHash=2021540695, hash=674030145, employeeNumber=65348765,
> departmentNumber=123]] ][ John, Smith
> class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> B+Tree is corrupted [pages(groupId, pageId)=[IgniteBiTuple [val1=1258113742,
> val2=844420635164673]], cacheId=1976096430, cacheName=EMPLOYEE,
> indexName=_key_PK, msg=Runtime failure on row: Row@2233cac0[ key:
> model.EmployeeId [idHash=1744523301, hash=674030145, employeeNumber=65348765,
> departmentNumber=123], val: model.Employee [idHash=382762227,
> hash=1627745429, firstName=John, lastName=Smith, id=model.EmployeeId
> [idHash=2021540695, hash=674030145, employeeNumber=65348765,
> departmentNumber=123]] ][ John, Smith ]]
> at
> org.apache.ignite.internal.processors.query.h2.database.H2Tree.corruptedTreeException(H2Tree.java:836)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2447)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putx(BPlusTree.java:2394)
> at
> org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.putx(H2TreeIndex.java:437)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.update(GridH2Table.java:756)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.store(IgniteH2Indexing.java:363)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.store(GridQueryProcessor.java:2016)
> at
>
[jira] [Commented] (IGNITE-14781) Ignite examples from binary package fail to build due to ClientKubernetesPutGetExample
[
https://issues.apache.org/jira/browse/IGNITE-14781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17351167#comment-17351167
]
Ilya Kasnacheev commented on IGNITE-14781:
--
This is because IGNITE-13796 has added this class but did not add its
dependencies into pom-standalone file.
> Ignite examples from binary package fail to build due to
> ClientKubernetesPutGetExample
> --
>
> Key: IGNITE-14781
> URL: https://issues.apache.org/jira/browse/IGNITE-14781
> Project: Ignite
> Issue Type: Bug
> Components: examples
>Affects Versions: 2.10
>Reporter: Ilya Kasnacheev
>Priority: Blocker
> Fix For: 2.11
>
>
> {code}
> ~/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples% mvn clean install
> [INFO]
> [INFO] -< org.apache.ignite:ignite-examples
> >--
> [INFO] Building ignite-examples 2.11.0-SNAPSHOT
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ ignite-examples ---
> [INFO]
> [INFO] --- build-helper-maven-plugin:3.2.0:add-source (add-sources) @
> ignite-examples ---
> [INFO] Source directory:
> /home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java
> added.
> [INFO] Source directory:
> /home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java
> added.
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @
> ignite-examples ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 2 resources
> [INFO] Copying 14 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @
> ignite-examples ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 266 source files to
> /home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/target/classes
> [INFO] -
> [WARNING] COMPILATION WARNING :
> [INFO] -
> [WARNING]
> /home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/datagrid/CacheAsyncApiExample.java:
> Some input files use or override a deprecated API.
> [WARNING]
> /home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/datagrid/CacheAsyncApiExample.java:
> Recompile with -Xlint:deprecation for details.
> [WARNING]
> /home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/datagrid/store/CacheLoadOnlyStoreExample.java:
> Some input files use unchecked or unsafe operations.
> [WARNING]
> /home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/datagrid/store/CacheLoadOnlyStoreExample.java:
> Recompile with -Xlint:unchecked for details.
> [INFO] 4 warnings
> [INFO] -
> [INFO] -
> [ERROR] COMPILATION ERROR :
> [INFO] -
> [ERROR]
> /home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/client/ClientKubernetesPutGetExample.java:[23,32]
> cannot find symbol
> symbol: class ThinClientKubernetesAddressFinder
> location: package org.apache.ignite.client
> [ERROR]
> /home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/client/ClientKubernetesPutGetExample.java:[26,50]
> package org.apache.ignite.kubernetes.configuration does not exist
> [ERROR]
> /home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/client/ClientKubernetesPutGetExample.java:[42,9]
> cannot find symbol
> symbol: class KubernetesConnectionConfiguration
> location: class
> org.apache.ignite.examples.client.ClientKubernetesPutGetExample
> [ERROR]
> /home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/client/ClientKubernetesPutGetExample.java:[42,54]
> cannot find symbol
> symbol: class KubernetesConnectionConfiguration
> location: class
> org.apache.ignite.examples.client.ClientKubernetesPutGetExample
> [ERROR]
> /home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/client/ClientKubernetesPutGetExample.java:[46,36]
> cannot find symbol
> symbol: class ThinClientKubernetesAddressFinder
> location: class
>
[jira] [Created] (IGNITE-14781) Ignite examples from binary package fail to build due to ClientKubernetesPutGetExample
Ilya Kasnacheev created IGNITE-14781:
Summary: Ignite examples from binary package fail to build due to
ClientKubernetesPutGetExample
Key: IGNITE-14781
URL: https://issues.apache.org/jira/browse/IGNITE-14781
Project: Ignite
Issue Type: Bug
Components: examples
Affects Versions: 2.10
Reporter: Ilya Kasnacheev
Fix For: 2.11
{code}
~/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples% mvn clean install
[INFO]
[INFO] -< org.apache.ignite:ignite-examples >--
[INFO] Building ignite-examples 2.11.0-SNAPSHOT
[INFO] [ jar ]-
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ ignite-examples ---
[INFO]
[INFO] --- build-helper-maven-plugin:3.2.0:add-source (add-sources) @
ignite-examples ---
[INFO] Source directory:
/home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java
added.
[INFO] Source directory:
/home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java
added.
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @
ignite-examples ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] Copying 14 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @
ignite-examples ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 266 source files to
/home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/target/classes
[INFO] -
[WARNING] COMPILATION WARNING :
[INFO] -
[WARNING]
/home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/datagrid/CacheAsyncApiExample.java:
Some input files use or override a deprecated API.
[WARNING]
/home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/datagrid/CacheAsyncApiExample.java:
Recompile with -Xlint:deprecation for details.
[WARNING]
/home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/datagrid/store/CacheLoadOnlyStoreExample.java:
Some input files use unchecked or unsafe operations.
[WARNING]
/home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/datagrid/store/CacheLoadOnlyStoreExample.java:
Recompile with -Xlint:unchecked for details.
[INFO] 4 warnings
[INFO] -
[INFO] -
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR]
/home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/client/ClientKubernetesPutGetExample.java:[23,32]
cannot find symbol
symbol: class ThinClientKubernetesAddressFinder
location: package org.apache.ignite.client
[ERROR]
/home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/client/ClientKubernetesPutGetExample.java:[26,50]
package org.apache.ignite.kubernetes.configuration does not exist
[ERROR]
/home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/client/ClientKubernetesPutGetExample.java:[42,9]
cannot find symbol
symbol: class KubernetesConnectionConfiguration
location: class
org.apache.ignite.examples.client.ClientKubernetesPutGetExample
[ERROR]
/home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/client/ClientKubernetesPutGetExample.java:[42,54]
cannot find symbol
symbol: class KubernetesConnectionConfiguration
location: class
org.apache.ignite.examples.client.ClientKubernetesPutGetExample
[ERROR]
/home/ikasnacheev/Downloads/apache-ignite-2.11.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/client/ClientKubernetesPutGetExample.java:[46,36]
cannot find symbol
symbol: class ThinClientKubernetesAddressFinder
location: class
org.apache.ignite.examples.client.ClientKubernetesPutGetExample
[INFO] 5 errors
[INFO] -
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 4.852 s
[INFO] Finished at: 2021-05-25T18:57:12+03:00
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on
[jira] [Commented] (IGNITE-12911) B+Tree Corrupted exception when using a key extracted from a BinaryObject value object --- and SQL enabled.
[
https://issues.apache.org/jira/browse/IGNITE-12911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17351125#comment-17351125
]
Ilya Kasnacheev commented on IGNITE-12911:
--
Looks OK if you are going to mark the subKey case as known issue. Just move the
test to a different site.
> B+Tree Corrupted exception when using a key extracted from a BinaryObject
> value object --- and SQL enabled.
> ---
>
> Key: IGNITE-12911
> URL: https://issues.apache.org/jira/browse/IGNITE-12911
> Project: Ignite
> Issue Type: Bug
> Components: cache, sql
>Reporter: Alexander Korenshteyn
>Assignee: Sergey Chugunov
>Priority: Blocker
> Attachments: Employee.java, EmployeeId.java, ServerNode.java,
> image-2020-04-21-17-10-55-797.png, image-2020-04-21-17-11-31-242.png,
> image-2020-04-21-17-16-10-703.png, image-2020-04-21-17-16-29-107.png,
> image-2020-04-21-17-16-46-381.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If a key is part of the value like so:
> class key \{ ... }
> class value
> { private Key key getKey() }
> cache = ignite.cache()*.withKeepBinary()*
> the following scenario yields a B+ Tree exception:
> 1. *Enable SQL via annotations or QueryEntities.*
> key1= new Key()
> value1 = new Value(key1)
> cache.put(key1, value1)
> BinaryObject val2 = cache.get(key1)
> BinaryObject key2 = val2.field("key")
>
> *cache2.put(key2.toBuilder().build(), emp1); // OK!*
>
> *cache.put(key2, emp1); // CRASH!!! CorruptedTreeException: B+Tree
> iscorrupted ...*
> user list:
>
> [http://apache-ignite-users.70518.x6.nabble.com/Ignite-crashes-with-CorruptedTreeException-quot-B-Tree-is-corrupted-quot-on-a-composite-BinaryObjecto-tc32032.html]
> *Reproducer – attached*
>
> his happens because:
> CacheRowAdapter.readFullRow() reads the length
> *int len = PageUtils.getInt(addr,off)*
> *it returns 0 when val2.field("key") is used*
>
> *the data is written correctly in DataPageIO.writeDataPageIO():*
> !image-2020-04-21-17-16-46-381.png!
>
> *but read incorrectly in CacheRowAdapter.readFullRow()*
> !image-2020-04-21-17-16-29-107.png!
>
>
> Exception:
> [2020-04-17 11:24:33,475][ERROR][main][root] Critical system error detected.
> Will be handled accordingly to configured handler
> [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
> super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
> [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
> failureCtx=FailureContext [type=CRITICAL_ERROR, err=class
> o.a.i.i.processors.cache.persistence.tree.CorruptedTreeException: B+Tree is
> corrupted [pages(groupId, pageId)=[IgniteBiTuple [val1=1258113742,
> val2=844420635164673]], cacheId=1976096430, cacheName=EMPLOYEE,
> indexName=_key_PK, msg=Runtime failure on row: Row@2233cac0[ key:
> model.EmployeeId [idHash=1744523301, hash=674030145, employeeNumber=65348765,
> departmentNumber=123], val: model.Employee [idHash=382762227,
> hash=1627745429, firstName=John, lastName=Smith, id=model.EmployeeId
> [idHash=2021540695, hash=674030145, employeeNumber=65348765,
> departmentNumber=123]] ][ John, Smith
> class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> B+Tree is corrupted [pages(groupId, pageId)=[IgniteBiTuple [val1=1258113742,
> val2=844420635164673]], cacheId=1976096430, cacheName=EMPLOYEE,
> indexName=_key_PK, msg=Runtime failure on row: Row@2233cac0[ key:
> model.EmployeeId [idHash=1744523301, hash=674030145, employeeNumber=65348765,
> departmentNumber=123], val: model.Employee [idHash=382762227,
> hash=1627745429, firstName=John, lastName=Smith, id=model.EmployeeId
> [idHash=2021540695, hash=674030145, employeeNumber=65348765,
> departmentNumber=123]] ][ John, Smith ]]
> at
> org.apache.ignite.internal.processors.query.h2.database.H2Tree.corruptedTreeException(H2Tree.java:836)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2447)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putx(BPlusTree.java:2394)
> at
> org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.putx(H2TreeIndex.java:437)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.update(GridH2Table.java:756)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.store(IgniteH2Indexing.java:363)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.store(GridQueryProcessor.java:2016)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.store(GridCacheQueryManager.java:401)
> at
>
[jira] [Resolved] (IGNITE-14761) "Page locks dump" messages print lots of newlines, no page locks
[ https://issues.apache.org/jira/browse/IGNITE-14761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev resolved IGNITE-14761. -- Resolution: Invalid Does not seem to be the case in master. > "Page locks dump" messages print lots of newlines, no page locks > > > Key: IGNITE-14761 > URL: https://issues.apache.org/jira/browse/IGNITE-14761 > Project: Ignite > Issue Type: Bug > Components: persistence >Affects Versions: 2.10 >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Major > Labels: easyfix > > I can see the following message in the log: > [CacheDiagnosticManager] Page locks dump: > and then 1134 newlines. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14761) "Page locks dump" messages print lots of newlines, no page locks
Ilya Kasnacheev created IGNITE-14761: Summary: "Page locks dump" messages print lots of newlines, no page locks Key: IGNITE-14761 URL: https://issues.apache.org/jira/browse/IGNITE-14761 Project: Ignite Issue Type: Bug Components: persistence Affects Versions: 2.10 Reporter: Ilya Kasnacheev Assignee: Ilya Kasnacheev I can see the following message in the log: [CacheDiagnosticManager] Page locks dump: and then 1134 newlines. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12885) Checkpoint thread executes partitions fsync in single thread
[ https://issues.apache.org/jira/browse/IGNITE-12885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev reassigned IGNITE-12885: Assignee: Ilya Kasnacheev (was: Ivan Bessonov) > Checkpoint thread executes partitions fsync in single thread > > > Key: IGNITE-12885 > URL: https://issues.apache.org/jira/browse/IGNITE-12885 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Bessonov >Assignee: Ilya Kasnacheev >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > It should use "asyncRunner" if it was configured, this will optimize > checkpoint speed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14720) Remove warning about disabling explicit GC
[
https://issues.apache.org/jira/browse/IGNITE-14720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev updated IGNITE-14720:
-
Ignite Flags: Docs Required (was: Docs Required,Release Notes Required)
> Remove warning about disabling explicit GC
> --
>
> Key: IGNITE-14720
> URL: https://issues.apache.org/jira/browse/IGNITE-14720
> Project: Ignite
> Issue Type: Improvement
>Reporter: Vladimir Pligin
>Assignee: Ilya
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Right now we suggest the following
> {code:java}
> INFO: ^-- Disable processing of calls to System.gc() (add
> '-XX:+DisableExplicitGC' to JVM options){code}
> It does not make sense anymore (people don't call gc() when not needed) and
> may actually prevent JVM from reclaiming heap and the failing due to running
> out of direct memory buffers.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14731) .NET node may occasionally catch SIGSEGV in managed code
Ilya Kasnacheev created IGNITE-14731:
Summary: .NET node may occasionally catch SIGSEGV in managed code
Key: IGNITE-14731
URL: https://issues.apache.org/jira/browse/IGNITE-14731
Project: Ignite
Issue Type: Bug
Components: platforms
Reporter: Ilya Kasnacheev
{code}
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `dotnet exec
/home/ikasnacheev/14733/bin/Debug/netcoreapp2.0/14733.dll 12'.
Program terminated with signal 11, Segmentation fault.
#0 0x7f971c2cc7b9 in CONTEXTFromNativeContext () from
/usr/share/dotnet/shared/Microsoft.NETCore.App/2.0.5/libclrjit.so
Missing separate debuginfos, use: debuginfo-install dotnet-host-5.0.5-1.x86_64
(gdb) bt
#0 0x7f971c2cc7b9 in CONTEXTFromNativeContext () from
/usr/share/dotnet/shared/Microsoft.NETCore.App/2.0.5/libclrjit.so
#1 0x7f971c2a1de8 in common_signal_handler(int, siginfo_t*, void*, int,
...) () from /usr/share/dotnet/shared/Microsoft.NETCore.App/2.0.5/libclrjit.so
#2 0x7f971c2a1c16 in signal_handler_worker () from
/usr/share/dotnet/shared/Microsoft.NETCore.App/2.0.5/libclrjit.so
#3 0x7f971c2de7ce in CallSignalHandlerWrapper0 () from
/usr/share/dotnet/shared/Microsoft.NETCore.App/2.0.5/libclrjit.so
#4 0x7f96a6a1291d in ?? ()
#5 0x7f9410a56fd0 in ?? ()
#6 0x7f92ef5611e8 in ?? ()
#7 0x000a in ?? ()
#8 0x7f95d420c0e0 in ?? ()
#9 0x7f9410a57030 in ?? ()
#10 0x7f96a69f6cb6 in ?? ()
#11 0x7f9410a57000 in ?? ()
#12 0x7f96800256c0 in ?? ()
#13 0x in ?? ()
{code}
Please note that it happens once a few days on three node setup. Maybe if will
happen more often if null dereference is simulated explicitly.
COMPlus_EnableAlternateStackCheck=1 is set.
.NET Core SDK (3.1.408), Linux.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14490) cache.invoke() triggers failure handler and freezes if entry processor is not urideployed
[ https://issues.apache.org/jira/browse/IGNITE-14490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-14490: - Fix Version/s: 2.11 > cache.invoke() triggers failure handler and freezes if entry processor is not > urideployed > - > > Key: IGNITE-14490 > URL: https://issues.apache.org/jira/browse/IGNITE-14490 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.10 >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Major > Fix For: 2.11 > > Attachments: LoclerMain.java > > Time Spent: 10m > Remaining Estimate: 0h > > If URI deployment is specified > Caused by: java.lang.ClassNotFoundException: [Ljava.lang.StackTraceElement;" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (IGNITE-14490) cache.invoke() triggers failure handler and freezes if entry processor is not urideployed
[
https://issues.apache.org/jira/browse/IGNITE-14490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev updated IGNITE-14490:
-
Comment: was deleted
(was: {panel:title=Branch: [pull/8976/head] Base: [master] : Possible Blockers
(8)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}JDBC Driver{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6001609]]
{color:#d04437}RDD{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=6001611]]
{color:#d04437}Cache 9{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6001650]]
* IgniteCacheTestSuite9:
TxPartitionCounterStateConsistencyVolatileRebalanceTest.testPartitionConsistencyDuringRebalanceAndConcurrentUpdates_TxDuringPME
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6001623]]
* ZookeeperDiscoverySpiTestSuite1:
ZookeeperDiscoveryCommunicationFailureTest.testCommunicationFailureResolve_ConcurrentMultinode
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Cache 5{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=6001646]]
* IgniteCacheTestSuite5:
CacheSerializableTransactionsTest.testTxConflictReadEntry1 - Test has low fail
rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite5: IgniteCacheAtomicProtocolTest.testFullAsyncPutRemap -
Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}PDS (Indexing){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6001655]]
* IgnitePdsWithIndexingCoreTestSuite:
IgniteLogicalRecoveryWithParamsTest.testPartiallyCommitedTx_TwoNode_WithoutCpOnNodeStop_SingleNodeTx[nodesCnt=2,
singleNodeTx=true, backups=0] - Test has low fail rate in base branch 0,0% and
is not flaky
{color:#d04437}Cache 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6001642]]
* IgniteBinaryCacheTestSuite:
GridCacheStopSelfTest.testStopImplicitMvccTransactionsReplicated - Test has low
fail rate in base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/8976/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}SPI (URI Deploy){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6001617]]
* {color:#013220}IgniteUriDeploymentTestSuite:
UriDeploymentAbsentProcessorClassTest.test - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6001688buildTypeId=IgniteTests24Java8_RunAll])
> cache.invoke() triggers failure handler and freezes if entry processor is not
> urideployed
> -
>
> Key: IGNITE-14490
> URL: https://issues.apache.org/jira/browse/IGNITE-14490
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.10
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
> Attachments: LoclerMain.java
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If URI deployment is specified
> Caused by: java.lang.ClassNotFoundException: [Ljava.lang.StackTraceElement;"
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14711) Client discovery thread interrupt/stop causes endless communication reconnect attempt
[ https://issues.apache.org/jira/browse/IGNITE-14711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-14711: - Attachment: IgniteDiscoveryThreadKillingTest.java > Client discovery thread interrupt/stop causes endless communication reconnect > attempt > - > > Key: IGNITE-14711 > URL: https://issues.apache.org/jira/browse/IGNITE-14711 > Project: Ignite > Issue Type: Bug > Components: networking >Affects Versions: 2.10 >Reporter: Ilya Kasnacheev >Priority: Major > Attachments: IgniteDiscoveryThreadKillingTest.java > > > Original issue: if tcp-client-disco-sock-reader thread dies on client node, > it will never disconnect from the cluster despite NODE_FAILED, and will > endlessly try to open communication connections to server while getting > "Remote node does not observe current node in topology" exceptions on client > and "Close incoming connection, unknown node" on server. > Generalized issue: stop()ing or interrupt()ing discovery threads cause > cluster to hang in many cases, where it is expected that any such node will: > * Restart the thread and continue normally > * Disconnect from the cluster to re-establish discovery connection > * Stop and close all remaining threads. > See the attached reproducer. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14711) Client discovery thread interrupt/stop causes endless communication reconnect attempt
Ilya Kasnacheev created IGNITE-14711: Summary: Client discovery thread interrupt/stop causes endless communication reconnect attempt Key: IGNITE-14711 URL: https://issues.apache.org/jira/browse/IGNITE-14711 Project: Ignite Issue Type: Bug Components: networking Affects Versions: 2.10 Reporter: Ilya Kasnacheev Original issue: if tcp-client-disco-sock-reader thread dies on client node, it will never disconnect from the cluster despite NODE_FAILED, and will endlessly try to open communication connections to server while getting "Remote node does not observe current node in topology" exceptions on client and "Close incoming connection, unknown node" on server. Generalized issue: stop()ing or interrupt()ing discovery threads cause cluster to hang in many cases, where it is expected that any such node will: * Restart the thread and continue normally * Disconnect from the cluster to re-establish discovery connection * Stop and close all remaining threads. See the attached reproducer. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14710) Cache API operations throw IgniteClientDisconnectedException
Ilya Kasnacheev created IGNITE-14710:
Summary: Cache API operations throw
IgniteClientDisconnectedException
Key: IGNITE-14710
URL: https://issues.apache.org/jira/browse/IGNITE-14710
Project: Ignite
Issue Type: Bug
Components: cache
Affects Versions: 2.10
Reporter: Ilya Kasnacheev
Is it possible for Cache.put() operation to throw raw
IgniteClientDisconnectedException:
{code}
class org.apache.ignite.IgniteClientDisconnectedException: Client node
disconnected: discovery.IgniteDiscoveryThreadInterruptTest1
at
org.apache.ignite.internal.GridKernalGatewayImpl.readLock(GridKernalGatewayImpl.java:93)
at org.apache.ignite.internal.IgniteKernal.guard(IgniteKernal.java:4163)
at
org.apache.ignite.internal.IgniteKernal.transactions(IgniteKernal.java:3173)
at
org.apache.ignite.internal.processors.cache.GridCacheGateway.checkAtomicOpsInTx(GridCacheGateway.java:363)
at
org.apache.ignite.internal.processors.cache.GridCacheGateway.onEnter(GridCacheGateway.java:262)
at
org.apache.ignite.internal.processors.cache.GridCacheGateway.enter(GridCacheGateway.java:177)
at
org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.onEnter(GatewayProtectedCacheProxy.java:1625)
at
org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:853)
at
org.apache.ignite.spi.discovery.IgniteDiscoveryThreadInterruptTest.run(IgniteDiscoveryThreadInterruptTest.java:117)
at
org.apache.ignite.spi.discovery.IgniteDiscoveryThreadInterruptTest.testStopClientSockWriter(IgniteDiscoveryThreadInterruptTest.java:89)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2428)
at java.lang.Thread.run(Thread.java:748)
{code}
This is incorrect behavior. Usually cache.put() throws only CacheException and
it should always throw CacheException with IgniteClientDisconnectedException in
getCause().
Currently we are both violating JSR107 and forcing users to handle both
CacheException and IgniteClientDisconnectedException, then check the former to
see if its cause is the latter, and duplicate future recovery code.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14687) BinaryHeapOutputStream BinaryOffheapOutputStream corrupt memory in case of overflow and cause JVM crash
[ https://issues.apache.org/jira/browse/IGNITE-14687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-14687: - Component/s: binary > BinaryHeapOutputStream BinaryOffheapOutputStream corrupt memory in case of > overflow and cause JVM crash > --- > > Key: IGNITE-14687 > URL: https://issues.apache.org/jira/browse/IGNITE-14687 > Project: Ignite > Issue Type: Bug > Components: binary >Affects Versions: 2.10 >Reporter: Sergey Kosarev >Assignee: Sergey Kosarev >Priority: Major > Fix For: 2.11 > > Time Spent: 10m > Remaining Estimate: 0h > > Reproducer is easy: > while (true) out.writeByteArray(bytes); > > # > # A fatal error has been detected by the Java Runtime Environment: > # > # EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x02742b26, > pid=17128, tid=0x24e4 > # > > > Actually It happened to me occassionally when by mistake a compute job tried > to return too many results. JVM crashed on the job result serialization. > See link to full reproducers below. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14683) Binary type registration fails when class present in different packages with simple name mapper
[ https://issues.apache.org/jira/browse/IGNITE-14683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17339663#comment-17339663 ] Ilya Kasnacheev commented on IGNITE-14683: -- It may seem that Ignite need to map simple type to complete type, but if query entities/indexed types are used, complete type is known to Ignite anyway, for a specific cache. So no collision may indeed happen unless the types are stored in the same cache (which they were not). > Binary type registration fails when class present in different packages with > simple name mapper > --- > > Key: IGNITE-14683 > URL: https://issues.apache.org/jira/browse/IGNITE-14683 > Project: Ignite > Issue Type: Bug > Components: binary >Affects Versions: 2.8 >Reporter: Ilya Kasnacheev >Priority: Major > > The following exception will be caught: > IgniteCheckedException: Failed to merge new and existing marshaller mappings. > For [platformId=0, typeId=12345689] new > typeName=com.pany.services.restApi.ContactList, existing > typeName=com.pany.services.handler.Contactlist > It is expected that there is no metadata conflict and simple name is always > used, if possible. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14683) Binary type registration fails when class present in different packages with simple name mapper
[ https://issues.apache.org/jira/browse/IGNITE-14683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-14683: - Description: The following exception will be caught: IgniteCheckedException: Failed to merge new and existing marshaller mappings. For [platformId=0, typeId=12345689] new typeName=com.pany.services.restApi.ContactList, existing typeName=com.pany.services.handler.Contactlist It is expected that there is no metadata conflict and simple name is always used, if possible. was: The following exception will be caught: IgniteCheckedException: Failed to merge new and existing marshaller mappings. For [platformId=0, typeId=12345689] new typeName=com.pany.services.restApi.ContactList, existing typeName=com.pany.services.handler.Contactlist > Binary type registration fails when class present in different packages with > simple name mapper > --- > > Key: IGNITE-14683 > URL: https://issues.apache.org/jira/browse/IGNITE-14683 > Project: Ignite > Issue Type: Bug > Components: binary >Affects Versions: 2.8 >Reporter: Ilya Kasnacheev >Priority: Major > > The following exception will be caught: > IgniteCheckedException: Failed to merge new and existing marshaller mappings. > For [platformId=0, typeId=12345689] new > typeName=com.pany.services.restApi.ContactList, existing > typeName=com.pany.services.handler.Contactlist > It is expected that there is no metadata conflict and simple name is always > used, if possible. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14683) Binary type registration fails when class present in different packages with simple name mapper
Ilya Kasnacheev created IGNITE-14683: Summary: Binary type registration fails when class present in different packages with simple name mapper Key: IGNITE-14683 URL: https://issues.apache.org/jira/browse/IGNITE-14683 Project: Ignite Issue Type: Bug Components: binary Affects Versions: 2.8 Reporter: Ilya Kasnacheev The following exception will be caught: IgniteCheckedException: Failed to merge new and existing marshaller mappings. For [platformId=0, typeId=12345689] new typeName=com.pany.services.restApi.ContactList, existing typeName=com.pany.services.handler.Contactlist -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14678) Remove a note about TLS 1.3 being unsupported from Java quick start
[ https://issues.apache.org/jira/browse/IGNITE-14678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17339558#comment-17339558 ] Ilya Kasnacheev commented on IGNITE-14678: -- Thank you for this doc update, I have merged it. > Remove a note about TLS 1.3 being unsupported from Java quick start > --- > > Key: IGNITE-14678 > URL: https://issues.apache.org/jira/browse/IGNITE-14678 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Igor Gusev >Assignee: Igor Gusev >Priority: Major > Fix For: 2.11 > > Time Spent: 10m > Remaining Estimate: 0h > > TLS 1.3 has been supported for a while, so we should remove a note about it > being unsupported from Java quickstart doc. > https://ignite.apache.org/docs/latest/quick-start/java#running-ignite-with-java-11-or-later -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14678) Remove a note about TLS 1.3 being unsupported from Java quick start
[ https://issues.apache.org/jira/browse/IGNITE-14678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-14678: - Ignite Flags: (was: Docs Required,Release Notes Required) > Remove a note about TLS 1.3 being unsupported from Java quick start > --- > > Key: IGNITE-14678 > URL: https://issues.apache.org/jira/browse/IGNITE-14678 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Igor Gusev >Assignee: Igor Gusev >Priority: Major > Fix For: 2.11 > > Time Spent: 10m > Remaining Estimate: 0h > > TLS 1.3 has been supported for a while, so we should remove a note about it > being unsupported from Java quickstart doc. > https://ignite.apache.org/docs/latest/quick-start/java#running-ignite-with-java-11-or-later -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13564) Improve SYSTEM_WORKER_BLOCKED reporting.
[
https://issues.apache.org/jira/browse/IGNITE-13564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17339115#comment-17339115
]
Ilya Kasnacheev commented on IGNITE-13564:
--
Is there any scope left in this ticket after IGNITE-13665?
> Improve SYSTEM_WORKER_BLOCKED reporting.
>
>
> Key: IGNITE-13564
> URL: https://issues.apache.org/jira/browse/IGNITE-13564
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.9, 2.8.1
>Reporter: Ivan Daschinsky
>Priority: Major
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Currently, reporting of system thread blocking has major drawbacks.
> 1. As system worker blocking is detected by another thread, due to
> implementation, failure handler receives not full information about problem.
> In {{FailureContext}} we have only two fields -- {{type}} and {{err}}.
> Throwable {{err}} is generated in thread-detector flow, so we lost a context
> of main problem.
> 2. Currently, due to implementation, we print not full stacktrace of blocking
> thread in {{org.apache.ignite.internal.worker.WorkersRegistry#onIdle}}.
> This two drawbacks can lead to completely loss of information about blocking
> system thread.
> I suggests:
> 1. Add another parameter in {{FailureContext}}, namely {{worker}}
> 2. Fix threaddump printing.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14607) Regex Based Filter in IPFinders
[ https://issues.apache.org/jira/browse/IGNITE-14607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17337818#comment-17337818 ] Ilya Kasnacheev commented on IGNITE-14607: -- Can you please file a documentation ticket for this feature? > Regex Based Filter in IPFinders > --- > > Key: IGNITE-14607 > URL: https://issues.apache.org/jira/browse/IGNITE-14607 > Project: Ignite > Issue Type: Sub-task >Reporter: Atri Sharma >Assignee: Atri Sharma >Priority: Major > Fix For: 2.11 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > This Jira tracks the effort to implement regex based IP filtering in IPFinders -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14607) Regex Based Filter in IPFinders
[ https://issues.apache.org/jira/browse/IGNITE-14607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-14607: - Ignite Flags: Docs Required (was: Docs Required,Release Notes Required) > Regex Based Filter in IPFinders > --- > > Key: IGNITE-14607 > URL: https://issues.apache.org/jira/browse/IGNITE-14607 > Project: Ignite > Issue Type: Sub-task >Reporter: Atri Sharma >Assignee: Atri Sharma >Priority: Major > Fix For: 2.11 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > This Jira tracks the effort to implement regex based IP filtering in IPFinders -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14607) Regex Based Filter in IPFinders
[ https://issues.apache.org/jira/browse/IGNITE-14607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-14607: - Fix Version/s: 2.11 > Regex Based Filter in IPFinders > --- > > Key: IGNITE-14607 > URL: https://issues.apache.org/jira/browse/IGNITE-14607 > Project: Ignite > Issue Type: Sub-task >Reporter: Atri Sharma >Assignee: Atri Sharma >Priority: Major > Fix For: 2.11 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > This Jira tracks the effort to implement regex based IP filtering in IPFinders -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14607) Regex Based Filter in IPFinders
[ https://issues.apache.org/jira/browse/IGNITE-14607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17337482#comment-17337482 ] Ilya Kasnacheev commented on IGNITE-14607: -- Please make sure to re-run tests after you make changes, and make sure that MTCGA has no blockers for your pull request. > Regex Based Filter in IPFinders > --- > > Key: IGNITE-14607 > URL: https://issues.apache.org/jira/browse/IGNITE-14607 > Project: Ignite > Issue Type: Sub-task >Reporter: Atri Sharma >Assignee: Atri Sharma >Priority: Major > Time Spent: 1h 10m > Remaining Estimate: 0h > > This Jira tracks the effort to implement regex based IP filtering in IPFinders -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14674) Assembly conflict when using POCO classes in compute of different peer-loaded version
Ilya Kasnacheev created IGNITE-14674: Summary: Assembly conflict when using POCO classes in compute of different peer-loaded version Key: IGNITE-14674 URL: https://issues.apache.org/jira/browse/IGNITE-14674 Project: Ignite Issue Type: Bug Components: platforms Reporter: Ilya Kasnacheev Assignee: Pavel Tupitsyn System.InvalidCastException: [A]DataTypes.ValueType cannot be cast to [B]DataTypes.ValueType. Type A originates from 'DataTypes, Version=1.0.0.1, Culture=neutral, PublicKeyToken=null' in the context 'Default' in a byte array. Type B originates from 'DataTypes, Version=1.0.0.2, Culture=neutral, PublicKeyToken=null' in the context 'Default' in a byte array. Is it possible to load the correct one? This assumes the type is identical but assembly is different. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14665) Security test suite runs no tests after CI test suite checker
[
https://issues.apache.org/jira/browse/IGNITE-14665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17337213#comment-17337213
]
Ilya Kasnacheev commented on IGNITE-14665:
--
Thank you for this fix, I have merged it.
> Security test suite runs no tests after CI test suite checker
> -
>
> Key: IGNITE-14665
> URL: https://issues.apache.org/jira/browse/IGNITE-14665
> Project: Ignite
> Issue Type: Bug
> Components: general
>Reporter: Ilya Kasnacheev
>Assignee: Maksim Timonin
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Please see linked development list thread as well as suite
> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Security?mode=builds
> All runs end with:
> {code}
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [WARNING] ForkStarter IOException:
> org.apache.maven.surefire.util.internal.StringUtils.unescapeString(Ljava/lang/StringBuilder;Ljava/lang/CharSequence;)V
> org.apache.maven.surefire.util.internal.StringUtils.unescapeBytes(Ljava/lang/String;Ljava/lang/String;)Ljava/nio/ByteBuffer;
>
> org.apache.maven.surefire.util.internal.StringUtils.unescapeString(Ljava/lang/StringBuilder;Ljava/lang/CharSequence;)V
>
> org.apache.maven.surefire.util.internal.StringUtils.unescapeString(Ljava/lang/StringBuilder;Ljava/lang/CharSequence;)V.
> See the dump file
> /opt/buildagent/work/7bc1c54bc719b67c/modules/core/target/surefire-reports/2021-04-28T14-22-01_678-jvmRun1.dumpstream
> [INFO]
> [INFO] Results:
> [INFO]
> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
> {code}
> After bisecting, this is the offender:
> {code}
> commit 62cc45861c0273286e00eb6fbc510c0bb5589e52
> Author: Maksim Timonin
> Date: Fri Feb 5 19:10:18 2021 +0300
> IGNITE-13512 Add travis check that tests are not in suites - Fixes #8367.
>
> Signed-off-by: Ilya Kasnacheev
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14665) Security test suite runs no tests after CI test suite checker
[
https://issues.apache.org/jira/browse/IGNITE-14665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev updated IGNITE-14665:
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> Security test suite runs no tests after CI test suite checker
> -
>
> Key: IGNITE-14665
> URL: https://issues.apache.org/jira/browse/IGNITE-14665
> Project: Ignite
> Issue Type: Bug
> Components: general
>Reporter: Ilya Kasnacheev
>Assignee: Maksim Timonin
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Please see linked development list thread as well as suite
> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Security?mode=builds
> All runs end with:
> {code}
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [WARNING] ForkStarter IOException:
> org.apache.maven.surefire.util.internal.StringUtils.unescapeString(Ljava/lang/StringBuilder;Ljava/lang/CharSequence;)V
> org.apache.maven.surefire.util.internal.StringUtils.unescapeBytes(Ljava/lang/String;Ljava/lang/String;)Ljava/nio/ByteBuffer;
>
> org.apache.maven.surefire.util.internal.StringUtils.unescapeString(Ljava/lang/StringBuilder;Ljava/lang/CharSequence;)V
>
> org.apache.maven.surefire.util.internal.StringUtils.unescapeString(Ljava/lang/StringBuilder;Ljava/lang/CharSequence;)V.
> See the dump file
> /opt/buildagent/work/7bc1c54bc719b67c/modules/core/target/surefire-reports/2021-04-28T14-22-01_678-jvmRun1.dumpstream
> [INFO]
> [INFO] Results:
> [INFO]
> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
> {code}
> After bisecting, this is the offender:
> {code}
> commit 62cc45861c0273286e00eb6fbc510c0bb5589e52
> Author: Maksim Timonin
> Date: Fri Feb 5 19:10:18 2021 +0300
> IGNITE-13512 Add travis check that tests are not in suites - Fixes #8367.
>
> Signed-off-by: Ilya Kasnacheev
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14669) NPE in GridCacheIoManager when sending GridCacheQueryResponse, target node left grid
[
https://issues.apache.org/jira/browse/IGNITE-14669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev updated IGNITE-14669:
-
Ignite Flags: (was: Release Notes Required)
> NPE in GridCacheIoManager when sending GridCacheQueryResponse, target node
> left grid
>
>
> Key: IGNITE-14669
> URL: https://issues.apache.org/jira/browse/IGNITE-14669
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.10
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code:java}
> ERROR o.a.i.i.p.cache.GridCacheIoManager - Failed to process message
> java.lang.NullPointerException: null
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.sendOrderedMessage(GridCacheIoManager.java:1309)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processFailedMessage(GridCacheIoManager.java:932)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:589)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:392)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:318)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:109)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:308)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1721)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1328)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4600(GridIoManager.java:157)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$8.execute(GridIoManager.java:1213)
> at
> org.apache.ignite.internal.managers.communication.TraceRunnable.run(TraceRunnable.java:54)
> 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)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14669) NPE in GridCacheIoManager when sending GridCacheQueryResponse, target node left grid
[
https://issues.apache.org/jira/browse/IGNITE-14669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev updated IGNITE-14669:
-
Description:
{code:java}
ERROR o.a.i.i.p.cache.GridCacheIoManager - Failed to process message
java.lang.NullPointerException: null
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.sendOrderedMessage(GridCacheIoManager.java:1309)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processFailedMessage(GridCacheIoManager.java:932)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:589)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:392)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:318)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:109)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:308)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1721)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1328)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4600(GridIoManager.java:157)
at
org.apache.ignite.internal.managers.communication.GridIoManager$8.execute(GridIoManager.java:1213)
at
org.apache.ignite.internal.managers.communication.TraceRunnable.run(TraceRunnable.java:54)
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)
{code}
was:
ERROR o.a.i.i.p.cache.GridCacheIoManager - Failed to process message
java.lang.NullPointerException: null
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.sendOrderedMessage(GridCacheIoManager.java:1309)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processFailedMessage(GridCacheIoManager.java:932)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:589)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:392)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:318)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:109)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:308)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1721)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1328)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4600(GridIoManager.java:157)
at
org.apache.ignite.internal.managers.communication.GridIoManager$8.execute(GridIoManager.java:1213)
at
org.apache.ignite.internal.managers.communication.TraceRunnable.run(TraceRunnable.java:54)
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)
> NPE in GridCacheIoManager when sending GridCacheQueryResponse, target node
> left grid
>
>
> Key: IGNITE-14669
> URL: https://issues.apache.org/jira/browse/IGNITE-14669
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.10
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
>
> {code:java}
> ERROR o.a.i.i.p.cache.GridCacheIoManager - Failed to process message
> java.lang.NullPointerException: null
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.sendOrderedMessage(GridCacheIoManager.java:1309)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processFailedMessage(GridCacheIoManager.java:932)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:589)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:392)
> at
>
[jira] [Created] (IGNITE-14669) NPE in GridCacheIoManager when sending GridCacheQueryResponse, target node left grid
Ilya Kasnacheev created IGNITE-14669: Summary: NPE in GridCacheIoManager when sending GridCacheQueryResponse, target node left grid Key: IGNITE-14669 URL: https://issues.apache.org/jira/browse/IGNITE-14669 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.10 Reporter: Ilya Kasnacheev Assignee: Ilya Kasnacheev ERROR o.a.i.i.p.cache.GridCacheIoManager - Failed to process message java.lang.NullPointerException: null at org.apache.ignite.internal.processors.cache.GridCacheIoManager.sendOrderedMessage(GridCacheIoManager.java:1309) at org.apache.ignite.internal.processors.cache.GridCacheIoManager.processFailedMessage(GridCacheIoManager.java:932) at org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:589) at org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:392) at org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:318) at org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:109) at org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:308) at org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1721) at org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1328) at org.apache.ignite.internal.managers.communication.GridIoManager.access$4600(GridIoManager.java:157) at org.apache.ignite.internal.managers.communication.GridIoManager$8.execute(GridIoManager.java:1213) at org.apache.ignite.internal.managers.communication.TraceRunnable.run(TraceRunnable.java:54) 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) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14665) Security test suite runs no tests after CI test suite checker
Ilya Kasnacheev created IGNITE-14665:
Summary: Security test suite runs no tests after CI test suite
checker
Key: IGNITE-14665
URL: https://issues.apache.org/jira/browse/IGNITE-14665
Project: Ignite
Issue Type: Bug
Components: general
Reporter: Ilya Kasnacheev
Assignee: Maksim Timonin
Please see linked development list thread as well as suite
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Security?mode=builds
All runs end with:
{code}
[INFO] ---
[INFO] T E S T S
[INFO] ---
[WARNING] ForkStarter IOException:
org.apache.maven.surefire.util.internal.StringUtils.unescapeString(Ljava/lang/StringBuilder;Ljava/lang/CharSequence;)V
org.apache.maven.surefire.util.internal.StringUtils.unescapeBytes(Ljava/lang/String;Ljava/lang/String;)Ljava/nio/ByteBuffer;
org.apache.maven.surefire.util.internal.StringUtils.unescapeString(Ljava/lang/StringBuilder;Ljava/lang/CharSequence;)V
org.apache.maven.surefire.util.internal.StringUtils.unescapeString(Ljava/lang/StringBuilder;Ljava/lang/CharSequence;)V.
See the dump file
/opt/buildagent/work/7bc1c54bc719b67c/modules/core/target/surefire-reports/2021-04-28T14-22-01_678-jvmRun1.dumpstream
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO]
{code}
After bisecting, this is the offender:
{code}
commit 62cc45861c0273286e00eb6fbc510c0bb5589e52
Author: Maksim Timonin
Date: Fri Feb 5 19:10:18 2021 +0300
IGNITE-13512 Add travis check that tests are not in suites - Fixes #8367.
Signed-off-by: Ilya Kasnacheev
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14613) Mark CacheConfiguration.rebalanceDelay as deprecated.
Ilya Kasnacheev created IGNITE-14613: Summary: Mark CacheConfiguration.rebalanceDelay as deprecated. Key: IGNITE-14613 URL: https://issues.apache.org/jira/browse/IGNITE-14613 Project: Ignite Issue Type: Improvement Reporter: Ilya Kasnacheev Assignee: Ilya Kasnacheev Now that we have baseline topology and baseline auto-adjust, rebalance delay is rarely needed and does not see enough use/testing. See for example the mailing list thread where it became apparent it will disable historical rebalancing. Let's mark it as deprecated, target its removal in 3.0. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14505) Print information about striped pool in metrics for local node
[ https://issues.apache.org/jira/browse/IGNITE-14505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-14505: - Fix Version/s: 2.11 > Print information about striped pool in metrics for local node > -- > > Key: IGNITE-14505 > URL: https://issues.apache.org/jira/browse/IGNITE-14505 > Project: Ignite > Issue Type: Improvement >Reporter: Denis Mekhanikov >Assignee: Denis Mekhanikov >Priority: Major > Fix For: 2.11 > > Time Spent: 20m > Remaining Estimate: 0h > > Currently only information about public and system thread pools are printed > in metrics for a local node. It would be good to have the same information > about striped pool as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14505) Print information about striped pool in metrics for local node
[ https://issues.apache.org/jira/browse/IGNITE-14505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17325067#comment-17325067 ] Ilya Kasnacheev commented on IGNITE-14505: -- Can you please also file release notes field? > Print information about striped pool in metrics for local node > -- > > Key: IGNITE-14505 > URL: https://issues.apache.org/jira/browse/IGNITE-14505 > Project: Ignite > Issue Type: Improvement >Reporter: Denis Mekhanikov >Assignee: Denis Mekhanikov >Priority: Major > Fix For: 2.11 > > Time Spent: 20m > Remaining Estimate: 0h > > Currently only information about public and system thread pools are printed > in metrics for a local node. It would be good to have the same information > about striped pool as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14505) Print information about striped pool in metrics for local node
[ https://issues.apache.org/jira/browse/IGNITE-14505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-14505: - Ignite Flags: (was: Release Notes Required) > Print information about striped pool in metrics for local node > -- > > Key: IGNITE-14505 > URL: https://issues.apache.org/jira/browse/IGNITE-14505 > Project: Ignite > Issue Type: Improvement >Reporter: Denis Mekhanikov >Assignee: Denis Mekhanikov >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Currently only information about public and system thread pools are printed > in metrics for a local node. It would be good to have the same information > about striped pool as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14505) Print information about striped pool in metrics for local node
[ https://issues.apache.org/jira/browse/IGNITE-14505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-14505: - Ignite Flags: Release Notes Required > Print information about striped pool in metrics for local node > -- > > Key: IGNITE-14505 > URL: https://issues.apache.org/jira/browse/IGNITE-14505 > Project: Ignite > Issue Type: Improvement >Reporter: Denis Mekhanikov >Assignee: Denis Mekhanikov >Priority: Major > Fix For: 2.11 > > Time Spent: 20m > Remaining Estimate: 0h > > Currently only information about public and system thread pools are printed > in metrics for a local node. It would be good to have the same information > about striped pool as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14505) Print information about striped pool in metrics for local node
[ https://issues.apache.org/jira/browse/IGNITE-14505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-14505: - Ignite Flags: Release Notes Required (was: Docs Required,Release Notes Required) > Print information about striped pool in metrics for local node > -- > > Key: IGNITE-14505 > URL: https://issues.apache.org/jira/browse/IGNITE-14505 > Project: Ignite > Issue Type: Improvement >Reporter: Denis Mekhanikov >Assignee: Denis Mekhanikov >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Currently only information about public and system thread pools are printed > in metrics for a local node. It would be good to have the same information > about striped pool as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14505) Print information about striped pool in metrics for local node
[ https://issues.apache.org/jira/browse/IGNITE-14505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17325066#comment-17325066 ] Ilya Kasnacheev commented on IGNITE-14505: -- Thank you for this improvement [~dmekhanikov], I have merged it to master. > Print information about striped pool in metrics for local node > -- > > Key: IGNITE-14505 > URL: https://issues.apache.org/jira/browse/IGNITE-14505 > Project: Ignite > Issue Type: Improvement >Reporter: Denis Mekhanikov >Assignee: Denis Mekhanikov >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Currently only information about public and system thread pools are printed > in metrics for a local node. It would be good to have the same information > about striped pool as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14346) Implement Azure Blob Storage Based IP Finder
[ https://issues.apache.org/jira/browse/IGNITE-14346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17323946#comment-17323946 ] Ilya Kasnacheev commented on IGNITE-14346: -- Thank you for this module [~atri] It have been merged to master. > Implement Azure Blob Storage Based IP Finder > > > Key: IGNITE-14346 > URL: https://issues.apache.org/jira/browse/IGNITE-14346 > Project: Ignite > Issue Type: Improvement > Components: integrations >Reporter: Atri Sharma >Assignee: Atri Sharma >Priority: Major > Fix For: 2.11 > > Attachments: Screenshot 2021-03-23 at 8.42.31 PM.png, Screenshot > 2021-03-23 at 8.43.31 PM.png, Screenshot 2021-03-23 at 8.44.11 PM.png, > Screenshot 2021-03-23 at 8.45.05 PM.png, azure-container.png > > Time Spent: 3h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14346) Implement Azure Blob Storage Based IP Finder
[ https://issues.apache.org/jira/browse/IGNITE-14346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-14346: - Ignite Flags: Docs Required (was: Docs Required,Release Notes Required) > Implement Azure Blob Storage Based IP Finder > > > Key: IGNITE-14346 > URL: https://issues.apache.org/jira/browse/IGNITE-14346 > Project: Ignite > Issue Type: Improvement > Components: integrations >Reporter: Atri Sharma >Assignee: Atri Sharma >Priority: Major > Fix For: 2.11 > > Attachments: Screenshot 2021-03-23 at 8.42.31 PM.png, Screenshot > 2021-03-23 at 8.43.31 PM.png, Screenshot 2021-03-23 at 8.44.11 PM.png, > Screenshot 2021-03-23 at 8.45.05 PM.png, azure-container.png > > Time Spent: 3h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14346) Implement Azure Blob Storage Based IP Finder
[ https://issues.apache.org/jira/browse/IGNITE-14346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-14346: - Labels: (was: ReviewNeeded) > Implement Azure Blob Storage Based IP Finder > > > Key: IGNITE-14346 > URL: https://issues.apache.org/jira/browse/IGNITE-14346 > Project: Ignite > Issue Type: Improvement > Components: integrations >Reporter: Atri Sharma >Assignee: Atri Sharma >Priority: Major > Fix For: 2.11 > > Attachments: Screenshot 2021-03-23 at 8.42.31 PM.png, Screenshot > 2021-03-23 at 8.43.31 PM.png, Screenshot 2021-03-23 at 8.44.11 PM.png, > Screenshot 2021-03-23 at 8.45.05 PM.png, azure-container.png > > Time Spent: 3h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14346) Implement Azure Blob Storage Based IP Finder
[ https://issues.apache.org/jira/browse/IGNITE-14346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-14346: - Component/s: integrations > Implement Azure Blob Storage Based IP Finder > > > Key: IGNITE-14346 > URL: https://issues.apache.org/jira/browse/IGNITE-14346 > Project: Ignite > Issue Type: Improvement > Components: integrations >Reporter: Atri Sharma >Assignee: Atri Sharma >Priority: Major > Labels: ReviewNeeded > Fix For: 2.11 > > Attachments: Screenshot 2021-03-23 at 8.42.31 PM.png, Screenshot > 2021-03-23 at 8.43.31 PM.png, Screenshot 2021-03-23 at 8.44.11 PM.png, > Screenshot 2021-03-23 at 8.45.05 PM.png, azure-container.png > > Time Spent: 3h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-14346) Implement Azure Blob Storage Based IP Finder
[ https://issues.apache.org/jira/browse/IGNITE-14346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev resolved IGNITE-14346. -- Fix Version/s: 2.11 Release Note: Added Azure Blob Storage-based Discovery IP Finder Resolution: Fixed > Implement Azure Blob Storage Based IP Finder > > > Key: IGNITE-14346 > URL: https://issues.apache.org/jira/browse/IGNITE-14346 > Project: Ignite > Issue Type: Improvement >Reporter: Atri Sharma >Assignee: Atri Sharma >Priority: Major > Labels: ReviewNeeded > Fix For: 2.11 > > Attachments: Screenshot 2021-03-23 at 8.42.31 PM.png, Screenshot > 2021-03-23 at 8.43.31 PM.png, Screenshot 2021-03-23 at 8.44.11 PM.png, > Screenshot 2021-03-23 at 8.45.05 PM.png, azure-container.png > > Time Spent: 3h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14346) Implement Azure Blob Storage Based IP Finder
[ https://issues.apache.org/jira/browse/IGNITE-14346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17323929#comment-17323929 ] Ilya Kasnacheev commented on IGNITE-14346: -- LGTM. I will re-run basic tests and then hope to merge. > Implement Azure Blob Storage Based IP Finder > > > Key: IGNITE-14346 > URL: https://issues.apache.org/jira/browse/IGNITE-14346 > Project: Ignite > Issue Type: Improvement >Reporter: Atri Sharma >Assignee: Atri Sharma >Priority: Major > Labels: ReviewNeeded > Attachments: Screenshot 2021-03-23 at 8.42.31 PM.png, Screenshot > 2021-03-23 at 8.43.31 PM.png, Screenshot 2021-03-23 at 8.44.11 PM.png, > Screenshot 2021-03-23 at 8.45.05 PM.png, azure-container.png > > Time Spent: 3h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14577) .NET: error serialization failed when thread is interrupted
[
https://issues.apache.org/jira/browse/IGNITE-14577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17323896#comment-17323896
]
Ilya Kasnacheev commented on IGNITE-14577:
--
I think we should not interrupt binary meta updates. It causes issues for Java
code too.
> .NET: error serialization failed when thread is interrupted
> ---
>
> Key: IGNITE-14577
> URL: https://issues.apache.org/jira/browse/IGNITE-14577
> Project: Ignite
> Issue Type: New Feature
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Minor
> Labels: .NET
> Attachments: Untitled, Untitled (1), Untitled (2)
>
>
> When using {{ICompute.WithTimeout}}, the following scenario is possible:
> * Timeout is reached, and Ignite interrupts compute job thread
> * {{InterruptedException}} is thrown from the job code
> * Ignite.NET tries to serialize the job result (exception) in
> {{BinaryUtils.WriteInvocationResult}}
> * {{BinaryProcessor.PutBinaryTypes}} is called during the serialization
> * Thread is interrupted, so metadata update fails with
> {{InterruptedException}}
> As a result, instead of a simple timeout exception, there is a lot of cryptic
> errors in the log.
> Possible fixes:
> * Handle {{InterruptedException}} as a special case in
> {{WriteInvocationResult}} so we don't need to send meta updates
> * Do not interrupt binary meta updates
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14547) NPE in control.sh if there is unknown argument after --cache indexes_force_rebuild
[
https://issues.apache.org/jira/browse/IGNITE-14547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev updated IGNITE-14547:
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> NPE in control.sh if there is unknown argument after --cache
> indexes_force_rebuild
> --
>
> Key: IGNITE-14547
> URL: https://issues.apache.org/jira/browse/IGNITE-14547
> Project: Ignite
> Issue Type: Bug
> Components: control.sh
>Affects Versions: 2.10
>Reporter: Ilya Kazakov
>Assignee: Ilya Kazakov
>Priority: Minor
> Fix For: 2.11
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> ./control.sh --cache indexes_force_rebuild --foo
> gets NPE instead of "Unknown argument: --foo" message
> {code:java}
> java.lang.NullPointerException
> Command [] finished with code: 4
> Error stack trace:
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.commandline.cache.CacheIndexesForceRebuild.parseArguments(CacheIndexesForceRebuild.java:210)
> at
> org.apache.ignite.internal.commandline.cache.CacheCommands.parseArguments(CacheCommands.java:97)
> at
> org.apache.ignite.internal.commandline.CommonArgParser.parseAndValidate(CommonArgParser.java:241)
> at
> org.apache.ignite.internal.commandline.CommandHandler.execute(CommandHandler.java:244)
> at
> org.apache.ignite.internal.commandline.CommandHandler.main(CommandHandler.java:141){code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13976) WAL disable/enable with node restarts results in mismatching state, data loss
[ https://issues.apache.org/jira/browse/IGNITE-13976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319569#comment-17319569 ] Ilya Kasnacheev commented on IGNITE-13976: -- We should discuss reverting IGNITE-14039 in the future when we make sure the problem no longer manifests. Thank you for this fix. > WAL disable/enable with node restarts results in mismatching state, data loss > - > > Key: IGNITE-13976 > URL: https://issues.apache.org/jira/browse/IGNITE-13976 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.9.1 >Reporter: Ilya Kasnacheev >Assignee: Sergey Chugunov >Priority: Critical > Fix For: 2.11 > > Time Spent: 20m > Remaining Estimate: 0h > > If you try to enable/disable WAL on unstable topology, you will get to state > when WAL status is undefined, nodes might have different wall status and the > only way to fix it is to restart the cluster, which will lead to data loss > because ignite removes data if WAL is disabled on restart. > See the reproducer in PR. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13976) WAL disable/enable with node restarts results in mismatching state, data loss
[ https://issues.apache.org/jira/browse/IGNITE-13976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17318005#comment-17318005 ] Ilya Kasnacheev commented on IGNITE-13976: -- https://github.com/apache/ignite/pull/8643 LGTM now, the only red flag is misplaced cache context access in ClusterCachesInfo [~sergeychugunov] > WAL disable/enable with node restarts results in mismatching state, data loss > - > > Key: IGNITE-13976 > URL: https://issues.apache.org/jira/browse/IGNITE-13976 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.9.1 >Reporter: Ilya Kasnacheev >Assignee: Sergey Chugunov >Priority: Critical > Time Spent: 10m > Remaining Estimate: 0h > > If you try to enable/disable WAL on unstable topology, you will get to state > when WAL status is undefined, nodes might have different wall status and the > only way to fix it is to restart the cluster, which will lead to data loss > because ignite removes data if WAL is disabled on restart. > See the reproducer in PR. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14507) Un-deprecate IGNITE_BINARY_SORT_OBJECT_FIELDS
[ https://issues.apache.org/jira/browse/IGNITE-14507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17317928#comment-17317928 ] Ilya Kasnacheev commented on IGNITE-14507: -- I have merged this change. > Un-deprecate IGNITE_BINARY_SORT_OBJECT_FIELDS > - > > Key: IGNITE-14507 > URL: https://issues.apache.org/jira/browse/IGNITE-14507 > Project: Ignite > Issue Type: Improvement > Components: binary >Reporter: Stanislav Lukyanov >Assignee: Kirill Tkalenko >Priority: Major > Fix For: 2.11 > > Time Spent: 50m > Remaining Estimate: 0h > > IGNITE_BINARY_SORT_OBJECT_FIELDS should not be deprecated - on the contrary, > every new environment better have this option. We need to advertise it more, > so we need to remove the deprecation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14346) Implement Azure Blob Storage Based IP Finder
[ https://issues.apache.org/jira/browse/IGNITE-14346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-14346: - Attachment: azure-container.png > Implement Azure Blob Storage Based IP Finder > > > Key: IGNITE-14346 > URL: https://issues.apache.org/jira/browse/IGNITE-14346 > Project: Ignite > Issue Type: Improvement >Reporter: Atri Sharma >Assignee: Atri Sharma >Priority: Major > Labels: ReviewNeeded > Attachments: Screenshot 2021-03-23 at 8.42.31 PM.png, Screenshot > 2021-03-23 at 8.43.31 PM.png, Screenshot 2021-03-23 at 8.44.11 PM.png, > Screenshot 2021-03-23 at 8.45.05 PM.png, azure-container.png > > Time Spent: 2h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14346) Implement Azure Blob Storage Based IP Finder
[
https://issues.apache.org/jira/browse/IGNITE-14346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17317910#comment-17317910
]
Ilya Kasnacheev commented on IGNITE-14346:
--
I have tried the fresh build of the PR, now the dependencies issue seems
resolved, but there are at least two new issues:
If IPv6 is active, I get the following error:
{code}
class org.apache.ignite.IgniteException: URLDecoder: Illegal hex characters in
escape (%) pattern - Error at index 0 in: "lo"
at
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:1098)
at org.apache.ignite.Ignition.start(Ignition.java:356)
at
org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:367)
Caused by: class org.apache.ignite.IgniteCheckedException: URLDecoder: Illegal
hex characters in escape (%) pattern - Error at index 0 in: "lo"
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1454)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2112)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1758)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1143)
at
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1061)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:947)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:846)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:716)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:685)
at org.apache.ignite.Ignition.start(Ignition.java:353)
... 1 more
Caused by: java.lang.IllegalArgumentException: URLDecoder: Illegal hex
characters in escape (%) pattern - Error at index 0 in: "lo"
at java.base/java.net.URLDecoder.decode(URLDecoder.java:232)
at java.base/java.net.URLDecoder.decode(URLDecoder.java:142)
at com.azure.storage.common.Utility.decode(Utility.java:91)
at com.azure.storage.common.Utility.urlDecode(Utility.java:82)
at
com.azure.storage.blob.BlobContainerAsyncClient.getBlobAsyncClient(BlobContainerAsyncClient.java:144)
at
com.azure.storage.blob.BlobContainerAsyncClient.getBlobAsyncClient(BlobContainerAsyncClient.java:125)
at
com.azure.storage.blob.BlobContainerClient.getBlobClient(BlobContainerClient.java:76)
at
org.apache.ignite.spi.discovery.tcp.ipfinder.azure.TcpDiscoveryAzureBlobStoreIpFinder.registerAddresses(TcpDiscoveryAzureBlobStoreIpFinder.java:140)
at
org.apache.ignite.spi.discovery.tcp.ipfinder.TcpDiscoveryIpFinderAdapter.initializeLocalAddresses(TcpDiscoveryIpFinderAdapter.java:66)
at
org.apache.ignite.spi.discovery.tcp.TcpDiscoveryImpl.registerLocalNodeAddress(TcpDiscoveryImpl.java:401)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl.spiStart(ServerImpl.java:457)
at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.spiStart(TcpDiscoverySpi.java:2166)
at
org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:278)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:981)
at
org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1965)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1323)
... 10 more
Failed to start grid: URLDecoder: Illegal hex characters in escape (%) pattern
- Error at index 0 in: "lo"
{code}
I believe this is because IPv6 binding addresses have %interface prepended to
them (::1%localhost, ::1%eth0), it looks like they need some extra escaping in
your use case.
When IPv6 is on, azure discovery will start all right but cluster will not
assemble - neither of my two nodes will discover itself and start. Maybe I'm
doing something wrong? My Azure container has some entries (see attach) but
cluster does not come online in a few minutes. When using static discovery, the
cluster is up and running instantly.
Please advise.
> Implement Azure Blob Storage Based IP Finder
>
>
> Key: IGNITE-14346
> URL: https://issues.apache.org/jira/browse/IGNITE-14346
> Project: Ignite
> Issue Type: Improvement
>Reporter: Atri Sharma
>Assignee: Atri Sharma
>Priority: Major
> Labels: ReviewNeeded
> Attachments: Screenshot 2021-03-23 at 8.42.31 PM.png, Screenshot
> 2021-03-23 at 8.43.31 PM.png, Screenshot 2021-03-23 at 8.44.11 PM.png,
> Screenshot 2021-03-23 at 8.45.05 PM.png
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-13381) ClusterGroupEmptyException: Cluster group is empty error after client reconnect
[ https://issues.apache.org/jira/browse/IGNITE-13381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17317338#comment-17317338 ] Ilya Kasnacheev edited comment on IGNITE-13381 at 4/8/21, 4:55 PM: --- Thank you for this fix [~aealeksandrov] was (Author: ilyak): Thank you for this fix [~aalexandrov] > ClusterGroupEmptyException: Cluster group is empty error after client > reconnect > --- > > Key: IGNITE-13381 > URL: https://issues.apache.org/jira/browse/IGNITE-13381 > Project: Ignite > Issue Type: Bug > Components: networking >Affects Versions: 2.8.1 >Reporter: Andrey Aleksandrov >Assignee: Andrey Aleksandrov >Priority: Major > Fix For: 2.11 > > Attachments: SendMessageAfterClientReconnect.java > > Time Spent: 20m > Remaining Estimate: 0h > > Please run the attached test. > It will produce the following exception: > Exception in thread "main" class > org.apache.ignite.cluster.ClusterGroupEmptyException: Cluster group is empty. > at org.apache.ignite.internal.util.IgniteUtils$6.apply(IgniteUtils.java:927) > at org.apache.ignite.internal.util.IgniteUtils$6.apply(IgniteUtils.java:925) > at > org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:1083) > at > org.apache.ignite.internal.IgniteMessagingImpl.send0(IgniteMessagingImpl.java:105) > at > org.apache.ignite.internal.IgniteMessagingImpl.send(IgniteMessagingImpl.java:81) > at npe.IgnitePartitioningTest.main(IgnitePartitioningTest.java:110) > Caused by: class > org.apache.ignite.internal.cluster.ClusterGroupEmptyCheckedException: Cluster > group is empty. > at > org.apache.ignite.internal.util.IgniteUtils.emptyTopologyException(IgniteUtils.java:5106) > at > org.apache.ignite.internal.IgniteMessagingImpl.send0(IgniteMessagingImpl.java:100) > ... 2 more > Fix: > change > return new ClusterGroupAdapter(ctx, null, > Collections.singleton(cfg.getNodeId())); > on > return new ClusterGroupAdapter(ctx, null, > Collections.singleton(ctx.discovery().localNode().id())); -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13381) ClusterGroupEmptyException: Cluster group is empty error after client reconnect
[ https://issues.apache.org/jira/browse/IGNITE-13381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-13381: - Ignite Flags: (was: Docs Required,Release Notes Required) > ClusterGroupEmptyException: Cluster group is empty error after client > reconnect > --- > > Key: IGNITE-13381 > URL: https://issues.apache.org/jira/browse/IGNITE-13381 > Project: Ignite > Issue Type: Bug > Components: networking >Affects Versions: 2.8.1 >Reporter: Andrey Aleksandrov >Assignee: Andrey Aleksandrov >Priority: Major > Fix For: 2.11 > > Attachments: SendMessageAfterClientReconnect.java > > Time Spent: 20m > Remaining Estimate: 0h > > Please run the attached test. > It will produce the following exception: > Exception in thread "main" class > org.apache.ignite.cluster.ClusterGroupEmptyException: Cluster group is empty. > at org.apache.ignite.internal.util.IgniteUtils$6.apply(IgniteUtils.java:927) > at org.apache.ignite.internal.util.IgniteUtils$6.apply(IgniteUtils.java:925) > at > org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:1083) > at > org.apache.ignite.internal.IgniteMessagingImpl.send0(IgniteMessagingImpl.java:105) > at > org.apache.ignite.internal.IgniteMessagingImpl.send(IgniteMessagingImpl.java:81) > at npe.IgnitePartitioningTest.main(IgnitePartitioningTest.java:110) > Caused by: class > org.apache.ignite.internal.cluster.ClusterGroupEmptyCheckedException: Cluster > group is empty. > at > org.apache.ignite.internal.util.IgniteUtils.emptyTopologyException(IgniteUtils.java:5106) > at > org.apache.ignite.internal.IgniteMessagingImpl.send0(IgniteMessagingImpl.java:100) > ... 2 more > Fix: > change > return new ClusterGroupAdapter(ctx, null, > Collections.singleton(cfg.getNodeId())); > on > return new ClusterGroupAdapter(ctx, null, > Collections.singleton(ctx.discovery().localNode().id())); -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14499) TcpDiscoveryVM IP Finder: thick client does not try to resolve the FQDN again during reconnection
[ https://issues.apache.org/jira/browse/IGNITE-14499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-14499: - Ignite Flags: (was: Release Notes Required) > TcpDiscoveryVM IP Finder: thick client does not try to resolve the FQDN again > during reconnection > - > > Key: IGNITE-14499 > URL: https://issues.apache.org/jira/browse/IGNITE-14499 > Project: Ignite > Issue Type: Bug > Components: messaging >Affects Versions: 2.10 >Reporter: Andrey Aleksandrov >Assignee: Andrey Aleksandrov >Priority: Major > Fix For: 2.11 > > Time Spent: 20m > Remaining Estimate: 0h > > Client reconnect logic has for the following scenarios: > 1)You have 3 servers. FQDN name can be resolved to one of them (but only to > reachable server node). > 2)You have 3 servers. FQDN name will be resolved to the list of the reachable > server IPs. > Results: > Thick clients do not try to resolve FQDN once again upon connection failure. > Reconnect doesn't work. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14499) TcpDiscoveryVM IP Finder: thick client does not try to resolve the FQDN again during reconnection
[ https://issues.apache.org/jira/browse/IGNITE-14499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-14499: - Release Note: Support for dynamic DNS in static IP discovery. > TcpDiscoveryVM IP Finder: thick client does not try to resolve the FQDN again > during reconnection > - > > Key: IGNITE-14499 > URL: https://issues.apache.org/jira/browse/IGNITE-14499 > Project: Ignite > Issue Type: Bug > Components: messaging >Affects Versions: 2.10 >Reporter: Andrey Aleksandrov >Assignee: Andrey Aleksandrov >Priority: Major > Fix For: 2.11 > > Time Spent: 20m > Remaining Estimate: 0h > > Client reconnect logic has for the following scenarios: > 1)You have 3 servers. FQDN name can be resolved to one of them (but only to > reachable server node). > 2)You have 3 servers. FQDN name will be resolved to the list of the reachable > server IPs. > Results: > Thick clients do not try to resolve FQDN once again upon connection failure. > Reconnect doesn't work. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14482) Update the code snippet
[
https://issues.apache.org/jira/browse/IGNITE-14482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev updated IGNITE-14482:
-
Priority: Minor (was: Major)
> Update the code snippet
>
>
> Key: IGNITE-14482
> URL: https://issues.apache.org/jira/browse/IGNITE-14482
> Project: Ignite
> Issue Type: Bug
> Components: documentation
>Reporter: Nikita Safonov
>Assignee: Igor Gusev
>Priority: Minor
> Labels: Documentation, documentation
> Fix For: 2.11
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> See the XML code snippet of this section:
> [https://ignite.apache.org/docs/latest/clustering/discovery-in-the-cloud#google-compute-discovery]
> and change the line
> {{}}
> {code:java}
> name="projectName" ref="YOUR_GOOGLE_PLATFORM_PROJECT_NAME"{code}
> {{}} to{{}}
> {code:java}
> name="projectName" value="YOUR_GOOGLE_PLATFORM_PROJECT_NAME" on both
> pages{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14482) Update the code snippet
[
https://issues.apache.org/jira/browse/IGNITE-14482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev updated IGNITE-14482:
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> Update the code snippet
>
>
> Key: IGNITE-14482
> URL: https://issues.apache.org/jira/browse/IGNITE-14482
> Project: Ignite
> Issue Type: Bug
> Components: documentation
>Reporter: Nikita Safonov
>Assignee: Igor Gusev
>Priority: Major
> Labels: Documentation, documentation
> Fix For: 2.11
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> See the XML code snippet of this section:
> [https://ignite.apache.org/docs/latest/clustering/discovery-in-the-cloud#google-compute-discovery]
> and change the line
> {{}}
> {code:java}
> name="projectName" ref="YOUR_GOOGLE_PLATFORM_PROJECT_NAME"{code}
> {{}} to{{}}
> {code:java}
> name="projectName" value="YOUR_GOOGLE_PLATFORM_PROJECT_NAME" on both
> pages{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14490) cache.invoke() triggers failure handler and freezes if entry processor is not urideployed
[ https://issues.apache.org/jira/browse/IGNITE-14490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17315506#comment-17315506 ] Ilya Kasnacheev commented on IGNITE-14490: -- Please see the test in the PR > cache.invoke() triggers failure handler and freezes if entry processor is not > urideployed > - > > Key: IGNITE-14490 > URL: https://issues.apache.org/jira/browse/IGNITE-14490 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.10 >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Major > Attachments: LoclerMain.java > > Time Spent: 10m > Remaining Estimate: 0h > > If URI deployment is specified > Caused by: java.lang.ClassNotFoundException: [Ljava.lang.StackTraceElement;" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14490) cache.invoke() triggers failure handler and freezes if entry processor is not urideployed
[ https://issues.apache.org/jira/browse/IGNITE-14490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-14490: - Attachment: LoclerMain.java > cache.invoke() triggers failure handler and freezes if entry processor is not > urideployed > - > > Key: IGNITE-14490 > URL: https://issues.apache.org/jira/browse/IGNITE-14490 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.10 >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Major > Attachments: LoclerMain.java > > > If URI deployment is specified > Caused by: java.lang.ClassNotFoundException: [Ljava.lang.StackTraceElement;" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14490) cache.invoke() triggers failure handler and freezes if entry processor is not urideployed
[ https://issues.apache.org/jira/browse/IGNITE-14490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-14490: - Ignite Flags: Release Notes Required (was: Docs Required,Release Notes Required) > cache.invoke() triggers failure handler and freezes if entry processor is not > urideployed > - > > Key: IGNITE-14490 > URL: https://issues.apache.org/jira/browse/IGNITE-14490 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.10 >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Major > Attachments: LoclerMain.java > > > If URI deployment is specified > Caused by: java.lang.ClassNotFoundException: [Ljava.lang.StackTraceElement;" -- This message was sent by Atlassian Jira (v8.3.4#803005)
