Ignite Enhancement Proposal #6 (Metrics)

[Anton Vinogradov-2]

Igniters,

As you may know Ignite have a lot of JMX based metric, but to perform more
effective grid monitoring some new JMX metrics needs to be implemented.

Here's the accumulated list of metrics I'd like to see at nearest Ignite
version:
Topology
- Current topology version
- Total server nodes count
- Total client nodes count
- Method to count nodes filtered by some node attribute
- Method to count nodes grouped by some node attribute

Communication SPI
- Received messages count grouped by message type
- Received messages count grouped by sender node
- Sent messages count grouped by message type
- Sent messages count grouped by receiver node

Partitions allocation (for cache groups)
- Total primary partitions count located on the current node
- Total backup partitions count located on the current node
- Min/max partition backups left in the cluster for cache group
- Maybe some methods to show partitions map/partition distribution
statistics in the cluster

Jobs execution
- Total jobs execution time (now job execution statistics gathered since
node started and can't be used to calculate average execution time between
probes, implementation of this metric can solve this problem)

Cache
- Topology validation status for cache

IEP-6 [1] was prepared and ready to be discussed.

Please, feel free to suggect or decline some metric.

Anton.

[1]
https://cwiki.apache.org/confluence/display/IGNITE/IEP-6%3A+Metrics+improvements

[dsetrakyan]

Thanks, Anton! All makes sense. I was actually under impression that Ignite
already provides some of these metrics.

Can you please create relevant tickets and add them to the IEP page?
Perhaps someone in the community could pick these up. This would be a very
nice way to get started with the project.

D.

On Mon, Nov 13, 2017 at 9:14 AM, Anton Vinogradov <[hidden email]> wrote:

> Igniters,
>
> As you may know Ignite have a lot of JMX based metric, but to perform more
> effective grid monitoring some new JMX metrics needs to be implemented.
>
> Here's the accumulated list of metrics I'd like to see at nearest Ignite
> version:
> Topology
> - Current topology version
> - Total server nodes count
> - Total client nodes count
> - Method to count nodes filtered by some node attribute
> - Method to count nodes grouped by some node attribute
>
> Communication SPI
> - Received messages count grouped by message type
> - Received messages count grouped by sender node
> - Sent messages count grouped by message type
> - Sent messages count grouped by receiver node
>
> Partitions allocation (for cache groups)
> - Total primary partitions count located on the current node
> - Total backup partitions count located on the current node
> - Min/max partition backups left in the cluster for cache group
> - Maybe some methods to show partitions map/partition distribution
> statistics in the cluster
>
> Jobs execution
> - Total jobs execution time (now job execution statistics gathered since
> node started and can't be used to calculate average execution time between
> probes, implementation of this metric can solve this problem)
>
> Cache
> - Topology validation status for cache
>
> IEP-6 [1] was prepared and ready to be discussed.
>
> Please, feel free to suggect or decline some metric.
>
> Anton.
>
> [1]
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-
> 6%3A+Metrics+improvements
>

[dmagda]

Hi Anton,

Thanks for brining this out!

The memory metrics really need a serious overhaul. For instance we a missing basic things like:
- Bytes used per data region.
- Bytes used per cache.
- Size of checkpointing buffer.

Plus advanced memory metrics will not be harmful:
- Space occupied by indexes.

The ticket for the memory metrics improved is anxiously waiting to be solved: https://issues.apache.org/jira/browse/IGNITE-5796 <https://issues.apache.org/jira/browse/IGNITE-5796>

—
Denis

> On Nov 13, 2017, at 9:14 AM, Anton Vinogradov <[hidden email]> wrote:
>
> Igniters,
>
> As you may know Ignite have a lot of JMX based metric, but to perform more
> effective grid monitoring some new JMX metrics needs to be implemented.
>
> Here's the accumulated list of metrics I'd like to see at nearest Ignite
> version:
> Topology
> - Current topology version
> - Total server nodes count
> - Total client nodes count
> - Method to count nodes filtered by some node attribute
> - Method to count nodes grouped by some node attribute
>
> Communication SPI
> - Received messages count grouped by message type
> - Received messages count grouped by sender node
> - Sent messages count grouped by message type
> - Sent messages count grouped by receiver node
>
> Partitions allocation (for cache groups)
> - Total primary partitions count located on the current node
> - Total backup partitions count located on the current node
> - Min/max partition backups left in the cluster for cache group
> - Maybe some methods to show partitions map/partition distribution
> statistics in the cluster
>
> Jobs execution
> - Total jobs execution time (now job execution statistics gathered since
> node started and can't be used to calculate average execution time between
> probes, implementation of this metric can solve this problem)
>
> Cache
> - Topology validation status for cache
>
> IEP-6 [1] was prepared and ready to be discussed.
>
> Please, feel free to suggect or decline some metric.
>
> Anton.
>
> [1]
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-6%3A+Metrics+improvements

[Valentin Kulichenko]

One of the users also brought up the issue that we don't have any metrics
for entry processors [1]. Probably, makes sense to include this into IEP as
well.

-Val

On Mon, Nov 13, 2017 at 4:48 PM, Denis Magda <[hidden email]> wrote:

> Hi Anton,
>
> Thanks for brining this out!
>
> The memory metrics really need a serious overhaul. For instance we a
> missing basic things like:
> - Bytes used per data region.
> - Bytes used per cache.
> - Size of checkpointing buffer.
>
> Plus advanced memory metrics will not be harmful:
> - Space occupied by indexes.
>
> The ticket for the memory metrics improved is anxiously waiting to be
> solved: https://issues.apache.org/jira/browse/IGNITE-5796 <
> https://issues.apache.org/jira/browse/IGNITE-5796>
>
> —
> Denis
> > On Nov 13, 2017, at 9:14 AM, Anton Vinogradov <[hidden email]> wrote:
> >
> > Igniters,
> >
> > As you may know Ignite have a lot of JMX based metric, but to perform
> more
> > effective grid monitoring some new JMX metrics needs to be implemented.
> >
> > Here's the accumulated list of metrics I'd like to see at nearest Ignite
> > version:
> > Topology
> > - Current topology version
> > - Total server nodes count
> > - Total client nodes count
> > - Method to count nodes filtered by some node attribute
> > - Method to count nodes grouped by some node attribute
> >
> > Communication SPI
> > - Received messages count grouped by message type
> > - Received messages count grouped by sender node
> > - Sent messages count grouped by message type
> > - Sent messages count grouped by receiver node
> >
> > Partitions allocation (for cache groups)
> > - Total primary partitions count located on the current node
> > - Total backup partitions count located on the current node
> > - Min/max partition backups left in the cluster for cache group
> > - Maybe some methods to show partitions map/partition distribution
> > statistics in the cluster
> >
> > Jobs execution
> > - Total jobs execution time (now job execution statistics gathered since
> > node started and can't be used to calculate average execution time
> between
> > probes, implementation of this metric can solve this problem)
> >
> > Cache
> > - Topology validation status for cache
> >
> > IEP-6 [1] was prepared and ready to be discussed.
> >
> > Please, feel free to suggect or decline some metric.
> >
> > Anton.
> >
> > [1]
> > https://cwiki.apache.org/confluence/display/IGNITE/IEP-
> 6%3A+Metrics+improvements
>
>

