[jira] [Commented] (IGNITE-22149) Thin 3.0: Implement Table partition API
[ https://issues.apache.org/jira/browse/IGNITE-22149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848640#comment-17848640 ] Mikhail Pochatkin commented on IGNITE-22149: Merged to main 1ae5d75b973ad8069af886e1dcfcfa2f9c801ab4 > Thin 3.0: Implement Table partition API > --- > > Key: IGNITE-22149 > URL: https://issues.apache.org/jira/browse/IGNITE-22149 > Project: Ignite > Issue Type: Improvement > Components: platforms, thin client >Reporter: Mikhail Pochatkin >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > Time Spent: 3h 40m > Remaining Estimate: 0h > > Need to implement *org.apache.ignite.table.partition.PartitionManager* > interface in Thin Client. > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-22289) Migrate shadowJar plugin to the new fork
[
https://issues.apache.org/jira/browse/IGNITE-22289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848243#comment-17848243
]
Mikhail Pochatkin commented on IGNITE-22289:
Merged to main 18434f2b376b8b15dba92ade85903f77bfd07392
> Migrate shadowJar plugin to the new fork
>
>
> Key: IGNITE-22289
> URL: https://issues.apache.org/jira/browse/IGNITE-22289
> Project: Ignite
> Issue Type: Task
> Components: build
>Reporter: Viacheslav Blinov
>Assignee: Viacheslav Blinov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> * Sometimes build fails with this error:
> {{java.lang.IllegalArgumentException: Unsupported class file major version
> 65}}
> * Found a related PR and a few issues in shadowjar plugin repository:
> [https://github.com/johnrengelman/shadow/pull/876]
> * Looks like problem is caused by compatibility between shadowJar, Gradle
> and asm library that shadowJar uses to alter classes
> * There is a workaround for this issue which is to bump the asm version used
> by shadowJar plugin
> * ShadowJar plugin we are using doesn’t target Gradle 8.6 we are using, and
> has no releases for the last year. Meanwhile usually it requires new releases
> with new versions of Gradle and asm due to it’s fragile nature
> * ShadowJar plugin we are using is not maintained anymore, see
> [https://github.com/johnrengelman/shadow/issues/908]
> * There is a fork of this plugin [https://github.com/Goooler/shadow] which
> fixes all the issues mentioned above
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (IGNITE-21812) Add automatic product version resolve
[ https://issues.apache.org/jira/browse/IGNITE-21812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin resolved IGNITE-21812. Resolution: Fixed > Add automatic product version resolve > - > > Key: IGNITE-21812 > URL: https://issues.apache.org/jira/browse/IGNITE-21812 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr >Assignee: Vadim Pakhnushev >Priority: Major > Labels: ignite-3 > Time Spent: 20m > Remaining Estimate: 0h > > Now the product version is hardcoded in EventBuilder but we can fetch the > product version automatically from the environment that can be formed during > the build. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21812) Add automatic product version resolve
[ https://issues.apache.org/jira/browse/IGNITE-21812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846998#comment-17846998 ] Mikhail Pochatkin commented on IGNITE-21812: Merged to main b60fed3ff2265755c78d6217c806104d0e35ced6 > Add automatic product version resolve > - > > Key: IGNITE-21812 > URL: https://issues.apache.org/jira/browse/IGNITE-21812 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr >Assignee: Vadim Pakhnushev >Priority: Major > Labels: ignite-3 > Time Spent: 20m > Remaining Estimate: 0h > > Now the product version is hardcoded in EventBuilder but we can fetch the > product version automatically from the environment that can be formed during > the build. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-22224) Rework embedded mode API
[
https://issues.apache.org/jira/browse/IGNITE-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Pochatkin reassigned IGNITE-4:
--
Assignee: Vadim Pakhnushev
> Rework embedded mode API
> -
>
> Key: IGNITE-4
> URL: https://issues.apache.org/jira/browse/IGNITE-4
> Project: Ignite
> Issue Type: Improvement
>Reporter: Mikhail Pochatkin
>Assignee: Vadim Pakhnushev
>Priority: Major
> Labels: ignite-3
>
> Currently, we have follow classes in *ignite-api*
> # org.apache.ignite.Ignite
> # org.apache.ignite.Ignition
> # org.apache.ignite.IgnitionManager
> # org.apache.ignite.InitParameters
> # org.apache.ignite.InitParametersBuilder
> While the first interface still makes sense, since it is the access point to
> the entire public API, the others have no such relationship to the API. These
> classes and interface are necessary to start *Apache Ignite 3* in embedded
> mode and cannot be used on their own, but you need to have access to the
> *ignite-runner* module and use implementations from there.
>
> This ticket proposes to remove these interfaces from the module with the
> public API and move them to the new module {*}ignite-embedded{*}. Also, by
> anology with Thin Clients we should rework *Ignition* interface and create
> *IgniteEmbedded* interface which should be entry point to embedded mode.
> *IgnitionManager* interface should be removed and *IgniteEmbedded* creation
> process reworked to builder pattern like Thin Clients.
> Cluster initialization process also should be reworked and all initialization
> methods moved to *IgniteEmbedded* interface.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-22225) Start embedded AI3 in isolated class loader
[ https://issues.apache.org/jira/browse/IGNITE-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-5: --- Description: > Start embedded AI3 in isolated class loader > --- > > Key: IGNITE-5 > URL: https://issues.apache.org/jira/browse/IGNITE-5 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22225) Start embedded AI3 in isolated class loader
[ https://issues.apache.org/jira/browse/IGNITE-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-5: --- Description: (was: ) > Start embedded AI3 in isolated class loader > --- > > Key: IGNITE-5 > URL: https://issues.apache.org/jira/browse/IGNITE-5 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22225) Start embedded AI3 in isolated class loader
Mikhail Pochatkin created IGNITE-5: -- Summary: Start embedded AI3 in isolated class loader Key: IGNITE-5 URL: https://issues.apache.org/jira/browse/IGNITE-5 Project: Ignite Issue Type: Improvement Reporter: Mikhail Pochatkin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22224) Rework embedded mode API
[
https://issues.apache.org/jira/browse/IGNITE-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Pochatkin updated IGNITE-4:
---
Description:
Currently, we have follow classes in *ignite-api*
# org.apache.ignite.Ignite
# org.apache.ignite.Ignition
# org.apache.ignite.IgnitionManager
# org.apache.ignite.InitParameters
# org.apache.ignite.InitParametersBuilder
While the first interface still makes sense, since it is the access point to
the entire public API, the others have no such relationship to the API. These
classes and interface are necessary to start *Apache Ignite 3* in embedded mode
and cannot be used on their own, but you need to have access to the
*ignite-runner* module and use implementations from there.
This ticket proposes to remove these interfaces from the module with the public
API and move them to the new module {*}ignite-embedded{*}. Also, by anology
with Thin Clients we should rework *Ignition* interface and create
*IgniteEmbedded* interface which should be entry point to embedded mode.
*IgnitionManager* interface should be removed and *IgniteEmbedded* creation
process reworked to builder pattern like Thin Clients.
Cluster initialization process also should be reworked and all initialization
methods moved to *IgniteEmbedded* interface.
> Rework embedded mode API
> -
>
> Key: IGNITE-4
> URL: https://issues.apache.org/jira/browse/IGNITE-4
> Project: Ignite
> Issue Type: Improvement
>Reporter: Mikhail Pochatkin
>Priority: Major
> Labels: ignite-3
>
> Currently, we have follow classes in *ignite-api*
> # org.apache.ignite.Ignite
> # org.apache.ignite.Ignition
> # org.apache.ignite.IgnitionManager
> # org.apache.ignite.InitParameters
> # org.apache.ignite.InitParametersBuilder
> While the first interface still makes sense, since it is the access point to
> the entire public API, the others have no such relationship to the API. These
> classes and interface are necessary to start *Apache Ignite 3* in embedded
> mode and cannot be used on their own, but you need to have access to the
> *ignite-runner* module and use implementations from there.
>
> This ticket proposes to remove these interfaces from the module with the
> public API and move them to the new module {*}ignite-embedded{*}. Also, by
> anology with Thin Clients we should rework *Ignition* interface and create
> *IgniteEmbedded* interface which should be entry point to embedded mode.
> *IgnitionManager* interface should be removed and *IgniteEmbedded* creation
> process reworked to builder pattern like Thin Clients.
> Cluster initialization process also should be reworked and all initialization
> methods moved to *IgniteEmbedded* interface.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-22224) Rework embedded mode API
Mikhail Pochatkin created IGNITE-4: -- Summary: Rework embedded mode API Key: IGNITE-4 URL: https://issues.apache.org/jira/browse/IGNITE-4 Project: Ignite Issue Type: Improvement Reporter: Mikhail Pochatkin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-22065) Table partition API
[ https://issues.apache.org/jira/browse/IGNITE-22065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17845295#comment-17845295 ] Mikhail Pochatkin commented on IGNITE-22065: Merged to main 2a6cc4f2930db3c260e9b5b014bfa22896af7759 > Table partition API > --- > > Key: IGNITE-22065 > URL: https://issues.apache.org/jira/browse/IGNITE-22065 > Project: Ignite > Issue Type: Improvement > Components: compute >Reporter: Mikhail Pochatkin >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > Time Spent: 6h 20m > Remaining Estimate: 0h > > IEP [IEP-120: MapReduce API - Apache Ignite - Apache Software > Foundation|https://cwiki.apache.org/confluence/display/IGNITE/IEP-120%3A+MapReduce+API] > > Need to implement part about Table API. > # Modify Table interface > # HashPartition > # PartitionManager -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-22149) Thin 3.0: Implement Table partition API
[ https://issues.apache.org/jira/browse/IGNITE-22149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin reassigned IGNITE-22149: -- Assignee: Mikhail Pochatkin > Thin 3.0: Implement Table partition API > --- > > Key: IGNITE-22149 > URL: https://issues.apache.org/jira/browse/IGNITE-22149 > Project: Ignite > Issue Type: Improvement > Components: platforms, thin client >Reporter: Mikhail Pochatkin >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > > Need to implement *org.apache.ignite.table.partition.PartitionManager* > interface in Thin Client. > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-22064) General MapReduce API
[ https://issues.apache.org/jira/browse/IGNITE-22064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842899#comment-17842899 ] Mikhail Pochatkin commented on IGNITE-22064: LGTM! Thanks Merged to main cb34325ecc033c68885d146b83f63602af58fd4e > General MapReduce API > - > > Key: IGNITE-22064 > URL: https://issues.apache.org/jira/browse/IGNITE-22064 > Project: Ignite > Issue Type: Improvement > Components: compute >Reporter: Mikhail Pochatkin >Assignee: Vadim Pakhnushev >Priority: Major > Labels: compute, ignite-3 > Time Spent: 20m > Remaining Estimate: 0h > > IEP [IEP-120: MapReduce API - Apache Ignite - Apache Software > Foundation|https://cwiki.apache.org/confluence/display/IGNITE/IEP-120%3A+MapReduce+API] > > Need to implement part of IEP related to Compute API. > # ComputeTask > # TaskExecution > # Modify IgniteCompute > # ComputeJobRunner > # TaskContext > The part about colocation is not a target for this ticket. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22153) Support partition filter in Criteria API
Mikhail Pochatkin created IGNITE-22153: -- Summary: Support partition filter in Criteria API Key: IGNITE-22153 URL: https://issues.apache.org/jira/browse/IGNITE-22153 Project: Ignite Issue Type: Improvement Components: sql Reporter: Mikhail Pochatkin After IGNITE-22065 and IGNITE-22152 we need to support partition filter in Criteria API -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22152) Support partition filter in SQL
Mikhail Pochatkin created IGNITE-22152: -- Summary: Support partition filter in SQL Key: IGNITE-22152 URL: https://issues.apache.org/jira/browse/IGNITE-22152 Project: Ignite Issue Type: Improvement Components: sql Reporter: Mikhail Pochatkin After IGNITE-22065 we need to introduce filter by partition in SELECT operator -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22149) Thin 3.0: Implement Table partition API
[ https://issues.apache.org/jira/browse/IGNITE-22149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-22149: --- Description: Need to implement *org.apache.ignite.table.partition.PartitionManager* interface in Thin Client. was: Need to implement `org.apache.ignite.table.partition.PartitionManager` interface in Thin Client. > Thin 3.0: Implement Table partition API > --- > > Key: IGNITE-22149 > URL: https://issues.apache.org/jira/browse/IGNITE-22149 > Project: Ignite > Issue Type: Improvement > Components: thin client >Reporter: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > > Need to implement *org.apache.ignite.table.partition.PartitionManager* > interface in Thin Client. > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22149) Thin 3.0: Implement Table partition API
[ https://issues.apache.org/jira/browse/IGNITE-22149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-22149: --- Component/s: platforms > Thin 3.0: Implement Table partition API > --- > > Key: IGNITE-22149 > URL: https://issues.apache.org/jira/browse/IGNITE-22149 > Project: Ignite > Issue Type: Improvement > Components: platforms, thin client >Reporter: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > > Need to implement *org.apache.ignite.table.partition.PartitionManager* > interface in Thin Client. > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22151) C++ Thin 3.0: Implement Table partition API
[ https://issues.apache.org/jira/browse/IGNITE-22151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-22151: --- Component/s: platforms > C++ Thin 3.0: Implement Table partition API > --- > > Key: IGNITE-22151 > URL: https://issues.apache.org/jira/browse/IGNITE-22151 > Project: Ignite > Issue Type: Improvement > Components: platforms, thin client >Reporter: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > > Need to implement *org.apache.ignite.table.partition.PartitionManager* > interface in C++ Thin Client. > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22150) .NET Thin 3.0: Implement Table partition API
[ https://issues.apache.org/jira/browse/IGNITE-22150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-22150: --- Description: Need to implement *org.apache.ignite.table.partition.PartitionManager* interface in C++ Thin Client. was: Need to implement `org.apache.ignite.table.partition.PartitionManager` interface in C++ Thin Client. > .NET Thin 3.0: Implement Table partition API > > > Key: IGNITE-22150 > URL: https://issues.apache.org/jira/browse/IGNITE-22150 > Project: Ignite > Issue Type: Improvement > Components: thin client >Reporter: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > > Need to implement *org.apache.ignite.table.partition.PartitionManager* > interface in C++ Thin Client. > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22150) .NET Thin 3.0: Implement Table partition API
[ https://issues.apache.org/jira/browse/IGNITE-22150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-22150: --- Description: Need to implement *org.apache.ignite.table.partition.PartitionManager* interface in .NET Thin Client. was: Need to implement *org.apache.ignite.table.partition.PartitionManager* interface in C++ Thin Client. > .NET Thin 3.0: Implement Table partition API > > > Key: IGNITE-22150 > URL: https://issues.apache.org/jira/browse/IGNITE-22150 > Project: Ignite > Issue Type: Improvement > Components: thin client >Reporter: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > > Need to implement *org.apache.ignite.table.partition.PartitionManager* > interface in .NET Thin Client. > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22150) .NET Thin 3.0: Implement Table partition API
[ https://issues.apache.org/jira/browse/IGNITE-22150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-22150: --- Component/s: platforms > .NET Thin 3.0: Implement Table partition API > > > Key: IGNITE-22150 > URL: https://issues.apache.org/jira/browse/IGNITE-22150 > Project: Ignite > Issue Type: Improvement > Components: platforms, thin client >Reporter: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > > Need to implement *org.apache.ignite.table.partition.PartitionManager* > interface in .NET Thin Client. > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22151) C++ Thin 3.0: Implement Table partition API
Mikhail Pochatkin created IGNITE-22151: -- Summary: C++ Thin 3.0: Implement Table partition API Key: IGNITE-22151 URL: https://issues.apache.org/jira/browse/IGNITE-22151 Project: Ignite Issue Type: Improvement Components: thin client Reporter: Mikhail Pochatkin Need to implement *org.apache.ignite.table.partition.PartitionManager* interface in C++ Thin Client. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22149) Thin 3.0: Implement Table partition API
Mikhail Pochatkin created IGNITE-22149: -- Summary: Thin 3.0: Implement Table partition API Key: IGNITE-22149 URL: https://issues.apache.org/jira/browse/IGNITE-22149 Project: Ignite Issue Type: Improvement Components: thin client Reporter: Mikhail Pochatkin Need to implement `org.apache.ignite.table.partition.PartitionManager` interface in Thin Client. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22150) .NET Thin 3.0: Implement Table partition API
Mikhail Pochatkin created IGNITE-22150: -- Summary: .NET Thin 3.0: Implement Table partition API Key: IGNITE-22150 URL: https://issues.apache.org/jira/browse/IGNITE-22150 Project: Ignite Issue Type: Improvement Components: thin client Reporter: Mikhail Pochatkin Need to implement `org.apache.ignite.table.partition.PartitionManager` interface in Thin Client. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22150) .NET Thin 3.0: Implement Table partition API
[ https://issues.apache.org/jira/browse/IGNITE-22150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-22150: --- Description: Need to implement `org.apache.ignite.table.partition.PartitionManager` interface in C++ Thin Client. was: Need to implement `org.apache.ignite.table.partition.PartitionManager` interface in Thin Client. > .NET Thin 3.0: Implement Table partition API > > > Key: IGNITE-22150 > URL: https://issues.apache.org/jira/browse/IGNITE-22150 > Project: Ignite > Issue Type: Improvement > Components: thin client >Reporter: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > > Need to implement `org.apache.ignite.table.partition.PartitionManager` > interface in C++ Thin Client. > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-22065) Table partition API
[ https://issues.apache.org/jira/browse/IGNITE-22065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin reassigned IGNITE-22065: -- Assignee: Mikhail Pochatkin > Table partition API > --- > > Key: IGNITE-22065 > URL: https://issues.apache.org/jira/browse/IGNITE-22065 > Project: Ignite > Issue Type: Improvement > Components: compute >Reporter: Mikhail Pochatkin >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > > IEP [IEP-120: MapReduce API - Apache Ignite - Apache Software > Foundation|https://cwiki.apache.org/confluence/display/IGNITE/IEP-120%3A+MapReduce+API] > > Need to implement part about Table API. > # Modify Table interface > # HashPartition > # PartitionManager -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-22066) Memory leak in the DummyInternalTableImpl
[
https://issues.apache.org/jira/browse/IGNITE-22066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17838170#comment-17838170
]
Mikhail Pochatkin commented on IGNITE-22066:
Merged to main 98a2a22830851fca768d864f140e243214949257
> Memory leak in the DummyInternalTableImpl
> -
>
> Key: IGNITE-22066
> URL: https://issues.apache.org/jira/browse/IGNITE-22066
> Project: Ignite
> Issue Type: Bug
>Reporter: Vadim Pakhnushev
>Assignee: Vadim Pakhnushev
>Priority: Major
> Labels: ignite-3
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Static {{LOW_WATERMARK}} field keeps references to the listeners.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-22065) Table partition API
[ https://issues.apache.org/jira/browse/IGNITE-22065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-22065: --- Description: IEP [IEP-120: MapReduce API - Apache Ignite - Apache Software Foundation|https://cwiki.apache.org/confluence/display/IGNITE/IEP-120%3A+MapReduce+API] Need to implement part about Table API. # Modify Table interface # HashPartition # PartitionManager > Table partition API > --- > > Key: IGNITE-22065 > URL: https://issues.apache.org/jira/browse/IGNITE-22065 > Project: Ignite > Issue Type: Improvement > Components: compute >Reporter: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > > IEP [IEP-120: MapReduce API - Apache Ignite - Apache Software > Foundation|https://cwiki.apache.org/confluence/display/IGNITE/IEP-120%3A+MapReduce+API] > > Need to implement part about Table API. > # Modify Table interface > # HashPartition > # PartitionManager -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22064) General MapReduce API
[ https://issues.apache.org/jira/browse/IGNITE-22064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-22064: --- Description: IEP [IEP-120: MapReduce API - Apache Ignite - Apache Software Foundation|https://cwiki.apache.org/confluence/display/IGNITE/IEP-120%3A+MapReduce+API] Need to implement part of IEP related to Compute API. # ComputeTask # TaskExecution # Modify IgniteCompute # ComputeJobRunner # TaskContext The part about colocation is not a target for this ticket. > General MapReduce API > - > > Key: IGNITE-22064 > URL: https://issues.apache.org/jira/browse/IGNITE-22064 > Project: Ignite > Issue Type: Improvement > Components: compute >Reporter: Mikhail Pochatkin >Priority: Major > Labels: compute, ignite-3 > > IEP [IEP-120: MapReduce API - Apache Ignite - Apache Software > Foundation|https://cwiki.apache.org/confluence/display/IGNITE/IEP-120%3A+MapReduce+API] > > Need to implement part of IEP related to Compute API. > # ComputeTask > # TaskExecution > # Modify IgniteCompute > # ComputeJobRunner > # TaskContext > The part about colocation is not a target for this ticket. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22065) Table partition API
Mikhail Pochatkin created IGNITE-22065: -- Summary: Table partition API Key: IGNITE-22065 URL: https://issues.apache.org/jira/browse/IGNITE-22065 Project: Ignite Issue Type: Improvement Components: compute Reporter: Mikhail Pochatkin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22064) General MapReduce API
Mikhail Pochatkin created IGNITE-22064: -- Summary: General MapReduce API Key: IGNITE-22064 URL: https://issues.apache.org/jira/browse/IGNITE-22064 Project: Ignite Issue Type: Improvement Components: compute Reporter: Mikhail Pochatkin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-20516) Remove openapi.yaml spec from git repository
[ https://issues.apache.org/jira/browse/IGNITE-20516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17838059#comment-17838059 ] Mikhail Pochatkin commented on IGNITE-20516: Merged to main c69918e1485eaedc1d2deea648e3f51f08bec15c > Remove openapi.yaml spec from git repository > > > Key: IGNITE-20516 > URL: https://issues.apache.org/jira/browse/IGNITE-20516 > Project: Ignite > Issue Type: Task > Components: rest >Affects Versions: 3.0.0-beta1 >Reporter: Dmitry Baranov >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > Time Spent: 20m > Remaining Estimate: 0h > > Source of truth for rest api should be java code. So, generated openapi spec > should not be saved in repo (modules/rest-api/openapi/openapi.yaml) > spec should be provided as artifact in TC -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21904) Improve serializers architecture
[ https://issues.apache.org/jira/browse/IGNITE-21904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837623#comment-17837623 ] Mikhail Pochatkin commented on IGNITE-21904: Merged to main: a3e8fd1266334aa09e3789f15db2262a60057578 > Improve serializers architecture > > > Key: IGNITE-21904 > URL: https://issues.apache.org/jira/browse/IGNITE-21904 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksandr >Assignee: Viacheslav Blinov >Priority: Major > Labels: ignite-3 > Time Spent: 50m > Remaining Estimate: 0h > > Now the serialization for events are done in single class and this is not > extendible. For example, if some module wants to add its own event, it is > hard to figure out how to register a serializer for that. > We should rework the architecture of the serialization in the eventlog module > in order to make it open for extensions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22044) Ignite 3 MapReduce
Mikhail Pochatkin created IGNITE-22044: -- Summary: Ignite 3 MapReduce Key: IGNITE-22044 URL: https://issues.apache.org/jira/browse/IGNITE-22044 Project: Ignite Issue Type: Epic Components: compute Reporter: Mikhail Pochatkin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22037) AI3 3rd party dependencies checker
Mikhail Pochatkin created IGNITE-22037: -- Summary: AI3 3rd party dependencies checker Key: IGNITE-22037 URL: https://issues.apache.org/jira/browse/IGNITE-22037 Project: Ignite Issue Type: Improvement Components: build Reporter: Mikhail Pochatkin Currently we have approved list of 3rd party dependencies for runtime/test code scopes. [https://cwiki.apache.org/confluence/display/IGNITE/Java+Code+Style+Guide] So, we need to create some protection from adding new unapproved dependecies, at least for runtime dependencies. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-20516) Remove openapi.yaml spec from git repository
[ https://issues.apache.org/jira/browse/IGNITE-20516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836627#comment-17836627 ] Mikhail Pochatkin commented on IGNITE-20516: TC task [--> Run :: All Tests / #30340 at 12 Apr 12:42 — TeamCity (apache.org)|https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Release_Build_9OpenAPISpecification#all-projects] > Remove openapi.yaml spec from git repository > > > Key: IGNITE-20516 > URL: https://issues.apache.org/jira/browse/IGNITE-20516 > Project: Ignite > Issue Type: Task > Components: rest >Affects Versions: 3.0.0-beta1 >Reporter: Dmitry Baranov >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > Source of truth for rest api should be java code. So, generated openapi spec > should not be saved in repo (modules/rest-api/openapi/openapi.yaml) > spec should be provided as artifact in TC -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-22035) Integration tests consume a lot of RAM
[ https://issues.apache.org/jira/browse/IGNITE-22035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836564#comment-17836564 ] Mikhail Pochatkin commented on IGNITE-22035: LGTM! Thanks Merged to main: f38ecb94b7f1ce447de332082773e1d1c05d0fad > Integration tests consume a lot of RAM > -- > > Key: IGNITE-22035 > URL: https://issues.apache.org/jira/browse/IGNITE-22035 > Project: Ignite > Issue Type: Bug >Reporter: Vadim Pakhnushev >Assignee: Vadim Pakhnushev >Priority: Major > Labels: ignite-3 > Time Spent: 20m > Remaining Estimate: 0h > > In the IGNITE-21594 the test node configuration was updated but the default > storage profile remained with the default configuration which consumes a lot > of RAM. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-22018) Fix flaky ItConnectionHeartbeatTest.restoreConnectionAfterConnectionLost
[ https://issues.apache.org/jira/browse/IGNITE-22018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17835649#comment-17835649 ] Mikhail Pochatkin commented on IGNITE-22018: LGTM! Thanks Merged to main: 010111eaa29163f40a498a7fcd43b3826d490f65 > Fix flaky ItConnectionHeartbeatTest.restoreConnectionAfterConnectionLost > > > Key: IGNITE-22018 > URL: https://issues.apache.org/jira/browse/IGNITE-22018 > Project: Ignite > Issue Type: Bug > Components: cli >Reporter: Vadim Pakhnushev >Assignee: Vadim Pakhnushev >Priority: Major > Labels: ignite-3 > Time Spent: 20m > Remaining Estimate: 0h > > [TeamCity > (apache.org)|https://ci.ignite.apache.org/test/-5833809022834415010?currentProjectId=ApacheIgnite3xGradle_Test_IntegrationTests=true] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21480) Check local node before broadcasting
[ https://issues.apache.org/jira/browse/IGNITE-21480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17835408#comment-17835408 ] Mikhail Pochatkin commented on IGNITE-21480: LGTM! Thanks Merged to main: 7a479e147cc7a0efc8e7238d1eeaa4834c6376f3 > Check local node before broadcasting > > > Key: IGNITE-21480 > URL: https://issues.apache.org/jira/browse/IGNITE-21480 > Project: Ignite > Issue Type: Improvement > Components: compute >Reporter: Vadim Pakhnushev >Assignee: Vadim Pakhnushev >Priority: Major > Labels: ignite-3 > Time Spent: 20m > Remaining Estimate: 0h > > Status, cancel and change priority requests are broadcast to entire cluster > but only one node contains the necessary information. In most cases it could > be the local node so let's optimize these requests by first checking the > local node and only then broadcasting it to other nodes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-20516) Remove openapi.yaml spec from git repository
[ https://issues.apache.org/jira/browse/IGNITE-20516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin reassigned IGNITE-20516: -- Assignee: Mikhail Pochatkin > Remove openapi.yaml spec from git repository > > > Key: IGNITE-20516 > URL: https://issues.apache.org/jira/browse/IGNITE-20516 > Project: Ignite > Issue Type: Task > Components: rest >Affects Versions: 3.0.0-beta1 >Reporter: Dmitry Baranov >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > > Source of truth for rest api should be java code. So, generated openapi spec > should not be saved in repo (modules/rest-api/openapi/openapi.yaml) > spec should be provided as artifact in TC -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-21427) Rename IndexType.TREE to SORTED
[ https://issues.apache.org/jira/browse/IGNITE-21427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin reassigned IGNITE-21427: -- Assignee: Vadim Kolodin > Rename IndexType.TREE to SORTED > --- > > Key: IGNITE-21427 > URL: https://issues.apache.org/jira/browse/IGNITE-21427 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Vadim Kolodin >Assignee: Vadim Kolodin >Priority: Major > Labels: ignite-3 > > Rename index type after IGNITE-21353 in sql engine. > Aslo need to get rid keyword TREE from > [config.fmpp|https://github.com/apache/ignite-3/pull/3344/files#diff-58db677088127853e0aae90ed7083e3e3d55a7e00670f7b37dc35672442f5e4f] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-19962) Actualize list of 3rd party dependencies for AI 3.0
[ https://issues.apache.org/jira/browse/IGNITE-19962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin reassigned IGNITE-19962: -- Assignee: Vadim Kolodin > Actualize list of 3rd party dependencies for AI 3.0 > --- > > Key: IGNITE-19962 > URL: https://issues.apache.org/jira/browse/IGNITE-19962 > Project: Ignite > Issue Type: Improvement >Reporter: Iurii Gerzhedovich >Assignee: Vadim Kolodin >Priority: Blocker > Labels: ignite-3 > > AI3 codestyle guide contains part about using 3rd party libraries. Right now > the document present just 5 such libraries, however we already use > signifignetely more. > Let's do two steps: > # analizy which dependencies could be get rid, even in tests. We must have > minimum dependency for whole project. > # Actualize list of 3rd party libraries in > [codestyle|https://cwiki.apache.org/confluence/display/IGNITE/Java+Code+Style+Guide#JavaCodeStyleGuide-2Using3rdpartylibraries]]. > The first step should be discussed at developers mailing list and have strong > explanation of necessety for each of dependencies. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21864) Provide cluster name in thin client
[ https://issues.apache.org/jira/browse/IGNITE-21864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17831853#comment-17831853 ] Mikhail Pochatkin commented on IGNITE-21864: Merged to main: a4dac8ef738a9000bd24d50fb356333e3c6898f1 > Provide cluster name in thin client > --- > > Key: IGNITE-21864 > URL: https://issues.apache.org/jira/browse/IGNITE-21864 > Project: Ignite > Issue Type: Improvement > Components: thin client >Reporter: Vadim Pakhnushev >Assignee: Vadim Pakhnushev >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 20m > Remaining Estimate: 0h > > Some clients could benefit from knowing cluster name, we already have it > received in the handshake process, let's provide it in the internal API. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-21864) Provide cluster name in thin client
[ https://issues.apache.org/jira/browse/IGNITE-21864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin resolved IGNITE-21864. Resolution: Fixed > Provide cluster name in thin client > --- > > Key: IGNITE-21864 > URL: https://issues.apache.org/jira/browse/IGNITE-21864 > Project: Ignite > Issue Type: Improvement > Components: thin client >Reporter: Vadim Pakhnushev >Assignee: Vadim Pakhnushev >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 20m > Remaining Estimate: 0h > > Some clients could benefit from knowing cluster name, we already have it > received in the handshake process, let's provide it in the internal API. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-21843) ItRebalanceDistributedTest silently fails to start TableManager
[
https://issues.apache.org/jira/browse/IGNITE-21843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830879#comment-17830879
]
Mikhail Pochatkin commented on IGNITE-21843:
Merged to main: 095aeb01c0b489ed8e14e3868970034c7ab3beac
> ItRebalanceDistributedTest silently fails to start TableManager
> ---
>
> Key: IGNITE-21843
> URL: https://issues.apache.org/jira/browse/IGNITE-21843
> Project: Ignite
> Issue Type: Bug
>Reporter: Vadim Pakhnushev
>Assignee: Vadim Pakhnushev
>Priority: Major
> Labels: ignite-3
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In the IGNITE-21540 the txConfig for TableManager was taken from
> clusterConfigRegistry, but the registry doesn't contain it. There is a
> TransactionConfiguration injected in the field so it's probably enough to
> take it from there.
> In order to better find these errors we should replace
> {{forEach(IgniteComponent::start)}} with {{igniteComponent ->
> assertThat(igniteComponent.start(), willCompleteSuccessfully())}} in the
> {{org.apache.ignite.internal.rebalance.ItRebalanceDistributedTest.Node#start}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-21615) Update the config updated message to correctly reflect the need to restart
[ https://issues.apache.org/jira/browse/IGNITE-21615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830499#comment-17830499 ] Mikhail Pochatkin commented on IGNITE-21615: Merged to main: c4c0811f2e24d7a3c9c11c49a67f29c48b7c471c > Update the config updated message to correctly reflect the need to restart > -- > > Key: IGNITE-21615 > URL: https://issues.apache.org/jira/browse/IGNITE-21615 > Project: Ignite > Issue Type: Task >Reporter: Igor Gusev >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > Time Spent: 0.5h > Remaining Estimate: 0h > > Currently, a number of configuration updates require node restart to apply, > but the CLI message remains the same regarless. We should provide users with > more detailed information on when they need to restart the node. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-21615) Update the config updated message to correctly reflect the need to restart
[ https://issues.apache.org/jira/browse/IGNITE-21615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin reassigned IGNITE-21615: -- Assignee: Mikhail Pochatkin > Update the config updated message to correctly reflect the need to restart > -- > > Key: IGNITE-21615 > URL: https://issues.apache.org/jira/browse/IGNITE-21615 > Project: Ignite > Issue Type: Task >Reporter: Igor Gusev >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > Currently, a number of configuration updates require node restart to apply, > but the CLI message remains the same regarless. We should provide users with > more detailed information on when they need to restart the node. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21724) Support "-ea" version in ItInitializedClusterRestTest
[
https://issues.apache.org/jira/browse/IGNITE-21724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Pochatkin updated IGNITE-21724:
---
Description:
Every release we encounter the following problem:
{code:java}
"(?\\d+)\\.(?\\d+)\\.(?\\d+)((?-SNAPSHOT)|-(?alpha\\d+)|--(?beta\\d+))?"
Apache Ignite ver. 9.0.0-ea5{code}
was:
Every release we encounter the following problem:
{{java.lang.AssertionError: Expected: a string matching the pattern
<(?\d+)\.(?\d+)\.(?\d+)((?-SNAPSHOT)|-(?alpha\d+)|--(?beta\d+))?>
but: the string was "9.0.0-ea5"}}
{{Apache Ignite ver. 9.0.0-ea5}}
> Support "-ea" version in ItInitializedClusterRestTest
> -
>
> Key: IGNITE-21724
> URL: https://issues.apache.org/jira/browse/IGNITE-21724
> Project: Ignite
> Issue Type: Improvement
>Reporter: Mikhail Pochatkin
>Assignee: Mikhail Pochatkin
>Priority: Major
> Labels: ignite-3
>
> Every release we encounter the following problem:
>
> {code:java}
> "(?\\d+)\\.(?\\d+)\\.(?\\d+)((?-SNAPSHOT)|-(?alpha\\d+)|--(?beta\\d+))?"
>
> Apache Ignite ver. 9.0.0-ea5{code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-21724) Support "-ea" version in ItInitializedClusterRestTest
Mikhail Pochatkin created IGNITE-21724:
--
Summary: Support "-ea" version in ItInitializedClusterRestTest
Key: IGNITE-21724
URL: https://issues.apache.org/jira/browse/IGNITE-21724
Project: Ignite
Issue Type: Improvement
Reporter: Mikhail Pochatkin
Assignee: Mikhail Pochatkin
Every release we encounter the following problem:
{{java.lang.AssertionError: Expected: a string matching the pattern
<(?\d+)\.(?\d+)\.(?\d+)((?-SNAPSHOT)|-(?alpha\d+)|--(?beta\d+))?>
but: the string was "9.0.0-ea5"}}
{{Apache Ignite ver. 9.0.0-ea5}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-21681) QueryCriteriaAsyncCursor doesn't satisfy AsyncCursor contract
Mikhail Pochatkin created IGNITE-21681:
--
Summary: QueryCriteriaAsyncCursor doesn't satisfy AsyncCursor
contract
Key: IGNITE-21681
URL: https://issues.apache.org/jira/browse/IGNITE-21681
Project: Ignite
Issue Type: Improvement
Reporter: Mikhail Pochatkin
Assignee: Andrey Novikov
Current implementation of QueryCriteriaAsyncCursor
{code:java}
/** {@inheritDoc} */
@Override
public CompletableFuture> fetchNextPage() {
return ars.fetchNextPage()
.thenApply((rs) -> {
if (!hasMorePages()) {
closeAsync();
}
return new QueryCriteriaAsyncCursor<>(rs, mapper, closeRun);
});
} {code}
doesn't comply with the contract described in AsyncCursor
{code:java}
* @return A future which will be completed when next page will be fetched and
set as the current page.
* The future will return {@code this} for chaining. {code}
Implementation must returns `this` in future, not the new instance
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-21617) Update to Gradle 8.6
[ https://issues.apache.org/jira/browse/IGNITE-21617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17822453#comment-17822453 ] Mikhail Pochatkin commented on IGNITE-21617: LGTM. Thanks! > Update to Gradle 8.6 > > > Key: IGNITE-21617 > URL: https://issues.apache.org/jira/browse/IGNITE-21617 > Project: Ignite > Issue Type: Improvement >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 10m > Remaining Estimate: 0h > > We need this to fully support Java 21 (with the currently used Gradle 7.x, > builds fail on the TC). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-21489) Add running script files to .jar file
[ https://issues.apache.org/jira/browse/IGNITE-21489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin resolved IGNITE-21489. Resolution: Won't Fix > Add running script files to .jar file > - > > Key: IGNITE-21489 > URL: https://issues.apache.org/jira/browse/IGNITE-21489 > Project: Ignite > Issue Type: Improvement > Components: binary, build >Affects Versions: 3.0.0-beta1 >Reporter: Igor >Priority: Major > Labels: ignite-3 > > The `ignite-runner-3.0.0-SNAPSHOT.jar` requires a lot of custom setup to run > the server. It would be useful to have the setup scripts inside jar to be > able to unpack them and use. > The files required to be added to `ignite-runner-3.0.0-SNAPSHOT.jar`: > # bootstrap-functions.sh > # ignite.java.util.logging.properties > # ignite3db > # ignite-config.conf > # setup-java.sh > # vars.env -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-21467) Improve PMD and Checkstyle rulesets
[
https://issues.apache.org/jira/browse/IGNITE-21467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Pochatkin reassigned IGNITE-21467:
--
Assignee: Viacheslav Blinov (was: Mikhail Pochatkin)
> Improve PMD and Checkstyle rulesets
> ---
>
> Key: IGNITE-21467
> URL: https://issues.apache.org/jira/browse/IGNITE-21467
> Project: Ignite
> Issue Type: Improvement
> Components: build
>Reporter: Mikhail Pochatkin
>Assignee: Viacheslav Blinov
>Priority: Major
> Labels: ignite-3
>
> # Remove modernizer plugin and migrate all rules to PMD\Checkstyle.
> check-rules/modernizer-rules.xml
> # Introduce separate checkstyle ruleset for public API module (modules/api).
> This ruleset should be more strict than internal one:
> ## All public method must have Javadocs (currently in internal code field
> getters may haven't Javadocs)
> ## /** \{@inheritDoc} */ is not applicable for public API
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-21467) Improve PMD and Checkstyle rulesets
[
https://issues.apache.org/jira/browse/IGNITE-21467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Pochatkin reassigned IGNITE-21467:
--
Assignee: Mikhail Pochatkin (was: Viacheslav Blinov)
> Improve PMD and Checkstyle rulesets
> ---
>
> Key: IGNITE-21467
> URL: https://issues.apache.org/jira/browse/IGNITE-21467
> Project: Ignite
> Issue Type: Improvement
> Components: build
>Reporter: Mikhail Pochatkin
>Assignee: Mikhail Pochatkin
>Priority: Major
> Labels: ignite-3
>
> # Remove modernizer plugin and migrate all rules to PMD\Checkstyle.
> check-rules/modernizer-rules.xml
> # Introduce separate checkstyle ruleset for public API module (modules/api).
> This ruleset should be more strict than internal one:
> ## All public method must have Javadocs (currently in internal code field
> getters may haven't Javadocs)
> ## /** \{@inheritDoc} */ is not applicable for public API
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-19608) Startup errors are ignored in ignite3db script
[
https://issues.apache.org/jira/browse/IGNITE-19608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Pochatkin reassigned IGNITE-19608:
--
Assignee: Mikhail Pochatkin
> Startup errors are ignored in ignite3db script
> --
>
> Key: IGNITE-19608
> URL: https://issues.apache.org/jira/browse/IGNITE-19608
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-beta1, 3.0.0-beta2
>Reporter: Andrey Khitrin
>Assignee: Mikhail Pochatkin
>Priority: Blocker
> Labels: cli, ignite-3
>
> Ignite3 node is started by `bin/ignite3db` shell script. Unfortunately, this
> script follows some shell scripting bad practices that makes troubleshooting
> harder when something goes wrong.
> Particullary, there are following issues:
> 1. No guarding bash options (like `nounset`, `errexit`, or `pipefile`) is set.
> 2. When starting Java application, its stderr and stdout are redirected into
> `/dev/null`.
> {code:bash}
> CMD="${JAVA_CMD_WITH_ARGS} ${APPLICATION_ARGS}"
> $CMD >>/dev/null 2>&1 ${IGNITE_HOME}/pid
> {code}
> Just for comparison: [control.sh in
> AI2|https://github.com/apache/ignite/blob/master/bin/control.sh] do not
> suffer from such behavior. This should be fixed in AI3 too.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21467) Improve PMD and Checkstyle rulesets
[
https://issues.apache.org/jira/browse/IGNITE-21467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Pochatkin updated IGNITE-21467:
---
Description:
# Remove modernizer plugin and migrate all rules to PMD\Checkstyle.
check-rules/modernizer-rules.xml
# Introduce separate checkstyle ruleset for public API module (modules/api).
This ruleset should be more strict than internal one:
## All public method must have Javadocs (currently in internal code field
getters may haven't Javadocs)
## /** \{@inheritDoc} */ is not applicable for public API
was:
# Remove modernizer plugin and migrate all rules to PMD\Checkstyle.
check-rules/modernizer-rules.xml
# Introduce separate checkstyle ruleset for public API module (modules/api).
This ruleset should be more strict than internal one:
## All public method must have Javadocs (currently in internal code field
getters may haven't Javadocs)
##
/** \{@inheritDoc} */ is not applicable for public API
> Improve PMD and Checkstyle rulesets
> ---
>
> Key: IGNITE-21467
> URL: https://issues.apache.org/jira/browse/IGNITE-21467
> Project: Ignite
> Issue Type: Improvement
> Components: build
>Reporter: Mikhail Pochatkin
>Assignee: Viacheslav Blinov
>Priority: Major
> Labels: ignite-3
>
> # Remove modernizer plugin and migrate all rules to PMD\Checkstyle.
> check-rules/modernizer-rules.xml
> # Introduce separate checkstyle ruleset for public API module (modules/api).
> This ruleset should be more strict than internal one:
> ## All public method must have Javadocs (currently in internal code field
> getters may haven't Javadocs)
> ## /** \{@inheritDoc} */ is not applicable for public API
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21467) Improve PMD and Checkstyle rulesets
[
https://issues.apache.org/jira/browse/IGNITE-21467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Pochatkin updated IGNITE-21467:
---
Description:
# Remove modernizer plugin and migrate all rules to PMD\Checkstyle.
check-rules/modernizer-rules.xml
# Introduce separate checkstyle ruleset for public API module (modules/api).
This ruleset should be more strict than internal one:
## All public method must have Javadocs (currently in internal code field
getters may haven't Javadocs)
##
/** \{@inheritDoc} */ is not applicable for public API
> Improve PMD and Checkstyle rulesets
> ---
>
> Key: IGNITE-21467
> URL: https://issues.apache.org/jira/browse/IGNITE-21467
> Project: Ignite
> Issue Type: Improvement
> Components: build
>Reporter: Mikhail Pochatkin
>Assignee: Viacheslav Blinov
>Priority: Major
> Labels: ignite-3
>
> # Remove modernizer plugin and migrate all rules to PMD\Checkstyle.
> check-rules/modernizer-rules.xml
> # Introduce separate checkstyle ruleset for public API module (modules/api).
> This ruleset should be more strict than internal one:
> ## All public method must have Javadocs (currently in internal code field
> getters may haven't Javadocs)
> ##
> /** \{@inheritDoc} */ is not applicable for public API
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-21467) Improve PMD and Checkstyle rulesets
Mikhail Pochatkin created IGNITE-21467: -- Summary: Improve PMD and Checkstyle rulesets Key: IGNITE-21467 URL: https://issues.apache.org/jira/browse/IGNITE-21467 Project: Ignite Issue Type: Improvement Components: build Reporter: Mikhail Pochatkin Assignee: Viacheslav Blinov -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-21426) Create tables from Java classes basic implementation
[ https://issues.apache.org/jira/browse/IGNITE-21426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin reassigned IGNITE-21426: -- Assignee: Vadim Pakhnushev > Create tables from Java classes basic implementation > > > Key: IGNITE-21426 > URL: https://issues.apache.org/jira/browse/IGNITE-21426 > Project: Ignite > Issue Type: New Feature >Reporter: Vadim Kolodin >Assignee: Vadim Pakhnushev >Priority: Major > Labels: ignite-3 > > * add a new module > * public interfaces, entry point is ignite.catalog() > * ignite annotations - table, id, index, colocateBy, zone > * table/zone definition builders > * basic sql generation implementation > * update existing MapperBuilder to support Column annotation > * some tests -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-21390) Inconsistent behavior of Compute APIs when target node does not exist
[
https://issues.apache.org/jira/browse/IGNITE-21390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Pochatkin reassigned IGNITE-21390:
--
Assignee: Vadim Pakhnushev (was: Pavel Tupitsyn)
> Inconsistent behavior of Compute APIs when target node does not exist
> -
>
> Key: IGNITE-21390
> URL: https://issues.apache.org/jira/browse/IGNITE-21390
> Project: Ignite
> Issue Type: Bug
> Components: compute, thin client
>Affects Versions: 3.0.0-beta1
>Reporter: Pavel Tupitsyn
>Assignee: Vadim Pakhnushev
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> *IgniteCompute.executeAsync* accepts a set of nodes. If we pass a single node
> that does not exist in the cluster, the API behavior is confusing and
> inconsistent across embedded and thin client modes:
> {code:java}
> var fakeNode = new ClusterNodeImpl("fakeId", "fakeName", new
> NetworkAddress("localhost", 12345));
> JobExecution execution =
> ignite.compute().executeAsync(Set.of(fakeNode), units(), "job", null);
> execution.resultAsync().join();
> {code}
> * Client: throws "Specified node is not present in the cluster" exception
> with a generic error code (uses deprecated constructor)
> * Embedded: actually tries to connect to the specified address and throws
> "io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection
> refused: localhost/127.0.0.1:12345"
> Ensure consistent behavior; probably add a dedicated error code.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-20858) Compute error handling
[ https://issues.apache.org/jira/browse/IGNITE-20858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin reassigned IGNITE-20858: -- Assignee: Vadim Pakhnushev (was: Ivan Gagarkin) > Compute error handling > -- > > Key: IGNITE-20858 > URL: https://issues.apache.org/jira/browse/IGNITE-20858 > Project: Ignite > Issue Type: Improvement > Components: compute >Reporter: Igor Sapego >Assignee: Vadim Pakhnushev >Priority: Major > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > Make sure that compute follows AI3 Error Handling rules, defined in > IGNITE-14611. More specifically: > - We should never throw to user anything that is not IgniteException, > IgniteCheckedException or a public class derived from one of them; > - Make sure exceptions thrown by a user code are wrapped by IgniteException > and have a meaningful message. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21397) Fix problem with fastutil shading in core module
Mikhail Pochatkin created IGNITE-21397:
--
Summary: Fix problem with fastutil shading in core module
Key: IGNITE-21397
URL: https://issues.apache.org/jira/browse/IGNITE-21397
Project: Ignite
Issue Type: Bug
Reporter: Mikhail Pochatkin
Assignee: Mikhail Pochatkin
Currently we have shaded fastutil dependency in ignite-core module but this
dependency currently used in many other modules, for example ignite-catalog.
So, this is a reason of ClassCastException in case when we have Intersection
between ignite-core utils methods and other modules import
{code:java}
Caused by: org.apache.ignite.lang.IgniteException: IGN-CMN-65535
TraceId:6215b511-da5d-40de-a967-6039fa137766 Unable to start [node=node1]
at
org.apache.ignite.internal.app.IgniteImpl.handleStartException(IgniteImpl.java:1046)
at
org.apache.ignite.internal.app.IgniteImpl.lambda$start$27(IgniteImpl.java:1023)
at
java.base/java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:930)
... 5 more
Caused by: java.util.concurrent.CompletionException:
java.lang.ClassCastException: class
org.apache.shaded.it.unimi.dsi.fastutil.ints.Int2ObjectOpenHashMap cannot be
cast to class it.unimi.dsi.fastutil.ints.Int2ObjectMap
(org.apache.shaded.it.unimi.dsi.fastutil.ints.Int2ObjectOpenHashMap and
it.unimi.dsi.fastutil.ints.Int2ObjectMap are in unnamed module of loader 'app')
at
java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:314)
at
java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:319)
at
java.base/java.util.concurrent.CompletableFuture$UniRun.tryFire(CompletableFuture.java:787)
... 4 more
Caused by: java.lang.ClassCastException: class
org.apache.shaded.it.unimi.dsi.fastutil.ints.Int2ObjectOpenHashMap cannot be
cast to class it.unimi.dsi.fastutil.ints.Int2ObjectMap
(org.apache.shaded.it.unimi.dsi.fastutil.ints.Int2ObjectOpenHashMap and
it.unimi.dsi.fastutil.ints.Int2ObjectMap are in unnamed module of loader 'app')
at java.base/java.util.function.Function.lambda$andThen$1(Function.java:88)
at
java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:582)
at org.apache.ignite.internal.catalog.Catalog.(Catalog.java:110)
at
org.apache.ignite.internal.catalog.CatalogManagerImpl.start(CatalogManagerImpl.java:170)
at
org.apache.ignite.internal.app.LifecycleManager.startComponent(LifecycleManager.java:79)
at
org.apache.ignite.internal.app.LifecycleManager.startComponents(LifecycleManager.java:91)
at
org.apache.ignite.internal.app.IgniteImpl.lambda$start$22(IgniteImpl.java:963)
at
java.base/java.util.concurrent.CompletableFuture$UniRun.tryFire(CompletableFuture.java:783)
... 4 more {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-21344) Extract fake tables class from client test modul to table testFixtures
Mikhail Pochatkin created IGNITE-21344: -- Summary: Extract fake tables class from client test modul to table testFixtures Key: IGNITE-21344 URL: https://issues.apache.org/jira/browse/IGNITE-21344 Project: Ignite Issue Type: Improvement Reporter: Mikhail Pochatkin We need to extract org.apache.ignite.client.fakes.FakeIgniteTables from client test module to reuse it in another modules. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-20851) Client disconnect and coordinator node shutdown failover
[ https://issues.apache.org/jira/browse/IGNITE-20851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin resolved IGNITE-20851. Assignee: Mikhail Pochatkin Resolution: Won't Fix > Client disconnect and coordinator node shutdown failover > > > Key: IGNITE-20851 > URL: https://issues.apache.org/jira/browse/IGNITE-20851 > Project: Ignite > Issue Type: Improvement > Components: compute >Reporter: Mikhail Pochatkin >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > > h2. Coordinator node shutdown > In the case when the coordinator node is turned off, the execution of the job > will not stop (except for the case where the worker node and the coordinator > node coincide), but in this case the client loses the opportunity to receive > the result of the job execution. > h2. Client disconnect > The current architecture implies that if the connection with the client is > broken, the execution of the job must be canceled, since there is no way to > get the result of the job execution. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-21195) Fix ClientArchTest
[
https://issues.apache.org/jira/browse/IGNITE-21195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Pochatkin resolved IGNITE-21195.
Resolution: Won't Fix
> Fix ClientArchTest
> ---
>
> Key: IGNITE-21195
> URL: https://issues.apache.org/jira/browse/IGNITE-21195
> Project: Ignite
> Issue Type: Bug
>Reporter: Mikhail Pochatkin
>Assignee: Mikhail Pochatkin
>Priority: Major
> Labels: ignite-3
>
> {code:java}
> Architecture Violation [Priority: MEDIUM] - Rule 'no fields that have raw
> type org.apache.ignite.internal.logger.IgniteLogger should have modifier
> STATIC' was violated (1 times):
> Field has
> modifier STATIC in (TrackableNetworkMessageHandler.java:0)
> java.lang.AssertionError: Architecture Violation [Priority: MEDIUM] - Rule
> 'no fields that have raw type org.apache.ignite.internal.logger.IgniteLogger
> should have modifier STATIC' was violated (1 times):
> Field has
> modifier STATIC in (TrackableNetworkMessageHandler.java:0)
> at
> com.tngtech.archunit.lang.ArchRule$Assertions.assertNoViolation(ArchRule.java:94)...
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21195) Fix ClientArchTest
[
https://issues.apache.org/jira/browse/IGNITE-21195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Pochatkin updated IGNITE-21195:
---
Description:
{code:java}
Architecture Violation [Priority: MEDIUM] - Rule 'no fields that have raw type
org.apache.ignite.internal.logger.IgniteLogger should have modifier STATIC' was
violated (1 times):
Field has
modifier STATIC in (TrackableNetworkMessageHandler.java:0)
java.lang.AssertionError: Architecture Violation [Priority: MEDIUM] - Rule 'no
fields that have raw type org.apache.ignite.internal.logger.IgniteLogger should
have modifier STATIC' was violated (1 times):
Field has
modifier STATIC in (TrackableNetworkMessageHandler.java:0)
at
com.tngtech.archunit.lang.ArchRule$Assertions.assertNoViolation(ArchRule.java:94)...
{code}
was:
```
Architecture Violation [Priority: MEDIUM] - Rule 'no fields that have raw type
org.apache.ignite.internal.logger.IgniteLogger should have modifier STATIC' was
violated (1 times):
Field has
modifier STATIC in (TrackableNetworkMessageHandler.java:0)
java.lang.AssertionError: Architecture Violation [Priority: MEDIUM] - Rule 'no
fields that have raw type org.apache.ignite.internal.logger.IgniteLogger should
have modifier STATIC' was violated (1 times):
Field has
modifier STATIC in (TrackableNetworkMessageHandler.java:0)
at
com.tngtech.archunit.lang.ArchRule$Assertions.assertNoViolation(ArchRule.java:94)
...
```
> Fix ClientArchTest
> ---
>
> Key: IGNITE-21195
> URL: https://issues.apache.org/jira/browse/IGNITE-21195
> Project: Ignite
> Issue Type: Bug
>Reporter: Mikhail Pochatkin
>Assignee: Mikhail Pochatkin
>Priority: Major
> Labels: ignite-3
>
> {code:java}
> Architecture Violation [Priority: MEDIUM] - Rule 'no fields that have raw
> type org.apache.ignite.internal.logger.IgniteLogger should have modifier
> STATIC' was violated (1 times):
> Field has
> modifier STATIC in (TrackableNetworkMessageHandler.java:0)
> java.lang.AssertionError: Architecture Violation [Priority: MEDIUM] - Rule
> 'no fields that have raw type org.apache.ignite.internal.logger.IgniteLogger
> should have modifier STATIC' was violated (1 times):
> Field has
> modifier STATIC in (TrackableNetworkMessageHandler.java:0)
> at
> com.tngtech.archunit.lang.ArchRule$Assertions.assertNoViolation(ArchRule.java:94)...
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-21195) Fix ClientArchTest
Mikhail Pochatkin created IGNITE-21195: -- Summary: Fix ClientArchTest Key: IGNITE-21195 URL: https://issues.apache.org/jira/browse/IGNITE-21195 Project: Ignite Issue Type: Bug Reporter: Mikhail Pochatkin Assignee: Mikhail Pochatkin ``` Architecture Violation [Priority: MEDIUM] - Rule 'no fields that have raw type org.apache.ignite.internal.logger.IgniteLogger should have modifier STATIC' was violated (1 times): Field has modifier STATIC in (TrackableNetworkMessageHandler.java:0) java.lang.AssertionError: Architecture Violation [Priority: MEDIUM] - Rule 'no fields that have raw type org.apache.ignite.internal.logger.IgniteLogger should have modifier STATIC' was violated (1 times): Field has modifier STATIC in (TrackableNetworkMessageHandler.java:0) at com.tngtech.archunit.lang.ArchRule$Assertions.assertNoViolation(ArchRule.java:94) ... ``` -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21066) Create job priority change API
[ https://issues.apache.org/jira/browse/IGNITE-21066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-21066: --- Summary: Create job priority change API (was: Change job priority API) > Create job priority change API > -- > > Key: IGNITE-21066 > URL: https://issues.apache.org/jira/browse/IGNITE-21066 > Project: Ignite > Issue Type: Improvement > Components: compute >Reporter: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21066) Create job priority change API
[ https://issues.apache.org/jira/browse/IGNITE-21066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-21066: --- Description: Once a job has been accepted for execution and is in the queue, we should be able to dynamically change its priority in order to move it up or down in the execution queue. > Create job priority change API > -- > > Key: IGNITE-21066 > URL: https://issues.apache.org/jira/browse/IGNITE-21066 > Project: Ignite > Issue Type: Improvement > Components: compute >Reporter: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > > Once a job has been accepted for execution and is in the queue, we should be > able to dynamically change its priority in order to move it up or down in the > execution queue. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-21066) Change job priority API
Mikhail Pochatkin created IGNITE-21066: -- Summary: Change job priority API Key: IGNITE-21066 URL: https://issues.apache.org/jira/browse/IGNITE-21066 Project: Ignite Issue Type: Improvement Components: compute Reporter: Mikhail Pochatkin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-20847) Ownership mechanism for Compute Jobs
[ https://issues.apache.org/jira/browse/IGNITE-20847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin resolved IGNITE-20847. Resolution: Won't Fix > Ownership mechanism for Compute Jobs > > > Key: IGNITE-20847 > URL: https://issues.apache.org/jira/browse/IGNITE-20847 > Project: Ignite > Issue Type: Improvement > Components: compute >Reporter: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > > If we have enabled authentication on AI3 each Compute job execution start > should store owner user. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-19365) Disable components until the cluster configuration is applied
[ https://issues.apache.org/jira/browse/IGNITE-19365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin reassigned IGNITE-19365: -- Assignee: Mikhail Pochatkin (was: Vadim Pakhnushev) > Disable components until the cluster configuration is applied > - > > Key: IGNITE-19365 > URL: https://issues.apache.org/jira/browse/IGNITE-19365 > Project: Ignite > Issue Type: New Feature > Components: clients, rest >Reporter: Vadim Pakhnushev >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > There are instances where the Ignite 3 component requires to be "enabled" > when the cluster configuration is applied. The lifecycle of the component can > be adjusted to follow these steps: creating the component, starting the > component, *waiting for the required cluster configuration, and enabling the > component*. > One particular example is the REST component, which needs to be configured > with basic authentication. There is a time-lapse between cluster > initialization and applying the authentication configuration. During this > time, the REST API remains unauthenticated, and the cluster endpoints are > available to everyone, as mentioned in the IGNITE-18943 ticket. The component > needs to be started -> the cluster must be initialized -> basic auth cluster > configuration should be applied -> REST is enabled. > Redesign of the Ignite 3 component lifecycle is a part of this issue. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-20643) BasicAuthenticationProviderConfiguration should contain a list of users
[ https://issues.apache.org/jira/browse/IGNITE-20643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin reassigned IGNITE-20643: -- Assignee: Mikhail Pochatkin > BasicAuthenticationProviderConfiguration should contain a list of users > --- > > Key: IGNITE-20643 > URL: https://issues.apache.org/jira/browse/IGNITE-20643 > Project: Ignite > Issue Type: Improvement > Components: security >Reporter: Ivan Gagarkin >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > > Creating a separate BasicAuthenticationProviderConfiguration for each user > doesn't make sense. Instead, BasicAuthenticationProviderConfiguration should > contain a list of users. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20986) Extract REST. SSL, Compute integration tests to corresponding modules
[ https://issues.apache.org/jira/browse/IGNITE-20986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-20986: --- Description: All intergartion tests from ignite-runner module should be extract to corresponding modules > Extract REST. SSL, Compute integration tests to corresponding modules > - > > Key: IGNITE-20986 > URL: https://issues.apache.org/jira/browse/IGNITE-20986 > Project: Ignite > Issue Type: Improvement > Components: compute, rest, security >Reporter: Mikhail Pochatkin >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > > All intergartion tests from ignite-runner module should be extract to > corresponding modules -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20986) Extract REST. SSL, Compute integration tests to corresponding modules
Mikhail Pochatkin created IGNITE-20986: -- Summary: Extract REST. SSL, Compute integration tests to corresponding modules Key: IGNITE-20986 URL: https://issues.apache.org/jira/browse/IGNITE-20986 Project: Ignite Issue Type: Improvement Components: compute, rest, security Reporter: Mikhail Pochatkin Assignee: Mikhail Pochatkin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-20843) Introduce job's states
[
https://issues.apache.org/jira/browse/IGNITE-20843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Pochatkin reassigned IGNITE-20843:
--
Assignee: Mikhail Pochatkin
> Introduce job's states
> --
>
> Key: IGNITE-20843
> URL: https://issues.apache.org/jira/browse/IGNITE-20843
> Project: Ignite
> Issue Type: Improvement
> Components: compute
>Reporter: Mikhail Pochatkin
>Assignee: Mikhail Pochatkin
>Priority: Major
> Labels: ignite-3
> Attachments: image-2023-11-13-18-23-21-152.png
>
>
> It is proposed to enter 7 states:
> # Submitted - a state that shows that the job was correctly created and
> accepted by the cluster. Initialization state.
> # Queued - a state indicating that the job is in the waiting queue for
> execution.
> # Executing - a state indicating the job is in execution.
> # Completed - a state indicating that the job was executed successfully and
> the execution result was returned.
> # Failed - a state indicating that a job was unexpectedly terminated during
> execution and its restart was unsuccessful for one reason or another (restart
> not supported or several restart failed in row).
> # Canceling – Job thread is interrupted and the cancel flag is raised.
> # Canceled – Job thread is not alive.
>
> {code:java}
> public enum JobState {
> SUBMITTED, QUEUED, EXECUTING, FAILED, COMPLETED,CANCELING, CANCELED
> } {code}
>
> !image-2023-11-13-18-23-21-152.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-20839) Compute jobs queue
[ https://issues.apache.org/jira/browse/IGNITE-20839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin reassigned IGNITE-20839: -- Assignee: Mikhail Pochatkin > Compute jobs queue > -- > > Key: IGNITE-20839 > URL: https://issues.apache.org/jira/browse/IGNITE-20839 > Project: Ignite > Issue Type: Improvement > Components: compute >Reporter: Mikhail Pochatkin >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > > A job queue is a structure showing upcoming Compute jobs for each node. From > this definition it follows that each node will have its own queue and no > mechanism for sharing information about queues is yet expected. > > The standard queue interface is almost enough for us, with the exception of > the priority adding method. When adding jobs to the queue normally, we will > follow the FIFO strategy, i.e. the default priority value when adding a job > to the queue is 0. > > Priority is an int value between [Int.MIN_VALUE, Int.MAX_VALUE]. Jobs with > the same priority have a FIFO resolving strategy. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19240) Use HTTPS port for dynamic completers when connected to SSL enabled node
[
https://issues.apache.org/jira/browse/IGNITE-19240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Pochatkin updated IGNITE-19240:
---
Reviewer: Mikhail Pochatkin
> Use HTTPS port for dynamic completers when connected to SSL enabled node
>
>
> Key: IGNITE-19240
> URL: https://issues.apache.org/jira/browse/IGNITE-19240
> Project: Ignite
> Issue Type: Bug
> Components: cli
>Reporter: Vadim Pakhnushev
>Assignee: Vadim Pakhnushev
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently {{NodeNameRegistryImpl.urlFromClusterNode}} uses an HTTP port when
> constructing URLs for completion. HTTPS port should be used if the node is
> configured with SSL enabled.
> Even if we construct proper URL, it might be incorrect due to the
> {{NodeMetadata.getRestHost}} returning some IP number which is not verifiable
> with provided trust store.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-20851) Client disconnect and coordinator node shutdown failover
Mikhail Pochatkin created IGNITE-20851: -- Summary: Client disconnect and coordinator node shutdown failover Key: IGNITE-20851 URL: https://issues.apache.org/jira/browse/IGNITE-20851 Project: Ignite Issue Type: Improvement Components: compute Reporter: Mikhail Pochatkin h2. Coordinator node shutdown In the case when the coordinator node is turned off, the execution of the job will not stop (except for the case where the worker node and the coordinator node coincide), but in this case the client loses the opportunity to receive the result of the job execution. h2. Client disconnect The current architecture implies that if the connection with the client is broken, the execution of the job must be canceled, since there is no way to get the result of the job execution. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20850) Worker node shutdown failover
Mikhail Pochatkin created IGNITE-20850: -- Summary: Worker node shutdown failover Key: IGNITE-20850 URL: https://issues.apache.org/jira/browse/IGNITE-20850 Project: Ignite Issue Type: Improvement Components: compute Reporter: Mikhail Pochatkin In this case, the job execution stops and you need to restart it. In this case, the coordinator will see that the worker node has turned off and all the tasks that this coordinator sent for execution must be redistributed to other nodes. In this context, it does not matter what state the tasks were in, in the queue or in the process of execution, we do not offer a safepoint mechanism, and all states of jobs can be written to the cache, so when a task is launched on another worker node, it will be able to read from the cache the state that the job I wrote it down last time. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20848) Management REST API for Compute
Mikhail Pochatkin created IGNITE-20848:
--
Summary: Management REST API for Compute
Key: IGNITE-20848
URL: https://issues.apache.org/jira/browse/IGNITE-20848
Project: Ignite
Issue Type: Improvement
Components: compute
Reporter: Mikhail Pochatkin
POST /management/v1/compute/priority
//Change priority for job
//Body with job is and new priority
GET /management/v1/compute/jobs
//List of all job's statuses
GET /management/v1/compute/jobs/\{id}
//Job status for specified id
DELETE /management/v1/compute/cancel/\{id}
//Cancel job for specified id
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-20843) Introduce job's states
[
https://issues.apache.org/jira/browse/IGNITE-20843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Pochatkin updated IGNITE-20843:
---
Description:
It is proposed to enter 7 states:
# Submitted - a state that shows that the job was correctly created and
accepted by the cluster. Initialization state.
# Queued - a state indicating that the job is in the waiting queue for
execution.
# Executing - a state indicating the job is in execution.
# Completed - a state indicating that the job was executed successfully and
the execution result was returned.
# Failed - a state indicating that a job was unexpectedly terminated during
execution and its restart was unsuccessful for one reason or another (restart
not supported or several restart failed in row).
# Canceling – Job thread is interrupted and the cancel flag is raised.
# Canceled – Job thread is not alive.
{code:java}
public enum JobState {
SUBMITTED, QUEUED, EXECUTING, FAILED, COMPLETED,CANCELING, CANCELED
} {code}
!image-2023-11-13-18-23-21-152.png!
was:
It is proposed to enter 7 states:
# Submitted - a state that shows that the job was correctly created and
accepted by the cluster. Initialization state.
# Queued - a state indicating that the job is in the waiting queue for
execution.
# Executing - a state indicating the job is in execution.
# Completed - a state indicating that the job was executed successfully and
the execution result was returned.
# Failed - a state indicating that a job was unexpectedly terminated during
execution and its restart was unsuccessful for one reason or another (restart
not supported or several restart failed in row).
# Canceling – Job thread is interrupted and the cancel flag is raised.
# Canceled – Job thread is not alive.
!image-2023-11-13-18-23-21-152.png!
> Introduce job's states
> --
>
> Key: IGNITE-20843
> URL: https://issues.apache.org/jira/browse/IGNITE-20843
> Project: Ignite
> Issue Type: Improvement
> Components: compute
>Reporter: Mikhail Pochatkin
>Priority: Major
> Labels: ignite-3
> Attachments: image-2023-11-13-18-23-21-152.png
>
>
> It is proposed to enter 7 states:
> # Submitted - a state that shows that the job was correctly created and
> accepted by the cluster. Initialization state.
> # Queued - a state indicating that the job is in the waiting queue for
> execution.
> # Executing - a state indicating the job is in execution.
> # Completed - a state indicating that the job was executed successfully and
> the execution result was returned.
> # Failed - a state indicating that a job was unexpectedly terminated during
> execution and its restart was unsuccessful for one reason or another (restart
> not supported or several restart failed in row).
> # Canceling – Job thread is interrupted and the cancel flag is raised.
> # Canceled – Job thread is not alive.
>
> {code:java}
> public enum JobState {
> SUBMITTED, QUEUED, EXECUTING, FAILED, COMPLETED,CANCELING, CANCELED
> } {code}
>
> !image-2023-11-13-18-23-21-152.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-20847) Ownership mechanism for Compute Jobs
Mikhail Pochatkin created IGNITE-20847: -- Summary: Ownership mechanism for Compute Jobs Key: IGNITE-20847 URL: https://issues.apache.org/jira/browse/IGNITE-20847 Project: Ignite Issue Type: Improvement Components: compute Reporter: Mikhail Pochatkin If we have enabled authentication on AI3 each Compute job execution start should store owner user. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20845) Compute jobs cancellation
Mikhail Pochatkin created IGNITE-20845:
--
Summary: Compute jobs cancellation
Key: IGNITE-20845
URL: https://issues.apache.org/jira/browse/IGNITE-20845
Project: Ignite
Issue Type: Improvement
Components: compute
Reporter: Mikhail Pochatkin
As stated above, we must provide a mechanism for canceling jobs. Users can
cancel jobs that have one of statuses {*}SUBMITTED{*}, {*}QUEUED{*},
{*}EXECUTING{*}.
# A job with status *SUBMITTED* should not be added to the execution queue.
# A job in the *QUEUED* status after calling cancel should never change to the
*EXECUTING* status and should immediately be removed from the execution queue.
# A job with status *EXECUTING* should be interrupted but this is not possible
in all cases.
h3. Cooperative cancellation
It is proposed to introduce a mechanism for cooperative cancellation. This
means adding properties to the parameters of the job execution method, with the
help of which the user can periodically check the job cancellation status in
the job code itself. Thus, this will allow users to write more flexible code.
However, it is worth noting that we will not depart from Java standards in this
place and everything will also interrupt the job execution flow. That is, in a
sense, this parameter will duplicate the mechanism
*Thread.currentThread().isInterrupted();* however, it will do this more
explicitly. Thus, we will achieve the effects that any standard IO operation on
a Compute job stream will be interrupted at the moment the job is canceled and
the user will be able to receive an exception.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-20844) Introduce JobExecution interface
Mikhail Pochatkin created IGNITE-20844:
--
Summary: Introduce JobExecution interface
Key: IGNITE-20844
URL: https://issues.apache.org/jira/browse/IGNITE-20844
Project: Ignite
Issue Type: Improvement
Components: compute
Reporter: Mikhail Pochatkin
Currently *org.apache.ignite.compute.IgniteCompute* have follow API
{code:java}
CompletableFuture executeAsync(...); {code}
In this task we need to inroduce JobExecution interface
{code:java}
public interface JobExecution {
CompletableStage resultAsync();
CompletableStage statusAsync();
default CompletableStage idAsync() {
return status().thenApply(status -> status.id());
}
CompletableStage cancelAsync();
CompletableStage changePriority(long newPriority);
} {code}
and modify public API
{code:java}
JobExecution executeAsync(...); {code}
+*Important note*+
Implementation of JobExecution interface on clients-side can be done in
follow-up tickets. But changes made in this ticket should be backward
compatibility.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-20843) Introduce job's states
[ https://issues.apache.org/jira/browse/IGNITE-20843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-20843: --- Attachment: image-2023-11-13-18-23-21-152.png > Introduce job's states > -- > > Key: IGNITE-20843 > URL: https://issues.apache.org/jira/browse/IGNITE-20843 > Project: Ignite > Issue Type: Improvement > Components: compute >Reporter: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > Attachments: image-2023-11-13-18-23-21-152.png > > > It is proposed to enter 7 states: > # Submitted - a state that shows that the job was correctly created and > accepted by the cluster. Initialization state. > # Queued - a state indicating that the job is in the waiting queue for > execution. > # Executing - a state indicating the job is in execution. > # Completed - a state indicating that the job was executed successfully and > the execution result was returned. > # Failed - a state indicating that a job was unexpectedly terminated during > execution and its restart was unsuccessful for one reason or another (restart > not supported or several restart failed in row). > # Canceling – Job thread is interrupted and the cancel flag is raised. > # Canceled – Job thread is not alive. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20843) Introduce job's states
[ https://issues.apache.org/jira/browse/IGNITE-20843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-20843: --- Description: It is proposed to enter 7 states: # Submitted - a state that shows that the job was correctly created and accepted by the cluster. Initialization state. # Queued - a state indicating that the job is in the waiting queue for execution. # Executing - a state indicating the job is in execution. # Completed - a state indicating that the job was executed successfully and the execution result was returned. # Failed - a state indicating that a job was unexpectedly terminated during execution and its restart was unsuccessful for one reason or another (restart not supported or several restart failed in row). # Canceling – Job thread is interrupted and the cancel flag is raised. # Canceled – Job thread is not alive. !image-2023-11-13-18-23-21-152.png! was: It is proposed to enter 7 states: # Submitted - a state that shows that the job was correctly created and accepted by the cluster. Initialization state. # Queued - a state indicating that the job is in the waiting queue for execution. # Executing - a state indicating the job is in execution. # Completed - a state indicating that the job was executed successfully and the execution result was returned. # Failed - a state indicating that a job was unexpectedly terminated during execution and its restart was unsuccessful for one reason or another (restart not supported or several restart failed in row). # Canceling – Job thread is interrupted and the cancel flag is raised. # Canceled – Job thread is not alive. > Introduce job's states > -- > > Key: IGNITE-20843 > URL: https://issues.apache.org/jira/browse/IGNITE-20843 > Project: Ignite > Issue Type: Improvement > Components: compute >Reporter: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > Attachments: image-2023-11-13-18-23-21-152.png > > > It is proposed to enter 7 states: > # Submitted - a state that shows that the job was correctly created and > accepted by the cluster. Initialization state. > # Queued - a state indicating that the job is in the waiting queue for > execution. > # Executing - a state indicating the job is in execution. > # Completed - a state indicating that the job was executed successfully and > the execution result was returned. > # Failed - a state indicating that a job was unexpectedly terminated during > execution and its restart was unsuccessful for one reason or another (restart > not supported or several restart failed in row). > # Canceling – Job thread is interrupted and the cancel flag is raised. > # Canceled – Job thread is not alive. > !image-2023-11-13-18-23-21-152.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20843) Introduce job's states
[ https://issues.apache.org/jira/browse/IGNITE-20843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-20843: --- Attachment: image-2023-11-13-18-22-38-443.png > Introduce job's states > -- > > Key: IGNITE-20843 > URL: https://issues.apache.org/jira/browse/IGNITE-20843 > Project: Ignite > Issue Type: Improvement > Components: compute >Reporter: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > > It is proposed to enter 7 states: > # Submitted - a state that shows that the job was correctly created and > accepted by the cluster. Initialization state. > # Queued - a state indicating that the job is in the waiting queue for > execution. > # Executing - a state indicating the job is in execution. > # Completed - a state indicating that the job was executed successfully and > the execution result was returned. > # Failed - a state indicating that a job was unexpectedly terminated during > execution and its restart was unsuccessful for one reason or another (restart > not supported or several restart failed in row). > # Canceling – Job thread is interrupted and the cancel flag is raised. > # Canceled – Job thread is not alive. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20843) Introduce job's states
[ https://issues.apache.org/jira/browse/IGNITE-20843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-20843: --- Attachment: (was: image-2023-11-13-18-21-56-475.png) > Introduce job's states > -- > > Key: IGNITE-20843 > URL: https://issues.apache.org/jira/browse/IGNITE-20843 > Project: Ignite > Issue Type: Improvement > Components: compute >Reporter: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > > It is proposed to enter 7 states: > # Submitted - a state that shows that the job was correctly created and > accepted by the cluster. Initialization state. > # Queued - a state indicating that the job is in the waiting queue for > execution. > # Executing - a state indicating the job is in execution. > # Completed - a state indicating that the job was executed successfully and > the execution result was returned. > # Failed - a state indicating that a job was unexpectedly terminated during > execution and its restart was unsuccessful for one reason or another (restart > not supported or several restart failed in row). > # Canceling – Job thread is interrupted and the cancel flag is raised. > # Canceled – Job thread is not alive. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20843) Introduce job's states
[ https://issues.apache.org/jira/browse/IGNITE-20843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-20843: --- Attachment: (was: image-2023-11-13-18-22-38-443.png) > Introduce job's states > -- > > Key: IGNITE-20843 > URL: https://issues.apache.org/jira/browse/IGNITE-20843 > Project: Ignite > Issue Type: Improvement > Components: compute >Reporter: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > > It is proposed to enter 7 states: > # Submitted - a state that shows that the job was correctly created and > accepted by the cluster. Initialization state. > # Queued - a state indicating that the job is in the waiting queue for > execution. > # Executing - a state indicating the job is in execution. > # Completed - a state indicating that the job was executed successfully and > the execution result was returned. > # Failed - a state indicating that a job was unexpectedly terminated during > execution and its restart was unsuccessful for one reason or another (restart > not supported or several restart failed in row). > # Canceling – Job thread is interrupted and the cancel flag is raised. > # Canceled – Job thread is not alive. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20843) Introduce job's states
[ https://issues.apache.org/jira/browse/IGNITE-20843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-20843: --- Attachment: image-2023-11-13-18-21-56-475.png > Introduce job's states > -- > > Key: IGNITE-20843 > URL: https://issues.apache.org/jira/browse/IGNITE-20843 > Project: Ignite > Issue Type: Improvement > Components: compute >Reporter: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > Attachments: image-2023-11-13-18-21-56-475.png > > > It is proposed to enter 7 states: > # Submitted - a state that shows that the job was correctly created and > accepted by the cluster. Initialization state. > # Queued - a state indicating that the job is in the waiting queue for > execution. > # Executing - a state indicating the job is in execution. > # Completed - a state indicating that the job was executed successfully and > the execution result was returned. > # Failed - a state indicating that a job was unexpectedly terminated during > execution and its restart was unsuccessful for one reason or another (restart > not supported or several restart failed in row). > # Canceling – Job thread is interrupted and the cancel flag is raised. > # Canceled – Job thread is not alive. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20843) Introduce job's states
Mikhail Pochatkin created IGNITE-20843: -- Summary: Introduce job's states Key: IGNITE-20843 URL: https://issues.apache.org/jira/browse/IGNITE-20843 Project: Ignite Issue Type: Improvement Components: compute Reporter: Mikhail Pochatkin It is proposed to enter 7 states: # Submitted - a state that shows that the job was correctly created and accepted by the cluster. Initialization state. # Queued - a state indicating that the job is in the waiting queue for execution. # Executing - a state indicating the job is in execution. # Completed - a state indicating that the job was executed successfully and the execution result was returned. # Failed - a state indicating that a job was unexpectedly terminated during execution and its restart was unsuccessful for one reason or another (restart not supported or several restart failed in row). # Canceling – Job thread is interrupted and the cancel flag is raised. # Canceled – Job thread is not alive. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20842) Introduce Job repeatable mechanism
Mikhail Pochatkin created IGNITE-20842: -- Summary: Introduce Job repeatable mechanism Key: IGNITE-20842 URL: https://issues.apache.org/jira/browse/IGNITE-20842 Project: Ignite Issue Type: Improvement Components: compute Reporter: Mikhail Pochatkin Repeatable mechanism provides the ability to restart a job if it fails as a result of an unhandled exception being thrown during execution. Repeatable config should be flexible and contain follow property: # Max retries counter Repeatable config should be defined on a job execution call and sent with an execution request. If a repeatable task fails with some unhandled exception, it is re-added to the queue with the same priority. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20841) Introduce Compute Job status internal layer
Mikhail Pochatkin created IGNITE-20841:
--
Summary: Introduce Compute Job status internal layer
Key: IGNITE-20841
URL: https://issues.apache.org/jira/browse/IGNITE-20841
Project: Ignite
Issue Type: Improvement
Components: compute
Reporter: Mikhail Pochatkin
Each not-finished Compute Job should provide their current status. This ticket
require only internal API layer. The structure of status class should be follow
{code:java}
public class JobStatus {
private final UUID id;
private JobState state;
private String ownership;
private Instant createTime;
private Instant startTime;
private Instant finishTime;
} {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-20840) Introduce Job execution options
[
https://issues.apache.org/jira/browse/IGNITE-20840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Pochatkin updated IGNITE-20840:
---
Description:
Each execute method in *org.apache.ignite.compute.IgniteCompute* should have
JobExecutionOptions argument. The structure of options class should be follow
{code:java}
public interface JobExecutionOptions {
long priority();
short maxRetries();
}{code}
Priority is Queue priority (default value 0). Max retries is failure retry
counter (default is 0).
> Introduce Job execution options
> ---
>
> Key: IGNITE-20840
> URL: https://issues.apache.org/jira/browse/IGNITE-20840
> Project: Ignite
> Issue Type: Improvement
> Components: compute
>Reporter: Mikhail Pochatkin
>Priority: Major
> Labels: ignite-3
>
> Each execute method in *org.apache.ignite.compute.IgniteCompute* should have
> JobExecutionOptions argument. The structure of options class should be follow
> {code:java}
> public interface JobExecutionOptions {
> long priority();
> short maxRetries();
> }{code}
> Priority is Queue priority (default value 0). Max retries is failure retry
> counter (default is 0).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-20840) Introduce Job execution options
[ https://issues.apache.org/jira/browse/IGNITE-20840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-20840: --- Labels: ignite-3 (was: ) > Introduce Job execution options > --- > > Key: IGNITE-20840 > URL: https://issues.apache.org/jira/browse/IGNITE-20840 > Project: Ignite > Issue Type: Improvement > Components: compute >Reporter: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20840) Introduce Job execution options
Mikhail Pochatkin created IGNITE-20840: -- Summary: Introduce Job execution options Key: IGNITE-20840 URL: https://issues.apache.org/jira/browse/IGNITE-20840 Project: Ignite Issue Type: Improvement Components: compute Reporter: Mikhail Pochatkin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20839) Compute jobs queue
Mikhail Pochatkin created IGNITE-20839: -- Summary: Compute jobs queue Key: IGNITE-20839 URL: https://issues.apache.org/jira/browse/IGNITE-20839 Project: Ignite Issue Type: Improvement Components: compute Reporter: Mikhail Pochatkin A job queue is a structure showing upcoming Compute jobs for each node. From this definition it follows that each node will have its own queue and no mechanism for sharing information about queues is yet expected. The standard queue interface is almost enough for us, with the exception of the priority adding method. When adding jobs to the queue normally, we will follow the FIFO strategy, i.e. the default priority value when adding a job to the queue is 0. Priority is an int value between [Int.MIN_VALUE, Int.MAX_VALUE]. Jobs with the same priority have a FIFO resolving strategy. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20838) Compute: queues, priority, failover, cancellation
Mikhail Pochatkin created IGNITE-20838: -- Summary: Compute: queues, priority, failover, cancellation Key: IGNITE-20838 URL: https://issues.apache.org/jira/browse/IGNITE-20838 Project: Ignite Issue Type: Epic Components: compute Reporter: Mikhail Pochatkin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-20664) Resolve compatibility issue with SnakeYAML versions in Micronaut tests
[
https://issues.apache.org/jira/browse/IGNITE-20664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Pochatkin resolved IGNITE-20664.
Resolution: Won't Fix
It's impossible currently to resolve this issue easaly.
*micronaut-junit5* dependency has *micronaut-inject* dependency with version
3.5.4 which recursively apply snakeyaml:1.33. So, at the moment we use latest
3.x *micronaut-junit5* and looks like new release is not possible becuase
micronaut community focused on 4.x.
4.x version of micronaut is not applicable for AI3 becuase it based on Java17
> Resolve compatibility issue with SnakeYAML versions in Micronaut tests
> --
>
> Key: IGNITE-20664
> URL: https://issues.apache.org/jira/browse/IGNITE-20664
> Project: Ignite
> Issue Type: Bug
> Components: cli
>Reporter: Ivan Gagarkin
>Assignee: Mikhail Pochatkin
>Priority: Major
> Labels: ignite-3
>
>
> We are encountering an issue with Micronaut tests involving the 'jarhell'
> component. Specifically, we are using two different versions of the SnakeYAML
> library - version 1.33 and version 2.0. When running the tests from IntelliJ
> IDEA, we observe the following error in the
> 'org.apache.ignite.internal.rest.ItGeneratedRestClientTest' class
> {code:java}
> java.lang.NoSuchMethodError: org.yaml.snakeyaml.constructor.SafeConstructor:
> method 'void ()' not found
> at
> io.micronaut.context.env.yaml.CustomSafeConstructor.(CustomSafeConstructor.java:36)
> at
> io.micronaut.context.env.yaml.YamlPropertySourceLoader.processInput(YamlPropertySourceLoader.java:56)
> at
> io.micronaut.context.env.AbstractPropertySourceLoader.read(AbstractPropertySourceLoader.java:117)
> at
> io.micronaut.context.env.AbstractPropertySourceLoader.loadProperties(AbstractPropertySourceLoader.java:102)
> at
> io.micronaut.context.env.AbstractPropertySourceLoader.load(AbstractPropertySourceLoader.java:68)
> at
> io.micronaut.context.env.AbstractPropertySourceLoader.load(AbstractPropertySourceLoader.java:55)
> at
> io.micronaut.context.env.DefaultEnvironment.loadPropertySourceFromLoader(DefaultEnvironment.java:607)
> at
> io.micronaut.context.env.DefaultEnvironment.readPropertySourceList(DefaultEnvironment.java:541)
> at
> io.micronaut.context.env.DefaultEnvironment.readPropertySourceList(DefaultEnvironment.java:527)
> at
> io.micronaut.context.DefaultApplicationContext$RuntimeConfiguredEnvironment.readPropertySourceList(DefaultApplicationContext.java:794)
>at
> io.micronaut.context.env.DefaultEnvironment.readPropertySources(DefaultEnvironment.java:412)
> at
> io.micronaut.context.env.DefaultEnvironment.start(DefaultEnvironment.java:270)
>at
> io.micronaut.context.DefaultApplicationContext$RuntimeConfiguredEnvironment.start(DefaultApplicationContext.java:769)
> at
> io.micronaut.context.DefaultApplicationContext$RuntimeConfiguredEnvironment.start(DefaultApplicationContext.java:738)
> at
> io.micronaut.context.DefaultApplicationContext.startEnvironment(DefaultApplicationContext.java:242)
> at
> io.micronaut.context.DefaultApplicationContext.start(DefaultApplicationContext.java:193)
> at
> io.micronaut.test.extensions.AbstractMicronautExtension.startApplicationContext(AbstractMicronautExtension.java:433)
> at
> io.micronaut.test.extensions.AbstractMicronautExtension.beforeClass(AbstractMicronautExtension.java:314)
> at
> io.micronaut.test.extensions.junit5.MicronautJunit5Extension.beforeAll(MicronautJunit5Extension.java:84)
> at
> org.junit.jupiter.engine.descriptor.ClassBasedTestDescriptor.lambda$invokeBeforeAllCallbacks$12(ClassBasedTestDescriptor.java:395)
>at
> org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
> at
> org.junit.jupiter.engine.descriptor.ClassBasedTestDescriptor.invokeBeforeAllCallbacks(ClassBasedTestDescriptor.java:395)
> at
> org.junit.jupiter.engine.descriptor.ClassBasedTestDescriptor.before(ClassBasedTestDescriptor.java:211)
>at
> org.junit.jupiter.engine.descriptor.ClassBasedTestDescriptor.before(ClassBasedTestDescriptor.java:84)
> at
> org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$6(NodeTestTask.java:148)
>at
> org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
> at
> org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$8(NodeTestTask.java:141)
>at
> org.junit.platform.engine.support.hierarchical.Node.around(Node.java:137)
> at
>
