[jira] [Updated] (IGNITE-17094) ColumnMetadata.nullable() returns value for non-nullable columns.
[ https://issues.apache.org/jira/browse/IGNITE-17094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Orlov updated IGNITE-17094: -- Ignite Flags: (was: Docs Required,Release Notes Required) > ColumnMetadata.nullable() returns value for non-nullable columns. > - > > Key: IGNITE-17094 > URL: https://issues.apache.org/jira/browse/IGNITE-17094 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Andrey Mashenkov >Assignee: Konstantin Orlov >Priority: Major > Labels: ignite-3 > > See ItSqlAsynchronousApiTest.metadata() test. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17194) The update-versions script not working on different OS
[
https://issues.apache.org/jira/browse/IGNITE-17194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-17194:
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> The update-versions script not working on different OS
> --
>
> Key: IGNITE-17194
> URL: https://issues.apache.org/jira/browse/IGNITE-17194
> Project: Ignite
> Issue Type: Task
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Fix For: 2.14
>
>
> {code}
> 17:39:00 Updating Java versions to 2.13.0 with Maven...
> 17:39:00 sed: can't read : No such file or directory
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (IGNITE-17194) The update-versions script not working on different OS
Maxim Muzafarov created IGNITE-17194:
Summary: The update-versions script not working on different OS
Key: IGNITE-17194
URL: https://issues.apache.org/jira/browse/IGNITE-17194
Project: Ignite
Issue Type: Task
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
Fix For: 2.14
{code}
17:39:00 Updating Java versions to 2.13.0 with Maven...
17:39:00 sed: can't read : No such file or directory
{code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-17180) Remove dev-tools directory from the source code
[ https://issues.apache.org/jira/browse/IGNITE-17180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-17180: - Ignite Flags: (was: Docs Required,Release Notes Required) > Remove dev-tools directory from the source code > --- > > Key: IGNITE-17180 > URL: https://issues.apache.org/jira/browse/IGNITE-17180 > Project: Ignite > Issue Type: Task >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > The directory `dev-tools` is not used and can be removed. > See the discussion thread for details: > https://lists.apache.org/thread/l9jcnsjjg51njxp0cblzht584g82l522 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17141) Use Maven to build .NET
[ https://issues.apache.org/jira/browse/IGNITE-17141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-17141: - Release Note: Added ability to build .NET from Maven command line > Use Maven to build .NET > --- > > Key: IGNITE-17141 > URL: https://issues.apache.org/jira/browse/IGNITE-17141 > Project: Ignite > Issue Type: Task >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.14 > > Time Spent: 3h 40m > Remaining Estimate: 0h > > It seems we can build the .NET using maven + maven-ant-plugin. This will > simplify the Apache Ignite release build distribution and will add a single > build point for the whole release. > Discussion: > https://lists.apache.org/thread/9os553vhcryko1jlfzywmx977o6lyor5 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17193) Map IgniteException to problem json
[ https://issues.apache.org/jira/browse/IGNITE-17193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr updated IGNITE-17193: --- Description: According to https://www.rfc-editor.org/rfc/rfc7807.html HTTP API has to return application/problem+json if an error happens. https://cwiki.apache.org/confluence/display/IGNITE/IEP-84%3A+Error+handling describes how Ignite 3 throws exceptions. The aim of this ticket is to map IgniteException to application/problem+json. Note, that there is no implementation of IEP-84. So, leave TODOs with Jira tickets where it is needed. Mapping strategy: “title”: a short, human-readable summary of the problem type “status”: HTTP status code “code”: error code “type”: URI to the error documentation (optional) “detail”: a human-readable explanation of the problem (optional) “invalid-params”: list of parameters that did not pass the validation (optional) “node”: Ignite 3 node name (optional) “trace-id”: unique identifier that will help to trace the error in the log (optional). was: According to https://www.rfc-editor.org/rfc/rfc7807.html HTTP API has to return application/problem+json if an error happens. https://cwiki.apache.org/confluence/display/IGNITE/IEP-84%3A+Error+handling describes how Ignite 3 throws exceptions. The aim of this ticket is to map IgniteException to application/problem+json. Note, that there is no implementation of IEP-84. So, leave TODOs with Jira tickets where it is needed. > Map IgniteException to problem json > --- > > Key: IGNITE-17193 > URL: https://issues.apache.org/jira/browse/IGNITE-17193 > Project: Ignite > Issue Type: Task >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha6 > > > According to https://www.rfc-editor.org/rfc/rfc7807.html HTTP API has to > return application/problem+json if an error happens. > https://cwiki.apache.org/confluence/display/IGNITE/IEP-84%3A+Error+handling > describes how Ignite 3 throws exceptions. > The aim of this ticket is to map IgniteException to application/problem+json. > Note, that there is no implementation of IEP-84. So, leave TODOs with Jira > tickets where it is needed. > Mapping strategy: > “title”: a short, human-readable summary of the problem type > “status”: HTTP status code > “code”: error code > “type”: URI to the error documentation (optional) > “detail”: a human-readable explanation of the problem (optional) > “invalid-params”: list of parameters that did not pass the validation > (optional) > “node”: Ignite 3 node name (optional) > “trace-id”: unique identifier that will help to trace the error in the log > (optional). -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (IGNITE-17193) Map IgniteException to problem json
[ https://issues.apache.org/jira/browse/IGNITE-17193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr reassigned IGNITE-17193: -- Assignee: Aleksandr > Map IgniteException to problem json > --- > > Key: IGNITE-17193 > URL: https://issues.apache.org/jira/browse/IGNITE-17193 > Project: Ignite > Issue Type: Task >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha6 > > > According to https://www.rfc-editor.org/rfc/rfc7807.html HTTP API has to > return application/problem+json if an error happens. > https://cwiki.apache.org/confluence/display/IGNITE/IEP-84%3A+Error+handling > describes how Ignite 3 throws exceptions. > The aim of this ticket is to map IgniteException to application/problem+json. > Note, that there is no implementation of IEP-84. So, leave TODOs with Jira > tickets where it is needed. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17193) Map IgniteException to problem json
Aleksandr created IGNITE-17193: -- Summary: Map IgniteException to problem json Key: IGNITE-17193 URL: https://issues.apache.org/jira/browse/IGNITE-17193 Project: Ignite Issue Type: Task Reporter: Aleksandr Fix For: 3.0.0-alpha6 According to https://www.rfc-editor.org/rfc/rfc7807.html HTTP API has to return application/problem+json if an error happens. https://cwiki.apache.org/confluence/display/IGNITE/IEP-84%3A+Error+handling describes how Ignite 3 throws exceptions. The aim of this ticket is to map IgniteException to application/problem+json. Note, that there is no implementation of IEP-84. So, leave TODOs with Jira tickets where it is needed. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (IGNITE-17162) Fix init cluster command options
[ https://issues.apache.org/jira/browse/IGNITE-17162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Pakhnushev reassigned IGNITE-17162: - Assignee: Vadim Pakhnushev > Fix init cluster command options > > > Key: IGNITE-17162 > URL: https://issues.apache.org/jira/browse/IGNITE-17162 > Project: Ignite > Issue Type: Task >Reporter: Vadim Pakhnushev >Assignee: Vadim Pakhnushev >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > > Currently "cluster init" command uses --node-endpoint option which requires > passing endpoint without the URL schema. > It should use --cluster-url option as stated in the IEP. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17192) IEP-92 implementation
Aleksey Demakov created IGNITE-17192: Summary: IEP-92 implementation Key: IGNITE-17192 URL: https://issues.apache.org/jira/browse/IGNITE-17192 Project: Ignite Issue Type: Improvement Reporter: Aleksey Demakov Assignee: Aleksey Demakov Fix For: 3.0.0-alpha6 Provide Java implementation of [IEP-92|https://cwiki.apache.org/confluence/display/IGNITE/IEP-92%3A+Binary+Tuple+Format] following the discussion on the [dev list|https://lists.apache.org/thread/0m14y1y25krompm0d2vsbmc5lo8727zy]. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17112) Consistency check must fix counter after the consistency fix
[
https://issues.apache.org/jira/browse/IGNITE-17112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-17112:
--
Labels: iep-31 ise (was: ise)
> Consistency check must fix counter after the consistency fix
>
>
> Key: IGNITE-17112
> URL: https://issues.apache.org/jira/browse/IGNITE-17112
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Labels: iep-31, ise
> Fix For: 2.14
>
>
> Consistency repair repairs the consistency for the data committed on at least
> single node.
> But partition counter may have gaps for prepared, but not committed data, and
> such gaps will cause exception on cluster activation:
> {noformat}
> 2022-06-03 22:01:59.695
> [ERROR][sys-#322][org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager]
> Failed to update partition counter. Most probably a node with most actual
> data is out of topology or data streamer is used in preload mode
> (allowOverride=false) concurrently with cache transactions [grpName=XXX,
> partId=9099]
> org.apache.ignite.IgniteCheckedException: Failed to update the counter
> [newVal=4854911, curState=Counter [lwm=4854911, holes={4854912=Item
> [start=4854912, delta=1]}, maxApplied=4854913, hwm=4854911]]
> at
> org.apache.ignite.internal.processors.cache.PartitionUpdateCounterTrackingImpl.update(PartitionUpdateCounterTrackingImpl.java:153)
> ~[ignite-core-2.11.0-p5.jar:2.11.0-p5]
> at
> org.apache.ignite.internal.processors.cache.PartitionUpdateCounterErrorWrapper.update(PartitionUpdateCounterErrorWrapper.java:97)
> ~[ignite-core-2.11.0-p5.jar:2.11.0-p5]
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.updateCounter(IgniteCacheOffheapManagerImpl.java:1687)
> ~[ignite-core-2.11.0-p5.jar:2.11.0-p5]
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.updateCounter(GridCacheOffheapManager.java:2530)
> ~[ignite-core-2.11.0-p5.jar:2.11.0-p5]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtLocalPartition.updateCounter(GridDhtLocalPartition.java:913)
> ~[ignite-core-2.11.0-p5.jar:2.11.0-p5]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtPartitionTopologyImpl.update(GridDhtPartitionTopologyImpl.java:1491)
> ~[ignite-core-2.11.0-p5.jar:2.11.0-p5]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.lambda$updatePartitionFullMap$81bdb8e8$1(GridDhtPartitionsExchangeFuture.java:4817)
> ~[ignite-core-2.11.0-p5.jar:2.11.0-p5]
> at
> org.apache.ignite.internal.util.IgniteUtils.lambda$null$1(IgniteUtils.java:11358)
> ~[ignite-core-2.11.0-p5.jar:2.11.0-p5]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> [?:1.8.0_322]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [?:1.8.0_322]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [?:1.8.0_322]
> at java.lang.Thread.run(Thread.java:750)
> {noformat}
> Consistency check via cli must close this gaps on successful consistency
> repair.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-17114) Idle_verify must print and compare full partition counter state instead of just LWM
[ https://issues.apache.org/jira/browse/IGNITE-17114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-17114: -- Labels: iep-31 ise (was: ise) > Idle_verify must print and compare full partition counter state instead of > just LWM > --- > > Key: IGNITE-17114 > URL: https://issues.apache.org/jira/browse/IGNITE-17114 > Project: Ignite > Issue Type: Sub-task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Labels: iep-31, ise > Fix For: 2.14 > > Time Spent: 20m > Remaining Estimate: 0h > > Gaps also should be printed/compared. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17191) Consistency check should support cacheGroup as a param as well
Anton Vinogradov created IGNITE-17191: - Summary: Consistency check should support cacheGroup as a param as well Key: IGNITE-17191 URL: https://issues.apache.org/jira/browse/IGNITE-17191 Project: Ignite Issue Type: Sub-task Reporter: Anton Vinogradov Assignee: Anton Vinogradov Both cache and cacheGroup should be supported at --cache param -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (IGNITE-17190) Calcite engine. Unbind statistics from H2
[ https://issues.apache.org/jira/browse/IGNITE-17190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky reassigned IGNITE-17190: Assignee: Ivan Daschinsky > Calcite engine. Unbind statistics from H2 > - > > Key: IGNITE-17190 > URL: https://issues.apache.org/jira/browse/IGNITE-17190 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksey Plekhanov >Assignee: Ivan Daschinsky >Priority: Major > Labels: calcite, calcite2-required > > Currently, table statistics in Ignite uses some H2 classes (Value for > example). We should unbind statistics from H2 and move statistics to the core > module to be able to use it in calcite module without dependency to H2. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-15424) Calcite engine. Move schema management infrastructure to the core module
[
https://issues.apache.org/jira/browse/IGNITE-15424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov updated IGNITE-15424:
---
Ignite Flags: (was: Docs Required,Release Notes Required)
> Calcite engine. Move schema management infrastructure to the core module
> -
>
> Key: IGNITE-15424
> URL: https://issues.apache.org/jira/browse/IGNITE-15424
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: calcite2-required
>
> Currently, schema management commands initiated in the {{ignite-core}}
> module, but all processing implemented in the {{ignite-indexing}} module.
> Ignite Calciite SQL engine use {{SchemaChangeListener}} to maintain own
> structures.
> To get rid of {{ignite-indexing}} (and H2) dependency from the
> {{ignite-calcite}} module we should move schema management implementation to
> the core module.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-15424) Calcite engine. Move schema management infrastructure to the core module
[
https://issues.apache.org/jira/browse/IGNITE-15424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov updated IGNITE-15424:
---
Labels: calcite2-required (was: calcite2-required calcite3-required)
> Calcite engine. Move schema management infrastructure to the core module
> -
>
> Key: IGNITE-15424
> URL: https://issues.apache.org/jira/browse/IGNITE-15424
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: calcite2-required
>
> Currently, schema management commands initiated in the {{ignite-core}}
> module, but all processing implemented in the {{ignite-indexing}} module.
> Ignite Calciite SQL engine use {{SchemaChangeListener}} to maintain own
> structures.
> To get rid of {{ignite-indexing}} (and H2) dependency from the
> {{ignite-calcite}} module we should move schema management implementation to
> the core module.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-15424) Calcite engine. Move schema management infrastructure to the core module
[
https://issues.apache.org/jira/browse/IGNITE-15424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov updated IGNITE-15424:
---
Description:
Currently, schema management commands initiated in the {{ignite-core}} module,
but all processing implemented in the {{ignite-indexing}} module. Ignite
Calciite SQL engine use {{SchemaChangeListener}} to maintain own structures.
To get rid of {{ignite-indexing}} (and H2) dependency from the
{{ignite-calcite}} module we should move schema management implementation to
the core module.
was:
Currently, schema management commands initiated in the {{ignite-core}} module,
but all processing implemented in the {{ignite-indexing}} module. Ignite
Calciite SQL engine use {{SchemaChangeListener}} to maintain own structures.
To get rid of {{ignite-indexing}} (and H2) dependency from the
{{ignite-calcite}} module we should move schema management and statistics
management implementation to the core module.
> Calcite engine. Move schema management infrastructure to the core module
> -
>
> Key: IGNITE-15424
> URL: https://issues.apache.org/jira/browse/IGNITE-15424
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksey Plekhanov
>Assignee: Ivan Daschinsky
>Priority: Major
> Labels: calcite2-required, calcite3-required
>
> Currently, schema management commands initiated in the {{ignite-core}}
> module, but all processing implemented in the {{ignite-indexing}} module.
> Ignite Calciite SQL engine use {{SchemaChangeListener}} to maintain own
> structures.
> To get rid of {{ignite-indexing}} (and H2) dependency from the
> {{ignite-calcite}} module we should move schema management implementation to
> the core module.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Assigned] (IGNITE-15424) Calcite engine. Move schema management infrastructure to the core module
[
https://issues.apache.org/jira/browse/IGNITE-15424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov reassigned IGNITE-15424:
--
Assignee: Aleksey Plekhanov (was: Ivan Daschinsky)
> Calcite engine. Move schema management infrastructure to the core module
> -
>
> Key: IGNITE-15424
> URL: https://issues.apache.org/jira/browse/IGNITE-15424
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: calcite2-required, calcite3-required
>
> Currently, schema management commands initiated in the {{ignite-core}}
> module, but all processing implemented in the {{ignite-indexing}} module.
> Ignite Calciite SQL engine use {{SchemaChangeListener}} to maintain own
> structures.
> To get rid of {{ignite-indexing}} (and H2) dependency from the
> {{ignite-calcite}} module we should move schema management implementation to
> the core module.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-17190) Calcite engine. Unbind statistics from H2
[ https://issues.apache.org/jira/browse/IGNITE-17190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-17190: --- Labels: calcite calcite2-required (was: ) > Calcite engine. Unbind statistics from H2 > - > > Key: IGNITE-17190 > URL: https://issues.apache.org/jira/browse/IGNITE-17190 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksey Plekhanov >Priority: Major > Labels: calcite, calcite2-required > > Currently, table statistics in Ignite uses some H2 classes (Value for > example). We should unbind statistics from H2 and move statistics to the core > module to be able to use it in calcite module without dependency to H2. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17190) Calcite engine. Unbind statistics from H2
Aleksey Plekhanov created IGNITE-17190: -- Summary: Calcite engine. Unbind statistics from H2 Key: IGNITE-17190 URL: https://issues.apache.org/jira/browse/IGNITE-17190 Project: Ignite Issue Type: Improvement Reporter: Aleksey Plekhanov Currently, table statistics in Ignite uses some H2 classes (Value for example). We should unbind statistics from H2 and move statistics to the core module to be able to use it in calcite module without dependency to H2. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-12117) Historical rebalance should NOT be processed in striped way
[
https://issues.apache.org/jira/browse/IGNITE-12117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luchnikov Alexander updated IGNITE-12117:
-
Labels: iep-16 ise (was: iep-16)
> Historical rebalance should NOT be processed in striped way
> ---
>
> Key: IGNITE-12117
> URL: https://issues.apache.org/jira/browse/IGNITE-12117
> Project: Ignite
> Issue Type: Task
>Reporter: Anton Vinogradov (Obsolete, actual is "av")
>Assignee: Alexey Scherbakov
>Priority: Major
> Labels: iep-16, ise
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Test
> {{org.apache.ignite.internal.processors.cache.transactions.TxPartitionCounterStateConsistencyTest#testPartitionConsistencyWithBackupsRestart}}
> have failure on attempt to handle historical rebalance using un-striped pool.
> You can reproduce it by replacing
> {noformat}
> if (historical) // Can not be reordered.
>
> ctx.kernalContext().getStripedRebalanceExecutorService().execute(r,
> Math.abs(nodeId.hashCode()));
> {noformat}
> with
> {noformat}
> if (historical) // Can be reordered?
> ctx.kernalContext().getRebalanceExecutorService().execute(r);
> {noformat}
> and you will gain the following
> {noformat}
> ava.lang.AssertionError: idle_verify failed on 1 node.
> idle_verify check has finished, found 7 conflict partitions:
> [counterConflicts=0, hashConflicts=7]
> Hash conflicts:
> Conflict partition: PartitionKeyV2 [grpId=1544803905, grpName=default,
> partId=23]
> Partition instances: [PartitionHashRecordV2 [isPrimary=false,
> consistentId=nodetransactions.TxPartitionCounterStateConsistencyHistoryRebalanceTest1,
> updateCntr=707143, partitionState=OWNING, size=495, partHash=-1503789370],
> PartitionHashRecordV2 [isPrimary=false,
> consistentId=nodetransactions.TxPartitionCounterStateConsistencyHistoryRebalanceTest2,
> updateCntr=707143, partitionState=OWNING, size=494, partHash=-1538739200]]
> Conflict partition: PartitionKeyV2 [grpId=1544803905, grpName=default,
> partId=8]
>
> {noformat}
> So, we need to investigate reasons and provide proper historical rebalance
> refactoring to use the unstriped pool, if possible.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-13777) idle_verify should report real size of the partitions
[ https://issues.apache.org/jira/browse/IGNITE-13777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luchnikov Alexander updated IGNITE-13777: - Labels: ise (was: ) > idle_verify should report real size of the partitions > - > > Key: IGNITE-13777 > URL: https://issues.apache.org/jira/browse/IGNITE-13777 > Project: Ignite > Issue Type: Improvement >Reporter: Stanislav Lukyanov >Priority: Major > Labels: ise > > Currently, idle_verify checks the content of partitions (through hash) and > the partition size that is stored in the partition meta. It will be better if > idle_verify also counts the entries inside the partition and returns both the > size from the meta AND the real size. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-8874) Blinking node in cluster may cause data corruption
[
https://issues.apache.org/jira/browse/IGNITE-8874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luchnikov Alexander updated IGNITE-8874:
Labels: ise (was: )
> Blinking node in cluster may cause data corruption
> --
>
> Key: IGNITE-8874
> URL: https://issues.apache.org/jira/browse/IGNITE-8874
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Dmitry Sherstobitov
>Priority: Critical
> Labels: ise
>
> All caches with 2 backups
> 4 nodes in cluster
> # Start cluster, load data
> # Start transactional loading (8 threads, 100 ops/second put/get in each op)
> # Repeat 10 times: kill one node, clean LFS, start node again, wait for
> rebalance
> # Check idle_verify, check data corruption
> Here is idle_verify report:
> node2 - node that was blinking while test. Update counter are equal between
> partitions but data is different.
> {code:java}
> Conflict partition: PartitionKey [grpId=374280886, grpName=cache_group_3,
> partId=41]
> Partition instances: [PartitionHashRecord [isPrimary=true,
> partHash=885018783, updateCntr=16, size=15, consistentId=node4],
> PartitionHashRecord [isPrimary=false, partHash=885018783, updateCntr=16,
> size=15, consistentId=node3], PartitionHashRecord [isPrimary=false,
> partHash=-357162793, updateCntr=16, size=15, consistentId=node2]]
> Conflict partition: PartitionKey [grpId=1586135625,
> grpName=cache_group_1_015, partId=15]
> Partition instances: [PartitionHashRecord [isPrimary=true,
> partHash=-562597978, updateCntr=22, size=16, consistentId=node3],
> PartitionHashRecord [isPrimary=false, partHash=-562597978, updateCntr=22,
> size=16, consistentId=node1], PartitionHashRecord [isPrimary=false,
> partHash=780813725, updateCntr=22, size=16, consistentId=node2]]
> Conflict partition: PartitionKey [grpId=374280885, grpName=cache_group_2,
> partId=75]
> Partition instances: [PartitionHashRecord [isPrimary=true,
> partHash=-1500797699, updateCntr=21, size=16, consistentId=node3],
> PartitionHashRecord [isPrimary=false, partHash=-1500797699, updateCntr=21,
> size=16, consistentId=node1], PartitionHashRecord [isPrimary=false,
> partHash=-1592034435, updateCntr=21, size=16, consistentId=node2]]
> Conflict partition: PartitionKey [grpId=374280884, grpName=cache_group_1,
> partId=713]
> Partition instances: [PartitionHashRecord [isPrimary=false,
> partHash=-63058826, updateCntr=4, size=2, consistentId=node3],
> PartitionHashRecord [isPrimary=true, partHash=-63058826, updateCntr=4,
> size=2, consistentId=node1], PartitionHashRecord [isPrimary=false,
> partHash=670869467, updateCntr=4, size=2, consistentId=node2]]
> Conflict partition: PartitionKey [grpId=374280886, grpName=cache_group_3,
> partId=11]
> Partition instances: [PartitionHashRecord [isPrimary=false,
> partHash=-224572810, updateCntr=17, size=16, consistentId=node3],
> PartitionHashRecord [isPrimary=true, partHash=-224572810, updateCntr=17,
> size=16, consistentId=node1], PartitionHashRecord [isPrimary=false,
> partHash=176419075, updateCntr=17, size=16, consistentId=node2]]{code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-9905) After transaction load cluster inconsistent
[
https://issues.apache.org/jira/browse/IGNITE-9905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luchnikov Alexander updated IGNITE-9905:
Labels: ise (was: )
> After transaction load cluster inconsistent
> ---
>
> Key: IGNITE-9905
> URL: https://issues.apache.org/jira/browse/IGNITE-9905
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Affects Versions: 2.7
>Reporter: ARomantsov
>Assignee: Ilya Lantukh
>Priority: Critical
> Labels: ise
>
> Loaded data into the cluster using transactions consisting of two get / two
> put
> Test env: one server, two server node, one client
> {code:java}
> idle_verify check has finished, found 60 conflict partitions:
> [counterConflicts=45, hashConflicts=15]
> Update counter conflicts:
> Conflict partition: PartitionKeyV2 [grpId=-1903385190,
> grpName=CACHEGROUP_PARTICLE_1, partId=98]
> Partition instances: [PartitionHashRecordV2 [isPrimary=true,
> consistentId=node2, updateCntr=1519, size=596, partHash=-1167688484],
> PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1520,
> size=596, partHash=-1167688484]]
> Conflict partition: PartitionKeyV2 [grpId=-1903385190,
> grpName=CACHEGROUP_PARTICLE_1, partId=34]
> Partition instances: [PartitionHashRecordV2 [isPrimary=false,
> consistentId=node2, updateCntr=1539, size=596, partHash=-99631005],
> PartitionHashRecordV2 [isPrimary=true, consistentId=node1, updateCntr=1537,
> size=596, partHash=-1284437377]]
> Conflict partition: PartitionKeyV2 [grpId=770187303,
> grpName=CACHEGROUP_PARTICLE_1, partId=31]
> Partition instances: [PartitionHashRecordV2 [isPrimary=true,
> consistentId=node2, updateCntr=15, size=4, partHash=-1125172674],
> PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=16,
> size=4, partHash=-1125172674]]
> Conflict partition: PartitionKeyV2 [grpId=-1903385190,
> grpName=CACHEGROUP_PARTICLE_1, partId=39]
> Partition instances: [PartitionHashRecordV2 [isPrimary=true,
> consistentId=node2, updateCntr=1555, size=596, partHash=-40303136],
> PartitionHashRecordV2 [isPrimary=false, consistentId=node1, updateCntr=1556,
> size=596, partHash=-40303136]]
> Conflict partition: PartitionKeyV2 [grpId=-1903385190,
> grpName=CACHEGROUP_PARTICLE_1, partId=90]
> Partition instances: [PartitionHashRecordV2 [isPrimary=false,
> consistentId=node2, updateCntr=1557, size=596, partHash=-1295145299],
> PartitionHashRecordV2 [isPrimary=true, consistentId=node1, updateCntr=1556,
> size=596, partHash=-1221175703]]
> ...
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-10825) After node restart and and new node to BLT due load - some partition inconsistent
[
https://issues.apache.org/jira/browse/IGNITE-10825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luchnikov Alexander updated IGNITE-10825:
-
Labels: ise (was: )
> After node restart and and new node to BLT due load - some partition
> inconsistent
> -
>
> Key: IGNITE-10825
> URL: https://issues.apache.org/jira/browse/IGNITE-10825
> Project: Ignite
> Issue Type: Bug
> Components: data structures
>Affects Versions: 2.8
>Reporter: ARomantsov
>Priority: Critical
> Labels: ise
>
> {code:java}
> 14:12:20 [14:12:20][:573 :252] idle_verify check has finished, found 2
> conflict partitions: [counterConflicts=1, hashConflicts=1]
> 14:12:20 [14:12:20][:573 :252] Update counter conflicts:
> 14:12:20 [14:12:20][:573 :252] Conflict partition: PartitionKeyV2
> [grpId=374280887, grpName=cache_group_4, partId=115]
> 14:12:20 [14:12:20][:573 :252] Partition instances:
>
> [PartitionHashRecordV2 [isPrimary=false, consistentId=node_1_5,
> updateCntr=10, size=2, partHash=-979021948],
>
>PartitionHashRecordV2 [isPrimary=true, consistentId=node_1_2,
> updateCntr=11, size=2, partHash=-731597536],
>
>PartitionHashRecordV2 [isPrimary=false, consistentId=node_1_1,
> updateCntr=11, size=2, partHash=-731597536],
>
>PartitionHashRecordV2 [isPrimary=false, consistentId=node_1_3,
> updateCntr=11, size=2, partHash=-731597536],
>
>PartitionHashRecordV2 [isPrimary=false, consistentId=node_1_6,
> updateCntr=11, size=2, partHash=-731597536],
>
>PartitionHashRecordV2 [isPrimary=false, consistentId=node_1_4,
> updateCntr=11, size=2, partHash=-731597536],
>
>PartitionHashRecordV2 [isPrimary=false, consistentId=node_1_10001,
> updateCntr=11, size=2, partHash=-731597536]]
> 14:12:20 [14:12:20][:573 :252] Hash conflicts:
> 14:12:20 [14:12:20][:573 :252] Conflict partition: PartitionKeyV2
> [grpId=374280887, grpName=cache_group_4, partId=115]
> 14:12:20 [14:12:20][:573 :252] Partition instances:
>
> [PartitionHashRecordV2 [isPrimary=false, consistentId=node_1_5,
> updateCntr=10, size=2, partHash=-979021948],
>
> PartitionHashRecordV2 [isPrimary=true, consistentId=node_1_2,
> updateCntr=11, size=2, partHash=-731597536],
>
> PartitionHashRecordV2 [isPrimary=false, consistentId=node_1_1,
> updateCntr=11, size=2, partHash=-731597536],
>
> PartitionHashRecordV2 [isPrimary=false, consistentId=node_1_3,
> updateCntr=11, size=2, partHash=-731597536],
>
> PartitionHashRecordV2 [isPrimary=false, consistentId=node_1_6,
> updateCntr=11, size=2, partHash=-731597536],
>
> PartitionHashRecordV2 [isPrimary=false, consistentId=node_1_4,
> updateCntr=11, size=2, partHash=-731597536],
>
> PartitionHashRecordV2 [isPrimary=false, consistentId=node_1_10001,
> updateCntr=11, size=2, partHash=-731597536]]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (IGNITE-10979) Add documentation for control.sh idle_verify --check-crc
[ https://issues.apache.org/jira/browse/IGNITE-10979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1700#comment-1700 ] Luchnikov Alexander commented on IGNITE-10979: -- [~Artem Budnikov] Сould you describe in the documentation: * When should this flag be used? * Is there any additional overhead when using it? > Add documentation for control.sh idle_verify --check-crc > > > Key: IGNITE-10979 > URL: https://issues.apache.org/jira/browse/IGNITE-10979 > Project: Ignite > Issue Type: New Feature > Components: control.sh, documentation >Reporter: Sergey Antonov >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.14 > > > We should document new option --check-crc in control.sh idle_verify command. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-10979) Add documentation for control.sh idle_verify --check-crc
[ https://issues.apache.org/jira/browse/IGNITE-10979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luchnikov Alexander updated IGNITE-10979: - Labels: ise (was: ) > Add documentation for control.sh idle_verify --check-crc > > > Key: IGNITE-10979 > URL: https://issues.apache.org/jira/browse/IGNITE-10979 > Project: Ignite > Issue Type: New Feature > Components: control.sh, documentation >Reporter: Sergey Antonov >Assignee: Artem Budnikov >Priority: Major > Labels: ise > Fix For: 2.14 > > > We should document new option --check-crc in control.sh idle_verify command. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-11076) Add documentation for control.sh idle_verify --exclude-caches and --cache-filter
[
https://issues.apache.org/jira/browse/IGNITE-11076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luchnikov Alexander updated IGNITE-11076:
-
Labels: ise (was: )
> Add documentation for control.sh idle_verify --exclude-caches and
> --cache-filter
>
>
> Key: IGNITE-11076
> URL: https://issues.apache.org/jira/browse/IGNITE-11076
> Project: Ignite
> Issue Type: Task
> Components: control.sh, documentation
>Reporter: Sergey Antonov
>Assignee: Artem Budnikov
>Priority: Major
> Labels: ise
> Fix For: 2.14
>
>
> control.sh cache --help output
> {noformat}
> The '--cache subcommand' is used to get information about and perform actions
> with caches. The command has the following syntax:
> control.sh [--host HOST_OR_IP] [--port PORT] [--user USER] [--password
> PASSWORD] [--ping-interval PING_INTERVAL] [--ping-timeout PING_TIMEOUT]
> [--ssl-protocol SSL_PROTOCOL[, SSL_PROTOCOL_2, ..., SSL_PROTOCOL_N]]
> [--ssl-cipher-suites SSL_CIPHER_1[, SSL_CIPHER_2, ..., SSL_CIPHER_N]]
> [--ssl-key-algorithm SSL_KEY_ALGORITHM] [--keystore-type KEYSTORE_TYPE]
> [--keystore KEYSTORE_PATH] [--keystore-password KEYSTORE_PASSWORD]
> [--truststore-type TRUSTSTORE_TYPE] [--truststore TRUSTSTORE_PATH]
> [--truststore-password TRUSTSTORE_PASSWORD] --cache [subcommand]
>
> The subcommands that take [nodeId] as an argument ('list', 'contention' and
> 'validate_indexes') will be executed on the given node or on all server nodes
> if the option is not specified. Other commands will run on a random server
> node.
> Subcommands:
>
> --cache list regexPattern [--groups|--seq] [nodeId] [--config]
> [--output-format multi-line]
> Show information about caches, groups or sequences that match a regular
> expression. When executed without parameters, this subcommand prints the list
> of caches.
> Parameters:
> --config - print all configuration parameters for each cache.
> --output-format multi-line - print configuration parameters per line. This
> option has effect only when used with --config and without [--groups|--seq].
> --groups - print information about groups.
> --seq - print information about sequences.
>
> --cache contention minQueueSize [nodeId] [maxPrint]
> Show the keys that are point of contention for multiple transactions.
>
> --cache idle_verify [--dump] [--skip-zeros] [--check-crc] [(--exclude-caches
> cacheName1,...,cacheNameN)|(--cache-filter
> ALL|SYSTEM|PERSISTENT|NOT_PERSISTENT)|cacheName1,...,cacheNameN]
> Verify counters and hash sums of primary and backup partitions for the
> specified caches on an idle cluster and print out the differences, if any.
> Parameters:
> --check-crc - check the CRC-sum of pages stored on disk before verifying data
> consistency in partitions between primary and backup nodes.
>
> --cache validate_indexes [cacheName1,...,cacheNameN] [nodeId] [--check-first
> N|--check-through K]
> Validate indexes on an idle cluster and print out the keys that are missing
> in the indexes.
> Parameters:
> --check-first N - validate only the first N keys
> --check-through K - validate every Kth key
>
> --cache distribution nodeId|null [cacheName1,...,cacheNameN]
> [--user-attributes attrName1,...,attrNameN]
> Prints the information about partition distribution.
>
> --cache reset_lost_partitions cacheName1,...,cacheNameN
> Reset the state of lost partitions for the specified caches.{noformat}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-13371) Sporadic partition inconsistency after historical rebalancing of updates with same key put-remove pattern
[
https://issues.apache.org/jira/browse/IGNITE-13371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luchnikov Alexander updated IGNITE-13371:
-
Labels: ise (was: )
> Sporadic partition inconsistency after historical rebalancing of updates with
> same key put-remove pattern
> -
>
> Key: IGNITE-13371
> URL: https://issues.apache.org/jira/browse/IGNITE-13371
> Project: Ignite
> Issue Type: Bug
>Reporter: Ivan Rakov
>Assignee: Ivan Rakov
>Priority: Major
> Labels: ise
>
> h4. scenario
> # start 3 servers 3 clients, create caches
> # clients start combined put + 1% remove of data in transactions
> PESSIMISTIC/REPEATABLE_READ
> ## kill one node
> ## restart one node
> # ensure all transactions completed
> # run idle_verify
> Expected: no conflicts found
> Actual:
> {noformat}
> [12:03:18][:55 :230] Control utility --cache idle_verify --skip-zeros
> --cache-filter PERSISTENT
> [12:03:20][:55 :230] Control utility [ver. 8.7.13#20200228-sha1:7b016d63]
> [12:03:20][:55 :230] 2020 Copyright(C) GridGain Systems, Inc. and Contributors
> [12:03:20][:55 :230] User: prtagent
> [12:03:20][:55 :230] Time: 2020-03-03T12:03:19.836
> [12:03:20][:55 :230] Command [CACHE] started
> [12:03:20][:55 :230] Arguments: --host 172.25.1.11 --port 11211 --cache
> idle_verify --skip-zeros --cache-filter PERSISTENT
> [12:03:20][:55 :230]
>
> [12:03:20][:55 :230] idle_verify task was executed with the following args:
> caches=[], excluded=[], cacheFilter=[PERSISTENT]
> [12:03:20][:55 :230] idle_verify check has finished, found 1 conflict
> partitions: [counterConflicts=0, hashConflicts=1]
> [12:03:20][:55 :230] Hash conflicts:
> [12:03:20][:55 :230] Conflict partition: PartitionKeyV2 [grpId=1338167321,
> grpName=cache_group_3_088_1, partId=24]
> [12:03:20][:55 :230] Partition instances: [PartitionHashRecordV2
> [isPrimary=false, consistentId=node_1_2, updateCntr=172349,
> partitionState=OWNING, size=6299, partHash=157875238], PartitionHashRecordV2
> [isPrimary=true, consistentId=node_1_1, updateCntr=172349,
> partitionState=OWNING, size=6299, partHash=157875238], PartitionHashRecordV2
> [isPrimary=false, consistentId=node_1_4, updateCntr=172349,
> partitionState=OWNING, size=6300, partHash=-944532882]]
> [12:03:20][:55 :230] Command [CACHE] finished with code: 0
> [12:03:20][:55 :230] Control utility has completed execution at:
> 2020-03-03T12:03:20.593
> [12:03:20][:55 :230] Execution time: 757 ms
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-15167) Control.sh should be able to fix cache inconsistency using Read Repair
[ https://issues.apache.org/jira/browse/IGNITE-15167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luchnikov Alexander updated IGNITE-15167: - Labels: iep-31 ise (was: iep-31) > Control.sh should be able to fix cache inconsistency using Read Repair > -- > > Key: IGNITE-15167 > URL: https://issues.apache.org/jira/browse/IGNITE-15167 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Critical > Labels: iep-31, ise > > Inconsistent caches can be found using idle_verify > (https://ignite.apache.org/docs/latest/tools/control-script#verifying-partition-checksums). > Additional commands allow finding/fixing inconsistent entries should be added > to control.sh. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-15327) Idle_verify fails on cluster check when nodesFilter is used
[
https://issues.apache.org/jira/browse/IGNITE-15327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luchnikov Alexander updated IGNITE-15327:
-
Labels: ise (was: )
> Idle_verify fails on cluster check when nodesFilter is used
> ---
>
> Key: IGNITE-15327
> URL: https://issues.apache.org/jira/browse/IGNITE-15327
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Anton Vinogradov
>Priority: Major
> Labels: ise
>
> Start cluster and create a cache with a filter
> {noformat}
> cfg.setNodeFilter(node -> !node.consistentId().equals(filteredId));
> {noformat}
> and idle_verify will return you
> {noformat}
> The check procedure task was executed with the following args: caches=[],
> excluded=[], cacheFilter=[DEFAULT]
> The check procedure failed.
> There are no caches matching given filter options.
> The check procedure failed on nodes:
> Node ID: 157c034a-4dfa-428f-a671-569fbad2 [127.0.0.1]
> Consistent ID: gridCommandHandlerTest2
> See log for additional information.
> /Users/user/IdeaProjects/ignite/work/idle_verify-2021-08-17T16-56-15_283.txt
> Control utility [ver. 2.12.0-SNAPSHOT#20210817-sha1:DEV]
> 2021 Copyright(C) Apache Software Foundation
> User: user
> Time: 2021-08-17T16:56:09.858
> Command [CACHE] started
> Arguments: --cache idle_verify --yes
>
> Command [CACHE] finished with code: 0
> Control utility has completed execution at: 2021-08-17T16:56:15.298
> Execution time: 5440 ms
> {noformat}
> because of empty caches list on a filtered node
> {noformat}
> class
> org.apache.ignite.internal.processors.cache.verify.NoMatchingCachesException:
> null
> at
> org.apache.ignite.internal.processors.cache.verify.VerifyBackupPartitionsTaskV2$VerifyBackupPartitionsJobV2.getGroupIds(VerifyBackupPartitionsTaskV2.java:335)
> at
> org.apache.ignite.internal.processors.cache.verify.VerifyBackupPartitionsTaskV2$VerifyBackupPartitionsJobV2.execute(VerifyBackupPartitionsTaskV2.java:206)
> at
> org.apache.ignite.internal.processors.cache.verify.VerifyBackupPartitionsTaskV2$VerifyBackupPartitionsJobV2.execute(VerifyBackupPartitionsTaskV2.java:171)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:601)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:7253)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:595)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:522)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:125)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1305)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:2155)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1908)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1529)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$5300(GridIoManager.java:242)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.execute(GridIoManager.java:1422)
> at
> org.apache.ignite.internal.managers.communication.TraceRunnable.run(TraceRunnable.java:55)
> {noformat}
> BTW, don't forget to remove the following
> {noformat}
> // Another cache without nodeFilter required to perform idle_verify check.
> // See https://issues.apache.org/jira/browse/IGNITE-15327 for details.
> ignite.getOrCreateCache(cacheConfiguration(true)).getName();
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (IGNITE-15835) Add control.sh utility feature to detect partition reserve counter(HWM) inconsistency.
[ https://issues.apache.org/jira/browse/IGNITE-15835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luchnikov Alexander updated IGNITE-15835: - Labels: ise (was: ) > Add control.sh utility feature to detect partition reserve counter(HWM) > inconsistency. > -- > > Key: IGNITE-15835 > URL: https://issues.apache.org/jira/browse/IGNITE-15835 > Project: Ignite > Issue Type: Improvement >Reporter: Eduard Rakhmankulov >Assignee: Eduard Rakhmankulov >Priority: Major > Labels: ise > > Check during idle_verify that update and reserve counters are consistent (HWM > >= LWM). > The current transaction protocol implementation allows lagging of HWM from > LWM on *backup* partitions. Therefore, idle_verify should check only primary > partitions. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17086) SQL: long query warning not printed for lazy queries
[ https://issues.apache.org/jira/browse/IGNITE-17086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-17086: - Priority: Minor (was: Major) > SQL: long query warning not printed for lazy queries > > > Key: IGNITE-17086 > URL: https://issues.apache.org/jira/browse/IGNITE-17086 > Project: Ignite > Issue Type: Bug >Reporter: Amelchev Nikita >Priority: Minor > Labels: ise > Attachments: LongQueryWarningTest.java > > > Long query warning not printed for lazy queries. See reproducer. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17189) Java 17: Untrusted Ignite node never exits after failure to connect to the cluster
Alexey Kukushkin created IGNITE-17189:
-
Summary: Java 17: Untrusted Ignite node never exits after failure
to connect to the cluster
Key: IGNITE-17189
URL: https://issues.apache.org/jira/browse/IGNITE-17189
Project: Ignite
Issue Type: Bug
Components: security
Affects Versions: 2.13
Reporter: Alexey Kukushkin
*Steps to reproduce*
* Start an Ignite server node with SSL enabled
* Start another Ignite node with SSL enabled and SSL keys signed by wrong CA
authority
*Expected*
*Actual*
*Reproducer*
{code:java}
@Test
public void untrustedServerNeverExitsOnFailureToConnectToCluster() {
final Function igniteConfigurationFactory
= name ->
new IgniteConfiguration()
.setIgniteInstanceName(name)
.setDiscoverySpi(
new TcpDiscoverySpi()
.setIpFinder(
new
TcpDiscoveryVmIpFinder().setAddresses(Collections.singleton("127.0.0.1:47500..47501"))
)
);
final var serverSslContextFactory = new SslContextFactory();
serverSslContextFactory.setProtocols("TLSv1.2");
serverSslContextFactory.setKeyStoreFilePath("server-keys.jks");
serverSslContextFactory.setKeyStorePassword("123456".toCharArray());
serverSslContextFactory.setTrustStoreFilePath("server-trust.jks");
serverSslContextFactory.setTrustStorePassword("123456".toCharArray());
final var tmpSslContextFactory = new SslContextFactory();
tmpSslContextFactory.setProtocols("TLSv1.2");
tmpSslContextFactory.setKeyStoreFilePath("tmp-keys.jks");
tmpSslContextFactory.setKeyStorePassword("123456".toCharArray());
tmpSslContextFactory.setTrustStoreFilePath("tmp-trust.jks");
tmpSslContextFactory.setTrustStorePassword("123456".toCharArray());
final var igniteConfiguration =
igniteConfigurationFactory.apply("server1")
.setSslContextFactory(tmpSslContextFactory);
final var untrustedIgniteConfiguration =
igniteConfigurationFactory.apply("server2")
.setSslContextFactory(tmpSslContextFactory);
try (final var unused = Ignition.start(igniteConfiguration)) {
try (final var unused2 =
Ignition.start(untrustedIgniteConfiguration)) {
}
}
}
{code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Resolved] (IGNITE-17188) Get rid of GridNearReadRepairAbstractFuture.ByteArrayWrapper and replace with o.a.i.i.u.o.GridByteArrayWrapper
[ https://issues.apache.org/jira/browse/IGNITE-17188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov resolved IGNITE-17188. --- Release Note: o.a.i.i.u.o.GridByteArrayWrapper is a test class. See no way to keep only one in this situation :) Resolution: Won't Fix > Get rid of GridNearReadRepairAbstractFuture.ByteArrayWrapper and replace with > o.a.i.i.u.o.GridByteArrayWrapper > -- > > Key: IGNITE-17188 > URL: https://issues.apache.org/jira/browse/IGNITE-17188 > Project: Ignite > Issue Type: Sub-task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > > It looks like classes are the same. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IGNITE-17188) Get rid of GridNearReadRepairAbstractFuture.ByteArrayWrapper and replace with o.a.i.i.u.o.GridByteArrayWrapper
[ https://issues.apache.org/jira/browse/IGNITE-17188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17555471#comment-17555471 ] Anton Vinogradov commented on IGNITE-17188: --- o.a.i.i.u.o.GridByteArrayWrapper is a test class. See no way to keep only one in this situation :( > Get rid of GridNearReadRepairAbstractFuture.ByteArrayWrapper and replace with > o.a.i.i.u.o.GridByteArrayWrapper > -- > > Key: IGNITE-17188 > URL: https://issues.apache.org/jira/browse/IGNITE-17188 > Project: Ignite > Issue Type: Sub-task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > > It looks like classes are the same. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17188) Get rid of GridNearReadRepairAbstractFuture.ByteArrayWrapper and replace with o.a.i.i.u.o.GridByteArrayWrapper
[ https://issues.apache.org/jira/browse/IGNITE-17188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-17188: -- Release Note: o.a.i.i.u.o.GridByteArrayWrapper is a test class. See no way to keep only one in this situation :( was: o.a.i.i.u.o.GridByteArrayWrapper is a test class. See no way to keep only one in this situation :) > Get rid of GridNearReadRepairAbstractFuture.ByteArrayWrapper and replace with > o.a.i.i.u.o.GridByteArrayWrapper > -- > > Key: IGNITE-17188 > URL: https://issues.apache.org/jira/browse/IGNITE-17188 > Project: Ignite > Issue Type: Sub-task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > > It looks like classes are the same. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17188) Get rid of GridNearReadRepairAbstractFuture.ByteArrayWrapper and replace with o.a.i.i.u.o.GridByteArrayWrapper
[ https://issues.apache.org/jira/browse/IGNITE-17188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-17188: -- Release Note: (was: o.a.i.i.u.o.GridByteArrayWrapper is a test class. See no way to keep only one in this situation :() > Get rid of GridNearReadRepairAbstractFuture.ByteArrayWrapper and replace with > o.a.i.i.u.o.GridByteArrayWrapper > -- > > Key: IGNITE-17188 > URL: https://issues.apache.org/jira/browse/IGNITE-17188 > Project: Ignite > Issue Type: Sub-task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > > It looks like classes are the same. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (IGNITE-17094) ColumnMetadata.nullable() returns value for non-nullable columns.
[ https://issues.apache.org/jira/browse/IGNITE-17094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Orlov reassigned IGNITE-17094: - Assignee: Konstantin Orlov > ColumnMetadata.nullable() returns value for non-nullable columns. > - > > Key: IGNITE-17094 > URL: https://issues.apache.org/jira/browse/IGNITE-17094 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Andrey Mashenkov >Assignee: Konstantin Orlov >Priority: Major > Labels: ignite-3 > > See ItSqlAsynchronousApiTest.metadata() test. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17188) Get rid of GridNearReadRepairAbstractFuture.ByteArrayWrapper and replace with o.a.i.i.u.o.GridByteArrayWrapper
Anton Vinogradov created IGNITE-17188: - Summary: Get rid of GridNearReadRepairAbstractFuture.ByteArrayWrapper and replace with o.a.i.i.u.o.GridByteArrayWrapper Key: IGNITE-17188 URL: https://issues.apache.org/jira/browse/IGNITE-17188 Project: Ignite Issue Type: Sub-task Reporter: Anton Vinogradov Assignee: Anton Vinogradov It looks like classes are the same. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17178) Notify preconfigured event listeners about node start after resources were injected.
[ https://issues.apache.org/jira/browse/IGNITE-17178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-17178: - Ignite Flags: Release Notes Required (was: Docs Required,Release Notes Required) > Notify preconfigured event listeners about node start after resources were > injected. > > > Key: IGNITE-17178 > URL: https://issues.apache.org/jira/browse/IGNITE-17178 > Project: Ignite > Issue Type: Task >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > We need to notify preconfigured event listeners about node start after > resources were injected. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (IGNITE-17178) Notify preconfigured event listeners about node start after resources were injected.
[ https://issues.apache.org/jira/browse/IGNITE-17178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita resolved IGNITE-17178. -- Release Note: Fixed configured event listeners resource injection order. Resolution: Fixed LGTM. Merged into the master. [~PetrovMikhail], thank you for the contribution. > Notify preconfigured event listeners about node start after resources were > injected. > > > Key: IGNITE-17178 > URL: https://issues.apache.org/jira/browse/IGNITE-17178 > Project: Ignite > Issue Type: Task >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > We need to notify preconfigured event listeners about node start after > resources were injected. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17185) Incorporate SQL integration tests into every visa acquisition process
[ https://issues.apache.org/jira/browse/IGNITE-17185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Orlov updated IGNITE-17185: -- Ignite Flags: (was: Docs Required,Release Notes Required) > Incorporate SQL integration tests into every visa acquisition process > - > > Key: IGNITE-17185 > URL: https://issues.apache.org/jira/browse/IGNITE-17185 > Project: Ignite > Issue Type: Epic > Components: sql >Reporter: Konstantin Orlov >Assignee: Konstantin Orlov >Priority: Major > Labels: ignite-3 > > Currently a vast majority of SQL tests are disabled, thus excluded from daily > TC runs. This epic aimed to spot and fix all the issues preventing a stable > execution of integration tests. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17185) Incorporate SQL integration tests into every visa acquisition process
[ https://issues.apache.org/jira/browse/IGNITE-17185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Orlov updated IGNITE-17185: -- Labels: ignite-3 (was: ) > Incorporate SQL integration tests into every visa acquisition process > - > > Key: IGNITE-17185 > URL: https://issues.apache.org/jira/browse/IGNITE-17185 > Project: Ignite > Issue Type: Epic > Components: sql >Reporter: Konstantin Orlov >Assignee: Konstantin Orlov >Priority: Major > Labels: ignite-3 > > Currently a vast majority of SQL tests are disabled, thus excluded from daily > TC runs. This epic aimed to spot and fix all the issues preventing a stable > execution of integration tests. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IGNITE-17187) Make SecurityPermission extendable in plugins
Andrey Novikov created IGNITE-17187: --- Summary: Make SecurityPermission extendable in plugins Key: IGNITE-17187 URL: https://issues.apache.org/jira/browse/IGNITE-17187 Project: Ignite Issue Type: Improvement Components: security Reporter: Andrey Novikov For now it not possible to define custom permission for the API that implemented in plugin. enum SecurityPermission can't be extended without changes in core product. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-14535) Caclite SQL engine capabilities
[ https://issues.apache.org/jira/browse/IGNITE-14535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Orlov updated IGNITE-14535: -- Epic Link: IGNITE-17185 > Caclite SQL engine capabilities > --- > > Key: IGNITE-14535 > URL: https://issues.apache.org/jira/browse/IGNITE-14535 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Taras Ledkov >Priority: Major > > Umbrella ticket to track issues related to SQL logical tests. -- This message was sent by Atlassian Jira (v8.20.7#820007)