[Valentin Kulichenko]

Here is the link:

[1] https://issues.apache.org/jira/browse/IGNITE-6846

-Val

On Mon, Nov 13, 2017 at 4:53 PM, Valentin Kulichenko <
[hidden email]> wrote:

> One of the users also brought up the issue that we don't have any metrics
> for entry processors [1]. Probably, makes sense to include this into IEP as
> well.
>
> -Val
>
> On Mon, Nov 13, 2017 at 4:48 PM, Denis Magda <[hidden email]> wrote:
>
>> Hi Anton,
>>
>> Thanks for brining this out!
>>
>> The memory metrics really need a serious overhaul. For instance we a
>> missing basic things like:
>> - Bytes used per data region.
>> - Bytes used per cache.
>> - Size of checkpointing buffer.
>>
>> Plus advanced memory metrics will not be harmful:
>> - Space occupied by indexes.
>>
>> The ticket for the memory metrics improved is anxiously waiting to be
>> solved: https://issues.apache.org/jira/browse/IGNITE-5796 <
>> https://issues.apache.org/jira/browse/IGNITE-5796>
>>
>> —
>> Denis
>> > On Nov 13, 2017, at 9:14 AM, Anton Vinogradov <[hidden email]> wrote:
>> >
>> > Igniters,
>> >
>> > As you may know Ignite have a lot of JMX based metric, but to perform
>> more
>> > effective grid monitoring some new JMX metrics needs to be implemented.
>> >
>> > Here's the accumulated list of metrics I'd like to see at nearest Ignite
>> > version:
>> > Topology
>> > - Current topology version
>> > - Total server nodes count
>> > - Total client nodes count
>> > - Method to count nodes filtered by some node attribute
>> > - Method to count nodes grouped by some node attribute
>> >
>> > Communication SPI
>> > - Received messages count grouped by message type
>> > - Received messages count grouped by sender node
>> > - Sent messages count grouped by message type
>> > - Sent messages count grouped by receiver node
>> >
>> > Partitions allocation (for cache groups)
>> > - Total primary partitions count located on the current node
>> > - Total backup partitions count located on the current node
>> > - Min/max partition backups left in the cluster for cache group
>> > - Maybe some methods to show partitions map/partition distribution
>> > statistics in the cluster
>> >
>> > Jobs execution
>> > - Total jobs execution time (now job execution statistics gathered since
>> > node started and can't be used to calculate average execution time
>> between
>> > probes, implementation of this metric can solve this problem)
>> >
>> > Cache
>> > - Topology validation status for cache
>> >
>> > IEP-6 [1] was prepared and ready to be discussed.
>> >
>> > Please, feel free to suggect or decline some metric.
>> >
>> > Anton.
>> >
>> > [1]
>> > https://cwiki.apache.org/confluence/display/IGNITE/IEP-6%3A+
>> Metrics+improvements
>>
>>
>

[Anton Vinogradov]

Val, Denis,

I've updated issues list, thanks for tips.

On Tue, Nov 14, 2017 at 3:57 AM, Valentin Kulichenko <
[hidden email]> wrote:

> Here is the link:
>
> [1] https://issues.apache.org/jira/browse/IGNITE-6846
>
> -Val
>
> On Mon, Nov 13, 2017 at 4:53 PM, Valentin Kulichenko <
> [hidden email]> wrote:
>
> > One of the users also brought up the issue that we don't have any metrics
> > for entry processors [1]. Probably, makes sense to include this into IEP
> as
> > well.
> >
> > -Val
> >
> > On Mon, Nov 13, 2017 at 4:48 PM, Denis Magda <[hidden email]> wrote:
> >
> >> Hi Anton,
> >>
> >> Thanks for brining this out!
> >>
> >> The memory metrics really need a serious overhaul. For instance we a
> >> missing basic things like:
> >> - Bytes used per data region.
> >> - Bytes used per cache.
> >> - Size of checkpointing buffer.
> >>
> >> Plus advanced memory metrics will not be harmful:
> >> - Space occupied by indexes.
> >>
> >> The ticket for the memory metrics improved is anxiously waiting to be
> >> solved: https://issues.apache.org/jira/browse/IGNITE-5796 <
> >> https://issues.apache.org/jira/browse/IGNITE-5796>
> >>
> >> —
> >> Denis
> >> > On Nov 13, 2017, at 9:14 AM, Anton Vinogradov <[hidden email]> wrote:
> >> >
> >> > Igniters,
> >> >
> >> > As you may know Ignite have a lot of JMX based metric, but to perform
> >> more
> >> > effective grid monitoring some new JMX metrics needs to be
> implemented.
> >> >
> >> > Here's the accumulated list of metrics I'd like to see at nearest
> Ignite
> >> > version:
> >> > Topology
> >> > - Current topology version
> >> > - Total server nodes count
> >> > - Total client nodes count
> >> > - Method to count nodes filtered by some node attribute
> >> > - Method to count nodes grouped by some node attribute
> >> >
> >> > Communication SPI
> >> > - Received messages count grouped by message type
> >> > - Received messages count grouped by sender node
> >> > - Sent messages count grouped by message type
> >> > - Sent messages count grouped by receiver node
> >> >
> >> > Partitions allocation (for cache groups)
> >> > - Total primary partitions count located on the current node
> >> > - Total backup partitions count located on the current node
> >> > - Min/max partition backups left in the cluster for cache group
> >> > - Maybe some methods to show partitions map/partition distribution
> >> > statistics in the cluster
> >> >
> >> > Jobs execution
> >> > - Total jobs execution time (now job execution statistics gathered
> since
> >> > node started and can't be used to calculate average execution time
> >> between
> >> > probes, implementation of this metric can solve this problem)
> >> >
> >> > Cache
> >> > - Topology validation status for cache
> >> >
> >> > IEP-6 [1] was prepared and ready to be discussed.
> >> >
> >> > Please, feel free to suggect or decline some metric.
> >> >
> >> > Anton.
> >> >
> >> > [1]
> >> > https://cwiki.apache.org/confluence/display/IGNITE/IEP-6%3A+
> >> Metrics+improvements
> >>
> >>
> >
>

