[jira] [Commented] (IGNITE-12129) Upgrade spring-5.0.X and spring-data-2.0.X dependencies to latest versions
[ https://issues.apache.org/jira/browse/IGNITE-12129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003933#comment-17003933 ] Ilya Kasnacheev commented on IGNITE-12129: -- I have initiated a discussion about version bumping on the userlist. > Upgrade spring-5.0.X and spring-data-2.0.X dependencies to latest versions > -- > > Key: IGNITE-12129 > URL: https://issues.apache.org/jira/browse/IGNITE-12129 > Project: Ignite > Issue Type: Wish > Components: spring >Reporter: Pavel >Assignee: Surkov Aleksandr >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The actual spring version is 5.1.9.RELEASE, spring boot version is > 2.1.7.RELEASE > In Ignite master branch spring versions are 5.0.8.RELEASE and 2.0.9.RELEASE -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12502) Document ignite-spring-data_2.2 module
Ilya Kasnacheev created IGNITE-12502: Summary: Document ignite-spring-data_2.2 module Key: IGNITE-12502 URL: https://issues.apache.org/jira/browse/IGNITE-12502 Project: Ignite Issue Type: Improvement Components: documentation Reporter: Ilya Kasnacheev After IGNITE-12259 I think there are no API changes, but we should mention that we have such module and what its dependencies are. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12259) Create new module for support spring-5.2.X and spring-data-2.2.X
[ https://issues.apache.org/jira/browse/IGNITE-12259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-12259: - Ignite Flags: (was: Docs Required) > Create new module for support spring-5.2.X and spring-data-2.2.X > > > Key: IGNITE-12259 > URL: https://issues.apache.org/jira/browse/IGNITE-12259 > Project: Ignite > Issue Type: Wish > Components: integrations >Reporter: Surkov Aleksandr >Assignee: Surkov Aleksandr >Priority: Minor > Fix For: 2.8 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The actual spring version is > [5.2.0.RELEASE|https://mvnrepository.com/artifact/org.springframework/spring-context/5.2.0.RELEASE], > spring data version is > [2.2.0.RELEASE.|https://mvnrepository.com/artifact/org.springframework.data/spring-data-commons/2.2.0.RELEASE] > It would be nice to add a module to support these versions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12259) Create new module for support spring-5.2.X and spring-data-2.2.X
[ https://issues.apache.org/jira/browse/IGNITE-12259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-12259: - Component/s: integrations > Create new module for support spring-5.2.X and spring-data-2.2.X > > > Key: IGNITE-12259 > URL: https://issues.apache.org/jira/browse/IGNITE-12259 > Project: Ignite > Issue Type: Wish > Components: integrations >Reporter: Surkov Aleksandr >Assignee: Surkov Aleksandr >Priority: Minor > Fix For: 2.8 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The actual spring version is > [5.2.0.RELEASE|https://mvnrepository.com/artifact/org.springframework/spring-context/5.2.0.RELEASE], > spring data version is > [2.2.0.RELEASE.|https://mvnrepository.com/artifact/org.springframework.data/spring-data-commons/2.2.0.RELEASE] > It would be nice to add a module to support these versions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12259) Create new module for support spring-5.2.X and spring-data-2.2.X
[ https://issues.apache.org/jira/browse/IGNITE-12259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-12259: - Fix Version/s: (was: 2.9) 2.8 > Create new module for support spring-5.2.X and spring-data-2.2.X > > > Key: IGNITE-12259 > URL: https://issues.apache.org/jira/browse/IGNITE-12259 > Project: Ignite > Issue Type: Wish >Reporter: Surkov Aleksandr >Assignee: Surkov Aleksandr >Priority: Minor > Fix For: 2.8 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The actual spring version is > [5.2.0.RELEASE|https://mvnrepository.com/artifact/org.springframework/spring-context/5.2.0.RELEASE], > spring data version is > [2.2.0.RELEASE.|https://mvnrepository.com/artifact/org.springframework.data/spring-data-commons/2.2.0.RELEASE] > It would be nice to add a module to support these versions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12259) Create new module for support spring-5.2.X and spring-data-2.2.X
[ https://issues.apache.org/jira/browse/IGNITE-12259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-12259: - Ignite Flags: Docs Required (was: Docs Required,Release Notes Required) > Create new module for support spring-5.2.X and spring-data-2.2.X > > > Key: IGNITE-12259 > URL: https://issues.apache.org/jira/browse/IGNITE-12259 > Project: Ignite > Issue Type: Wish > Components: integrations >Reporter: Surkov Aleksandr >Assignee: Surkov Aleksandr >Priority: Minor > Fix For: 2.8 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The actual spring version is > [5.2.0.RELEASE|https://mvnrepository.com/artifact/org.springframework/spring-context/5.2.0.RELEASE], > spring data version is > [2.2.0.RELEASE.|https://mvnrepository.com/artifact/org.springframework.data/spring-data-commons/2.2.0.RELEASE] > It would be nice to add a module to support these versions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12497) PartitionsEvictManager should log all partitions which will be evicted
[
https://issues.apache.org/jira/browse/IGNITE-12497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003901#comment-17003901
]
Ignite TC Bot commented on IGNITE-12497:
{panel:title=Branch: [pull/7202/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4881459buildTypeId=IgniteTests24Java8_RunAll]
> PartitionsEvictManager should log all partitions which will be evicted
> --
>
> Key: IGNITE-12497
> URL: https://issues.apache.org/jira/browse/IGNITE-12497
> Project: Ignite
> Issue Type: Improvement
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.9
>
>
> Now we print information about eviction only if it longer then threshold
> (i.e. progress). And we can't detect in logs, that partition was evicted due
> to different reasons (rebalance, wrong configuration custom affinity).
> I think we could print information on info level about each evicted partition
> before start of eviction. Information about partitions could be aggregated,
> compacted and printed by timer, but *all evicted partitions must be printed
> to log anyway.*
> I would have the following information about each partition:
> * partitionId
> * groupId
> * groupName
> * reason (eviction, clearing)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Issue Comment Deleted] (IGNITE-12470) Pme-free switch feature should be deactivatable
[
https://issues.apache.org/jira/browse/IGNITE-12470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-12470:
--
Comment: was deleted
(was: {panel:title=Branch: [pull/7189/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4878013buildTypeId=IgniteTests24Java8_RunAll])
> Pme-free switch feature should be deactivatable
> ---
>
> Key: IGNITE-12470
> URL: https://issues.apache.org/jira/browse/IGNITE-12470
> Project: Ignite
> Issue Type: Task
>Reporter: Anton Vinogradov
>Assignee: Sergei Ryzhov
>Priority: Blocker
> Labels: newbie
> Fix For: 2.8, 2.9
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> We should be able to disable this feature by some env/jvm property.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Issue Comment Deleted] (IGNITE-12470) Pme-free switch feature should be deactivatable
[
https://issues.apache.org/jira/browse/IGNITE-12470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-12470:
--
Comment: was deleted
(was: {panel:title=Branch: [pull/7189/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4881575buildTypeId=IgniteTests24Java8_RunAll])
> Pme-free switch feature should be deactivatable
> ---
>
> Key: IGNITE-12470
> URL: https://issues.apache.org/jira/browse/IGNITE-12470
> Project: Ignite
> Issue Type: Task
>Reporter: Anton Vinogradov
>Assignee: Sergei Ryzhov
>Priority: Blocker
> Labels: newbie
> Fix For: 2.8, 2.9
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> We should be able to disable this feature by some env/jvm property.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Issue Comment Deleted] (IGNITE-12470) Pme-free switch feature should be deactivatable
[
https://issues.apache.org/jira/browse/IGNITE-12470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-12470:
--
Comment: was deleted
(was: {panel:title=Branch: [pull/7189/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4872252buildTypeId=IgniteTests24Java8_RunAll])
> Pme-free switch feature should be deactivatable
> ---
>
> Key: IGNITE-12470
> URL: https://issues.apache.org/jira/browse/IGNITE-12470
> Project: Ignite
> Issue Type: Task
>Reporter: Anton Vinogradov
>Assignee: Sergei Ryzhov
>Priority: Blocker
> Labels: newbie
> Fix For: 2.8, 2.9
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> We should be able to disable this feature by some env/jvm property.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Issue Comment Deleted] (IGNITE-12470) Pme-free switch feature should be deactivatable
[
https://issues.apache.org/jira/browse/IGNITE-12470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-12470:
--
Comment: was deleted
(was: {panel:title=Branch: [pull/7189/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Integrations){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=4877986]]
* dll: EntityFrameworkCacheTest.TestOldEntriesCleanupMultithreaded - Test has
low fail rate in base branch 0,0% and is not flaky
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4878013buildTypeId=IgniteTests24Java8_RunAll])
> Pme-free switch feature should be deactivatable
> ---
>
> Key: IGNITE-12470
> URL: https://issues.apache.org/jira/browse/IGNITE-12470
> Project: Ignite
> Issue Type: Task
>Reporter: Anton Vinogradov
>Assignee: Sergei Ryzhov
>Priority: Blocker
> Labels: newbie
> Fix For: 2.8, 2.9
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> We should be able to disable this feature by some env/jvm property.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Issue Comment Deleted] (IGNITE-12470) Pme-free switch feature should be deactivatable
[
https://issues.apache.org/jira/browse/IGNITE-12470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-12470:
--
Comment: was deleted
(was: {panel:title=Branch: [pull/7189/head] Base: [master] : Possible Blockers
(3)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}PDS (Indexing){color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=4872216]]
{color:#d04437}Start Nodes{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=4872167]]
* IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStartOneNode - Test has low fail
rate in base branch 0,0% and is not flaky
{color:#d04437}Thin Client: Java{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=4872159]]
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4872252buildTypeId=IgniteTests24Java8_RunAll])
> Pme-free switch feature should be deactivatable
> ---
>
> Key: IGNITE-12470
> URL: https://issues.apache.org/jira/browse/IGNITE-12470
> Project: Ignite
> Issue Type: Task
>Reporter: Anton Vinogradov
>Assignee: Sergei Ryzhov
>Priority: Blocker
> Labels: newbie
> Fix For: 2.8, 2.9
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> We should be able to disable this feature by some env/jvm property.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Issue Comment Deleted] (IGNITE-12470) Pme-free switch feature should be deactivatable
[
https://issues.apache.org/jira/browse/IGNITE-12470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-12470:
--
Comment: was deleted
(was: {panel:title=Branch: [pull/7189/head] Base: [master] : Possible Blockers
(6)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=4880410]]
* IgniteCacheTestSuite2:
GridCachePartitionedEvictionSelfTest.testEvictionTxPessimisticRepeatableRead -
Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}MVCC PDS 4{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=4880456]]
* IgnitePdsMvccTestSuite4:
IgniteRebalanceOnCachesStoppingOrDestroyingTest.testStopCachesOnDeactivationSecondGroup
- Test has low fail rate in base branch 0,0% and is not flaky
* IgnitePdsMvccTestSuite4:
IgniteRebalanceOnCachesStoppingOrDestroyingTest.testDestroySpecificCachesInDifferentCacheGroupsSecondGroup
- Test has low fail rate in base branch 0,0% and is not flaky
* IgnitePdsMvccTestSuite4:
ResetLostPartitionTest.testReactivateGridBeforeResetLostPartitions - Test has
low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Queries 2{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=4880371]]
{color:#d04437}MVCC Cache{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=4880392]]
* IgniteCacheMvccTestSuite:
CacheMvccReplicatedCoordinatorFailoverTest.testAccountsTxGet_Server_Backups0_CoordinatorFails_Persistence
- Test has low fail rate in base branch 0,0% and is not flaky
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4880460buildTypeId=IgniteTests24Java8_RunAll])
> Pme-free switch feature should be deactivatable
> ---
>
> Key: IGNITE-12470
> URL: https://issues.apache.org/jira/browse/IGNITE-12470
> Project: Ignite
> Issue Type: Task
>Reporter: Anton Vinogradov
>Assignee: Sergei Ryzhov
>Priority: Blocker
> Labels: newbie
> Fix For: 2.8, 2.9
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> We should be able to disable this feature by some env/jvm property.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12007) Latest "apacheignite/web-console-backend" docker image is broken
[
https://issues.apache.org/jira/browse/IGNITE-12007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003884#comment-17003884
]
SANJAYA KUMAR SAHOO commented on IGNITE-12007:
--
I have fixed the issue in 2.7.6, can I raise a PR for this issue ?
> Latest "apacheignite/web-console-backend" docker image is broken
>
>
> Key: IGNITE-12007
> URL: https://issues.apache.org/jira/browse/IGNITE-12007
> Project: Ignite
> Issue Type: Bug
> Components: UI
>Affects Versions: 2.7
>Reporter: Igor Belyakov
>Priority: Critical
>
> It's not possible to run docker container by using the latest version of
> "apacheignite/web-console-backend" image.
> Next error happens on the start:
> {code:java}
> npm ERR! A complete log of this run can be found in:
> npm ERR! /root/.npm/_logs/2019-07-23T14_24_40_353Z-debug.log
> npm ERR! path /opt/web-console/package.json
> npm ERR! code ENOENT
> npm ERR! errno -2
> npm ERR! syscall open
> npm ERR! enoent ENOENT: no such file or directory, open
> '/opt/web-console/package.json'
> npm ERR! enoent This is related to npm not being able to find a file.
> npm ERR! enoent{code}
> How to reproduce:
> Run container by using docker-compose as described here:
> [https://hub.docker.com/r/apacheignite/web-console-backend]
>
> Seems like it was broken by the next commit:
> [https://github.com/apache/ignite/commit/4c295f8f468ddfce458948c17c13b1748b13e918#diff-ec0d595d738c4207e08ce210624e902aR22]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12470) Pme-free switch feature should be deactivatable
[
https://issues.apache.org/jira/browse/IGNITE-12470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003829#comment-17003829
]
Ignite TC Bot commented on IGNITE-12470:
{panel:title=Branch: [pull/7189/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4881575buildTypeId=IgniteTests24Java8_RunAll]
> Pme-free switch feature should be deactivatable
> ---
>
> Key: IGNITE-12470
> URL: https://issues.apache.org/jira/browse/IGNITE-12470
> Project: Ignite
> Issue Type: Task
>Reporter: Anton Vinogradov
>Assignee: Sergei Ryzhov
>Priority: Blocker
> Labels: newbie
> Fix For: 2.8, 2.9
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> We should be able to disable this feature by some env/jvm property.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12470) Pme-free switch feature should be deactivatable
[
https://issues.apache.org/jira/browse/IGNITE-12470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003820#comment-17003820
]
Ignite TC Bot commented on IGNITE-12470:
{panel:title=Branch: [pull/7189/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4881575buildTypeId=IgniteTests24Java8_RunAll]
> Pme-free switch feature should be deactivatable
> ---
>
> Key: IGNITE-12470
> URL: https://issues.apache.org/jira/browse/IGNITE-12470
> Project: Ignite
> Issue Type: Task
>Reporter: Anton Vinogradov
>Assignee: Sergei Ryzhov
>Priority: Blocker
> Labels: newbie
> Fix For: 2.8, 2.9
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> We should be able to disable this feature by some env/jvm property.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12501) The AuthenticationProcessorNodeRestartTest.testConcurrentAuthorize test is flacky.
[
https://issues.apache.org/jira/browse/IGNITE-12501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003681#comment-17003681
]
Amelchev Nikita commented on IGNITE-12501:
--
Also, I have found that the issue's test makes the
AuthenticationProcessorNodeRestartTest.test1kUsersNodeRestartServer test fails.
> The AuthenticationProcessorNodeRestartTest.testConcurrentAuthorize test is
> flacky.
> --
>
> Key: IGNITE-12501
> URL: https://issues.apache.org/jira/browse/IGNITE-12501
> Project: Ignite
> Issue Type: Bug
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Minor
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The test is flacky. [TC
> history|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=7463074180495175640=testDetails].
> (Success rate 76%)
> The reason is that there is not enough check for a message about the node
> exit:
> Now:
> {noformat}
> private boolean serverDownMessage(String text) {
> return text.contains("Failed to send message (node may have left the
> grid or "
> + "TCP connection cannot be established due to firewall issues)")
> || text.contains("Failed to send message, node left");
> }
> {noformat}
> But message send can be failed by follow message introduced in IGNITE-7648:
> {noformat}
> java.lang.AssertionError: Unexpected exception: Failed to send message (node
> left topology):
> {noformat}
> It seems we should to add this message to the check.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12301) Free-lists system view
[ https://issues.apache.org/jira/browse/IGNITE-12301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003656#comment-17003656 ] Aleksey Plekhanov commented on IGNITE-12301: [~nizhikov], thanks for the review! Merged to master. > Free-lists system view > -- > > Key: IGNITE-12301 > URL: https://issues.apache.org/jira/browse/IGNITE-12301 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Major > Labels: IEP-35 > Time Spent: 1h 50m > Remaining Estimate: 0h > > Implement a system view for free-lists monitoring. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12301) Free-lists system view
[ https://issues.apache.org/jira/browse/IGNITE-12301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-12301: --- Fix Version/s: 2.9 > Free-lists system view > -- > > Key: IGNITE-12301 > URL: https://issues.apache.org/jira/browse/IGNITE-12301 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Major > Labels: IEP-35 > Fix For: 2.9 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > Implement a system view for free-lists monitoring. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-12259) Create new module for support spring-5.2.X and spring-data-2.2.X
[ https://issues.apache.org/jira/browse/IGNITE-12259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003632#comment-17003632 ] Surkov Aleksandr edited comment on IGNITE-12259 at 12/26/19 1:49 PM: - [~ilyak] It's great news! I'm glad! Thank you! was (Author: surkov): It's great news! I'm glad! Thank you! > Create new module for support spring-5.2.X and spring-data-2.2.X > > > Key: IGNITE-12259 > URL: https://issues.apache.org/jira/browse/IGNITE-12259 > Project: Ignite > Issue Type: Wish >Reporter: Surkov Aleksandr >Assignee: Surkov Aleksandr >Priority: Minor > Fix For: 2.9 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The actual spring version is > [5.2.0.RELEASE|https://mvnrepository.com/artifact/org.springframework/spring-context/5.2.0.RELEASE], > spring data version is > [2.2.0.RELEASE.|https://mvnrepository.com/artifact/org.springframework.data/spring-data-commons/2.2.0.RELEASE] > It would be nice to add a module to support these versions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12342) Continuous Queries: Remote filter and transformer have to run with appropriate SecurityContext.
[
https://issues.apache.org/jira/browse/IGNITE-12342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003639#comment-17003639
]
Ignite TC Bot commented on IGNITE-12342:
{panel:title=Branch: [pull/7125/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4881330buildTypeId=IgniteTests24Java8_RunAll]
> Continuous Queries: Remote filter and transformer have to run with
> appropriate SecurityContext.
> ---
>
> Key: IGNITE-12342
> URL: https://issues.apache.org/jira/browse/IGNITE-12342
> Project: Ignite
> Issue Type: Bug
> Components: security
>Reporter: Denis Garus
>Assignee: Denis Garus
>Priority: Major
> Labels: iep-38
> Time Spent: 4h 50m
> Remaining Estimate: 0h
>
> Remote filter and transformer of ContinuousQueries have to run on a remote
> node with the SecurityContext of the initiator node.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12259) Create new module for support spring-5.2.X and spring-data-2.2.X
[ https://issues.apache.org/jira/browse/IGNITE-12259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003632#comment-17003632 ] Surkov Aleksandr commented on IGNITE-12259: --- It's great news! I'm glad! Thank you! > Create new module for support spring-5.2.X and spring-data-2.2.X > > > Key: IGNITE-12259 > URL: https://issues.apache.org/jira/browse/IGNITE-12259 > Project: Ignite > Issue Type: Wish >Reporter: Surkov Aleksandr >Assignee: Surkov Aleksandr >Priority: Minor > Fix For: 2.9 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The actual spring version is > [5.2.0.RELEASE|https://mvnrepository.com/artifact/org.springframework/spring-context/5.2.0.RELEASE], > spring data version is > [2.2.0.RELEASE.|https://mvnrepository.com/artifact/org.springframework.data/spring-data-commons/2.2.0.RELEASE] > It would be nice to add a module to support these versions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12501) The AuthenticationProcessorNodeRestartTest.testConcurrentAuthorize test is flacky.
Amelchev Nikita created IGNITE-12501:
Summary: The
AuthenticationProcessorNodeRestartTest.testConcurrentAuthorize test is flacky.
Key: IGNITE-12501
URL: https://issues.apache.org/jira/browse/IGNITE-12501
Project: Ignite
Issue Type: Bug
Reporter: Amelchev Nikita
Assignee: Amelchev Nikita
Fix For: 2.9
The test is flacky. [TC
history|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=7463074180495175640=testDetails].
(Success rate 76%)
The reason is that there is not enough check for a message about the node exit:
Now:
{noformat}
private boolean serverDownMessage(String text) {
return text.contains("Failed to send message (node may have left the
grid or "
+ "TCP connection cannot be established due to firewall issues)")
|| text.contains("Failed to send message, node left");
}
{noformat}
But message send can be failed by follow message introduced in IGNITE-7648:
{noformat}
java.lang.AssertionError: Unexpected exception: Failed to send message (node
left topology):
{noformat}
It seems we should to add this message to the check.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12385) .NET Thin Client: introduce ClusterGroup API
[ https://issues.apache.org/jira/browse/IGNITE-12385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003598#comment-17003598 ] Alexandr Shapkin commented on IGNITE-12385: --- [~ptupitsyn] please, check > .NET Thin Client: introduce ClusterGroup API > > > Key: IGNITE-12385 > URL: https://issues.apache.org/jira/browse/IGNITE-12385 > Project: Ignite > Issue Type: New Feature > Components: thin client >Affects Versions: 2.7.6 >Reporter: Alexandr Shapkin >Assignee: Alexandr Shapkin >Priority: Major > Fix For: 2.9 > > Time Spent: 10m > Remaining Estimate: 0h > > We need to implement IClusterGroup API for thin clients. > Let's start with following methods: > * IClusterGroup.ForDotNet() > * IClusterGroup.ForAttributes() > * IClusterGroup.GetNodes() -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12500) IgniteProxy should be injected into non-system types only.
Denis Garus created IGNITE-12500: Summary: IgniteProxy should be injected into non-system types only. Key: IGNITE-12500 URL: https://issues.apache.org/jira/browse/IGNITE-12500 Project: Ignite Issue Type: Improvement Reporter: Denis Garus When the Ignite Sandbox is enabled, the GridResourceProxiedIgniteInjector should inject an IgniteProxy into non-system types only. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12499) Node took a long time to start after kill
Ivan Bessonov created IGNITE-12499: -- Summary: Node took a long time to start after kill Key: IGNITE-12499 URL: https://issues.apache.org/jira/browse/IGNITE-12499 Project: Ignite Issue Type: Bug Reporter: Ivan Bessonov Assignee: Ivan Bessonov Fix For: 2.9 Test scenario: 1) Start 4 node cluster 2) Activate 3) Load 1k rows to each cache 4) Stop node 5) Return it back without index.bin files 6) Wait until start Somehow the first node takes Waiting for topology snapshot: server(s) 4/4, client(s) 0/*, timeout 1166/1800 sec to start. [10:47:21,360][INFO][main][G] Node started : [stage="Configure system pool" (129 ms),stage="Start managers" (440 ms),stage="Configure binary metadata" (86 ms),stage="Start processors" (39341 ms),stage="Start 'GridGain' plugin" (16 ms),s tage="Init and start regions" (210 ms),stage="Restore binary memory" (228224 ms),stage="Restore logical state" (859694 ms),stage="Finish recovery" (8938 ms),stage="Join topology" (6024 ms),stage="Await transition" (16 ms),stage="Await e xchange" (14855 ms),stage="Total time" (1157973 ms)] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12491) Eliminate contention on ConcurrentHashMap.size()
[ https://issues.apache.org/jira/browse/IGNITE-12491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003593#comment-17003593 ] Sergey Chugunov commented on IGNITE-12491: -- [~ibessonov], Change looks rational for me and reduces checkpoint read lock/unlock cost significantly. Lets merge it to master. Thank you for contribution! > Eliminate contention on ConcurrentHashMap.size() > > > Key: IGNITE-12491 > URL: https://issues.apache.org/jira/browse/IGNITE-12491 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Fix For: 2.9 > > Time Spent: 10m > Remaining Estimate: 0h > > Methods who invoked checkpointReadLock/checkpointReadUnlock spend much time > on calculation of quantity dirty pages. You will to see that when have some > hundreds of regions. > Any persistent operation will be cost hundreds invokes of size on > ConcurrentHashMap. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12486) Truncation of archived WAL segments doesn't work
[
https://issues.apache.org/jira/browse/IGNITE-12486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003584#comment-17003584
]
Ignite TC Bot commented on IGNITE-12486:
{panel:title=Branch: [pull/7185/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4869466buildTypeId=IgniteTests24Java8_RunAll]
> Truncation of archived WAL segments doesn't work
>
>
> Key: IGNITE-12486
> URL: https://issues.apache.org/jira/browse/IGNITE-12486
> Project: Ignite
> Issue Type: Bug
>Reporter: Ivan Bessonov
>Assignee: Ivan Bessonov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Index calculation is wrong in FileWriteAheadLogManager#rollOver.
> It leads to unexpected and faulty WAL segments truncation and data corruption
> as a result.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12491) Eliminate contention on ConcurrentHashMap.size()
[
https://issues.apache.org/jira/browse/IGNITE-12491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003582#comment-17003582
]
Ignite TC Bot commented on IGNITE-12491:
{panel:title=Branch: [pull/7190/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4871987buildTypeId=IgniteTests24Java8_RunAll]
> Eliminate contention on ConcurrentHashMap.size()
>
>
> Key: IGNITE-12491
> URL: https://issues.apache.org/jira/browse/IGNITE-12491
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ivan Bessonov
>Assignee: Ivan Bessonov
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Methods who invoked checkpointReadLock/checkpointReadUnlock spend much time
> on calculation of quantity dirty pages. You will to see that when have some
> hundreds of regions.
> Any persistent operation will be cost hundreds invokes of size on
> ConcurrentHashMap.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12487) Inconsistent GridIoManager API for sendToGridTopic(Collection nodes) and sendToGridTopic(UUID nodeId)
[
https://issues.apache.org/jira/browse/IGNITE-12487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003585#comment-17003585
]
Ignite TC Bot commented on IGNITE-12487:
{panel:title=Branch: [pull/7186/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4869582buildTypeId=IgniteTests24Java8_RunAll]
> Inconsistent GridIoManager API for sendToGridTopic(Collection nodes) and
> sendToGridTopic(UUID nodeId)
> -
>
> Key: IGNITE-12487
> URL: https://issues.apache.org/jira/browse/IGNITE-12487
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ivan Bessonov
>Assignee: Ivan Bessonov
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Method
> {{1}}{{ctx.io().sendToGridTopic(Collection nodes, )}}
> will throw exception "Internal Ignite code should never call the method with
> local node in a node list."
> But at the same time
> {{1}}{{ctx.io().sendToGridTopic(((IgniteEx)ignite).localNode().id(), ...)}}
> Works without any exception.
> From my point of view we should not throw exception.
> Processing messages in common listener is much more comfortable than writing
> same code twice, one for remote nodes and one for local.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12485) DiscoveryEvent make event message lazy initialization
[
https://issues.apache.org/jira/browse/IGNITE-12485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003583#comment-17003583
]
Ignite TC Bot commented on IGNITE-12485:
{panel:title=Branch: [pull/7184/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4869350buildTypeId=IgniteTests24Java8_RunAll]
> DiscoveryEvent make event message lazy initialization
> -
>
> Key: IGNITE-12485
> URL: https://issues.apache.org/jira/browse/IGNITE-12485
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ivan Bessonov
>Assignee: Ivan Bessonov
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In GridDiscoveryManager$DiscoveryWorker#recordEvent() we set to each event
> message: "msg " + clusterNode
> Invocation toString() on ClusterNode's inheritor could be expensive.
> I think event message could be lazy generated from event type and cluster
> node.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12458) Rename Affinity Awareness to Partition Awareness
[
https://issues.apache.org/jira/browse/IGNITE-12458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003579#comment-17003579
]
Ignite TC Bot commented on IGNITE-12458:
{panel:title=Branch: [pull/7199/head] Base: [master] : Possible Blockers
(4)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 6{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=4880922]]
{color:#d04437}Cache 5{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=4880921]]
* IgniteCacheTestSuite5:
IgniteCachePartitionLossPolicySelfTest.testReadWriteSafeWithBackupsWithPersistence[TRANSACTIONAL]
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite5:
IgniteCachePartitionLossPolicySelfTest.testReadWriteSafeAfterKillTwoNodesWithPersistence[TRANSACTIONAL]
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Thin Client: Java{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=4880875]]
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4880968buildTypeId=IgniteTests24Java8_RunAll]
> Rename Affinity Awareness to Partition Awareness
>
>
> Key: IGNITE-12458
> URL: https://issues.apache.org/jira/browse/IGNITE-12458
> Project: Ignite
> Issue Type: Task
> Components: platforms
>Affects Versions: 2.8
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Blocker
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Rename Affinity Awareness to Partition Awareness in all product components.
> Affinity Awareness was not released yet, so there are no breaking changes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12186) TDE - Phase-2. Master key rotation.
[ https://issues.apache.org/jira/browse/IGNITE-12186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003563#comment-17003563 ] Amelchev Nikita commented on IGNITE-12186: -- [~nizhikov], Thank you so much for the review of the changes! TC bot visa is ready. > TDE - Phase-2. Master key rotation. > --- > > Key: IGNITE-12186 > URL: https://issues.apache.org/jira/browse/IGNITE-12186 > Project: Ignite > Issue Type: Sub-task >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Labels: IEP-18 > Fix For: 2.9 > > Time Spent: 19h 20m > Remaining Estimate: 0h > > Need to implement master key rotation process. Master key(MK) rotation > required in case of it compromising or at the end of crypto period(key > validity period). > [Design > (cwiki).|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=95652381] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12470) Pme-free switch feature should be deactivatable
[
https://issues.apache.org/jira/browse/IGNITE-12470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003550#comment-17003550
]
Ignite TC Bot commented on IGNITE-12470:
{panel:title=Branch: [pull/7189/head] Base: [master] : Possible Blockers
(6)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=4880410]]
* IgniteCacheTestSuite2:
GridCachePartitionedEvictionSelfTest.testEvictionTxPessimisticRepeatableRead -
Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}MVCC PDS 4{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=4880456]]
* IgnitePdsMvccTestSuite4:
IgniteRebalanceOnCachesStoppingOrDestroyingTest.testStopCachesOnDeactivationSecondGroup
- Test has low fail rate in base branch 0,0% and is not flaky
* IgnitePdsMvccTestSuite4:
IgniteRebalanceOnCachesStoppingOrDestroyingTest.testDestroySpecificCachesInDifferentCacheGroupsSecondGroup
- Test has low fail rate in base branch 0,0% and is not flaky
* IgnitePdsMvccTestSuite4:
ResetLostPartitionTest.testReactivateGridBeforeResetLostPartitions - Test has
low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Queries 2{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=4880371]]
{color:#d04437}MVCC Cache{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=4880392]]
* IgniteCacheMvccTestSuite:
CacheMvccReplicatedCoordinatorFailoverTest.testAccountsTxGet_Server_Backups0_CoordinatorFails_Persistence
- Test has low fail rate in base branch 0,0% and is not flaky
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4880460buildTypeId=IgniteTests24Java8_RunAll]
> Pme-free switch feature should be deactivatable
> ---
>
> Key: IGNITE-12470
> URL: https://issues.apache.org/jira/browse/IGNITE-12470
> Project: Ignite
> Issue Type: Task
>Reporter: Anton Vinogradov
>Assignee: Sergei Ryzhov
>Priority: Blocker
> Labels: newbie
> Fix For: 2.8, 2.9
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> We should be able to disable this feature by some env/jvm property.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12440) Sensitive data leak in partition release future messages
[ https://issues.apache.org/jira/browse/IGNITE-12440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Rakov updated IGNITE-12440: Release Note: Fixed sensitive user data leak in diagnostic exchange log message (was: Fixed sensitive user data leak to the log) > Sensitive data leak in partition release future messages > > > Key: IGNITE-12440 > URL: https://issues.apache.org/jira/browse/IGNITE-12440 > Project: Ignite > Issue Type: Improvement >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Major > Fix For: 2.9 > > Time Spent: 20m > Remaining Estimate: 0h > > There is sensitive data leak in partition release future messages. > We should hide sensitive data when option > -DIGNITE_TO_STRING_INCLUDE_SENSITIVE=false is used > 2019-10-04 06:51:40.328[WARN > ]exchange-worker-#161%GRID%GridNodeName%[o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture] > Partition release future: PartitionReleaseFuture -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12498) Calcite integration. Create a test suite on TC.
[ https://issues.apache.org/jira/browse/IGNITE-12498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Pavlukhin updated IGNITE-12498: Issue Type: Task (was: Bug) > Calcite integration. Create a test suite on TC. > --- > > Key: IGNITE-12498 > URL: https://issues.apache.org/jira/browse/IGNITE-12498 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Ivan Pavlukhin >Assignee: Ivan Pavlukhin >Priority: Major > > A separate TC build job should be created. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12498) Calcite integration. Create a test suite on TC.
Ivan Pavlukhin created IGNITE-12498: --- Summary: Calcite integration. Create a test suite on TC. Key: IGNITE-12498 URL: https://issues.apache.org/jira/browse/IGNITE-12498 Project: Ignite Issue Type: Bug Components: sql Reporter: Ivan Pavlukhin Assignee: Ivan Pavlukhin A separate TC build job should be created. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12497) PartitionsEvictManager should log all partitions which will be evicted
Kirill Tkalenko created IGNITE-12497: Summary: PartitionsEvictManager should log all partitions which will be evicted Key: IGNITE-12497 URL: https://issues.apache.org/jira/browse/IGNITE-12497 Project: Ignite Issue Type: Improvement Reporter: Kirill Tkalenko Assignee: Kirill Tkalenko Fix For: 2.9 Now we print information about eviction only if it longer then threshold (i.e. progress). And we can't detect in logs, that partition was evicted due to different reasons (rebalance, wrong configuration custom affinity). I think we could print information on info level about each evicted partition before start of eviction. Information about partitions could be aggregated, compacted and printed by timer, but *all evicted partitions must be printed to log anyway.* I would have the following information about each partition: * partitionId * groupId * groupName * reason (eviction, clearing) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12385) .NET Thin Client: introduce ClusterGroup API
[
https://issues.apache.org/jira/browse/IGNITE-12385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003536#comment-17003536
]
Ignite TC Bot commented on IGNITE-12385:
{panel:title=Branch: [pull/7168/head] Base: [master] : Possible Blockers
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 5{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=4877537]]
{color:#d04437}PDS 3{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=4877601]]
* IgnitePdsTestSuite3:
IgnitePdsContinuousRestartTest.testRebalancingDuringLoad_1000_500_1_1 - Test
has low fail rate in base branch 0,0% and is not flaky
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4873652buildTypeId=IgniteTests24Java8_RunAll]
> .NET Thin Client: introduce ClusterGroup API
>
>
> Key: IGNITE-12385
> URL: https://issues.apache.org/jira/browse/IGNITE-12385
> Project: Ignite
> Issue Type: New Feature
> Components: thin client
>Affects Versions: 2.7.6
>Reporter: Alexandr Shapkin
>Assignee: Alexandr Shapkin
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We need to implement IClusterGroup API for thin clients.
> Let's start with following methods:
> * IClusterGroup.ForDotNet()
> * IClusterGroup.ForAttributes()
> * IClusterGroup.GetNodes()
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12248) Apache Calcite based query execution engine
[ https://issues.apache.org/jira/browse/IGNITE-12248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Pavlukhin updated IGNITE-12248: Issue Type: New Feature (was: Task) > Apache Calcite based query execution engine > --- > > Key: IGNITE-12248 > URL: https://issues.apache.org/jira/browse/IGNITE-12248 > Project: Ignite > Issue Type: New Feature > Components: sql >Reporter: Igor Seliverstov >Priority: Major > Time Spent: 2h > Remaining Estimate: 0h > > Currently used H2 based query execution engine has a number of critical > limitations Which do not allow to execute an arbitrary query. > The ticket aims to show potential of a new, Calcite based, execution engine > which may act not worse than current one on co-located queries, provide a > boost for queries, using distributed joins, and provide an ability to execute > arbitrary queries, requiring more than one map-reduce step in execution flow. > [IEP > link|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=130028084] > [Dev list > thread|http://apache-ignite-developers.2346864.n4.nabble.com/New-SQL-execution-engine-td43724.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12496) Index deletion blocks checkpoint for all of its duration, which can cause "Critical system error: system critical thread blocked"
Denis Chudov created IGNITE-12496: - Summary: Index deletion blocks checkpoint for all of its duration, which can cause "Critical system error: system critical thread blocked" Key: IGNITE-12496 URL: https://issues.apache.org/jira/browse/IGNITE-12496 Project: Ignite Issue Type: Bug Reporter: Denis Chudov Assignee: Denis Chudov GridH2Table#removeIndex(Session, Index) acquires checkpoint read lock and releases it only after full completion of deletion process. It happens because H2TreeIndex#destroy requires to be run when checkpoint lock is held. Meanwhile, checkpoint thread stops on Checkpointer#markCheckpointBegin, trying to acquire write lock, and stays locked for all the time of index deletion. The possible fix is that checkpoint read lock is periodically released while index deletion is in progress. To avoid persistence corruption in case of node crush in the middle of the process, we should put index root into some persistent structure like index meta tree and remember it as "pending delete". Then we must delete tree pages from leafs to root, this allows to avoid links to deleted pages. When deletion is complete, tree root can be removed from "pending delete". -- This message was sent by Atlassian Jira (v8.3.4#803005)
