[jira] [Updated] (IGNITE-16797) DDL support for Storage specific parameters
[ https://issues.apache.org/jira/browse/IGNITE-16797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko updated IGNITE-16797: - Ignite Flags: (was: Docs Required,Release Notes Required) > DDL support for Storage specific parameters > --- > > Key: IGNITE-16797 > URL: https://issues.apache.org/jira/browse/IGNITE-16797 > Project: Ignite > Issue Type: Task > Components: persistence >Reporter: Sergey Chugunov >Priority: Major > Labels: ignite-3 > > Different Storage Engines (SE) may have different sets of configuration > parameters. These parameters are supported on configuration level but should > be integrated with DDL as well. > DDL scripts should be able to transfer SE parameters from CREATE TABLE > command to configuration and properly handle any validation or other > exceptions generated by configuration module. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16792) Configuration for Default Storage Engine
[ https://issues.apache.org/jira/browse/IGNITE-16792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko updated IGNITE-16792: - Fix Version/s: 3.0.0-alpha5 > Configuration for Default Storage Engine > > > Key: IGNITE-16792 > URL: https://issues.apache.org/jira/browse/IGNITE-16792 > Project: Ignite > Issue Type: Task > Components: persistence >Reporter: Sergey Chugunov >Assignee: Kirill Tkalenko >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > Time Spent: 10m > Remaining Estimate: 0h > > Pluggable storage concept enables user to set up different storage engines > (SE) on the same node e.g. for performance reasons, each table can be hosted > only by one storage. > From DDL point of view SE is specified as part of CREATE TABLE command. But > in case of only one SE and some other cases specifying it for each table > creates a lot of unnecessary boilerplate code. > To address this and free user from writing exactly the same code a > cluster-wide setting *defaultStorageEngine* should be introduced. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16792) Configuration for Default Storage Engine
[ https://issues.apache.org/jira/browse/IGNITE-16792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko updated IGNITE-16792: - Reviewer: Ivan Bessonov > Configuration for Default Storage Engine > > > Key: IGNITE-16792 > URL: https://issues.apache.org/jira/browse/IGNITE-16792 > Project: Ignite > Issue Type: Task > Components: persistence >Reporter: Sergey Chugunov >Assignee: Kirill Tkalenko >Priority: Major > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > Pluggable storage concept enables user to set up different storage engines > (SE) on the same node e.g. for performance reasons, each table can be hosted > only by one storage. > From DDL point of view SE is specified as part of CREATE TABLE command. But > in case of only one SE and some other cases specifying it for each table > creates a lot of unnecessary boilerplate code. > To address this and free user from writing exactly the same code a > cluster-wide setting *defaultStorageEngine* should be introduced. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16822) Fix GridCacheLifecycleAwareSelfTest.testLifecycleAware
[ https://issues.apache.org/jira/browse/IGNITE-16822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519224#comment-17519224 ] Nikolay Izhikov commented on IGNITE-16822: -- https://ci.ignite.apache.org/viewQueued.html?itemId=6512313&tab=queuedBuildOverviewTab > Fix GridCacheLifecycleAwareSelfTest.testLifecycleAware > -- > > Key: IGNITE-16822 > URL: https://issues.apache.org/jira/browse/IGNITE-16822 > Project: Ignite > Issue Type: Bug >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > GridCacheLifecycleAwareSelfTest.testLifecycleAware always fail. > Need to fix it > https://ci2.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-5330309473671089592&tab=testDetails -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16735) .NET: Thin 3.0: Implement Compute Grid for .NET thin client
[ https://issues.apache.org/jira/browse/IGNITE-16735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-16735: Release Note: .NET: Added basic Compute functionality. > .NET: Thin 3.0: Implement Compute Grid for .NET thin client > --- > > Key: IGNITE-16735 > URL: https://issues.apache.org/jira/browse/IGNITE-16735 > Project: Ignite > Issue Type: New Feature > Components: compute, thin client >Reporter: Igor Sapego >Assignee: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > > Need to implement functionality similiar to Java's > org.apache.ignite.compute.IgniteCompute for .NET thin client. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16734) Thin 3.0: Implement IgniteCompute interface for Java thin client
[ https://issues.apache.org/jira/browse/IGNITE-16734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-16734: Release Note: Java thin: Added basic Compute functionality. > Thin 3.0: Implement IgniteCompute interface for Java thin client > > > Key: IGNITE-16734 > URL: https://issues.apache.org/jira/browse/IGNITE-16734 > Project: Ignite > Issue Type: New Feature > Components: compute, thin client >Reporter: Igor Sapego >Assignee: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > Time Spent: 10m > Remaining Estimate: 0h > > Need to implement org.apache.ignite.compute.IgniteCompute interface for Java > thin client. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16823) .NET: Thin 3.0: Compute cluster awareness
Pavel Tupitsyn created IGNITE-16823: --- Summary: .NET: Thin 3.0: Compute cluster awareness Key: IGNITE-16823 URL: https://issues.apache.org/jira/browse/IGNITE-16823 Project: Ignite Issue Type: Improvement Components: platforms, thin client Affects Versions: 3.0.0-alpha5 Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: 3.0.0-alpha5 Currently, all Compute operations go through the default node. Improve client compute with cluster awareness: * Correspond client connections with node id (extend handshake) * *Compute.Execute*: match specified set of nodes against active connections. If there are matches, pick random. Otherwise, use default connection and let the server handle node mapping. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (IGNITE-16822) Fix GridCacheLifecycleAwareSelfTest.testLifecycleAware
[ https://issues.apache.org/jira/browse/IGNITE-16822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov reassigned IGNITE-16822: Assignee: Nikolay Izhikov > Fix GridCacheLifecycleAwareSelfTest.testLifecycleAware > -- > > Key: IGNITE-16822 > URL: https://issues.apache.org/jira/browse/IGNITE-16822 > Project: Ignite > Issue Type: Bug >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Minor > > GridCacheLifecycleAwareSelfTest.testLifecycleAware always fail. > Need to fix it > https://ci2.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-5330309473671089592&tab=testDetails -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16822) Fix GridCacheLifecycleAwareSelfTest.testLifecycleAware
Nikolay Izhikov created IGNITE-16822: Summary: Fix GridCacheLifecycleAwareSelfTest.testLifecycleAware Key: IGNITE-16822 URL: https://issues.apache.org/jira/browse/IGNITE-16822 Project: Ignite Issue Type: Bug Reporter: Nikolay Izhikov GridCacheLifecycleAwareSelfTest.testLifecycleAware always fail. Need to fix it https://ci2.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-5330309473671089592&tab=testDetails -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16821) Print collection attributes of the CacheConfiguration
[
https://issues.apache.org/jira/browse/IGNITE-16821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519115#comment-17519115
]
Ignite TC Bot commented on IGNITE-16821:
{panel:title=Branch: [pull/9954/head] Base: [master] : Possible Blockers
(115)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache (Restarts) 1{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6511217]]
{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6511274]]
{color:#d04437}Examples{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6511283]]
{color:#d04437}SPI (Discovery){color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6511303]]
{color:#d04437}SPI{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6511271]]
{color:#d04437}PDS 6{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6511300]]
{color:#d04437}Service Grid{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6511262]]
{color:#d04437}Scala (Examples){color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6511282]]
{color:#d04437}Queries 4 (lazy=true){color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6511310]]
{color:#d04437}RDD{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6511264]]
{color:#d04437}PDS 5{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6511299]]
{color:#d04437}Cache 2{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6511222]]
{color:#d04437}Cache 13{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6511298]]
{color:#d04437}Continuous Query 2{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6511235]]
{color:#d04437}PDS (Compatibility){color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6511255]]
{color:#d04437}Snapshots{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6511288]]
{color:#d04437}Cache 6{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6511225]]
{color:#d04437}Basic 1{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6511207]]
{color:#d04437}Platform .NET (Windows){color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6511201]]
{color:#d04437}Continuous Query 4{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6511237]]
{color:#d04437}Cache 10{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6511295]]
{color:#d04437}Platform .NET (Core Linux){color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6511195]]
{color:#d04437}Calcite SQL{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6511311]]
{color:#d04437}Snapshots With Indexes{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6511289]]
{color:#d04437}Queries 2{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6511270]]
{color:#d04437}JDBC Driver{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6511250]]
{color:#d04437}Cache 5{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6511232]]
{color:#d04437}PDS (Indexing){color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6511268]]
{color:#d04437}Queries 2 (lazy=true){color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6511308]]
{color:#d04437}Queries 3{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6511304]]
{color:#d04437}Java Client{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6511281]]
{color:#d04437}Continuous Query 3{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6511236]]
{color:#d04437}Cache 12{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6511297]]
{color:#d04437}PDS 2{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6511266]]
{color:#d04437}Binary Objects{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6511206]]
{color:#d04437}Start Nodes{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6511284]]
{color:#d04437}Queries 3 (lazy=true){color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6511309]]
{color:#d04437}Thin client: Node.js{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=6511196]]
{color:#d04437}Cache (Deadlock Detection){color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId
[jira] [Commented] (IGNITE-16820) [IEP-80] Removal scalar module
[
https://issues.apache.org/jira/browse/IGNITE-16820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519105#comment-17519105
]
Ignite TC Bot commented on IGNITE-16820:
{panel:title=Branch: [pull/9953/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Scala (Examples){color} [[tests 0 Exit Code
|https://ci2.ignite.apache.org/viewLog.html?buildId=6382189]]
{panel}
{panel:title=Branch: [pull/9953/head] Base: [master] : New Tests
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Calcite SQL{color} [[tests
2|https://ci2.ignite.apache.org/viewLog.html?buildId=6382125]]
* {color:#013220}IgniteCalciteTestSuite: DataTypesTest.testOtherType -
PASSED{color}
* {color:#013220}IgniteCalciteTestSuite: JdbcQueryTest.testOtherType -
PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=6382212&buildTypeId=IgniteTests24Java8_RunAll]
> [IEP-80] Removal scalar module
> --
>
> Key: IGNITE-16820
> URL: https://issues.apache.org/jira/browse/IGNITE-16820
> Project: Ignite
> Issue Type: Improvement
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
> Labels: IEP-80
> Fix For: 2.14
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Scalar module unused and abandoned therefore can be removed
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-13914) wrong error message for bad selector (config get)
[
https://issues.apache.org/jira/browse/IGNITE-13914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-13914:
-
Description:
{code:bash}
x:~/ignite-cli-test$ ./ignite config get --selector=/
Connection issues while trying to send http request{code}
expected:
{code:java}
Can't get configuration{
"error" :
{ "type" : "CONFIG_PATH_UNRECOGNIZED", "message" : "wrong sab path" }}
{code}
was:
{code:bash}
x:~/ignite-cli-test$ ./ignite config get --selector=/
Connection issues while trying to send http request{code}
expected:
{code:java}
Can't get configuration{
"error" :
{ "type" : "CONFIG_PATH_UNRECOGNIZED", "message" : "wrong sab path" }}
{code}
{noformat}
*no* further _formatting_ is done here
{noformat}
> wrong error message for bad selector (config get)
> -
>
> Key: IGNITE-13914
> URL: https://issues.apache.org/jira/browse/IGNITE-13914
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha1
>Reporter: Fedor Malchikov
>Priority: Major
> Labels: ignite-3, ignite-3-cli-tool
>
> {code:bash}
> x:~/ignite-cli-test$ ./ignite config get --selector=/
> Connection issues while trying to send http request{code}
> expected:
> {code:java}
> Can't get configuration{
> "error" :
> { "type" : "CONFIG_PATH_UNRECOGNIZED", "message" : "wrong sab path" }}
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (IGNITE-16821) Print collection attributes of the CacheConfiguration
Stanislav Lukyanov created IGNITE-16821: --- Summary: Print collection attributes of the CacheConfiguration Key: IGNITE-16821 URL: https://issues.apache.org/jira/browse/IGNITE-16821 Project: Ignite Issue Type: Bug Reporter: Stanislav Lukyanov CacheConfiguration.toString() currently doesn't print its array and collection attributes such as query entities or plugin configuration. It would be useful to have all these properties in toString for debug purposes. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (IGNITE-16821) Print collection attributes of the CacheConfiguration
[ https://issues.apache.org/jira/browse/IGNITE-16821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanislav Lukyanov reassigned IGNITE-16821: --- Assignee: Stanislav Lukyanov > Print collection attributes of the CacheConfiguration > - > > Key: IGNITE-16821 > URL: https://issues.apache.org/jira/browse/IGNITE-16821 > Project: Ignite > Issue Type: Bug >Reporter: Stanislav Lukyanov >Assignee: Stanislav Lukyanov >Priority: Trivial > > CacheConfiguration.toString() currently doesn't print its array and > collection attributes such as query entities or plugin configuration. > > It would be useful to have all these properties in toString for debug > purposes. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-13914) wrong error message for bad selector (config get)
[
https://issues.apache.org/jira/browse/IGNITE-13914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-13914:
-
Description:
{code:bash}
x:~/ignite-cli-test$ ./ignite config get --selector=/
Connection issues while trying to send http request{code}
expected:
{code:java}
Can't get configuration{
"error" :
{ "type" : "CONFIG_PATH_UNRECOGNIZED", "message" : "wrong sab path" }}
{code}
{noformat}
*no* further _formatting_ is done here
{noformat}
was:
{code:bash}
x:~/ignite-cli-test$ ./ignite config get --selector=/
Connection issues while trying to send http request{code}
expected:
{code:java}
Can't get configuration{
"error" :
{ "type" : "CONFIG_PATH_UNRECOGNIZED", "message" : "wrong sab path" }}
{code}
> wrong error message for bad selector (config get)
> -
>
> Key: IGNITE-13914
> URL: https://issues.apache.org/jira/browse/IGNITE-13914
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha1
>Reporter: Fedor Malchikov
>Priority: Major
> Labels: ignite-3, ignite-3-cli-tool
>
> {code:bash}
> x:~/ignite-cli-test$ ./ignite config get --selector=/
> Connection issues while trying to send http request{code}
> expected:
> {code:java}
> Can't get configuration{
> "error" :
> { "type" : "CONFIG_PATH_UNRECOGNIZED", "message" : "wrong sab path" }}
> {code}
>
> {noformat}
> *no* further _formatting_ is done here
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-16598) CLI ignores an incorrect repository passed via --repo
[ https://issues.apache.org/jira/browse/IGNITE-16598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-16598: - Description: prom1se@prom1se-PC276:~/apache/ignite-3/modules/cli/target$ ls ~/temp/test ls: cannot access '/home/prom1se/temp/test': No such file or directory prom1se@prom1se-PC276:~/apache/ignite-3/modules/cli/target$ ./ignite init --repo=file:~/temp/test Creating directories... Done! +++ | Binaries Directory | /home/prom1se/apache/ignite-3/modules/cli/target/ignite-bin| +++ | Work Directory | /home/prom1se/apache/ignite-3/modules/cli/target/ignite-work | +++ | Config Directory | /home/prom1se/apache/ignite-3/modules/cli/target/ignite-config | +++ | Log Directory | /home/prom1se/apache/ignite-3/modules/cli/target/ignite-log| +++ Installing org.apache.ignite:ignite-runner:3.0.0-SNAPSHOT... |=> | 6%^C No errors or warnings, the cli immediately started initialization from the local maven cache. It seems to me that this behavior is incorrect, and the utility should stop working in case of an incorrectly passed repo parameter. Otherwise, the user may get the wrong version of the product that he expects. was: prom1se@prom1se-PC276:~/apache/ignite-3/modules/cli/target$ ls ~/temp/test ls: cannot access '/home/prom1se/temp/test': No such file or directory prom1se@prom1se-PC276:~/apache/ignite-3/modules/cli/target$ ./ignite init --repo=file:~/temp/test Creating directories... Done! +++ | Binaries Directory | /home/prom1se/apache/ignite-3/modules/cli/target/ignite-bin| +++ | Work Directory | /home/prom1se/apache/ignite-3/modules/cli/target/ignite-work | +++ | Config Directory | /home/prom1se/apache/ignite-3/modules/cli/target/ignite-config | +++ | Log Directory | /home/prom1se/apache/ignite-3/modules/cli/target/ignite-log| +++ Installing org.apache.ignite:ignite-runner:3.0.0-SNAPSHOT... |=> | 6%^C No errors or warnings, the cli immediately started initialization from the local maven cache. It seems to me that this behavior is incorrect, and the utility should stop working in case of an incorrectly passed repo parameter. Otherwise, the user may get the wrong version of the product that he expects. > CLI ignores an incorrect repository passed via --repo > - > > Key: IGNITE-16598 > URL: https://issues.apache.org/jira/browse/IGNITE-16598 > Project: Ignite > Issue Type: Bug >Affects Versions: 3.0.0-alpha4 >Reporter: Fedor Malchikov >Priority: Critical > Labels: ignite-3, ignite-3-cli-tool > > prom1se@prom1se-PC276:~/apache/ignite-3/modules/cli/target$ ls ~/temp/test > ls: cannot access '/home/prom1se/temp/test': No such file or directory > prom1se@prom1se-PC276:~/apache/ignite-3/modules/cli/target$ ./ignite init > --repo=file:~/temp/test > Creating directories... Done! > +++ > | Binaries Directory | > /home/prom1se/apache/ignite-3/modules/cli/target/ignite-bin| > +++ > | Work Directory | > /home/prom1se/apache/ignite-3/modules/cli/target/ignite-work | > +++ > | Config Directory | > /home/prom1se/apache/ignite-3/modules/cli/target/ignite-config | > +++ > | Log Directory | > /home/prom1se/apache/ignite-3/modules/cli/target/ignite-log| > +++ > Installing org.apache.ignite:ignite-runner:3.0.0-SNAPSHOT... > |=>
[jira] [Updated] (IGNITE-16598) CLI ignores an incorrect repository passed via --repo
[ https://issues.apache.org/jira/browse/IGNITE-16598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-16598: - Description: prom1se@prom1se-PC276:~/apache/ignite-3/modules/cli/target$ ls ~/temp/test ls: cannot access '/home/prom1se/temp/test': No such file or directory prom1se@prom1se-PC276:~/apache/ignite-3/modules/cli/target$ ./ignite init --repo=file:~/temp/test Creating directories... Done! +++ | Binaries Directory | /home/prom1se/apache/ignite-3/modules/cli/target/ignite-bin| +++ | Work Directory | /home/prom1se/apache/ignite-3/modules/cli/target/ignite-work | +++ | Config Directory | /home/prom1se/apache/ignite-3/modules/cli/target/ignite-config | +++ | Log Directory | /home/prom1se/apache/ignite-3/modules/cli/target/ignite-log| +++ Installing org.apache.ignite:ignite-runner:3.0.0-SNAPSHOT... |=> | 6%^C No errors or warnings, the cli immediately started initialization from the local maven cache. It seems to me that this behavior is incorrect, and the utility should stop working in case of an incorrectly passed repo parameter. Otherwise, the user may get the wrong version of the product that he expects... was: prom1se@prom1se-PC276:~/apache/ignite-3/modules/cli/target$ ls ~/temp/test ls: cannot access '/home/prom1se/temp/test': No such file or directory prom1se@prom1se-PC276:~/apache/ignite-3/modules/cli/target$ ./ignite init --repo=file:~/temp/test Creating directories... Done! +++ | Binaries Directory | /home/prom1se/apache/ignite-3/modules/cli/target/ignite-bin| +++ | Work Directory | /home/prom1se/apache/ignite-3/modules/cli/target/ignite-work | +++ | Config Directory | /home/prom1se/apache/ignite-3/modules/cli/target/ignite-config | +++ | Log Directory | /home/prom1se/apache/ignite-3/modules/cli/target/ignite-log| +++ Installing org.apache.ignite:ignite-runner:3.0.0-SNAPSHOT... |=> | 6%^C No errors or warnings, the cli immediately started initialization from the local maven cache. It seems to me that this behavior is incorrect, and the utility should stop working in case of an incorrectly passed repo parameter. Otherwise, the user may get the wrong version of the product that he expects. > CLI ignores an incorrect repository passed via --repo > - > > Key: IGNITE-16598 > URL: https://issues.apache.org/jira/browse/IGNITE-16598 > Project: Ignite > Issue Type: Bug >Affects Versions: 3.0.0-alpha4 >Reporter: Fedor Malchikov >Priority: Critical > Labels: ignite-3, ignite-3-cli-tool > > prom1se@prom1se-PC276:~/apache/ignite-3/modules/cli/target$ ls ~/temp/test > ls: cannot access '/home/prom1se/temp/test': No such file or directory > prom1se@prom1se-PC276:~/apache/ignite-3/modules/cli/target$ ./ignite init > --repo=file:~/temp/test > Creating directories... Done! > +++ > | Binaries Directory | > /home/prom1se/apache/ignite-3/modules/cli/target/ignite-bin| > +++ > | Work Directory | > /home/prom1se/apache/ignite-3/modules/cli/target/ignite-work | > +++ > | Config Directory | > /home/prom1se/apache/ignite-3/modules/cli/target/ignite-config | > +++ > | Log Directory | > /home/prom1se/apache/ignite-3/modules/cli/target/ignite-log| > +++ > Installing org.apache.ignite:ignite-runner:3.0.0-SNAPSHOT... > |=>
[jira] [Updated] (IGNITE-16601) The CLI uses a direct java call to run the node ignoring the JAVA_HOME variable.
[
https://issues.apache.org/jira/browse/IGNITE-16601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-16601:
-
Description:
As a result, working on environments where java is not directly installed or
several versions of java are used is significantly complicated. As far as I
know, in version 2, overriding java_home was the main method of switching
between java versions in the system.
was:
As a result, working on environments where java is not directly installed or
several versions of java are used is significantly complicated. As far as I
know, in version 2, overriding java_home was the main method of switching
between java versions in the system.
{noformat}
*no* further _formatting_ is done here
{noformat}
> The CLI uses a direct java call to run the node ignoring the JAVA_HOME
> variable.
>
>
> Key: IGNITE-16601
> URL: https://issues.apache.org/jira/browse/IGNITE-16601
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha4
>Reporter: Fedor Malchikov
>Priority: Blocker
> Labels: ignite-3, ignite-3-cli-tool
>
> As a result, working on environments where java is not directly installed or
> several versions of java are used is significantly complicated. As far as I
> know, in version 2, overriding java_home was the main method of switching
> between java versions in the system.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Resolved] (IGNITE-16813) Update pom dependencies to 2.14.0-SNAPSHOT version
[ https://issues.apache.org/jira/browse/IGNITE-16813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita resolved IGNITE-16813. -- Resolution: Fixed Merged into the master. > Update pom dependencies to 2.14.0-SNAPSHOT version > -- > > Key: IGNITE-16813 > URL: https://issues.apache.org/jira/browse/IGNITE-16813 > Project: Ignite > Issue Type: Task >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > The pom dependencies must be updated due to the ignite-2.13 branch has been > created. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16813) Update pom dependencies to 2.14.0-SNAPSHOT version
[
https://issues.apache.org/jira/browse/IGNITE-16813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519026#comment-17519026
]
Ignite TC Bot commented on IGNITE-16813:
{panel:title=Branch: [pull/9949/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9949/head] Base: [master] : New Tests
(4)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}PDS (Compatibility){color} [[tests
4|https://ci2.ignite.apache.org/viewLog.html?buildId=6381956]]
* {color:#013220}IgniteCompatibilityBasicTestSuite:
JdbcThinCompatibilityTest.testOldClientToCurrentServer[Version 2.14.0-SNAPSHOT]
- PASSED{color}
* {color:#013220}IgniteCompatibilityBasicTestSuite:
JavaThinCompatibilityTest.testCurrentClientToOldServer[Version 2.14.0-SNAPSHOT]
- PASSED{color}
* {color:#013220}IgniteCompatibilityBasicTestSuite:
JavaThinCompatibilityTest.testOldClientToCurrentServer[Version 2.14.0-SNAPSHOT]
- PASSED{color}
* {color:#013220}IgniteCompatibilityBasicTestSuite:
JdbcThinCompatibilityTest.testCurrentClientToOldServer[Version 2.14.0-SNAPSHOT]
- PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=6381997&buildTypeId=IgniteTests24Java8_RunAll]
> Update pom dependencies to 2.14.0-SNAPSHOT version
> --
>
> Key: IGNITE-16813
> URL: https://issues.apache.org/jira/browse/IGNITE-16813
> Project: Ignite
> Issue Type: Task
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Major
> Fix For: 2.14
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The pom dependencies must be updated due to the ignite-2.13 branch has been
> created.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-16601) The CLI uses a direct java call to run the node ignoring the JAVA_HOME variable.
[
https://issues.apache.org/jira/browse/IGNITE-16601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-16601:
-
Description:
As a result, working on environments where java is not directly installed or
several versions of java are used is significantly complicated. As far as I
know, in version 2, overriding java_home was the main method of switching
between java versions in the system.
{noformat}
*no* further _formatting_ is done here
{noformat}
was:As a result, working on environments where java is not directly installed
or several versions of java are used is significantly complicated. As far as I
know, in version 2, overriding java_home was the main method of switching
between java versions in the system.
> The CLI uses a direct java call to run the node ignoring the JAVA_HOME
> variable.
>
>
> Key: IGNITE-16601
> URL: https://issues.apache.org/jira/browse/IGNITE-16601
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha4
>Reporter: Fedor Malchikov
>Priority: Blocker
> Labels: ignite-3, ignite-3-cli-tool
>
> As a result, working on environments where java is not directly installed or
> several versions of java are used is significantly complicated. As far as I
> know, in version 2, overriding java_home was the main method of switching
> between java versions in the system.
> {noformat}
> *no* further _formatting_ is done here
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-16601) The CLI uses a direct java call to run the node ignoring the JAVA_HOME variable.
[ https://issues.apache.org/jira/browse/IGNITE-16601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-16601: - Epic Link: (was: IGNITE-16807) > The CLI uses a direct java call to run the node ignoring the JAVA_HOME > variable. > > > Key: IGNITE-16601 > URL: https://issues.apache.org/jira/browse/IGNITE-16601 > Project: Ignite > Issue Type: Bug >Affects Versions: 3.0.0-alpha4 >Reporter: Fedor Malchikov >Priority: Blocker > Labels: ignite-3, ignite-3-cli-tool > > As a result, working on environments where java is not directly installed or > several versions of java are used is significantly complicated. As far as I > know, in version 2, overriding java_home was the main method of switching > between java versions in the system. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16807) Ignite 3 Command Line Interface
[
https://issues.apache.org/jira/browse/IGNITE-16807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-16807:
-
Description:
Requirements - TBD
was:
Requirements - TBD
{noformat}
*no* further _formatting_ is done here
{noformat}
> Ignite 3 Command Line Interface
> ---
>
> Key: IGNITE-16807
> URL: https://issues.apache.org/jira/browse/IGNITE-16807
> Project: Ignite
> Issue Type: Epic
>Reporter: Vyacheslav Koptilin
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Labels: ignite-3-cli-tool
>
> Requirements - TBD
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-16598) CLI ignores an incorrect repository passed via --repo
[ https://issues.apache.org/jira/browse/IGNITE-16598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-16598: - Epic Link: (was: IGNITE-16807) > CLI ignores an incorrect repository passed via --repo > - > > Key: IGNITE-16598 > URL: https://issues.apache.org/jira/browse/IGNITE-16598 > Project: Ignite > Issue Type: Bug >Affects Versions: 3.0.0-alpha4 >Reporter: Fedor Malchikov >Priority: Critical > Labels: ignite-3, ignite-3-cli-tool > > prom1se@prom1se-PC276:~/apache/ignite-3/modules/cli/target$ ls ~/temp/test > ls: cannot access '/home/prom1se/temp/test': No such file or directory > prom1se@prom1se-PC276:~/apache/ignite-3/modules/cli/target$ ./ignite init > --repo=file:~/temp/test > Creating directories... Done! > +++ > | Binaries Directory | > /home/prom1se/apache/ignite-3/modules/cli/target/ignite-bin| > +++ > | Work Directory | > /home/prom1se/apache/ignite-3/modules/cli/target/ignite-work | > +++ > | Config Directory | > /home/prom1se/apache/ignite-3/modules/cli/target/ignite-config | > +++ > | Log Directory | > /home/prom1se/apache/ignite-3/modules/cli/target/ignite-log| > +++ > Installing org.apache.ignite:ignite-runner:3.0.0-SNAPSHOT... > |=> > | 6%^C > No errors or warnings, the cli immediately started initialization from the > local maven cache. > It seems to me that this behavior is incorrect, and the utility should stop > working in case of an incorrectly passed repo parameter. Otherwise, the user > may get the wrong version of the product that he expects. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-13914) wrong error message for bad selector (config get)
[
https://issues.apache.org/jira/browse/IGNITE-13914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-13914:
-
Epic Link: (was: IGNITE-16807)
> wrong error message for bad selector (config get)
> -
>
> Key: IGNITE-13914
> URL: https://issues.apache.org/jira/browse/IGNITE-13914
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha1
>Reporter: Fedor Malchikov
>Priority: Major
> Labels: ignite-3, ignite-3-cli-tool
>
> {code:bash}
> x:~/ignite-cli-test$ ./ignite config get --selector=/
> Connection issues while trying to send http request{code}
> expected:
> {code:java}
> Can't get configuration{
> "error" :
> { "type" : "CONFIG_PATH_UNRECOGNIZED", "message" : "wrong sab path" }}
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-13914) wrong error message for bad selector (config get)
[
https://issues.apache.org/jira/browse/IGNITE-13914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-13914:
-
Description:
{code:bash}
x:~/ignite-cli-test$ ./ignite config get --selector=/
Connection issues while trying to send http request{code}
expected:
{code:java}
Can't get configuration{
"error" :
{ "type" : "CONFIG_PATH_UNRECOGNIZED", "message" : "wrong sab path" }}
{code}
was:
{code:bash}
x:~/ignite-cli-test$ ./ignite config get --selector=/
Connection issues while trying to send http request{code}
expected:
{code:java}
Can't get configuration{
"error" :
{ "type" : "CONFIG_PATH_UNRECOGNIZED", "message" : "wrong sab path" }}
{code}
{noformat}
*no* further _formatting_ is done here
{noformat}
> wrong error message for bad selector (config get)
> -
>
> Key: IGNITE-13914
> URL: https://issues.apache.org/jira/browse/IGNITE-13914
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha1
>Reporter: Fedor Malchikov
>Priority: Major
> Labels: ignite-3, ignite-3-cli-tool
>
> {code:bash}
> x:~/ignite-cli-test$ ./ignite config get --selector=/
> Connection issues while trying to send http request{code}
> expected:
> {code:java}
> Can't get configuration{
> "error" :
> { "type" : "CONFIG_PATH_UNRECOGNIZED", "message" : "wrong sab path" }}
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] (IGNITE-16598) CLI ignores an incorrect repository passed via --repo
[ https://issues.apache.org/jira/browse/IGNITE-16598 ]
Vyacheslav Koptilin deleted comment on IGNITE-16598:
--
was (Author: slava.koptilin):
{noformat}
*no* further _formatting_ is done here
{noformat}
> CLI ignores an incorrect repository passed via --repo
> -
>
> Key: IGNITE-16598
> URL: https://issues.apache.org/jira/browse/IGNITE-16598
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha4
>Reporter: Fedor Malchikov
>Priority: Critical
> Labels: ignite-3, ignite-3-cli-tool
>
> prom1se@prom1se-PC276:~/apache/ignite-3/modules/cli/target$ ls ~/temp/test
> ls: cannot access '/home/prom1se/temp/test': No such file or directory
> prom1se@prom1se-PC276:~/apache/ignite-3/modules/cli/target$ ./ignite init
> --repo=file:~/temp/test
> Creating directories... Done!
> +++
> | Binaries Directory |
> /home/prom1se/apache/ignite-3/modules/cli/target/ignite-bin|
> +++
> | Work Directory |
> /home/prom1se/apache/ignite-3/modules/cli/target/ignite-work |
> +++
> | Config Directory |
> /home/prom1se/apache/ignite-3/modules/cli/target/ignite-config |
> +++
> | Log Directory |
> /home/prom1se/apache/ignite-3/modules/cli/target/ignite-log|
> +++
> Installing org.apache.ignite:ignite-runner:3.0.0-SNAPSHOT...
> |=>
> | 6%^C
> No errors or warnings, the cli immediately started initialization from the
> local maven cache.
> It seems to me that this behavior is incorrect, and the utility should stop
> working in case of an incorrectly passed repo parameter. Otherwise, the user
> may get the wrong version of the product that he expects.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-13914) wrong error message for bad selector (config get)
[
https://issues.apache.org/jira/browse/IGNITE-13914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-13914:
-
Description:
{code:bash}
x:~/ignite-cli-test$ ./ignite config get --selector=/
Connection issues while trying to send http request{code}
expected:
{code:java}
Can't get configuration{
"error" :
{ "type" : "CONFIG_PATH_UNRECOGNIZED", "message" : "wrong sab path" }}
{code}
{noformat}
*no* further _formatting_ is done here
{noformat}
was:
{code:bash}
x:~/ignite-cli-test$ ./ignite config get --selector=/
Connection issues while trying to send http request{code}
expected:
{code:java}
Can't get configuration{
"error" :
{ "type" : "CONFIG_PATH_UNRECOGNIZED", "message" : "wrong sab path" }}
{code}
{noformat}
*no* further _formatting_ is done here
{noformat}
> wrong error message for bad selector (config get)
> -
>
> Key: IGNITE-13914
> URL: https://issues.apache.org/jira/browse/IGNITE-13914
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha1
>Reporter: Fedor Malchikov
>Priority: Major
> Labels: ignite-3, ignite-3-cli-tool
>
> {code:bash}
> x:~/ignite-cli-test$ ./ignite config get --selector=/
> Connection issues while trying to send http request{code}
> expected:
> {code:java}
> Can't get configuration{
> "error" :
> { "type" : "CONFIG_PATH_UNRECOGNIZED", "message" : "wrong sab path" }}
> {code}
> {noformat}
> *no* further _formatting_ is done here
> {noformat}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-13914) wrong error message for bad selector (config get)
[
https://issues.apache.org/jira/browse/IGNITE-13914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-13914:
-
Description:
{code:bash}
x:~/ignite-cli-test$ ./ignite config get --selector=/
Connection issues while trying to send http request{code}
expected:
{code:java}
Can't get configuration{
"error" :
{ "type" : "CONFIG_PATH_UNRECOGNIZED", "message" : "wrong sab path" }}
{code}
{noformat}
*no* further _formatting_ is done here
{noformat}
was:
{code:bash}
x:~/ignite-cli-test$ ./ignite config get --selector=/
Connection issues while trying to send http request{code}
expected:
{code:java}
Can't get configuration{
"error" :
{ "type" : "CONFIG_PATH_UNRECOGNIZED", "message" : "wrong sab path" }}
{code}
> wrong error message for bad selector (config get)
> -
>
> Key: IGNITE-13914
> URL: https://issues.apache.org/jira/browse/IGNITE-13914
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha1
>Reporter: Fedor Malchikov
>Priority: Major
> Labels: ignite-3, ignite-3-cli-tool
>
> {code:bash}
> x:~/ignite-cli-test$ ./ignite config get --selector=/
> Connection issues while trying to send http request{code}
> expected:
> {code:java}
> Can't get configuration{
> "error" :
> { "type" : "CONFIG_PATH_UNRECOGNIZED", "message" : "wrong sab path" }}
> {code}
> {noformat}
> *no* further _formatting_ is done here
> {noformat}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-13914) wrong error message for bad selector (config get)
[
https://issues.apache.org/jira/browse/IGNITE-13914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-13914:
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> wrong error message for bad selector (config get)
> -
>
> Key: IGNITE-13914
> URL: https://issues.apache.org/jira/browse/IGNITE-13914
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha1
>Reporter: Fedor Malchikov
>Priority: Major
> Labels: ignite-3, ignite-3-cli-tool
>
> {code:bash}
> x:~/ignite-cli-test$ ./ignite config get --selector=/
> Connection issues while trying to send http request{code}
> expected:
> {code:java}
> Can't get configuration{
> "error" :
> { "type" : "CONFIG_PATH_UNRECOGNIZED", "message" : "wrong sab path" }}
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-13914) wrong error message for bad selector (config get)
[
https://issues.apache.org/jira/browse/IGNITE-13914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-13914:
-
Epic Link: IGNITE-16807
> wrong error message for bad selector (config get)
> -
>
> Key: IGNITE-13914
> URL: https://issues.apache.org/jira/browse/IGNITE-13914
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha1
>Reporter: Fedor Malchikov
>Priority: Major
> Labels: ignite-3, ignite-3-cli-tool
>
> {code:bash}
> x:~/ignite-cli-test$ ./ignite config get --selector=/
> Connection issues while trying to send http request{code}
> expected:
> {code:java}
> Can't get configuration{
> "error" :
> { "type" : "CONFIG_PATH_UNRECOGNIZED", "message" : "wrong sab path" }}
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-16598) CLI ignores an incorrect repository passed via --repo
[
https://issues.apache.org/jira/browse/IGNITE-16598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17518975#comment-17518975
]
Vyacheslav Koptilin commented on IGNITE-16598:
--
{noformat}
*no* further _formatting_ is done here
{noformat}
> CLI ignores an incorrect repository passed via --repo
> -
>
> Key: IGNITE-16598
> URL: https://issues.apache.org/jira/browse/IGNITE-16598
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha4
>Reporter: Fedor Malchikov
>Priority: Critical
> Labels: ignite-3, ignite-3-cli-tool
>
> prom1se@prom1se-PC276:~/apache/ignite-3/modules/cli/target$ ls ~/temp/test
> ls: cannot access '/home/prom1se/temp/test': No such file or directory
> prom1se@prom1se-PC276:~/apache/ignite-3/modules/cli/target$ ./ignite init
> --repo=file:~/temp/test
> Creating directories... Done!
> +++
> | Binaries Directory |
> /home/prom1se/apache/ignite-3/modules/cli/target/ignite-bin|
> +++
> | Work Directory |
> /home/prom1se/apache/ignite-3/modules/cli/target/ignite-work |
> +++
> | Config Directory |
> /home/prom1se/apache/ignite-3/modules/cli/target/ignite-config |
> +++
> | Log Directory |
> /home/prom1se/apache/ignite-3/modules/cli/target/ignite-log|
> +++
> Installing org.apache.ignite:ignite-runner:3.0.0-SNAPSHOT...
> |=>
> | 6%^C
> No errors or warnings, the cli immediately started initialization from the
> local maven cache.
> It seems to me that this behavior is incorrect, and the utility should stop
> working in case of an incorrectly passed repo parameter. Otherwise, the user
> may get the wrong version of the product that he expects.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-16601) The CLI uses a direct java call to run the node ignoring the JAVA_HOME variable.
[ https://issues.apache.org/jira/browse/IGNITE-16601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-16601: - Epic Link: IGNITE-16807 > The CLI uses a direct java call to run the node ignoring the JAVA_HOME > variable. > > > Key: IGNITE-16601 > URL: https://issues.apache.org/jira/browse/IGNITE-16601 > Project: Ignite > Issue Type: Bug >Affects Versions: 3.0.0-alpha4 >Reporter: Fedor Malchikov >Priority: Blocker > Labels: ignite-3, ignite-3-cli-tool > > As a result, working on environments where java is not directly installed or > several versions of java are used is significantly complicated. As far as I > know, in version 2, overriding java_home was the main method of switching > between java versions in the system. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16598) CLI ignores an incorrect repository passed via --repo
[ https://issues.apache.org/jira/browse/IGNITE-16598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-16598: - Epic Link: IGNITE-16807 > CLI ignores an incorrect repository passed via --repo > - > > Key: IGNITE-16598 > URL: https://issues.apache.org/jira/browse/IGNITE-16598 > Project: Ignite > Issue Type: Bug >Affects Versions: 3.0.0-alpha4 >Reporter: Fedor Malchikov >Priority: Critical > Labels: ignite-3, ignite-3-cli-tool > > prom1se@prom1se-PC276:~/apache/ignite-3/modules/cli/target$ ls ~/temp/test > ls: cannot access '/home/prom1se/temp/test': No such file or directory > prom1se@prom1se-PC276:~/apache/ignite-3/modules/cli/target$ ./ignite init > --repo=file:~/temp/test > Creating directories... Done! > +++ > | Binaries Directory | > /home/prom1se/apache/ignite-3/modules/cli/target/ignite-bin| > +++ > | Work Directory | > /home/prom1se/apache/ignite-3/modules/cli/target/ignite-work | > +++ > | Config Directory | > /home/prom1se/apache/ignite-3/modules/cli/target/ignite-config | > +++ > | Log Directory | > /home/prom1se/apache/ignite-3/modules/cli/target/ignite-log| > +++ > Installing org.apache.ignite:ignite-runner:3.0.0-SNAPSHOT... > |=> > | 6%^C > No errors or warnings, the cli immediately started initialization from the > local maven cache. > It seems to me that this behavior is incorrect, and the utility should stop > working in case of an incorrectly passed repo parameter. Otherwise, the user > may get the wrong version of the product that he expects. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16807) Ignite 3 Command Line Interface
[
https://issues.apache.org/jira/browse/IGNITE-16807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-16807:
-
Description:
Requirements - TBD
{noformat}
*no* further _formatting_ is done here
{noformat}
was:Requirements - TBD.
> Ignite 3 Command Line Interface
> ---
>
> Key: IGNITE-16807
> URL: https://issues.apache.org/jira/browse/IGNITE-16807
> Project: Ignite
> Issue Type: Epic
>Reporter: Vyacheslav Koptilin
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Labels: ignite-3-cli-tool
>
> Requirements - TBD
> {noformat}
> *no* further _formatting_ is done here
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-16820) [IEP-80] Removal scalar module
[ https://issues.apache.org/jira/browse/IGNITE-16820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-16820: - Release Note: Removed scalar module (was: Removed the legacy service grid implementation) > [IEP-80] Removal scalar module > -- > > Key: IGNITE-16820 > URL: https://issues.apache.org/jira/browse/IGNITE-16820 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-80 > Fix For: 2.13 > > > Scalar module unused and abandoned therefore can be removed -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16820) [IEP-80] Removal scalar module
[ https://issues.apache.org/jira/browse/IGNITE-16820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-16820: - Labels: IEP-80 (was: IEP-80 important) > [IEP-80] Removal scalar module > -- > > Key: IGNITE-16820 > URL: https://issues.apache.org/jira/browse/IGNITE-16820 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-80 > Fix For: 2.13 > > > Scalar module unused and abandoned therefore can be removed -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16820) [IEP-80] Removal scalar module
[ https://issues.apache.org/jira/browse/IGNITE-16820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-16820: - Fix Version/s: 2.14 (was: 2.13) > [IEP-80] Removal scalar module > -- > > Key: IGNITE-16820 > URL: https://issues.apache.org/jira/browse/IGNITE-16820 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-80 > Fix For: 2.14 > > > Scalar module unused and abandoned therefore can be removed -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16820) [IEP-80] Removal scalar module
[ https://issues.apache.org/jira/browse/IGNITE-16820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-16820: - Description: Scalar module unused and abandoned therefore can be removed (was: Legacy service grid implementation are based on internal cache and has many known limitation and bugs. There are new service grid implementation based on discovery API that existed several releases. Legacy implementation should be removed in 2.13) > [IEP-80] Removal scalar module > -- > > Key: IGNITE-16820 > URL: https://issues.apache.org/jira/browse/IGNITE-16820 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-80, important > Fix For: 2.13 > > > Scalar module unused and abandoned therefore can be removed -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (IGNITE-16820) [IEP-80] Removal scalar module
[ https://issues.apache.org/jira/browse/IGNITE-16820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov reassigned IGNITE-16820: Assignee: Nikolay Izhikov (was: Maxim Muzafarov) > [IEP-80] Removal scalar module > -- > > Key: IGNITE-16820 > URL: https://issues.apache.org/jira/browse/IGNITE-16820 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-80, important > Fix For: 2.13 > > > Legacy service grid implementation are based on internal cache and has many > known limitation and bugs. > There are new service grid implementation based on discovery API that existed > several releases. > Legacy implementation should be removed in 2.13 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16820) [IEP-80] Removal scalar module
Nikolay Izhikov created IGNITE-16820: Summary: [IEP-80] Removal scalar module Key: IGNITE-16820 URL: https://issues.apache.org/jira/browse/IGNITE-16820 Project: Ignite Issue Type: Improvement Reporter: Nikolay Izhikov Assignee: Maxim Muzafarov Fix For: 2.13 Legacy service grid implementation are based on internal cache and has many known limitation and bugs. There are new service grid implementation based on discovery API that existed several releases. Legacy implementation should be removed in 2.13 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16819) Handle case when cluster state is empty after local recovery
Aleksandr Polovtcev created IGNITE-16819: Summary: Handle case when cluster state is empty after local recovery Key: IGNITE-16819 URL: https://issues.apache.org/jira/browse/IGNITE-16819 Project: Ignite Issue Type: Task Reporter: Aleksandr Polovtcev Assignee: Aleksandr Polovtcev If a local state can be found in the Vault, but the Raft Cluster State is empty, it means that the CMG leader failed to write the state after the initialization. In this case Raft service should not be started during local recovery and an error should be logged. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16807) Ignite 3 Command Line Interface
[ https://issues.apache.org/jira/browse/IGNITE-16807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-16807: - Description: Requirements - TBD. (was: Requirements - TBD) > Ignite 3 Command Line Interface > --- > > Key: IGNITE-16807 > URL: https://issues.apache.org/jira/browse/IGNITE-16807 > Project: Ignite > Issue Type: Epic >Reporter: Vyacheslav Koptilin >Assignee: Vyacheslav Koptilin >Priority: Major > Labels: ignite-3-cli-tool > > Requirements - TBD. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16598) CLI ignores an incorrect repository passed via --repo
[ https://issues.apache.org/jira/browse/IGNITE-16598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-16598: - Epic Link: (was: IGNITE-16807) > CLI ignores an incorrect repository passed via --repo > - > > Key: IGNITE-16598 > URL: https://issues.apache.org/jira/browse/IGNITE-16598 > Project: Ignite > Issue Type: Bug >Affects Versions: 3.0.0-alpha4 >Reporter: Fedor Malchikov >Priority: Critical > Labels: ignite-3, ignite-3-cli-tool > > prom1se@prom1se-PC276:~/apache/ignite-3/modules/cli/target$ ls ~/temp/test > ls: cannot access '/home/prom1se/temp/test': No such file or directory > prom1se@prom1se-PC276:~/apache/ignite-3/modules/cli/target$ ./ignite init > --repo=file:~/temp/test > Creating directories... Done! > +++ > | Binaries Directory | > /home/prom1se/apache/ignite-3/modules/cli/target/ignite-bin| > +++ > | Work Directory | > /home/prom1se/apache/ignite-3/modules/cli/target/ignite-work | > +++ > | Config Directory | > /home/prom1se/apache/ignite-3/modules/cli/target/ignite-config | > +++ > | Log Directory | > /home/prom1se/apache/ignite-3/modules/cli/target/ignite-log| > +++ > Installing org.apache.ignite:ignite-runner:3.0.0-SNAPSHOT... > |=> > | 6%^C > No errors or warnings, the cli immediately started initialization from the > local maven cache. > It seems to me that this behavior is incorrect, and the utility should stop > working in case of an incorrectly passed repo parameter. Otherwise, the user > may get the wrong version of the product that he expects. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16601) The CLI uses a direct java call to run the node ignoring the JAVA_HOME variable.
[ https://issues.apache.org/jira/browse/IGNITE-16601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-16601: - Epic Link: (was: IGNITE-16807) > The CLI uses a direct java call to run the node ignoring the JAVA_HOME > variable. > > > Key: IGNITE-16601 > URL: https://issues.apache.org/jira/browse/IGNITE-16601 > Project: Ignite > Issue Type: Bug >Affects Versions: 3.0.0-alpha4 >Reporter: Fedor Malchikov >Priority: Blocker > Labels: ignite-3, ignite-3-cli-tool > > As a result, working on environments where java is not directly installed or > several versions of java are used is significantly complicated. As far as I > know, in version 2, overriding java_home was the main method of switching > between java versions in the system. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (IGNITE-10456) Lost data in cache during restart node
[ https://issues.apache.org/jira/browse/IGNITE-10456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita resolved IGNITE-10456. -- Resolution: Won't Fix The test is not flaky: https://ci.ignite.apache.org/test/-5440530939858694701?currentProjectId=IgniteTests24Java8&branch=%3Cdefault%3E > Lost data in cache during restart node > -- > > Key: IGNITE-10456 > URL: https://issues.apache.org/jira/browse/IGNITE-10456 > Project: Ignite > Issue Type: Test >Reporter: Ivan Fedotov >Priority: Major > > [testGetRestartPartitioned2|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-5440530939858694701&tab=testDetails] > looks like flaky: [assertion > error|https://github.com/apache/ignite/blob/master/modules/core/src/test/java/org/apache/ignite/internal/processors/cache/distributed/IgniteCacheGetRestartTest.java#L188] > sometimed arrises during restart nodes in the other thread. > It seems that some data in cache was lost. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-15628) Get rid of waitForTopology method from ITNodeTest
[
https://issues.apache.org/jira/browse/IGNITE-15628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Chudov updated IGNITE-15628:
--
Labels: ignite-3 tech-debt test-fail (was: ignite-3 tech-debt)
> Get rid of waitForTopology method from ITNodeTest
> -
>
> Key: IGNITE-15628
> URL: https://issues.apache.org/jira/browse/IGNITE-15628
> Project: Ignite
> Issue Type: Improvement
>Reporter: Mirza Aliev
>Assignee: Denis Chudov
>Priority: Major
> Labels: ignite-3, tech-debt, test-fail
>
> Get rid of {{waitForTopology}} method from
> {{org.apache.ignite.raft.jraft.core.ITNodeTest}}
> Ticket was created after decompostion of
> https://issues.apache.org/jira/browse/IGNITE-14832
> See todo on {{org.apache.ignite.raft.jraft.core.ITNodeTest#waitForTopology}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-16509) Calcite engine. Support OTHER data type
[
https://issues.apache.org/jira/browse/IGNITE-16509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov updated IGNITE-16509:
---
Fix Version/s: 2.13
> Calcite engine. Support OTHER data type
> ---
>
> Key: IGNITE-16509
> URL: https://issues.apache.org/jira/browse/IGNITE-16509
> Project: Ignite
> Issue Type: New Feature
>Reporter: Aleksey Plekhanov
>Assignee: Vladimir Steshin
>Priority: Major
> Labels: calcite, calcite3-required
> Fix For: 2.13
>
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> Table with {{OTHER}} (Object) data type can be created by H2-based SQL engine:
> {noformat}
> CREATE TABLE t(val OTHER)
> {noformat}
> But such a data type is not supported by Calcite-based SQL engine (at least
> in DDL)
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-16509) Calcite engine. Support OTHER data type
[
https://issues.apache.org/jira/browse/IGNITE-16509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov updated IGNITE-16509:
---
Labels: calcite calcite3-required (was: calcite calcite2-required
calcite3-required)
> Calcite engine. Support OTHER data type
> ---
>
> Key: IGNITE-16509
> URL: https://issues.apache.org/jira/browse/IGNITE-16509
> Project: Ignite
> Issue Type: New Feature
>Reporter: Aleksey Plekhanov
>Assignee: Vladimir Steshin
>Priority: Major
> Labels: calcite, calcite3-required
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> Table with {{OTHER}} (Object) data type can be created by H2-based SQL engine:
> {noformat}
> CREATE TABLE t(val OTHER)
> {noformat}
> But such a data type is not supported by Calcite-based SQL engine (at least
> in DDL)
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-16509) Calcite engine. Support OTHER data type
[
https://issues.apache.org/jira/browse/IGNITE-16509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17518941#comment-17518941
]
Aleksey Plekhanov commented on IGNITE-16509:
[~vladsz83], LGTM, merged to master, cherry picked to 2.13. Thanks for the
contribution!
> Calcite engine. Support OTHER data type
> ---
>
> Key: IGNITE-16509
> URL: https://issues.apache.org/jira/browse/IGNITE-16509
> Project: Ignite
> Issue Type: New Feature
>Reporter: Aleksey Plekhanov
>Assignee: Vladimir Steshin
>Priority: Major
> Labels: calcite, calcite2-required, calcite3-required
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> Table with {{OTHER}} (Object) data type can be created by H2-based SQL engine:
> {noformat}
> CREATE TABLE t(val OTHER)
> {noformat}
> But such a data type is not supported by Calcite-based SQL engine (at least
> in DDL)
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (IGNITE-14341) Significant performance drop when entries expiring concurrently
[
https://issues.apache.org/jira/browse/IGNITE-14341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin reassigned IGNITE-14341:
-
Assignee: Pavel Pereslegin
> Significant performance drop when entries expiring concurrently
> ---
>
> Key: IGNITE-14341
> URL: https://issues.apache.org/jira/browse/IGNITE-14341
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksey Plekhanov
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: ise
> Attachments: JmhCacheExpireBenchmark.java
>
>
> Currently, there is a significant performance drop when expired entries
> concurrently evicted by threads that perform some actions with cache (see
> attached reproducer):
> {noformat}
> Benchmark Mode Cnt Score Error
> Units
> JmhCacheExpireBenchmark.putWithExpire thrpt3 100,132 ± 21,025
> ops/ms
> JmhCacheExpireBenchmark.putWithoutExpire thrpt3 2133,122 ± 559,694
> ops/ms{noformat}
> Root cause: pending entries tree (offheap BPlusTree) is used to track expired
> entries, after each cache operation (and by timeout thread) there is an
> attempt to evict some amount of expired entries. these entries looked up from
> the start of the pending entries tree and there is a contention on the first
> leaf page of that tree.
> All threads waiting for the same page lock:
> {noformat}
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
> at
> org.apache.ignite.internal.util.OffheapReadWriteLock.waitAcquireWriteLock(OffheapReadWriteLock.java:503)
> at
> org.apache.ignite.internal.util.OffheapReadWriteLock.writeLock(OffheapReadWriteLock.java:244)
> at
> org.apache.ignite.internal.pagemem.impl.PageMemoryNoStoreImpl.writeLock(PageMemoryNoStoreImpl.java:528)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writeLock(PageHandler.java:422)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writePage(PageHandler.java:350)
> at
> org.apache.ignite.internal.processors.cache.persistence.DataStructure.write(DataStructure.java:325)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.access$13200(BPlusTree.java:100)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Remove.doRemoveFromLeaf(BPlusTree.java:4588)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Remove.removeFromLeaf(BPlusTree.java:4567)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Remove.tryRemoveFromLeaf(BPlusTree.java:5196)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Remove.access$6800(BPlusTree.java:4209)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.removeDown(BPlusTree.java:2189)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.removeDown(BPlusTree.java:2165)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.removeDown(BPlusTree.java:2165)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doRemove(BPlusTree.java:2076)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.removex(BPlusTree.java:1905)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.expireInternal(IgniteCacheOffheapManagerImpl.java:1426)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.expire(IgniteCacheOffheapManagerImpl.java:1375)
> at
> org.apache.ignite.internal.processors.cache.GridCacheTtlManager.expire(GridCacheTtlManager.java:246)
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.unwindEvicts(GridCacheUtils.java:882){noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15364) The rebalancing can be broken if historical rebalancing is reassigned after the client node joined the cluster.
[
https://issues.apache.org/jira/browse/IGNITE-15364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amelchev Nikita updated IGNITE-15364:
-
Release Note: Fixed rebalance issue when historical rebalancing is
reassigned after the client node joined the cluster. (was: Fixed rebalance
issue.)
> The rebalancing can be broken if historical rebalancing is reassigned after
> the client node joined the cluster.
> ---
>
> Key: IGNITE-15364
> URL: https://issues.apache.org/jira/browse/IGNITE-15364
> Project: Ignite
> Issue Type: Bug
>Reporter: Vyacheslav Koptilin
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Fix For: 2.13
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> Looks like the following scenario can break data consistency after
> rebalancing:
> - start and activate the cluster of three server nodes
> - create a cache with two backups and fill initial data into it
> - stop one server node and upload additional data to the cache in order to
> trigger historical rebalance after the node returns to the cluster
> - restart the node. make sure that historical rebalancing is started from
> two other nodes.
> - before rebalancing is completed a new client node should be started and
> joined the cluster. this leads to clean up partition update counters on
> server nodes, i.e. _GridDhtPartitionTopologyImpl#cntrMap_. ( * )
> - historical rebalancing from one node fails.
> - in that case, rebalancing is reassigned and starting node tries to
> rebalance missed partitions from another node.
> unfortunately, update counters for historical rebalance cannot be properly
> calculated due to ( * )
> An additional issue that was found while debugging:
> RebalanceReassignExchangeTask is skipped under some circumstances
> {code:java|title=GridCachePartitionExchangeManager.ExchangeWorker#body0}
> else if (lastAffChangedVer.after(exchId.topologyVersion())) {
> // There is a new exchange which should trigger rebalancing.
> // This reassignment request can be skipped.
> if (log.isInfoEnabled()) {
> log.info("Partitions reassignment request skipped due
> to affinity was already changed" +
> " [reassignTopVer=" + exchId.topologyVersion() +
> ", lastAffChangedTopVer=" + lastAffChangedVer +
> ']');
> }
> {code}
> There could be cases when the current rebalance is not canceled on PME which
> updates only minor versions and then triggers _RebalanceReassignExchangeTask_
> due to missed partitions on the supplier. After that,
> _RebalanceReassignExchangeTask_ is skipped, as the current minor version is
> higher than rebalance topology version, which leads to the situation when
> instances of missed partitions on demander remain in MOVING state until next
> PME that will trigger another rebalance.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (IGNITE-16818) Update Apache Ignite 2.13 release notes
Amelchev Nikita created IGNITE-16818: Summary: Update Apache Ignite 2.13 release notes Key: IGNITE-16818 URL: https://issues.apache.org/jira/browse/IGNITE-16818 Project: Ignite Issue Type: Task Reporter: Amelchev Nikita Assignee: Amelchev Nikita Update Apache Ignite 2.13 release notes -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16818) Update Apache Ignite 2.13 release notes
[ https://issues.apache.org/jira/browse/IGNITE-16818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-16818: - Fix Version/s: 2.13 > Update Apache Ignite 2.13 release notes > --- > > Key: IGNITE-16818 > URL: https://issues.apache.org/jira/browse/IGNITE-16818 > Project: Ignite > Issue Type: Task >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Fix For: 2.13 > > > Update Apache Ignite 2.13 release notes -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-15329) Atomics should be repairable by Read Repair
[
https://issues.apache.org/jira/browse/IGNITE-15329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17518867#comment-17518867
]
Ignite TC Bot commented on IGNITE-15329:
{panel:title=Branch: [pull/9907/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9907/head] Base: [master] : New Tests
(960)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Consistency{color} [[tests
960|https://ci.ignite.apache.org/viewLog.html?buildId=6508385]]
* {color:#013220}IgniteCacheConsistencySelfTestSuite:
AtomicReadRepairTest.test[getEntry=true, async=true, misses=false, nulls=false,
binary=true] - PASSED{color}
* {color:#013220}IgniteCacheConsistencySelfTestSuite:
AtomicReadRepairTest.test[getEntry=true, async=true, misses=false, nulls=true,
binary=false] - PASSED{color}
* {color:#013220}IgniteCacheConsistencySelfTestSuite:
AtomicReadRepairTest.test[getEntry=true, async=true, misses=false, nulls=true,
binary=true] - PASSED{color}
* {color:#013220}IgniteCacheConsistencySelfTestSuite:
AtomicReadRepairTest.test[getEntry=true, async=true, misses=true, nulls=false,
binary=false] - PASSED{color}
* {color:#013220}IgniteCacheConsistencySelfTestSuite:
AtomicReadRepairTest.test[getEntry=true, async=false, misses=true, nulls=false,
binary=true] - PASSED{color}
* {color:#013220}IgniteCacheConsistencySelfTestSuite:
AtomicReadRepairTest.test[getEntry=true, async=false, misses=true, nulls=true,
binary=false] - PASSED{color}
* {color:#013220}IgniteCacheConsistencySelfTestSuite:
AtomicReadRepairTest.test[getEntry=true, async=false, misses=true, nulls=true,
binary=true] - PASSED{color}
* {color:#013220}IgniteCacheConsistencySelfTestSuite:
AtomicReadRepairTest.test[getEntry=true, async=true, misses=false, nulls=false,
binary=false] - PASSED{color}
* {color:#013220}IgniteCacheConsistencySelfTestSuite:
AtomicReadRepairTest.test[getEntry=true, async=false, misses=false,
nulls=false, binary=true] - PASSED{color}
* {color:#013220}IgniteCacheConsistencySelfTestSuite:
AtomicReadRepairTest.test[getEntry=true, async=false, misses=false, nulls=true,
binary=false] - PASSED{color}
* {color:#013220}IgniteCacheConsistencySelfTestSuite:
AtomicReadRepairTest.test[getEntry=true, async=false, misses=false, nulls=true,
binary=true] - PASSED{color}
... and 949 new tests
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6508406&buildTypeId=IgniteTests24Java8_RunAll]
> Atomics should be repairable by Read Repair
> ---
>
> Key: IGNITE-15329
> URL: https://issues.apache.org/jira/browse/IGNITE-15329
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Labels: iep-12, iep-31
> Fix For: 2.14
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It's pretty clear that it's impossible to fix atomics with "Read Repair"
> atomically since it's impossible to lock entries during the repair process.
> Even get from backups has no guarantee to return consistent values under load.
> But to fix we must also perform an additional step - cache put.
> So, value can be changed between gets, can be changed after gets but before
> put, but it still seems to be possible to automize the fix.
> Idea is to decide what entry won on the last check attempt and put this value
> using the entry processor.
> During the entry processor execution, we should check the current node's
> value, and if the value is as it was during the check we must replace it with
> the consistent value.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Resolved] (IGNITE-16816) Change copyright to 2022
[ https://issues.apache.org/jira/browse/IGNITE-16816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita resolved IGNITE-16816. -- Resolution: Fixed Merged into the master and 2.13. > Change copyright to 2022 > > > Key: IGNITE-16816 > URL: https://issues.apache.org/jira/browse/IGNITE-16816 > Project: Ignite > Issue Type: Task >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Fix For: 2.13 > > Time Spent: 20m > Remaining Estimate: 0h > > Change copyright to 2022 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16817) Update packages version to 2.13
[ https://issues.apache.org/jira/browse/IGNITE-16817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17518863#comment-17518863 ] Amelchev Nikita commented on IGNITE-16817: -- Merged into the master and 2.13. > Update packages version to 2.13 > --- > > Key: IGNITE-16817 > URL: https://issues.apache.org/jira/browse/IGNITE-16817 > Project: Ignite > Issue Type: Task >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Fix For: 2.13 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (IGNITE-16817) Update packages version to 2.13
[ https://issues.apache.org/jira/browse/IGNITE-16817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita resolved IGNITE-16817. -- Resolution: Fixed > Update packages version to 2.13 > --- > > Key: IGNITE-16817 > URL: https://issues.apache.org/jira/browse/IGNITE-16817 > Project: Ignite > Issue Type: Task >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Fix For: 2.13 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16817) Update packages version to 2.13
[ https://issues.apache.org/jira/browse/IGNITE-16817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-16817: - Fix Version/s: 2.13 > Update packages version to 2.13 > --- > > Key: IGNITE-16817 > URL: https://issues.apache.org/jira/browse/IGNITE-16817 > Project: Ignite > Issue Type: Task >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Fix For: 2.13 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16817) Update packages version to 2.13
Amelchev Nikita created IGNITE-16817: Summary: Update packages version to 2.13 Key: IGNITE-16817 URL: https://issues.apache.org/jira/browse/IGNITE-16817 Project: Ignite Issue Type: Task Reporter: Amelchev Nikita Assignee: Amelchev Nikita -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16816) Change copyright to 2022
[ https://issues.apache.org/jira/browse/IGNITE-16816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-16816: - Fix Version/s: 2.13 > Change copyright to 2022 > > > Key: IGNITE-16816 > URL: https://issues.apache.org/jira/browse/IGNITE-16816 > Project: Ignite > Issue Type: Task >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Fix For: 2.13 > > Time Spent: 10m > Remaining Estimate: 0h > > Change copyright to 2022 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16814) Update release branch version for 2.13
[ https://issues.apache.org/jira/browse/IGNITE-16814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-16814: - Fix Version/s: 2.13 > Update release branch version for 2.13 > -- > > Key: IGNITE-16814 > URL: https://issues.apache.org/jira/browse/IGNITE-16814 > Project: Ignite > Issue Type: Task >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Fix For: 2.13 > > > Update release branch version for 2.13 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16813) Update pom dependencies to 2.14.0-SNAPSHOT version
[ https://issues.apache.org/jira/browse/IGNITE-16813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-16813: - Fix Version/s: 2.14 > Update pom dependencies to 2.14.0-SNAPSHOT version > -- > > Key: IGNITE-16813 > URL: https://issues.apache.org/jira/browse/IGNITE-16813 > Project: Ignite > Issue Type: Task >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Fix For: 2.14 > > Time Spent: 10m > Remaining Estimate: 0h > > The pom dependencies must be updated due to the ignite-2.13 branch has been > created. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16816) Change copyright to 2022
Amelchev Nikita created IGNITE-16816: Summary: Change copyright to 2022 Key: IGNITE-16816 URL: https://issues.apache.org/jira/browse/IGNITE-16816 Project: Ignite Issue Type: Task Reporter: Amelchev Nikita Assignee: Amelchev Nikita Change copyright to 2022 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16598) CLI ignores an incorrect repository passed via --repo
[ https://issues.apache.org/jira/browse/IGNITE-16598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-16598: - Description: prom1se@prom1se-PC276:~/apache/ignite-3/modules/cli/target$ ls ~/temp/test ls: cannot access '/home/prom1se/temp/test': No such file or directory prom1se@prom1se-PC276:~/apache/ignite-3/modules/cli/target$ ./ignite init --repo=file:~/temp/test Creating directories... Done! +++ | Binaries Directory | /home/prom1se/apache/ignite-3/modules/cli/target/ignite-bin| +++ | Work Directory | /home/prom1se/apache/ignite-3/modules/cli/target/ignite-work | +++ | Config Directory | /home/prom1se/apache/ignite-3/modules/cli/target/ignite-config | +++ | Log Directory | /home/prom1se/apache/ignite-3/modules/cli/target/ignite-log| +++ Installing org.apache.ignite:ignite-runner:3.0.0-SNAPSHOT... |=> | 6%^C No errors or warnings, the cli immediately started initialization from the local maven cache. It seems to me that this behavior is incorrect, and the utility should stop working in case of an incorrectly passed repo parameter. Otherwise, the user may get the wrong version of the product that he expects. was: prom1se@prom1se-PC276:~/apache/ignite-3/modules/cli/target$ ls ~/temp/test ls: cannot access '/home/prom1se/temp/test': No such file or directory prom1se@prom1se-PC276:~/apache/ignite-3/modules/cli/target$ ./ignite init --repo=file:~/temp/test Creating directories... Done! +++ | Binaries Directory | /home/prom1se/apache/ignite-3/modules/cli/target/ignite-bin| +++ | Work Directory | /home/prom1se/apache/ignite-3/modules/cli/target/ignite-work | +++ | Config Directory | /home/prom1se/apache/ignite-3/modules/cli/target/ignite-config | +++ | Log Directory | /home/prom1se/apache/ignite-3/modules/cli/target/ignite-log| +++ Installing org.apache.ignite:ignite-runner:3.0.0-SNAPSHOT... |=> | 6%^C No errors or warnings, the cli immediately started initialization from the local maven cache. It seems to me that this behavior is incorrect, and the utility should stop working in case of an incorrectly passed repo parameter. Otherwise, the user may get the wrong version of the product that he expects. > CLI ignores an incorrect repository passed via --repo > - > > Key: IGNITE-16598 > URL: https://issues.apache.org/jira/browse/IGNITE-16598 > Project: Ignite > Issue Type: Bug >Affects Versions: 3.0.0-alpha4 >Reporter: Fedor Malchikov >Priority: Critical > Labels: ignite-3, ignite-3-cli-tool > > prom1se@prom1se-PC276:~/apache/ignite-3/modules/cli/target$ ls ~/temp/test > ls: cannot access '/home/prom1se/temp/test': No such file or directory > prom1se@prom1se-PC276:~/apache/ignite-3/modules/cli/target$ ./ignite init > --repo=file:~/temp/test > Creating directories... Done! > +++ > | Binaries Directory | > /home/prom1se/apache/ignite-3/modules/cli/target/ignite-bin| > +++ > | Work Directory | > /home/prom1se/apache/ignite-3/modules/cli/target/ignite-work | > +++ > | Config Directory | > /home/prom1se/apache/ignite-3/modules/cli/target/ignite-config | > +++ > | Log Directory | > /home/prom1se/apache/ignite-3/modules/cli/target/ignite-log| > +++ > Installing org.apache.ignite:ignite-runner:3.0.0-SNAPSHOT... > |=>
[jira] [Updated] (IGNITE-16807) Ignite 3 Command Line Interface
[ https://issues.apache.org/jira/browse/IGNITE-16807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-16807: - Description: Requirements - TBD > Ignite 3 Command Line Interface > --- > > Key: IGNITE-16807 > URL: https://issues.apache.org/jira/browse/IGNITE-16807 > Project: Ignite > Issue Type: Epic >Reporter: Vyacheslav Koptilin >Assignee: Vyacheslav Koptilin >Priority: Major > Labels: ignite-3-cli-tool > > Requirements - TBD -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16815) [Extensions] Ignite extensions must use ignite-parent as a parent project
Maxim Muzafarov created IGNITE-16815: Summary: [Extensions] Ignite extensions must use ignite-parent as a parent project Key: IGNITE-16815 URL: https://issues.apache.org/jira/browse/IGNITE-16815 Project: Ignite Issue Type: Improvement Components: extensions Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Fix For: 2.14 Ignite Extensions currently use their own maven parent project which is lead for duplicated configuration of maven profiles, dependency versions and the build lifecycle. Since the ignite-parent pom is now available it's better to use shared pom as single parent for all extensions. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16592) Add ignite-parent pom and bom to a release lifecycle
[ https://issues.apache.org/jira/browse/IGNITE-16592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17518834#comment-17518834 ] Maxim Muzafarov commented on IGNITE-16592: -- Cherry-picked to 2.13 > Add ignite-parent pom and bom to a release lifecycle > > > Key: IGNITE-16592 > URL: https://issues.apache.org/jira/browse/IGNITE-16592 > Project: Ignite > Issue Type: Task >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.13 > > Time Spent: 1h > Remaining Estimate: 0h > > Include the ignite-parent pom artefact and ignite-plugin-bom to the Ignite > release lifecycle. This is required to share basic Ignite dependency versions > and configuration properties to the Ignite extensions. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16812) Use project base directory for checkstyle resources
[ https://issues.apache.org/jira/browse/IGNITE-16812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17518833#comment-17518833 ] Maxim Muzafarov commented on IGNITE-16812: -- Merged to the master branch, cherry-picked to 2.13 > Use project base directory for checkstyle resources > --- > > Key: IGNITE-16812 > URL: https://issues.apache.org/jira/browse/IGNITE-16812 > Project: Ignite > Issue Type: Bug >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.13 > > Time Spent: 20m > Remaining Estimate: 0h > > The build fails if the project root directory is not equal to the Ignite > repository directory. > [2022-04-06T22:56:01.396Z] [INFO] > > [2022-04-06T22:56:01.396Z] [INFO] BUILD FAILURE > [2022-04-06T22:56:01.396Z] [INFO] > > [2022-04-06T22:56:01.396Z] [INFO] Total time: 13.964 s (Wall Clock) > [2022-04-06T22:56:01.396Z] [INFO] Finished at: 2022-04-07T01:57:03+03:00 > [2022-04-06T22:56:01.396Z] [INFO] > > [2022-04-06T22:56:01.396Z] [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-checkstyle-plugin:3.1.1:check (style) on > project ignite-parent: Failed during checkstyle execution: Unable to find > suppressions file at location: checkstyle/checkstyle-suppressions.xml: Could > not find resource 'checkstyle/checkstyle-suppressions.xml'. -> [Help 1] > [2022-04-06T22:56:01.396Z] [ERROR] > [2022-04-06T22:56:01.396Z] [ERROR] To see the full stack trace of the errors, > re-run Maven with the -e switch. > [2022-04-06T22:56:01.396Z] [ERROR] Re-run Maven using the -X switch to enable > full debug logging. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16814) Update release branch version for 2.13
Amelchev Nikita created IGNITE-16814: Summary: Update release branch version for 2.13 Key: IGNITE-16814 URL: https://issues.apache.org/jira/browse/IGNITE-16814 Project: Ignite Issue Type: Task Reporter: Amelchev Nikita Assignee: Amelchev Nikita Update release branch version for 2.13 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16813) Update pom dependencies to 2.14.0-SNAPSHOT version
Amelchev Nikita created IGNITE-16813: Summary: Update pom dependencies to 2.14.0-SNAPSHOT version Key: IGNITE-16813 URL: https://issues.apache.org/jira/browse/IGNITE-16813 Project: Ignite Issue Type: Task Reporter: Amelchev Nikita Assignee: Amelchev Nikita The pom dependencies must be updated due to the ignite-2.13 branch has been created. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16509) Calcite engine. Support OTHER data type
[
https://issues.apache.org/jira/browse/IGNITE-16509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17518802#comment-17518802
]
Ignite TC Bot commented on IGNITE-16509:
{panel:title=Branch: [pull/9923/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9923/head] Base: [master] : New Tests
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Calcite SQL{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=6507978]]
* {color:#013220}IgniteCalciteTestSuite: JdbcQueryTest.testOtherType -
PASSED{color}
* {color:#013220}IgniteCalciteTestSuite: DataTypesTest.testOtherType -
PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6507979&buildTypeId=IgniteTests24Java8_RunAll]
> Calcite engine. Support OTHER data type
> ---
>
> Key: IGNITE-16509
> URL: https://issues.apache.org/jira/browse/IGNITE-16509
> Project: Ignite
> Issue Type: New Feature
>Reporter: Aleksey Plekhanov
>Assignee: Vladimir Steshin
>Priority: Major
> Labels: calcite, calcite2-required, calcite3-required
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> Table with {{OTHER}} (Object) data type can be created by H2-based SQL engine:
> {noformat}
> CREATE TABLE t(val OTHER)
> {noformat}
> But such a data type is not supported by Calcite-based SQL engine (at least
> in DDL)
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Resolved] (IGNITE-16744) ODBC: SQLGetStmtAttr with SQL_ATTR_ROW_ARRAY_SIZE always returns 1
[ https://issues.apache.org/jira/browse/IGNITE-16744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YuJue Li resolved IGNITE-16744. --- Resolution: Duplicate > ODBC: SQLGetStmtAttr with SQL_ATTR_ROW_ARRAY_SIZE always returns 1 > -- > > Key: IGNITE-16744 > URL: https://issues.apache.org/jira/browse/IGNITE-16744 > Project: Ignite > Issue Type: Bug > Components: odbc >Affects Versions: 2.12 >Reporter: Igor Sapego >Priority: Major > Fix For: 2.13 > > > SQLGetStmtAttr(SQL_ATTR_ROW_ARRAY_SIZE) returning the wrong value for row > array size. > Details here: https://github.com/apache/ignite/pull/9908 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16744) ODBC: SQLGetStmtAttr with SQL_ATTR_ROW_ARRAY_SIZE always returns 1
[ https://issues.apache.org/jira/browse/IGNITE-16744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YuJue Li updated IGNITE-16744: -- Fix Version/s: 2.13 (was: 2.14) > ODBC: SQLGetStmtAttr with SQL_ATTR_ROW_ARRAY_SIZE always returns 1 > -- > > Key: IGNITE-16744 > URL: https://issues.apache.org/jira/browse/IGNITE-16744 > Project: Ignite > Issue Type: Bug > Components: odbc >Affects Versions: 2.12 >Reporter: Igor Sapego >Priority: Major > Fix For: 2.13 > > > SQLGetStmtAttr(SQL_ATTR_ROW_ARRAY_SIZE) returning the wrong value for row > array size. > Details here: https://github.com/apache/ignite/pull/9908 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16812) Use project base directory for checkstyle resources
[ https://issues.apache.org/jira/browse/IGNITE-16812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-16812: - Ignite Flags: (was: Docs Required,Release Notes Required) > Use project base directory for checkstyle resources > --- > > Key: IGNITE-16812 > URL: https://issues.apache.org/jira/browse/IGNITE-16812 > Project: Ignite > Issue Type: Bug >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.13 > > > The build fails if the project root directory is not equal to the Ignite > repository directory. > [2022-04-06T22:56:01.396Z] [INFO] > > [2022-04-06T22:56:01.396Z] [INFO] BUILD FAILURE > [2022-04-06T22:56:01.396Z] [INFO] > > [2022-04-06T22:56:01.396Z] [INFO] Total time: 13.964 s (Wall Clock) > [2022-04-06T22:56:01.396Z] [INFO] Finished at: 2022-04-07T01:57:03+03:00 > [2022-04-06T22:56:01.396Z] [INFO] > > [2022-04-06T22:56:01.396Z] [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-checkstyle-plugin:3.1.1:check (style) on > project ignite-parent: Failed during checkstyle execution: Unable to find > suppressions file at location: checkstyle/checkstyle-suppressions.xml: Could > not find resource 'checkstyle/checkstyle-suppressions.xml'. -> [Help 1] > [2022-04-06T22:56:01.396Z] [ERROR] > [2022-04-06T22:56:01.396Z] [ERROR] To see the full stack trace of the errors, > re-run Maven with the -e switch. > [2022-04-06T22:56:01.396Z] [ERROR] Re-run Maven using the -X switch to enable > full debug logging. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16812) Use project base directory for checkstyle resources
Maxim Muzafarov created IGNITE-16812: Summary: Use project base directory for checkstyle resources Key: IGNITE-16812 URL: https://issues.apache.org/jira/browse/IGNITE-16812 Project: Ignite Issue Type: Bug Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Fix For: 2.13 The build fails if the project root directory is not equal to the Ignite repository directory. [2022-04-06T22:56:01.396Z] [INFO] [2022-04-06T22:56:01.396Z] [INFO] BUILD FAILURE [2022-04-06T22:56:01.396Z] [INFO] [2022-04-06T22:56:01.396Z] [INFO] Total time: 13.964 s (Wall Clock) [2022-04-06T22:56:01.396Z] [INFO] Finished at: 2022-04-07T01:57:03+03:00 [2022-04-06T22:56:01.396Z] [INFO] [2022-04-06T22:56:01.396Z] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:3.1.1:check (style) on project ignite-parent: Failed during checkstyle execution: Unable to find suppressions file at location: checkstyle/checkstyle-suppressions.xml: Could not find resource 'checkstyle/checkstyle-suppressions.xml'. -> [Help 1] [2022-04-06T22:56:01.396Z] [ERROR] [2022-04-06T22:56:01.396Z] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [2022-04-06T22:56:01.396Z] [ERROR] Re-run Maven using the -X switch to enable full debug logging. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-15575) Calcite engine. Benchmark calcite-based and H2 based SQL engines
[ https://issues.apache.org/jira/browse/IGNITE-15575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-15575: - Fix Version/s: (was: 2.13) > Calcite engine. Benchmark calcite-based and H2 based SQL engines > > > Key: IGNITE-15575 > URL: https://issues.apache.org/jira/browse/IGNITE-15575 > Project: Ignite > Issue Type: Task >Reporter: Aleksey Plekhanov >Priority: Major > Labels: calcite, ignite-3 > > Create yardstick configurations to compare Calcite-based and H2-based SQL > engines in different scenarios. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-15329) Atomics should be repairable by Read Repair
[ https://issues.apache.org/jira/browse/IGNITE-15329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-15329: - Fix Version/s: 2.14 (was: 2.13) > Atomics should be repairable by Read Repair > --- > > Key: IGNITE-15329 > URL: https://issues.apache.org/jira/browse/IGNITE-15329 > Project: Ignite > Issue Type: Sub-task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Labels: iep-12, iep-31 > Fix For: 2.14 > > Time Spent: 10m > Remaining Estimate: 0h > > It's pretty clear that it's impossible to fix atomics with "Read Repair" > atomically since it's impossible to lock entries during the repair process. > Even get from backups has no guarantee to return consistent values under load. > But to fix we must also perform an additional step - cache put. > So, value can be changed between gets, can be changed after gets but before > put, but it still seems to be possible to automize the fix. > Idea is to decide what entry won on the last check attempt and put this value > using the entry processor. > During the entry processor execution, we should check the current node's > value, and if the value is as it was during the check we must replace it with > the consistent value. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16755) C++ Thin: Add user threadpool size option to public configuration
[ https://issues.apache.org/jira/browse/IGNITE-16755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-16755: - Fix Version/s: 2.14 (was: 2.13) > C++ Thin: Add user threadpool size option to public configuration > - > > Key: IGNITE-16755 > URL: https://issues.apache.org/jira/browse/IGNITE-16755 > Project: Ignite > Issue Type: Bug > Components: thin client >Affects Versions: 2.12 >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Major > Fix For: 2.14 > > > There are some cases when application creates many instances of C++ thin > client. Therefore each client instance spawns many threads (equals number of > cores). I propose add configuration to > ignite::thin::IgniteClientConfiguration which will override default > threadpool size when provided. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16744) ODBC: SQLGetStmtAttr with SQL_ATTR_ROW_ARRAY_SIZE always returns 1
[ https://issues.apache.org/jira/browse/IGNITE-16744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-16744: - Fix Version/s: 2.14 (was: 2.13) > ODBC: SQLGetStmtAttr with SQL_ATTR_ROW_ARRAY_SIZE always returns 1 > -- > > Key: IGNITE-16744 > URL: https://issues.apache.org/jira/browse/IGNITE-16744 > Project: Ignite > Issue Type: Bug > Components: odbc >Affects Versions: 2.12 >Reporter: Igor Sapego >Priority: Major > Fix For: 2.14 > > > SQLGetStmtAttr(SQL_ATTR_ROW_ARRAY_SIZE) returning the wrong value for row > array size. > Details here: https://github.com/apache/ignite/pull/9908 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16806) Cache put/SQL table insert fails if SQL index created and LocalDateTime is used as value.
[
https://issues.apache.org/jira/browse/IGNITE-16806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Petrov updated IGNITE-16806:
Description:
Reproducer:
{code:java}
/** */
public class LocalDateIndexTest extends AbstractIndexingCommonTest {
/** */
@Test
public void test() throws Exception {
IgniteEx ignite = startGrids(2);
SqlFieldsQuery qry = new SqlFieldsQuery(
"CREATE TABLE DATA (STR VARCHAR PRIMARY KEY, LOCDATETIME TIMESTAMP)
WITH" +
" \"KEY_TYPE=java.lang.String" +
",
VALUE_TYPE=org.apache.ignite.internal.processors.query.LocalDateIndexTest$Data"
+
", CACHE_NAME=" + DEFAULT_CACHE_NAME + "\"");
ignite.context().query().querySqlFields(qry, false).getAll();
qry = new SqlFieldsQuery("CREATE INDEX TEST_IDX ON DATA(LOCDATETIME
DESC);");
ignite.context().query().querySqlFields(qry, false).getAll();
//ignite.cache(DEFAULT_CACHE_NAME).put("0", new Data("0",
LocalDateTime.MAX));
qry = new SqlFieldsQuery("INSERT INTO DATA(_key, str, locDateTime)
values(?, ?, ?)").setArgs("0", "0", LocalDateTime.MAX);
ignite.context().query().querySqlFields(qry, false).getAll();
}
public static class Data implements Serializable {
/** Serial version UID. */
private static final long serialVersionUID = 1L;
/** */
public String str;
/** */
public LocalDateTime locDateTime;
/** */
public Data(String str, LocalDateTime locDateTime) {
this.str = str;
this.locDateTime = locDateTime;
}
}
}
{code}
Exception:
{code:java}
class org.apache.ignite.internal.processors.query.IgniteSQLException: Type for
a column 'LOCDATETIME' is not compatible with index definition. Expected
'Timestamp', actual type 'LocalDateTime'
at
org.apache.ignite.internal.processors.query.QueryTypeDescriptorImpl.validateIndexes(QueryTypeDescriptorImpl.java:735)
at
org.apache.ignite.internal.processors.query.QueryTypeDescriptorImpl.validateKeyAndValue(QueryTypeDescriptorImpl.java:606)
at
org.apache.ignite.internal.processors.query.h2.dml.UpdatePlan.processRow(UpdatePlan.java:295)
at
org.apache.ignite.internal.processors.query.h2.dml.DmlUtils.dmlDoInsert(DmlUtils.java:212)
at
org.apache.ignite.internal.processors.query.h2.dml.DmlUtils.processSelectResult(DmlUtils.java:185)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeUpdateNonTransactional(IgniteH2Indexing.java:2902)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeUpdate(IgniteH2Indexing.java:2747)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeUpdateDistributed(IgniteH2Indexing.java:2673)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeDml(IgniteH2Indexing.java:1263)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:1185)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor$2.applyx(GridQueryProcessor.java:3005)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor$2.applyx(GridQueryProcessor.java:2988)
at
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:3650)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.lambda$querySqlFields$3(GridQueryProcessor.java:3022)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuerySafe(GridQueryProcessor.java:3094)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2982)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2909)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2882)
at
org.apache.ignite.internal.processors.query.LocalDateIndexTest.test(LocalDateIndexTest.java:50)
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(Inv
[jira] [Updated] (IGNITE-16266) Add unique id for indexes
[ https://issues.apache.org/jira/browse/IGNITE-16266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeny Stanilovsky updated IGNITE-16266: Fix Version/s: None (was: 3.0.0-alpha5) > Add unique id for indexes > - > > Key: IGNITE-16266 > URL: https://issues.apache.org/jira/browse/IGNITE-16266 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Evgeny Stanilovsky >Priority: Major > Labels: ignite-3, sql > Fix For: None > > Time Spent: 2.5h > Remaining Estimate: 0h > > As of now we address to index by name even internally. It could lead read > another version of index which was dropped and created with another set of > column . Let's introduce unique id (as we already have for tables) which > could be accessed only internally and use as identifier of indexes. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16811) Wait for nodes to be online upon CMG Raft group start
Aleksandr Polovtcev created IGNITE-16811: Summary: Wait for nodes to be online upon CMG Raft group start Key: IGNITE-16811 URL: https://issues.apache.org/jira/browse/IGNITE-16811 Project: Ignite Issue Type: Task Reporter: Aleksandr Polovtcev Assignee: Aleksandr Polovtcev When starting a CMG Raft Service (especially during the local state recovery), some nodes might be offline. Since Raft Service needs all Peer addresses to be resolved at the time of the service start, it is proposed to wait for the nodes to become online or fail after a timeout. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16810) Create tests for canceling init
Aleksandr Polovtcev created IGNITE-16810: Summary: Create tests for canceling init Key: IGNITE-16810 URL: https://issues.apache.org/jira/browse/IGNITE-16810 Project: Ignite Issue Type: Task Reporter: Aleksandr Polovtcev Assignee: Aleksandr Polovtcev We need to add tests for the scenario when a node fails during init, which leads to issuing the CancelInitMessage. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16266) Add unique id for indexes
[ https://issues.apache.org/jira/browse/IGNITE-16266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17518716#comment-17518716 ] Evgeny Stanilovsky commented on IGNITE-16266: - [~korlov] [~amashenkov] thanks ! merged into feature branch. > Add unique id for indexes > - > > Key: IGNITE-16266 > URL: https://issues.apache.org/jira/browse/IGNITE-16266 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Evgeny Stanilovsky >Priority: Major > Labels: ignite-3, sql > Fix For: 3.0.0-alpha5 > > Time Spent: 2.5h > Remaining Estimate: 0h > > As of now we address to index by name even internally. It could lead read > another version of index which was dropped and created with another set of > column . Let's introduce unique id (as we already have for tables) which > could be accessed only internally and use as identifier of indexes. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16718) ItIgniteNodeRestartTest#testCfgGap is flaky
[
https://issues.apache.org/jira/browse/IGNITE-16718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-16718:
-
Description:
ItIgniteNodeRestartTest#testCfgGap could be found in ignite-16362 branch.
The reason of failure is null value instead of previously upserted key.
With following (a bit simplified test: one table instead of two and one
insertion instead of one hundred)
{code:java}
public void testCfgGap(TestInfo testInfo) {
final int nodes = 4;
for (int i = 0; i < nodes; i++) {
startNode(testInfo, i);
}
createTableWithData(CLUSTER_NODES.get(0), "t1", nodes);
String igniteName = CLUSTER_NODES.get(nodes - 1).name();
log.info("Stopping the node.");
IgnitionManager.stop(igniteName);
checkTableWithData(CLUSTER_NODES.get(0), "t1");
log.info("Starting the node.");
Ignite newNode = IgnitionManager.start(igniteName, null,
workDir.resolve(igniteName));
CLUSTER_NODES.set(nodes - 1, newNode);
checkTableWithData(CLUSTER_NODES.get(0), "t1");
checkTableWithData(CLUSTER_NODES.get(nodes - 1), "t1");
}
private void checkTableWithData(Ignite ignite, String name) {
...
for (int i = 0; i < 1; i++) {
...
}
}
private void createTableWithData(Ignite ignite, String name, int replicas) {
...
for (int i = 0; i < 1; i++) {
...
}
}{code}
an inconsistent read is reproduced under the following flow:
# table.keyValueView.put(k1)
## PartitionListener#handleUpsertCommand on Node B
## PartitionListener#handleUpsertCommand on Node C
## PartitionListener#handleUpsertCommand on Node D
## Please pay attention that upsert command wasn't handled on Node A, that's
actually fine because B, C, D is a majority.
# node D stop
# nodeA.table.keyValueView().get(k1)
## PartitionListener#handleGetCommand on Node B // Means that B is a leader.
# node D start
## PartitionListener#handleUpsertCommand on Node D // Inner raft rebalance
# nodeA.table.keyValueView().get(k1)
## PartitionListener#handleGetCommand on Node B // Means that B is still a
leader.
# nodeD.table.keyValueView().get(k1)
## PartitionListener#handleGetCommand on Node *A* // Means that leader was
changed to A and what's very important there was no handling upsert command on
Node A.
I've checked this by adding
{code:java}
private void handleUpsertCommand(UpsertCommand cmd) {
System.out.println(">>> Upserted" +
((TxManagerImpl)txManager).clusterService.topologyService().localMember());
...
} {code}
and
{code:java}
private SingleRowResponse handleGetCommand(GetCommand cmd) {
System.out.println(">>> Get" +
((TxManagerImpl)txManager).clusterService.topologyService().localMember());
...
} {code}
Further investigation items might be:
* Checking whether k1 upsert was committed on node A or not, meaning that
committing and applying to state machine are different steps, and according to
RAFT it's not valid to be a leader with missing committed entries.
* Checking why leader was changed between reads.
h4. UPD 1:
>> Checking whether k1 upsert was committed on node A or not, meaning that
>> committing and applying to state machine are different steps, and according
>> to RAFT it's not valid to be a leader with missing committed entries.
Checked. k1 upsert was committed on node A, so it's only unavailable within
state machine. It also means that leader change to node A is valid.
was:
ItIgniteNodeRestartTest#testCfgGap could be found in ignite-16362 branch.
The reason of failure is null value instead of previously upserted key.
With following (a bit simplified test: one table instead of two and one
insertion instead of one hundred)
{code:java}
public void testCfgGap(TestInfo testInfo) {
final int nodes = 4;
for (int i = 0; i < nodes; i++) {
startNode(testInfo, i);
}
createTableWithData(CLUSTER_NODES.get(0), "t1", nodes);
String igniteName = CLUSTER_NODES.get(nodes - 1).name();
log.info("Stopping the node.");
IgnitionManager.stop(igniteName);
checkTableWithData(CLUSTER_NODES.get(0), "t1");
log.info("Starting the node.");
Ignite newNode = IgnitionManager.start(igniteName, null,
workDir.resolve(igniteName));
CLUSTER_NODES.set(nodes - 1, newNode);
checkTableWithData(CLUSTER_NODES.get(0), "t1");
checkTableWithData(CLUSTER_NODES.get(nodes - 1), "t1");
}
private void checkTableWithData(Ignite ignite, String name) {
...
for (int i = 0; i < 1; i++) {
...
}
}
private void createTableWithData(Ignite ignite, String name, int replicas) {
...
for (int i = 0; i < 1; i++) {
...
}
}{code}
an inconsistent read is reproduced under the following flow:
# table.keyValueView.put(k1)
## PartitionListener#handleUpsertCommand on Node B
## PartitionListener#handleUpsertCommand on Node C
## PartitionListener#handleUpsertCommand on Node D
## Please pay a
[jira] [Updated] (IGNITE-16718) ItIgniteNodeRestartTest#testCfgGap is flaky
[
https://issues.apache.org/jira/browse/IGNITE-16718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-16718:
-
Description:
ItIgniteNodeRestartTest#testCfgGap could be found in ignite-16362 branch.
The reason of failure is null value instead of previously upserted key.
With following (a bit simplified test: one table instead of two and one
insertion instead of one hundred)
{code:java}
public void testCfgGap(TestInfo testInfo) {
final int nodes = 4;
for (int i = 0; i < nodes; i++) {
startNode(testInfo, i);
}
createTableWithData(CLUSTER_NODES.get(0), "t1", nodes);
String igniteName = CLUSTER_NODES.get(nodes - 1).name();
log.info("Stopping the node.");
IgnitionManager.stop(igniteName);
checkTableWithData(CLUSTER_NODES.get(0), "t1");
log.info("Starting the node.");
Ignite newNode = IgnitionManager.start(igniteName, null,
workDir.resolve(igniteName));
CLUSTER_NODES.set(nodes - 1, newNode);
checkTableWithData(CLUSTER_NODES.get(0), "t1");
checkTableWithData(CLUSTER_NODES.get(nodes - 1), "t1");
}
private void checkTableWithData(Ignite ignite, String name) {
...
for (int i = 0; i < 1; i++) {
...
}
}
private void createTableWithData(Ignite ignite, String name, int replicas) {
...
for (int i = 0; i < 1; i++) {
...
}
}{code}
an inconsistent read is reproduced under the following flow:
# table.keyValueView.put(k1)
## PartitionListener#handleUpsertCommand on Node B
## PartitionListener#handleUpsertCommand on Node C
## PartitionListener#handleUpsertCommand on Node D
## Please pay attention that upsert command wasn't handled on Node A, that's
actually fine because B, C, D is a majority.
# node D stop
# nodeA.table.keyValueView().get(k1)
## PartitionListener#handleGetCommand on Node B // Means that B is a leader.
# node D start
## PartitionListener#handleUpsertCommand on Node D // Inner raft rebalance
# nodeA.table.keyValueView().get(k1)
## PartitionListener#handleGetCommand on Node B // Means that B is still a
leader.
# nodeD.table.keyValueView().get(k1)
## PartitionListener#handleGetCommand on Node *A* // Means that leader was
changed to A and what's very important there was no handling upsert command on
Node A.
I've checked this by adding
{code:java}
private void handleUpsertCommand(UpsertCommand cmd) {
System.out.println(">>> Upserted" +
((TxManagerImpl)txManager).clusterService.topologyService().localMember());
...
} {code}
and
{code:java}
private SingleRowResponse handleGetCommand(GetCommand cmd) {
System.out.println(">>> Get" +
((TxManagerImpl)txManager).clusterService.topologyService().localMember());
...
} {code}
Further investigation items might be:
* Checking whether k1 upsert was committed on node A or not, meaning that
committing and applying to state machine are different steps, and according to
RAFT it's not valid to be a leader with missing committed entries.
* Checking why leader was changed between reads.
h4. UPD 1:
h4. UPD 1:
>> Checking whether k1 upsert was committed on node A or not, meaning that
>> committing and applying to state machine are different steps, and according
>> to RAFT it's not valid to be a leader with missing committed entries.
Checked. k1 upsert was committed on node A, so it's only unavailable within
state machine. It also means that leader change to node A is valid.
was:
ItIgniteNodeRestartTest#testCfgGap could be found in ignite-16362 branch.
The reason of failure is null value instead of previously upserted key.
With following (a bit simplified test: one table instead of two and one
insertion instead of one hundred)
{code:java}
public void testCfgGap(TestInfo testInfo) {
final int nodes = 4;
for (int i = 0; i < nodes; i++) {
startNode(testInfo, i);
}
createTableWithData(CLUSTER_NODES.get(0), "t1", nodes);
String igniteName = CLUSTER_NODES.get(nodes - 1).name();
log.info("Stopping the node.");
IgnitionManager.stop(igniteName);
checkTableWithData(CLUSTER_NODES.get(0), "t1");
log.info("Starting the node.");
Ignite newNode = IgnitionManager.start(igniteName, null,
workDir.resolve(igniteName));
CLUSTER_NODES.set(nodes - 1, newNode);
checkTableWithData(CLUSTER_NODES.get(0), "t1");
checkTableWithData(CLUSTER_NODES.get(nodes - 1), "t1");
}
private void checkTableWithData(Ignite ignite, String name) {
...
for (int i = 0; i < 1; i++) {
...
}
}
private void createTableWithData(Ignite ignite, String name, int replicas) {
...
for (int i = 0; i < 1; i++) {
...
}
}{code}
an inconsistent read is reproduced under the following flow:
# table.keyValueView.put(k1)
## PartitionListener#handleUpsertCommand on Node B
## PartitionListener#handleUpsertCommand on Node C
## PartitionListener#handleUpsertCommand on Node D
## P