[dsetrakyan]

Anton, for the IEP to be complete, you should add a list of Jira tickets to
the IEP page. Otherwise, it is unclear how to get started on it.

Thanks,
D.

On Tue, Nov 14, 2017 at 3:44 AM, Anton Vinogradov <[hidden email]>
wrote:

> Val, Denis,
>
> I've updated issues list, thanks for tips.
>
> On Tue, Nov 14, 2017 at 3:57 AM, Valentin Kulichenko <
> [hidden email]> wrote:
>
> > Here is the link:
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-6846
> >
> > -Val
> >
> > On Mon, Nov 13, 2017 at 4:53 PM, Valentin Kulichenko <
> > [hidden email]> wrote:
> >
> > > One of the users also brought up the issue that we don't have any
> metrics
> > > for entry processors [1]. Probably, makes sense to include this into
> IEP
> > as
> > > well.
> > >
> > > -Val
> > >
> > > On Mon, Nov 13, 2017 at 4:48 PM, Denis Magda <[hidden email]>
> wrote:
> > >
> > >> Hi Anton,
> > >>
> > >> Thanks for brining this out!
> > >>
> > >> The memory metrics really need a serious overhaul. For instance we a
> > >> missing basic things like:
> > >> - Bytes used per data region.
> > >> - Bytes used per cache.
> > >> - Size of checkpointing buffer.
> > >>
> > >> Plus advanced memory metrics will not be harmful:
> > >> - Space occupied by indexes.
> > >>
> > >> The ticket for the memory metrics improved is anxiously waiting to be
> > >> solved: https://issues.apache.org/jira/browse/IGNITE-5796 <
> > >> https://issues.apache.org/jira/browse/IGNITE-5796>
> > >>
> > >> —
> > >> Denis
> > >> > On Nov 13, 2017, at 9:14 AM, Anton Vinogradov <[hidden email]>
> wrote:
> > >> >
> > >> > Igniters,
> > >> >
> > >> > As you may know Ignite have a lot of JMX based metric, but to
> perform
> > >> more
> > >> > effective grid monitoring some new JMX metrics needs to be
> > implemented.
> > >> >
> > >> > Here's the accumulated list of metrics I'd like to see at nearest
> > Ignite
> > >> > version:
> > >> > Topology
> > >> > - Current topology version
> > >> > - Total server nodes count
> > >> > - Total client nodes count
> > >> > - Method to count nodes filtered by some node attribute
> > >> > - Method to count nodes grouped by some node attribute
> > >> >
> > >> > Communication SPI
> > >> > - Received messages count grouped by message type
> > >> > - Received messages count grouped by sender node
> > >> > - Sent messages count grouped by message type
> > >> > - Sent messages count grouped by receiver node
> > >> >
> > >> > Partitions allocation (for cache groups)
> > >> > - Total primary partitions count located on the current node
> > >> > - Total backup partitions count located on the current node
> > >> > - Min/max partition backups left in the cluster for cache group
> > >> > - Maybe some methods to show partitions map/partition distribution
> > >> > statistics in the cluster
> > >> >
> > >> > Jobs execution
> > >> > - Total jobs execution time (now job execution statistics gathered
> > since
> > >> > node started and can't be used to calculate average execution time
> > >> between
> > >> > probes, implementation of this metric can solve this problem)
> > >> >
> > >> > Cache
> > >> > - Topology validation status for cache
> > >> >
> > >> > IEP-6 [1] was prepared and ready to be discussed.
> > >> >
> > >> > Please, feel free to suggect or decline some metric.
> > >> >
> > >> > Anton.
> > >> >
> > >> > [1]
> > >> > https://cwiki.apache.org/confluence/display/IGNITE/IEP-6%3A+
> > >> Metrics+improvements
> > >>
> > >>
> > >
> >
>

[Anton Vinogradov]

Dmitriy,

It looks like a confluence bug.
Please login and push refresh button at issues list.

Вт, 14 нояб. 2017 г. в 20:51, Dmitriy Setrakyan <[hidden email]>:

