Client Cache metrics API design discussion.

Igniters! Here is a handsome moment in our current cache metrics API, that begs for an improvement and due to it significancy assumed to be discussed communitywise. Current CacheMetrics interface is confusing for a case, when it is accessed from a client node. One of the typical question is:

[jira] [Created] (IGNITE-2567) Grouping

Pavel Tupitsyn created IGNITE-2567: -- Summary: Grouping Key: IGNITE-2567 URL: https://issues.apache.org/jira/browse/IGNITE-2567 Project: Ignite Issue Type: Sub-task Reporter:

Re: Client Cache metrics API design discussion.

Vladimir, As I already suggested in the ticket [1], I think that by default we should return metrics for the whole cluster. Now we collect them only from local node, which is confusing, especially on the client. If one needs metrics for one node or from subset of nodes, metrics(ClusterGroup)

Re: Proxy serialization issue

Alex, I don't know in advance how many bytes I will write because some classes can be successfully registered, but some not. Therefore I can't extend by more than 5 bytes at this point. Makes sense? -Val On Fri, Feb 5, 2016 at 4:02 AM, Alexey Goncharuk wrote: >

[jira] [Created] (IGNITE-2569) Ignite GridComponent used incorrectly during IgniteStart. Could cause NPE

Vladimir Ershov created IGNITE-2569: --- Summary: Ignite GridComponent used incorrectly during IgniteStart. Could cause NPE Key: IGNITE-2569 URL: https://issues.apache.org/jira/browse/IGNITE-2569

Re: API doc for .NET

I uploaded the docs and added links under 'Documentation' menu on the website. https://ignite.apache.org/releases/1.5.0.final/dotnetdoc/ https://ignite.apache.org/releases/1.5.0.final/cppdoc/ -Val On Thu, Feb 4, 2016 at 10:04 PM, Vladimir Ozerov wrote: > We have doxygen

Re: API doc for .NET

Great! Now we have to work on adding C++ documentation in readme. D. On Fri, Feb 5, 2016 at 12:40 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > I uploaded the docs and added links under 'Documentation' menu on the > website. > >

Re: Client Cache metrics API design discussion.

Agree. All metrics should return the data for the whole cache, unless specifically specified otherwise by user. D. On Fri, Feb 5, 2016 at 10:56 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Vladimir, > > As I already suggested in the ticket [1], I think that by default we

[jira] [Created] (IGNITE-2562) Affix is blinking in some cases

Alexey Kuznetsov created IGNITE-2562: Summary: Affix is blinking in some cases Key: IGNITE-2562 URL: https://issues.apache.org/jira/browse/IGNITE-2562 Project: Ignite Issue Type:

Re: Proxy serialization issue

Val, The code looks good to me. The only place that made me wonder was out.unsafeEnsure(1 + 4) call which extends the stream by 5 bytes, however we can write significantly more bytes. I see that we use the same approach in other places, so I was wondering if this is a required call or a

[jira] [Created] (IGNITE-2564) CPP: Memory reallocation callback doesn't work.

Vladimir Ozerov created IGNITE-2564: --- Summary: CPP: Memory reallocation callback doesn't work. Key: IGNITE-2564 URL: https://issues.apache.org/jira/browse/IGNITE-2564 Project: Ignite Issue

[jira] [Created] (IGNITE-2565) TCK suite fail periodically

Anton Vinogradov created IGNITE-2565: Summary: TCK suite fail periodically Key: IGNITE-2565 URL: https://issues.apache.org/jira/browse/IGNITE-2565 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-2570) LoadCacheClosure and several other classes in GridCacheAdapter are not marked as internal

Valentin Kulichenko created IGNITE-2570: --- Summary: LoadCacheClosure and several other classes in GridCacheAdapter are not marked as internal Key: IGNITE-2570 URL: