[jira] [Created] (IGNITE-13210) Parameterized tests in ServiceDeploymentProcessIdSelfTest class have different name each time

2020-07-03 Thread Sergey Uttsel (Jira)
Sergey Uttsel created IGNITE-13210: -- Summary: Parameterized tests in ServiceDeploymentProcessIdSelfTest class have different name each time Key: IGNITE-13210 URL:

[jira] [Created] (IGNITE-13211) Improve public exceptions for case when user attempts to access data from a lost partition

2020-07-03 Thread Ivan Rakov (Jira)
Ivan Rakov created IGNITE-13211: --- Summary: Improve public exceptions for case when user attempts to access data from a lost partition Key: IGNITE-13211 URL: https://issues.apache.org/jira/browse/IGNITE-13211

[jira] [Created] (IGNITE-13212) Peer class loading does not work for Scan Query

2020-07-03 Thread Sergey Chugunov (Jira)
Sergey Chugunov created IGNITE-13212: Summary: Peer class loading does not work for Scan Query Key: IGNITE-13212 URL: https://issues.apache.org/jira/browse/IGNITE-13212 Project: Ignite

Re: IGNITE-12362 Migrate MQTT module to ignite-extensions

2020-07-03 Thread Saikat Maitra
Hi I have created PRs for the following jira issue. https://issues.apache.org/jira/browse/IGNITE-12362 IGNITE-12362 Migrate MQTT module to ignite-extensions PRs https://github.com/apache/ignite-extensions https://github.com/apache/ignite/pull/7950 Please review and share your feedback.

Re: Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]

2020-07-03 Thread Alex Plehanov
Anton, thank you. Guys, I've cut the release branch. From now on please pin resolved in the master branch tickets to 2.10 release in Jira and cherry-pick targeted to 2.9 tickets to ignite-2.9 branch. As far as the release branch cut was delayed, I propose to move code freeze dates by one week

Re: Extended logging for rebalance performance analysis

2020-07-03 Thread ткаленко кирилл
Sorry, forget. [1] - org.apache.ignite.internal.processors.cache.CacheGroupsMetricsRebalanceTest#testCacheGroupRebalance 03.07.2020, 17:20, "ткаленко кирилл" : > Hi, Stan! > > I don't understand you yet. > > Now you can use metrics as it was done in the test [1]. Or can you tell me > where to

Re: Extended logging for rebalance performance analysis

2020-07-03 Thread ткаленко кирилл
Hi, Stan! I don't understand you yet. Now you can use metrics as it was done in the test [1]. Or can you tell me where to do this, for example when completing rebalancing for all groups? See what is now available and added in the logs: 1)Which group is rebalanced and which type of rebalance.

Re: Extended logging for rebalance performance analysis

2020-07-03 Thread Stanislav Lukyanov
> On 3 Jul 2020, at 09:51, ткаленко кирилл wrote: > > To calculate the average value, you can use the existing metrics > "RebalancingStartTime", "RebalancingLastCancelledTime", "RebalancingEndTime", > "RebalancingPartitionsLeft", "RebalancingReceivedKeys" and > "RebalancingReceivedBytes".

Re: [DISCUSSION] Add index rebuild time metrics

2020-07-03 Thread ткаленко кирилл
Hi, Stan! Perhaps it is worth clarifying what exactly I wanted to say. Now we have 2 processes: building and rebuilding indexes. At moment, we have some metrics for rebuilding indexes: "IsIndexRebuildInProgress", "IndexBuildCountPartitionsLeft". I suggest adding another metric

Re: Extended logging for rebalance performance analysis

2020-07-03 Thread ткаленко кирилл
LongMetric startTime = mreg.findMetric("RebalancingStartTime"); LongMetric lastCancelledTime = mreg.findMetric("RebalancingLastCancelledTime"); LongMetric endTime = mreg.findMetric("RebalancingEndTime"); LongMetric partitionsLeft = mreg.findMetric();