> Anton, for the IEP to be complete, you should add a list of Jira tickets to
> the IEP page. Otherwise, it is unclear how to get started on it.
>
> Thanks,
> D.
>
> On Tue, Nov 14, 2017 at 3:44 AM, Anton Vinogradov <
> [hidden email]>
> wrote:
>
> > Val, Denis,
> >
> > I've updated issues list, thanks for tips.
> >
> > On Tue, Nov 14, 2017 at 3:57 AM, Valentin Kulichenko <
> > [hidden email]> wrote:
> >
> > > Here is the link:
> > >
> > > [1] https://issues.apache.org/jira/browse/IGNITE-6846
> > >
> > > -Val
> > >
> > > On Mon, Nov 13, 2017 at 4:53 PM, Valentin Kulichenko <
> > > [hidden email]> wrote:
> > >
> > > > One of the users also brought up the issue that we don't have any
> > metrics
> > > > for entry processors [1]. Probably, makes sense to include this into
> > IEP
> > > as
> > > > well.
> > > >
> > > > -Val
> > > >
> > > > On Mon, Nov 13, 2017 at 4:48 PM, Denis Magda <[hidden email]>
> > wrote:
> > > >
> > > >> Hi Anton,
> > > >>
> > > >> Thanks for brining this out!
> > > >>
> > > >> The memory metrics really need a serious overhaul. For instance we a
> > > >> missing basic things like:
> > > >> - Bytes used per data region.
> > > >> - Bytes used per cache.
> > > >> - Size of checkpointing buffer.
> > > >>
> > > >> Plus advanced memory metrics will not be harmful:
> > > >> - Space occupied by indexes.
> > > >>
> > > >> The ticket for the memory metrics improved is anxiously waiting to
> be
> > > >> solved: https://issues.apache.org/jira/browse/IGNITE-5796 <
> > > >> https://issues.apache.org/jira/browse/IGNITE-5796>
> > > >>
> > > >> —
> > > >> Denis
> > > >> > On Nov 13, 2017, at 9:14 AM, Anton Vinogradov <[hidden email]>
> > wrote:
> > > >> >
> > > >> > Igniters,
> > > >> >
> > > >> > As you may know Ignite have a lot of JMX based metric, but to
> > perform
> > > >> more
> > > >> > effective grid monitoring some new JMX metrics needs to be
> > > implemented.
> > > >> >
> > > >> > Here's the accumulated list of metrics I'd like to see at nearest
> > > Ignite
> > > >> > version:
> > > >> > Topology
> > > >> > - Current topology version
> > > >> > - Total server nodes count
> > > >> > - Total client nodes count
> > > >> > - Method to count nodes filtered by some node attribute
> > > >> > - Method to count nodes grouped by some node attribute
> > > >> >
> > > >> > Communication SPI
> > > >> > - Received messages count grouped by message type
> > > >> > - Received messages count grouped by sender node
> > > >> > - Sent messages count grouped by message type
> > > >> > - Sent messages count grouped by receiver node
> > > >> >
> > > >> > Partitions allocation (for cache groups)
> > > >> > - Total primary partitions count located on the current node
> > > >> > - Total backup partitions count located on the current node
> > > >> > - Min/max partition backups left in the cluster for cache group
> > > >> > - Maybe some methods to show partitions map/partition distribution
> > > >> > statistics in the cluster
> > > >> >
> > > >> > Jobs execution
> > > >> > - Total jobs execution time (now job execution statistics gathered
> > > since
> > > >> > node started and can't be used to calculate average execution time
> > > >> between
> > > >> > probes, implementation of this metric can solve this problem)
> > > >> >
> > > >> > Cache
> > > >> > - Topology validation status for cache
> > > >> >
> > > >> > IEP-6 [1] was prepared and ready to be discussed.
> > > >> >
> > > >> > Please, feel free to suggect or decline some metric.
> > > >> >
> > > >> > Anton.
> > > >> >
> > > >> > [1]
> > > >> > https://cwiki.apache.org/confluence/display/IGNITE/IEP-6%3A+
> > > >> Metrics+improvements
> > > >>
> > > >>
> > > >
> > >
> >
>

[dsetrakyan]

On Tue, Nov 14, 2017 at 10:12 AM, Anton Vinogradov <[hidden email]
> wrote:

> Dmitriy,
>
> It looks like a confluence bug.
> Please login and push refresh button at issues list.
>

Works now. It is unfortunate that it does not work for the community
members who do not login. Perhaps we can provide a link to the Jira filter,
so folks could click on it and view the tickets.

[dmagda]

Anton,

I do not see a section for the proposed memory metrics and this ticket [1] among the tasks. Did you forget to consider them?

[1] https://issues.apache.org/jira/browse/IGNITE-5796 <https://issues.apache.org/jira/browse/IGNITE-5796>

—
Denis

> On Nov 14, 2017, at 3:44 AM, Anton Vinogradov <[hidden email]> wrote:
>
> Val, Denis,
>
> I've updated issues list, thanks for tips.
>
> On Tue, Nov 14, 2017 at 3:57 AM, Valentin Kulichenko <
> [hidden email]> wrote:
>
>> Here is the link:
>>
>> [1] https://issues.apache.org/jira/browse/IGNITE-6846
>>
>> -Val
>>
>> On Mon, Nov 13, 2017 at 4:53 PM, Valentin Kulichenko <
>> [hidden email]> wrote:
>>
>>> One of the users also brought up the issue that we don't have any metrics
>>> for entry processors [1]. Probably, makes sense to include this into IEP
>> as
>>> well.
>>>
>>> -Val
>>>
>>> On Mon, Nov 13, 2017 at 4:48 PM, Denis Magda <[hidden email]> wrote:
>>>
>>>> Hi Anton,
>>>>
>>>> Thanks for brining this out!
>>>>
>>>> The memory metrics really need a serious overhaul. For instance we a
>>>> missing basic things like:
>>>> - Bytes used per data region.
>>>> - Bytes used per cache.
>>>> - Size of checkpointing buffer.
>>>>
>>>> Plus advanced memory metrics will not be harmful:
>>>> - Space occupied by indexes.
>>>>
>>>> The ticket for the memory metrics improved is anxiously waiting to be
>>>> solved: https://issues.apache.org/jira/browse/IGNITE-5796 <
>>>> https://issues.apache.org/jira/browse/IGNITE-5796>
>>>>
>>>> —
>>>> Denis
>>>>> On Nov 13, 2017, at 9:14 AM, Anton Vinogradov <[hidden email]> wrote:
>>>>>
>>>>> Igniters,
>>>>>
>>>>> As you may know Ignite have a lot of JMX based metric, but to perform
>>>> more
>>>>> effective grid monitoring some new JMX metrics needs to be
>> implemented.
>>>>>
>>>>> Here's the accumulated list of metrics I'd like to see at nearest
>> Ignite
>>>>> version:
>>>>> Topology
>>>>> - Current topology version
>>>>> - Total server nodes count
>>>>> - Total client nodes count
>>>>> - Method to count nodes filtered by some node attribute
>>>>> - Method to count nodes grouped by some node attribute
>>>>>
>>>>> Communication SPI
>>>>> - Received messages count grouped by message type
>>>>> - Received messages count grouped by sender node
>>>>> - Sent messages count grouped by message type
>>>>> - Sent messages count grouped by receiver node
>>>>>
>>>>> Partitions allocation (for cache groups)
>>>>> - Total primary partitions count located on the current node
>>>>> - Total backup partitions count located on the current node
>>>>> - Min/max partition backups left in the cluster for cache group
>>>>> - Maybe some methods to show partitions map/partition distribution
>>>>> statistics in the cluster
>>>>>
>>>>> Jobs execution
>>>>> - Total jobs execution time (now job execution statistics gathered
>> since
>>>>> node started and can't be used to calculate average execution time
>>>> between
>>>>> probes, implementation of this metric can solve this problem)
>>>>>
>>>>> Cache
>>>>> - Topology validation status for cache
>>>>>
>>>>> IEP-6 [1] was prepared and ready to be discussed.
>>>>>
>>>>> Please, feel free to suggect or decline some metric.
>>>>>
>>>>> Anton.
>>>>>
>>>>> [1]
>>>>> https://cwiki.apache.org/confluence/display/IGNITE/IEP-6%3A+
>>>> Metrics+improvements
>>>>
>>>>
>>>
>>

