[jira] [Commented] (IGNITE-13327) Add a metric for processed keys when rebuilding indexes.

2020-08-18 Thread Ivan Rakov (Jira) 


[ 
https://issues.apache.org/jira/browse/IGNITE-13327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17179737#comment-17179737
 ] 

Ivan Rakov commented on IGNITE-13327:
-

[~ktkale...@gridgain.com] Thanks! Merged to master.

> Add a metric for processed keys when rebuilding indexes.
> 
>
> Key: IGNITE-13327
> URL: https://issues.apache.org/jira/browse/IGNITE-13327
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.10
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> It would be useful to understand how long it will take to rebuild indexes, 
> since there can be a lot of data and indexes. Now there are following metrics 
> that allow to estimate approximately how many indexes are left to rebuild:
> # IsIndexRebuildInProgress - rebuilding cache indexes in the process;
> # IndexBuildCountPartitionsLeft - remaining number of partitions (by cache 
> group) to rebuild indexes for.
> For a more accurate estimate, I suggest adding a metric for caches "Number of 
> keys processed when rebuilding indexes" with the name 
> "IndexRebuildKeyProcessed". This way we can estimate for cache how much index 
> rebuilding will take. To do this, we can get "CacheSize" and use new metric 
> to find out how many keys are left to process.
> I also suggest adding methods:
> # org.apache.ignite.cache.CacheMetrics#getIndexRebuildKeyProcessed
> # org.apache.ignite.cache.CacheMetrics#IsIndexRebuildInProgress



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (IGNITE-13327) Add a metric for processed keys when rebuilding indexes.

2020-08-17 Thread Kirill Tkalenko (Jira) 


[ 
https://issues.apache.org/jira/browse/IGNITE-13327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17178849#comment-17178849
 ] 

Kirill Tkalenko commented on IGNITE-13327:
--

[~ivan.glukos] I made changes to PR on your comments, please make a review, I 
think [1] will be sufficient for visa.

[1] - 
https://ci.ignite.apache.org/viewLog.html?buildId=5544749=queuedBuildOverviewTab

> Add a metric for processed keys when rebuilding indexes.
> 
>
> Key: IGNITE-13327
> URL: https://issues.apache.org/jira/browse/IGNITE-13327
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.10
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> It would be useful to understand how long it will take to rebuild indexes, 
> since there can be a lot of data and indexes. Now there are following metrics 
> that allow to estimate approximately how many indexes are left to rebuild:
> # IsIndexRebuildInProgress - rebuilding cache indexes in the process;
> # IndexBuildCountPartitionsLeft - remaining number of partitions (by cache 
> group) to rebuild indexes for.
> For a more accurate estimate, I suggest adding a metric for caches "Number of 
> keys processed when rebuilding indexes" with the name 
> "IndexRebuildKeyProcessed". This way we can estimate for cache how much index 
> rebuilding will take. To do this, we can get "CacheSize" and use new metric 
> to find out how many keys are left to process.
> I also suggest adding methods:
> # org.apache.ignite.cache.CacheMetrics#getIndexRebuildKeyProcessed
> # org.apache.ignite.cache.CacheMetrics#IsIndexRebuildInProgress



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (IGNITE-13327) Add a metric for processed keys when rebuilding indexes.

2020-08-10 Thread Ivan Rakov (Jira) 


[ 
https://issues.apache.org/jira/browse/IGNITE-13327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17174421#comment-17174421
 ] 

Ivan Rakov commented on IGNITE-13327:
-

[~ktkale...@gridgain.com] I've shared my thoughts regarding the suggested 
metric on the dev list.

> Add a metric for processed keys when rebuilding indexes.
> 
>
> Key: IGNITE-13327
> URL: https://issues.apache.org/jira/browse/IGNITE-13327
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.10
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> It would be useful to understand how long it will take to rebuild indexes, 
> since there can be a lot of data and indexes. Now there are following metrics 
> that allow to estimate approximately how many indexes are left to rebuild:
> # IsIndexRebuildInProgress - rebuilding cache indexes in the process;
> # IndexBuildCountPartitionsLeft - remaining number of partitions (by cache 
> group) to rebuild indexes for.
> For a more accurate estimate, I suggest adding a metric for caches "Number of 
> keys processed when rebuilding indexes" with the name 
> "IndexRebuildKeyProcessed". This way we can estimate for cache how much index 
> rebuilding will take. To do this, we can get "CacheSize" and use new metric 
> to find out how many keys are left to process.
> I also suggest adding methods:
> # org.apache.ignite.cache.CacheMetrics#getIndexRebuildKeyProcessed
> # org.apache.ignite.cache.CacheMetrics#IsIndexRebuildInProgress



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (IGNITE-13327) Add a metric for processed keys when rebuilding indexes.

2020-08-07 Thread Kirill Tkalenko (Jira) 


[ 
https://issues.apache.org/jira/browse/IGNITE-13327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17173121#comment-17173121
 ] 

Kirill Tkalenko commented on IGNITE-13327:
--

I checked *TutorialStepByStepExampleSelfTest.testExampletest* on master it also 
fell.
https://ci.ignite.apache.org/viewLog.html?buildId=5526816;

> Add a metric for processed keys when rebuilding indexes.
> 
>
> Key: IGNITE-13327
> URL: https://issues.apache.org/jira/browse/IGNITE-13327
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.10
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> It would be useful to understand how long it will take to rebuild indexes, 
> since there can be a lot of data and indexes. Now there are following metrics 
> that allow to estimate approximately how many indexes are left to rebuild:
> # IsIndexRebuildInProgress - rebuilding cache indexes in the process;
> # IndexBuildCountPartitionsLeft - remaining number of partitions (by cache 
> group) to rebuild indexes for.
> For a more accurate estimate, I suggest adding a metric for caches "Number of 
> keys processed when rebuilding indexes" with the name 
> "IndexRebuildKeyProcessed". This way we can estimate for cache how much index 
> rebuilding will take. To do this, we can get "CacheSize" and use new metric 
> to find out how many keys are left to process.
> I also suggest adding methods:
> # org.apache.ignite.cache.CacheMetrics#getIndexRebuildKeyProcessed
> # org.apache.ignite.cache.CacheMetrics#IsIndexRebuildInProgress



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (IGNITE-13327) Add a metric for processed keys when rebuilding indexes.

2020-08-07 Thread Ignite TC Bot (Jira) 


[ 
https://issues.apache.org/jira/browse/IGNITE-13327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17173118#comment-17173118
 ] 

Ignite TC Bot commented on IGNITE-13327:


{panel:title=Branch: [pull/8126/head] Base: [master] : Possible Blockers 
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Examples{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=5526812]]
* IgniteExamplesSelfTestSuite: TutorialStepByStepExampleSelfTest.testExample - 
Test has low fail rate in base branch 0,0% and is not flaky

{panel}
{panel:title=Branch: [pull/8126/head] Base: [master] : New Tests 
(8)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Service Grid{color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=5525629]]
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=1d378ac3-7651-445d-a76e-48be0636e231, topVer=0, 
msgTemplate=null, span=null, nodeId8=8e09d4dc, msg=, type=NODE_JOINED, 
tstamp=1596744332378], val2=AffinityTopologyVersion 
[topVer=8389012778780031521, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=1d378ac3-7651-445d-a76e-48be0636e231, topVer=0, 
msgTemplate=null, span=null, nodeId8=8e09d4dc, msg=, type=NODE_JOINED, 
tstamp=1596744332378], val2=AffinityTopologyVersion 
[topVer=8389012778780031521, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=f1bca65c371-d457ff8c-2ae1-4a90-a4fa-1665e2ff7b7b, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=2f9d86a9-13c3-4633-8a10-5f8aa827ce8b, topVer=0, msgTemplate=null, 
span=null, nodeId8=2f9d86a9, msg=null, type=DISCOVERY_CUSTOM_EVT, 
tstamp=1596744332378]], val2=AffinityTopologyVersion 
[topVer=-5874992666583183135, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=f1bca65c371-d457ff8c-2ae1-4a90-a4fa-1665e2ff7b7b, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=2f9d86a9-13c3-4633-8a10-5f8aa827ce8b, topVer=0, msgTemplate=null, 
span=null, nodeId8=2f9d86a9, msg=null, type=DISCOVERY_CUSTOM_EVT, 
tstamp=1596744332378]], val2=AffinityTopologyVersion 
[topVer=-5874992666583183135, minorTopVer=0]]] - PASSED{color}

{color:#8b}Service Grid (legacy mode){color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=5525630]]
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=bb086e8c-8cfb-4761-8289-e896eac00884, topVer=0, 
msgTemplate=null, span=null, nodeId8=9f0efa02, msg=, type=NODE_JOINED, 
tstamp=1596744256139], val2=AffinityTopologyVersion 
[topVer=-6607061135612521726, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=bb086e8c-8cfb-4761-8289-e896eac00884, topVer=0, 
msgTemplate=null, span=null, nodeId8=9f0efa02, msg=, type=NODE_JOINED, 
tstamp=1596744256139], val2=AffinityTopologyVersion 
[topVer=-6607061135612521726, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=f8acf55c371-059a8177-ff39-46ed-b0b9-dec57149fabf, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=f07361c6-1fcb-4a67-a005-2d2441c68229, topVer=0, msgTemplate=null, 
span=null, nodeId8=f07361c6, msg=null, type=DISCOVERY_CUSTOM_EVT, 
tstamp=1596744256139]], val2=AffinityTopologyVersion 
[topVer=7320540078826162217, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=f8acf55c371-059a8177-ff39-46ed-b0b9-dec57149fabf, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=f07361c6-1fcb-4a67-a005-2d2441c68229, topVer=0, msgTemplate=null, 
span=null, nodeId8=f07361c6, msg=null, type=DISCOVERY_CUSTOM_EVT, 
tstamp=1596744256139]], val2=AffinityTopologyVersion 
[topVer=7320540078826162217, minorTopVer=0]]] - PASSED{color}

{panel}
[TeamCity *-- Run :: All*