[jira] [Commented] (IGNITE-17002) Indexes rebuild in Maintenance Mode
Title: Message Title Semyon Danilov commented on IGNITE-17002 Re: Indexes rebuild in Maintenance Mode The new command's syntax is as follows: --cache schedule_indexes_rebuild --node-id nodeId --cache-names cacheName[index1,...indexN],cacheName2,cacheName3[index1] --group-names groupName1,groupName2,...groupNameN Schedules rebuild of the indexes for specified caches via the Maintenance Mode. Schedules rebuild of specified caches and cache-groups Parameters: --node-id - (Optional) Specify node for indexes rebuild. If not specified, schedules rebuild on all nodes. --cache-names - Comma-separated list of cache names with optionally specified indexes. If indexes are not specified then all indexes of the cache will be scheduled for the rebuild operation. Can be used simultaneously with cache group names. --group-names - Comma-separated list of cache group names for which indexes should be scheduled for the rebuild. Can be used simultaneously with cache names. Thanks for the review, merged to the master branch Add Comment This message was sent by Atlassian Jira (v8.20.10#820010-sha1:ace47f9)
[jira] [Commented] (IGNITE-17002) Indexes rebuild in Maintenance Mode
Title: Message Title Ignite TC Bot commented on IGNITE-17002 Re: Indexes rebuild in Maintenance Mode Branch: [pull/10042/head] Base: [master] : No blockers found! Branch: [pull/10042/head] Base: [master] : New Tests (13) Control Utility [tests 12 IgniteControlUtilityTestSuite: CommandHandlerParsingTest.testScheduleIndexRebuildArgs - PASSED IgniteControlUtilityTestSuite: CommandHandlerParsingTest.testScheduleIndexRebuildWrongArgs - PASSED IgniteControlUtilityTestSuite: GridCommandHandlerScheduleIndexRebuildTest.testConsecutiveCommandInvocations - PASSED IgniteControlUtilityTestSuite: GridCommandHandlerScheduleIndexRebuildTest.testErrors - PASSED IgniteControlUtilityTestSuite: GridCommandHandlerScheduleIndexRebuildTest.testCorruptedIndexRebuildCacheWithGroup - PASSED IgniteControlUtilityTestSuite: GridCommandHandlerScheduleIndexRebuildTest.testSpecificIndexes - PASSED IgniteControlUtilityTestSuite: GridCommandHandlerScheduleIndexRebuildTest.testCorruptedIndexRebuildCacheOnAllNodes - PASSED IgniteControlUtilityTestSuite: GridCommandHandlerScheduleIndexRebuildTest.testCacheGroupParameter - PASSED IgniteControlUtilityTestSuite: GridCommandHandlerScheduleIndexRebuildTest.testCorruptedIndexRebuildCacheWithGroupOnAllNodes - PASSED IgniteControlUtilityTestSuite: GridCommandHandlerScheduleIndexRebuildTest.testRebuild - PASSED IgniteControlUtilityTestSuite: GridCommandHandlerScheduleIndexRebuildTest.testCacheGroupParameterWithCacheNames - PASSED ... and 1 new tests PDS (Indexing) [tests 1 IgnitePdsWithIndexingTestSuite: MaintenanceRebuildIndexUtilsSelfTest.testConstructFromMap - PASSED TeamCity --> Run :: All Results
[jira] [Commented] (IGNITE-17002) Indexes rebuild in Maintenance Mode
Title: Message Title Roman Puchkovskiy commented on IGNITE-17002 Re: Indexes rebuild in Maintenance Mode The patch looks good, thank you for the contribution! Add Comment This message was sent by Atlassian Jira (v8.20.10#820010-sha1:ace47f9)
[jira] [Commented] (IGNITE-17002) Indexes rebuild in Maintenance Mode
[
https://issues.apache.org/jira/browse/IGNITE-17002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17559079#comment-17559079
]
Ignite TC Bot commented on IGNITE-17002:
{panel:title=Branch: [pull/10042/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10042/head] Base: [master] : New Tests
(13)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Control Utility{color} [[tests
12|https://ci.ignite.apache.org/viewLog.html?buildId=6647402]]
* {color:#013220}IgniteControlUtilityTestSuite:
CommandHandlerParsingTest.testScheduleIndexRebuildArgs - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
CommandHandlerParsingTest.testScheduleIndexRebuildWrongArgs - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerScheduleIndexRebuildTest.testConsecutiveCommandInvocations -
PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerScheduleIndexRebuildTest.testErrors - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerScheduleIndexRebuildTest.testCorruptedIndexRebuildCacheWithGroup
- PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerScheduleIndexRebuildTest.testSpecificIndexes - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerScheduleIndexRebuildTest.testCorruptedIndexRebuildCacheOnAllNodes
- PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerScheduleIndexRebuildTest.testCacheGroupParameter -
PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerScheduleIndexRebuildTest.testCorruptedIndexRebuildCacheWithGroupOnAllNodes
- PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerScheduleIndexRebuildTest.testRebuild - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerScheduleIndexRebuildTest.testCacheGroupParameterWithCacheNames
- PASSED{color}
... and 1 new tests
{color:#8b}PDS (Indexing){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6646137]]
* {color:#013220}IgnitePdsWithIndexingTestSuite:
MaintenanceRebuildIndexUtilsSelfTest.testConstructFromMap - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6645056buildTypeId=IgniteTests24Java8_RunAll]
> Indexes rebuild in Maintenance Mode
> ---
>
> Key: IGNITE-17002
> URL: https://issues.apache.org/jira/browse/IGNITE-17002
> Project: Ignite
> Issue Type: Improvement
> Components: control.sh, persistence
>Reporter: Sergey Chugunov
>Assignee: Semyon Danilov
>Priority: Major
> Fix For: 2.14
>
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> Now Ignite supports entering Maintenance Mode after index corruption
> automatically - this was implemented in linked issue.
> But there are use-cases when user needs to request rebuilding specific
> indexes in MM, so we need to provide a control.sh API to make these requests.
> Also for better integration with monitoring tools it is nice to provide an
> API to check status of rebuilding task and print message to logs when each
> task is finished and all tasks are finished.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (IGNITE-17002) Indexes rebuild in Maintenance Mode
[
https://issues.apache.org/jira/browse/IGNITE-17002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17545548#comment-17545548
]
Ignite TC Bot commented on IGNITE-17002:
{panel:title=Branch: [pull/10042/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10042/head] Base: [master] : New Tests
(10)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}PDS (Indexing){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6599337]]
* {color:#013220}IgnitePdsWithIndexingTestSuite:
MaintenanceRebuildIndexUtilsSelfTest.testConstructFromMap - PASSED{color}
{color:#8b}Control Utility{color} [[tests
9|https://ci.ignite.apache.org/viewLog.html?buildId=6603939]]
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerIndexRebuildTest.testSpecificIndexes - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerIndexRebuildTest.testCorruptedIndexRebuildCacheWithGroupOnAllNodes
- PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerIndexRebuildTest.testErrors - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerIndexRebuildTest.testConsecutiveCommandInvocations -
PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerIndexRebuildTest.testCorruptedIndexRebuildCacheWithGroup -
PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerIndexRebuildTest.testCorruptedIndexRebuildCache -
PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerIndexRebuildTest.testCorruptedIndexRebuildCacheOnAllNodes -
PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerIndexRebuildTest.testRebuild - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
CommandHandlerParsingTest.testIndexRebuildWrongArgs - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6599380buildTypeId=IgniteTests24Java8_RunAll]
> Indexes rebuild in Maintenance Mode
> ---
>
> Key: IGNITE-17002
> URL: https://issues.apache.org/jira/browse/IGNITE-17002
> Project: Ignite
> Issue Type: Improvement
> Components: control.sh, persistence
>Reporter: Sergey Chugunov
>Assignee: Semyon Danilov
>Priority: Major
> Fix For: 2.14
>
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> Now Ignite supports entering Maintenance Mode after index corruption
> automatically - this was implemented in linked issue.
> But there are use-cases when user needs to request rebuilding specific
> indexes in MM, so we need to provide a control.sh API to make these requests.
> Also for better integration with monitoring tools it is nice to provide an
> API to check status of rebuilding task and print message to logs when each
> task is finished and all tasks are finished.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (IGNITE-17002) Indexes rebuild in Maintenance Mode
[
https://issues.apache.org/jira/browse/IGNITE-17002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17544191#comment-17544191
]
Ignite TC Bot commented on IGNITE-17002:
{panel:title=Branch: [pull/10042/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10042/head] Base: [master] : New Tests
(9)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}PDS (Indexing){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6591334]]
* {color:#013220}IgnitePdsWithIndexingTestSuite:
MaintenanceRebuildIndexUtilsSelfTest.testConstructFromMap - PASSED{color}
{color:#8b}Control Utility{color} [[tests
8|https://ci.ignite.apache.org/viewLog.html?buildId=6591342]]
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerIndexRebuildTest.testCorruptedIndexRebuildCacheWithGroupOnAllNodes
- PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerIndexRebuildTest.testErrors - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerIndexRebuildTest.testConsecutiveCommandInvocations -
PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerIndexRebuildTest.testCorruptedIndexRebuildCacheWithGroup -
PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerIndexRebuildTest.testCorruptedIndexRebuildCache -
PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerIndexRebuildTest.testCorruptedIndexRebuildCacheOnAllNodes -
PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerIndexRebuildTest.testRebuild - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
CommandHandlerParsingTest.testIndexRebuildWrongArgs - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6598030buildTypeId=IgniteTests24Java8_RunAll]
> Indexes rebuild in Maintenance Mode
> ---
>
> Key: IGNITE-17002
> URL: https://issues.apache.org/jira/browse/IGNITE-17002
> Project: Ignite
> Issue Type: Improvement
> Components: control.sh, persistence
>Reporter: Sergey Chugunov
>Assignee: Semyon Danilov
>Priority: Major
> Fix For: 2.14
>
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> Now Ignite supports entering Maintenance Mode after index corruption
> automatically - this was implemented in linked issue.
> But there are use-cases when user needs to request rebuilding specific
> indexes in MM, so we need to provide a control.sh API to make these requests.
> Also for better integration with monitoring tools it is nice to provide an
> API to check status of rebuilding task and print message to logs when each
> task is finished and all tasks are finished.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (IGNITE-17002) Indexes rebuild in Maintenance Mode
[
https://issues.apache.org/jira/browse/IGNITE-17002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17544190#comment-17544190
]
Ignite TC Bot commented on IGNITE-17002:
{panel:title=Branch: [pull/10042/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10042/head] Base: [master] : New Tests
(9)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}PDS (Indexing){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6591334]]
* {color:#013220}IgnitePdsWithIndexingTestSuite:
MaintenanceRebuildIndexUtilsSelfTest.testConstructFromMap - PASSED{color}
{color:#8b}Control Utility{color} [[tests
8|https://ci.ignite.apache.org/viewLog.html?buildId=6591342]]
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerIndexRebuildTest.testCorruptedIndexRebuildCacheWithGroupOnAllNodes
- PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerIndexRebuildTest.testErrors - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerIndexRebuildTest.testConsecutiveCommandInvocations -
PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerIndexRebuildTest.testCorruptedIndexRebuildCacheWithGroup -
PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerIndexRebuildTest.testCorruptedIndexRebuildCache -
PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerIndexRebuildTest.testCorruptedIndexRebuildCacheOnAllNodes -
PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerIndexRebuildTest.testRebuild - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
CommandHandlerParsingTest.testIndexRebuildWrongArgs - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6598030buildTypeId=IgniteTests24Java8_RunAll]
> Indexes rebuild in Maintenance Mode
> ---
>
> Key: IGNITE-17002
> URL: https://issues.apache.org/jira/browse/IGNITE-17002
> Project: Ignite
> Issue Type: Improvement
> Components: control.sh, persistence
>Reporter: Sergey Chugunov
>Assignee: Semyon Danilov
>Priority: Major
> Fix For: 2.14
>
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> Now Ignite supports entering Maintenance Mode after index corruption
> automatically - this was implemented in linked issue.
> But there are use-cases when user needs to request rebuilding specific
> indexes in MM, so we need to provide a control.sh API to make these requests.
> Also for better integration with monitoring tools it is nice to provide an
> API to check status of rebuilding task and print message to logs when each
> task is finished and all tasks are finished.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (IGNITE-17002) Indexes rebuild in Maintenance Mode
[
https://issues.apache.org/jira/browse/IGNITE-17002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17542909#comment-17542909
]
Ignite TC Bot commented on IGNITE-17002:
{panel:title=Branch: [pull/10042/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10042/head] Base: [master] : New Tests
(9)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}PDS (Indexing){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6591334]]
* {color:#013220}IgnitePdsWithIndexingTestSuite:
MaintenanceRebuildIndexUtilsSelfTest.testConstructFromMap - PASSED{color}
{color:#8b}Control Utility{color} [[tests
8|https://ci.ignite.apache.org/viewLog.html?buildId=6591342]]
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerIndexRebuildTest.testCorruptedIndexRebuildCacheWithGroupOnAllNodes
- PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerIndexRebuildTest.testErrors - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerIndexRebuildTest.testConsecutiveCommandInvocations -
PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerIndexRebuildTest.testCorruptedIndexRebuildCacheWithGroup -
PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerIndexRebuildTest.testCorruptedIndexRebuildCache -
PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerIndexRebuildTest.testCorruptedIndexRebuildCacheOnAllNodes -
PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerIndexRebuildTest.testRebuild - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
CommandHandlerParsingTest.testIndexRebuildWrongArgs - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6590633buildTypeId=IgniteTests24Java8_RunAll]
> Indexes rebuild in Maintenance Mode
> ---
>
> Key: IGNITE-17002
> URL: https://issues.apache.org/jira/browse/IGNITE-17002
> Project: Ignite
> Issue Type: Improvement
> Components: control.sh, persistence
>Reporter: Sergey Chugunov
>Assignee: Semyon Danilov
>Priority: Major
> Fix For: 2.14
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Now Ignite supports entering Maintenance Mode after index corruption
> automatically - this was implemented in linked issue.
> But there are use-cases when user needs to request rebuilding specific
> indexes in MM, so we need to provide a control.sh API to make these requests.
> Also for better integration with monitoring tools it is nice to provide an
> API to check status of rebuilding task and print message to logs when each
> task is finished and all tasks are finished.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