[Vladimir Ozerov]

Dima,

This appears to be a INFRA's bug. I filed a ticket [1].

[1] https://issues.apache.org/jira/browse/INFRA-15487

On Tue, Nov 14, 2017 at 9:25 PM, Dmitriy Setrakyan <[hidden email]>
wrote:

> On Tue, Nov 14, 2017 at 10:12 AM, Anton Vinogradov <
> [hidden email]
> > wrote:
>
> > Dmitriy,
> >
> > It looks like a confluence bug.
> > Please login and push refresh button at issues list.
> >
>
> Works now. It is unfortunate that it does not work for the community
> members who do not login. Perhaps we can provide a link to the Jira filter,
> so folks could click on it and view the tickets.
>

[Anton Vinogradov]

Denis,

It looks like [1] is a duplicate of [2] and [3]

[1] https://issues.apache.org/jira/browse/IGNITE-5796
[2] https://issues.apache.org/jira/browse/IGNITE-6903
[3] https://issues.apache.org/jira/browse/IGNITE-6902

Please close issue as duplicate in case that's true.

On Wed, Nov 15, 2017 at 11:18 AM, Vladimir Ozerov <[hidden email]>
wrote:

> Dima,
>
> This appears to be a INFRA's bug. I filed a ticket [1].
>
> [1] https://issues.apache.org/jira/browse/INFRA-15487
>
> On Tue, Nov 14, 2017 at 9:25 PM, Dmitriy Setrakyan <[hidden email]>
> wrote:
>
> > On Tue, Nov 14, 2017 at 10:12 AM, Anton Vinogradov <
> > [hidden email]
> > > wrote:
> >
> > > Dmitriy,
> > >
> > > It looks like a confluence bug.
> > > Please login and push refresh button at issues list.
> > >
> >
> > Works now. It is unfortunate that it does not work for the community
> > members who do not login. Perhaps we can provide a link to the Jira
> filter,
> > so folks could click on it and view the tickets.
> >
>

[dmagda]

Ok, closed the previously existed as a duplicate and add another usability issue to fix in the scope of this IEP:
https://issues.apache.org/jira/browse/IGNITE-6925 <https://issues.apache.org/jira/browse/IGNITE-6925>

—
Denis

> On Nov 15, 2017, at 9:21 AM, Anton Vinogradov <[hidden email]> wrote:
>
> Denis,
>
> It looks like [1] is a duplicate of [2] and [3]
>
> [1] https://issues.apache.org/jira/browse/IGNITE-5796
> [2] https://issues.apache.org/jira/browse/IGNITE-6903
> [3] https://issues.apache.org/jira/browse/IGNITE-6902
>
> Please close issue as duplicate in case that's true.
>
> On Wed, Nov 15, 2017 at 11:18 AM, Vladimir Ozerov <[hidden email]>
> wrote:
>
>> Dima,
>>
>> This appears to be a INFRA's bug. I filed a ticket [1].
>>
>> [1] https://issues.apache.org/jira/browse/INFRA-15487
>>
>> On Tue, Nov 14, 2017 at 9:25 PM, Dmitriy Setrakyan <[hidden email]>
>> wrote:
>>
>>> On Tue, Nov 14, 2017 at 10:12 AM, Anton Vinogradov <
>>> [hidden email]
>>>> wrote:
>>>
>>>> Dmitriy,
>>>>
>>>> It looks like a confluence bug.
>>>> Please login and push refresh button at issues list.
>>>>
>>>
>>> Works now. It is unfortunate that it does not work for the community
>>> members who do not login. Perhaps we can provide a link to the Jira
>> filter,
>>> so folks could click on it and view the tickets.
>>>
>>

[Pavel Tupitsyn]

Hi Anton,

Looks like none of the new metrics are added on .NET side.
Please make sure it happens, either as part of existing tickets or
separately.

Thanks,
Pavel

On Thu, Nov 16, 2017 at 4:32 AM, Denis Magda <[hidden email]> wrote:

> Ok, closed the previously existed as a duplicate and add another usability
> issue to fix in the scope of this IEP:
> https://issues.apache.org/jira/browse/IGNITE-6925 <
> https://issues.apache.org/jira/browse/IGNITE-6925>
>
> —
> Denis
>
> > On Nov 15, 2017, at 9:21 AM, Anton Vinogradov <[hidden email]>
> wrote:
> >
> > Denis,
> >
> > It looks like [1] is a duplicate of [2] and [3]
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-5796
> > [2] https://issues.apache.org/jira/browse/IGNITE-6903
> > [3] https://issues.apache.org/jira/browse/IGNITE-6902
> >
> > Please close issue as duplicate in case that's true.
> >
> > On Wed, Nov 15, 2017 at 11:18 AM, Vladimir Ozerov <[hidden email]>
> > wrote:
> >
> >> Dima,
> >>
> >> This appears to be a INFRA's bug. I filed a ticket [1].
> >>
> >> [1] https://issues.apache.org/jira/browse/INFRA-15487
> >>
> >> On Tue, Nov 14, 2017 at 9:25 PM, Dmitriy Setrakyan <
> [hidden email]>
> >> wrote:
> >>
> >>> On Tue, Nov 14, 2017 at 10:12 AM, Anton Vinogradov <
> >>> [hidden email]
> >>>> wrote:
> >>>
> >>>> Dmitriy,
> >>>>
> >>>> It looks like a confluence bug.
> >>>> Please login and push refresh button at issues list.
> >>>>
> >>>
> >>> Works now. It is unfortunate that it does not work for the community
> >>> members who do not login. Perhaps we can provide a link to the Jira
> >> filter,
> >>> so folks could click on it and view the tickets.
> >>>
> >>
>
>

[Anton Vinogradov]

Pavel,

These changes mostly about JMX Beans.
Could you please explain what should be added to .Net? Provide some
examples please.

On Tue, Dec 5, 2017 at 10:40 AM, Pavel Tupitsyn <[hidden email]>
wrote:

> Hi Anton,
>
> Looks like none of the new metrics are added on .NET side.
> Please make sure it happens, either as part of existing tickets or
> separately.
>
> Thanks,
> Pavel
>
> On Thu, Nov 16, 2017 at 4:32 AM, Denis Magda <[hidden email]> wrote:
>
> > Ok, closed the previously existed as a duplicate and add another
> usability
> > issue to fix in the scope of this IEP:
> > https://issues.apache.org/jira/browse/IGNITE-6925 <
> > https://issues.apache.org/jira/browse/IGNITE-6925>
> >
> > —
> > Denis
> >
> > > On Nov 15, 2017, at 9:21 AM, Anton Vinogradov <
> [hidden email]>
> > wrote:
> > >
> > > Denis,
> > >
> > > It looks like [1] is a duplicate of [2] and [3]
> > >
> > > [1] https://issues.apache.org/jira/browse/IGNITE-5796
> > > [2] https://issues.apache.org/jira/browse/IGNITE-6903
> > > [3] https://issues.apache.org/jira/browse/IGNITE-6902
> > >
> > > Please close issue as duplicate in case that's true.
> > >
> > > On Wed, Nov 15, 2017 at 11:18 AM, Vladimir Ozerov <
> [hidden email]>
> > > wrote:
> > >
> > >> Dima,
> > >>
> > >> This appears to be a INFRA's bug. I filed a ticket [1].
> > >>
> > >> [1] https://issues.apache.org/jira/browse/INFRA-15487
> > >>
> > >> On Tue, Nov 14, 2017 at 9:25 PM, Dmitriy Setrakyan <
> > [hidden email]>
> > >> wrote:
> > >>
> > >>> On Tue, Nov 14, 2017 at 10:12 AM, Anton Vinogradov <
> > >>> [hidden email]
> > >>>> wrote:
> > >>>
> > >>>> Dmitriy,
> > >>>>
> > >>>> It looks like a confluence bug.
> > >>>> Please login and push refresh button at issues list.
> > >>>>
> > >>>
> > >>> Works now. It is unfortunate that it does not work for the community
> > >>> members who do not login. Perhaps we can provide a link to the Jira
> > >> filter,
> > >>> so folks could click on it and view the tickets.
> > >>>
> > >>
> >
> >
>

[Pavel Tupitsyn]

Anton,

https://issues.apache.org/jira/browse/IGNITE-6869 adds new properties to
ClusterMetrics.
There is corresponding
modules\platforms\dotnet\Apache.Ignite.Core\Cluster\IClusterMetrics.cs in
.NET.
Actually, IGNITE-6869 has a comment from Vladimir about this.

Same thing for IGNITE-6870, IGNITE-6903, IGNITE-6902, etc.


PS Looks like you don't close pull requests when merging them to master.
Please make sure to include "This closes #prnum" in the commit messages,
as the autogenerated comments in JIRA suggest.


On Tue, Dec 5, 2017 at 12:41 PM, Anton Vinogradov <[hidden email]>
wrote:

> Pavel,
>
> These changes mostly about JMX Beans.
> Could you please explain what should be added to .Net? Provide some
> examples please.
>
> On Tue, Dec 5, 2017 at 10:40 AM, Pavel Tupitsyn <[hidden email]>
> wrote:
>
> > Hi Anton,
> >
> > Looks like none of the new metrics are added on .NET side.
> > Please make sure it happens, either as part of existing tickets or
> > separately.
> >
> > Thanks,
> > Pavel
> >
> > On Thu, Nov 16, 2017 at 4:32 AM, Denis Magda <[hidden email]> wrote:
> >
> > > Ok, closed the previously existed as a duplicate and add another
> > usability
> > > issue to fix in the scope of this IEP:
> > > https://issues.apache.org/jira/browse/IGNITE-6925 <
> > > https://issues.apache.org/jira/browse/IGNITE-6925>
> > >
> > > —
> > > Denis
> > >
> > > > On Nov 15, 2017, at 9:21 AM, Anton Vinogradov <
> > [hidden email]>
> > > wrote:
> > > >
> > > > Denis,
> > > >
> > > > It looks like [1] is a duplicate of [2] and [3]
> > > >
> > > > [1] https://issues.apache.org/jira/browse/IGNITE-5796
> > > > [2] https://issues.apache.org/jira/browse/IGNITE-6903
> > > > [3] https://issues.apache.org/jira/browse/IGNITE-6902
> > > >
> > > > Please close issue as duplicate in case that's true.
> > > >
> > > > On Wed, Nov 15, 2017 at 11:18 AM, Vladimir Ozerov <
> > [hidden email]>
> > > > wrote:
> > > >
> > > >> Dima,
> > > >>
> > > >> This appears to be a INFRA's bug. I filed a ticket [1].
> > > >>
> > > >> [1] https://issues.apache.org/jira/browse/INFRA-15487
> > > >>
> > > >> On Tue, Nov 14, 2017 at 9:25 PM, Dmitriy Setrakyan <
> > > [hidden email]>
> > > >> wrote:
> > > >>
> > > >>> On Tue, Nov 14, 2017 at 10:12 AM, Anton Vinogradov <
> > > >>> [hidden email]
> > > >>>> wrote:
> > > >>>
> > > >>>> Dmitriy,
> > > >>>>
> > > >>>> It looks like a confluence bug.
> > > >>>> Please login and push refresh button at issues list.
> > > >>>>
> > > >>>
> > > >>> Works now. It is unfortunate that it does not work for the
> community
> > > >>> members who do not login. Perhaps we can provide a link to the Jira
> > > >> filter,
> > > >>> so folks could click on it and view the tickets.
> > > >>>
> > > >>
> > >
> > >
> >
>

[Anton Vinogradov]

Pavel,

>> There is corresponding
>> modules\platforms\dotnet\Apache.Ignite.Core\Cluster\IClusterMetrics.cs in
>> .NET.

Got it.

>> PS Looks like you don't close pull requests when merging them to master.
>> Please make sure to include "This closes #prnum" in the commit messages,
>> as the autogenerated comments in JIRA suggest.

Could you please explain profit of doing this?

On Tue, Dec 5, 2017 at 2:27 PM, Pavel Tupitsyn <[hidden email]> wrote:

> Anton,
>
> https://issues.apache.org/jira/browse/IGNITE-6869 adds new properties to
> ClusterMetrics.
> There is corresponding
> modules\platforms\dotnet\Apache.Ignite.Core\Cluster\IClusterMetrics.cs in
> .NET.
> Actually, IGNITE-6869 has a comment from Vladimir about this.
>
> Same thing for IGNITE-6870, IGNITE-6903, IGNITE-6902, etc.
>
>
> PS Looks like you don't close pull requests when merging them to master.
> Please make sure to include "This closes #prnum" in the commit messages,
> as the autogenerated comments in JIRA suggest.
>
>
> On Tue, Dec 5, 2017 at 12:41 PM, Anton Vinogradov <
> [hidden email]>
> wrote:
>
> > Pavel,
> >
> > These changes mostly about JMX Beans.
> > Could you please explain what should be added to .Net? Provide some
> > examples please.
> >
> > On Tue, Dec 5, 2017 at 10:40 AM, Pavel Tupitsyn <[hidden email]>
> > wrote:
> >
> > > Hi Anton,
> > >
> > > Looks like none of the new metrics are added on .NET side.
> > > Please make sure it happens, either as part of existing tickets or
> > > separately.
> > >
> > > Thanks,
> > > Pavel
> > >
> > > On Thu, Nov 16, 2017 at 4:32 AM, Denis Magda <[hidden email]>
> wrote:
> > >
> > > > Ok, closed the previously existed as a duplicate and add another
> > > usability
> > > > issue to fix in the scope of this IEP:
> > > > https://issues.apache.org/jira/browse/IGNITE-6925 <
> > > > https://issues.apache.org/jira/browse/IGNITE-6925>
> > > >
> > > > —
> > > > Denis
> > > >
> > > > > On Nov 15, 2017, at 9:21 AM, Anton Vinogradov <
> > > [hidden email]>
> > > > wrote:
> > > > >
> > > > > Denis,
> > > > >
> > > > > It looks like [1] is a duplicate of [2] and [3]
> > > > >
> > > > > [1] https://issues.apache.org/jira/browse/IGNITE-5796
> > > > > [2] https://issues.apache.org/jira/browse/IGNITE-6903
> > > > > [3] https://issues.apache.org/jira/browse/IGNITE-6902
> > > > >
> > > > > Please close issue as duplicate in case that's true.
> > > > >
> > > > > On Wed, Nov 15, 2017 at 11:18 AM, Vladimir Ozerov <
> > > [hidden email]>
> > > > > wrote:
> > > > >
> > > > >> Dima,
> > > > >>
> > > > >> This appears to be a INFRA's bug. I filed a ticket [1].
> > > > >>
> > > > >> [1] https://issues.apache.org/jira/browse/INFRA-15487
> > > > >>
> > > > >> On Tue, Nov 14, 2017 at 9:25 PM, Dmitriy Setrakyan <
> > > > [hidden email]>
> > > > >> wrote:
> > > > >>
> > > > >>> On Tue, Nov 14, 2017 at 10:12 AM, Anton Vinogradov <
> > > > >>> [hidden email]
> > > > >>>> wrote:
> > > > >>>
> > > > >>>> Dmitriy,
> > > > >>>>
> > > > >>>> It looks like a confluence bug.
> > > > >>>> Please login and push refresh button at issues list.
> > > > >>>>
> > > > >>>
> > > > >>> Works now. It is unfortunate that it does not work for the
> > community
> > > > >>> members who do not login. Perhaps we can provide a link to the
> Jira
> > > > >> filter,
> > > > >>> so folks could click on it and view the tickets.
> > > > >>>
> > > > >>
> > > >
> > > >
> > >
> >
>

[Pavel Tupitsyn]

> Could you please explain profit of doing this?
The point is that pull requests should not be left open.
Either close them manually or use that autoclose feature.

On Tue, Dec 5, 2017 at 4:02 PM, Anton Vinogradov <[hidden email]>
wrote:

> Pavel,
>
> >> There is corresponding
> >> modules\platforms\dotnet\Apache.Ignite.Core\Cluster\IClusterMetrics.cs
> in
> >> .NET.
>
> Got it.
>
> >> PS Looks like you don't close pull requests when merging them to master.
> >> Please make sure to include "This closes #prnum" in the commit messages,
> >> as the autogenerated comments in JIRA suggest.
>
> Could you please explain profit of doing this?
>
> On Tue, Dec 5, 2017 at 2:27 PM, Pavel Tupitsyn <[hidden email]>
> wrote:
>
> > Anton,
> >
> > https://issues.apache.org/jira/browse/IGNITE-6869 adds new properties to
> > ClusterMetrics.
> > There is corresponding
> > modules\platforms\dotnet\Apache.Ignite.Core\Cluster\IClusterMetrics.cs
> in
> > .NET.
> > Actually, IGNITE-6869 has a comment from Vladimir about this.
> >
> > Same thing for IGNITE-6870, IGNITE-6903, IGNITE-6902, etc.
> >
> >
> > PS Looks like you don't close pull requests when merging them to master.
> > Please make sure to include "This closes #prnum" in the commit messages,
> > as the autogenerated comments in JIRA suggest.
> >
> >
> > On Tue, Dec 5, 2017 at 12:41 PM, Anton Vinogradov <
> > [hidden email]>
> > wrote:
> >
> > > Pavel,
> > >
> > > These changes mostly about JMX Beans.
> > > Could you please explain what should be added to .Net? Provide some
> > > examples please.
> > >
> > > On Tue, Dec 5, 2017 at 10:40 AM, Pavel Tupitsyn <[hidden email]>
> > > wrote:
> > >
> > > > Hi Anton,
> > > >
> > > > Looks like none of the new metrics are added on .NET side.
> > > > Please make sure it happens, either as part of existing tickets or
> > > > separately.
> > > >
> > > > Thanks,
> > > > Pavel
> > > >
> > > > On Thu, Nov 16, 2017 at 4:32 AM, Denis Magda <[hidden email]>
> > wrote:
> > > >
> > > > > Ok, closed the previously existed as a duplicate and add another
> > > > usability
> > > > > issue to fix in the scope of this IEP:
> > > > > https://issues.apache.org/jira/browse/IGNITE-6925 <
> > > > > https://issues.apache.org/jira/browse/IGNITE-6925>
> > > > >
> > > > > —
> > > > > Denis
> > > > >
> > > > > > On Nov 15, 2017, at 9:21 AM, Anton Vinogradov <
> > > > [hidden email]>
> > > > > wrote:
> > > > > >
> > > > > > Denis,
> > > > > >
> > > > > > It looks like [1] is a duplicate of [2] and [3]
> > > > > >
> > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-5796
> > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-6903
> > > > > > [3] https://issues.apache.org/jira/browse/IGNITE-6902
> > > > > >
> > > > > > Please close issue as duplicate in case that's true.
> > > > > >
> > > > > > On Wed, Nov 15, 2017 at 11:18 AM, Vladimir Ozerov <
> > > > [hidden email]>
> > > > > > wrote:
> > > > > >
> > > > > >> Dima,
> > > > > >>
> > > > > >> This appears to be a INFRA's bug. I filed a ticket [1].
> > > > > >>
> > > > > >> [1] https://issues.apache.org/jira/browse/INFRA-15487
> > > > > >>
> > > > > >> On Tue, Nov 14, 2017 at 9:25 PM, Dmitriy Setrakyan <
> > > > > [hidden email]>
> > > > > >> wrote:
> > > > > >>
> > > > > >>> On Tue, Nov 14, 2017 at 10:12 AM, Anton Vinogradov <
> > > > > >>> [hidden email]
> > > > > >>>> wrote:
> > > > > >>>
> > > > > >>>> Dmitriy,
> > > > > >>>>
> > > > > >>>> It looks like a confluence bug.
> > > > > >>>> Please login and push refresh button at issues list.
> > > > > >>>>
> > > > > >>>
> > > > > >>> Works now. It is unfortunate that it does not work for the
> > > community
> > > > > >>> members who do not login. Perhaps we can provide a link to the
> > Jira
> > > > > >> filter,
> > > > > >>> so folks could click on it and view the tickets.
> > > > > >>>
> > > > > >>
> > > > >
> > > > >
> > > >
> > >
> >
>

[Anton Vinogradov]

Why it should not be open?
That's just a tool allows to merge something.
Since we're not using PR's in github's way - I see no reason to close them.

On Tue, Dec 5, 2017 at 4:11 PM, Pavel Tupitsyn <[hidden email]> wrote:

> > Could you please explain profit of doing this?
> The point is that pull requests should not be left open.
> Either close them manually or use that autoclose feature.
>
> On Tue, Dec 5, 2017 at 4:02 PM, Anton Vinogradov <[hidden email]
> >
> wrote:
>
> > Pavel,
> >
> > >> There is corresponding
> > >> modules\platforms\dotnet\Apache.Ignite.Core\Cluster\
> IClusterMetrics.cs
> > in
> > >> .NET.
> >
> > Got it.
> >
> > >> PS Looks like you don't close pull requests when merging them to
> master.
> > >> Please make sure to include "This closes #prnum" in the commit
> messages,
> > >> as the autogenerated comments in JIRA suggest.
> >
> > Could you please explain profit of doing this?
> >
> > On Tue, Dec 5, 2017 at 2:27 PM, Pavel Tupitsyn <[hidden email]>
> > wrote:
> >
> > > Anton,
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-6869 adds new properties
> to
> > > ClusterMetrics.
> > > There is corresponding
> > > modules\platforms\dotnet\Apache.Ignite.Core\Cluster\IClusterMetrics.cs
> > in
> > > .NET.
> > > Actually, IGNITE-6869 has a comment from Vladimir about this.
> > >
> > > Same thing for IGNITE-6870, IGNITE-6903, IGNITE-6902, etc.
> > >
> > >
> > > PS Looks like you don't close pull requests when merging them to
> master.
> > > Please make sure to include "This closes #prnum" in the commit
> messages,
> > > as the autogenerated comments in JIRA suggest.
> > >
> > >
> > > On Tue, Dec 5, 2017 at 12:41 PM, Anton Vinogradov <
> > > [hidden email]>
> > > wrote:
> > >
> > > > Pavel,
> > > >
> > > > These changes mostly about JMX Beans.
> > > > Could you please explain what should be added to .Net? Provide some
> > > > examples please.
> > > >
> > > > On Tue, Dec 5, 2017 at 10:40 AM, Pavel Tupitsyn <
> [hidden email]>
> > > > wrote:
> > > >
> > > > > Hi Anton,
> > > > >
> > > > > Looks like none of the new metrics are added on .NET side.
> > > > > Please make sure it happens, either as part of existing tickets or
> > > > > separately.
> > > > >
> > > > > Thanks,
> > > > > Pavel
> > > > >
> > > > > On Thu, Nov 16, 2017 at 4:32 AM, Denis Magda <[hidden email]>
> > > wrote:
> > > > >
> > > > > > Ok, closed the previously existed as a duplicate and add another
> > > > > usability
> > > > > > issue to fix in the scope of this IEP:
> > > > > > https://issues.apache.org/jira/browse/IGNITE-6925 <
> > > > > > https://issues.apache.org/jira/browse/IGNITE-6925>
> > > > > >
> > > > > > —
> > > > > > Denis
> > > > > >
> > > > > > > On Nov 15, 2017, at 9:21 AM, Anton Vinogradov <
> > > > > [hidden email]>
> > > > > > wrote:
> > > > > > >
> > > > > > > Denis,
> > > > > > >
> > > > > > > It looks like [1] is a duplicate of [2] and [3]
> > > > > > >
> > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-5796
> > > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-6903
> > > > > > > [3] https://issues.apache.org/jira/browse/IGNITE-6902
> > > > > > >
> > > > > > > Please close issue as duplicate in case that's true.
> > > > > > >
> > > > > > > On Wed, Nov 15, 2017 at 11:18 AM, Vladimir Ozerov <
> > > > > [hidden email]>
> > > > > > > wrote:
> > > > > > >
> > > > > > >> Dima,
> > > > > > >>
> > > > > > >> This appears to be a INFRA's bug. I filed a ticket [1].
> > > > > > >>
> > > > > > >> [1] https://issues.apache.org/jira/browse/INFRA-15487
> > > > > > >>
> > > > > > >> On Tue, Nov 14, 2017 at 9:25 PM, Dmitriy Setrakyan <
> > > > > > [hidden email]>
> > > > > > >> wrote:
> > > > > > >>
> > > > > > >>> On Tue, Nov 14, 2017 at 10:12 AM, Anton Vinogradov <
> > > > > > >>> [hidden email]
> > > > > > >>>> wrote:
> > > > > > >>>
> > > > > > >>>> Dmitriy,
> > > > > > >>>>
> > > > > > >>>> It looks like a confluence bug.
> > > > > > >>>> Please login and push refresh button at issues list.
> > > > > > >>>>
> > > > > > >>>
> > > > > > >>> Works now. It is unfortunate that it does not work for the
> > > > community
> > > > > > >>> members who do not login. Perhaps we can provide a link to
> the
> > > Jira
> > > > > > >> filter,
> > > > > > >>> so folks could click on it and view the tickets.
> > > > > > >>>
> > > > > > >>
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>