Re: Identifying grid transactions

2017-11-08 Thread Valentin Kulichenko
Yakov, Here is the ticket: https://issues.apache.org/jira/browse/IGNITE-6847 Feel free to add if I missed anything. -Val On Tue, Oct 10, 2017 at 3:22 AM, Yakov Zhdanov wrote: > Val, I really like your idea to implement common mechanism for all APIs. > Can you please file a ticket? > > --Yakov

Re: Identifying grid transactions

2017-10-10 Thread Yakov Zhdanov
Val, I really like your idea to implement common mechanism for all APIs. Can you please file a ticket? --Yakov

Re: Identifying grid transactions

2017-10-06 Thread Valentin Kulichenko
Yakov, Ideally - all of them :) Or at least those APIs that execute remote operations (all cache operations, compute, service proxy invocations, ...). Having an ability to add custom metadata to this kind of operations can be very valuable for auditing purposes. -Val On Thu, Oct 5, 2017 at 8:38

Re: Identifying grid transactions

2017-10-05 Thread Yakov Zhdanov
>>That's a very useful suggestion. Can it be supported for other APIs as >> well, not only transactions? >> -Val Val, please clarify. What APIs do you mean? --Yakov

Re: Identifying grid transactions

2017-10-05 Thread Dmitry Pavlov
Hi Igniters, Would it be useful to provide some traceability identifier for messages participating in the partition map exchange? This can be used to filter all logs associated with the exchange. Or now there is some possibility? Sincerely, Dmitriy Pavlov чт, 5 окт. 2017 г. в 2:01, Valentin Kuli

Re: Identifying grid transactions

2017-10-04 Thread Valentin Kulichenko
That's a very useful suggestion. Can it be supported for other APIs as well, not only transactions? -Val On Wed, Oct 4, 2017 at 12:47 PM, Vladimir Ozerov wrote: > +1 for withTag() > > ср, 4 окт. 2017 г. в 17:19, Yakov Zhdanov : > > > Really like .withTag() suggestion! > > > > --Yakov > > >

Re: Identifying grid transactions

2017-10-04 Thread Vladimir Ozerov
+1 for withTag() ср, 4 окт. 2017 г. в 17:19, Yakov Zhdanov : > Really like .withTag() suggestion! > > --Yakov >

Re: Identifying grid transactions

2017-10-04 Thread Yakov Zhdanov
Really like .withTag() suggestion! --Yakov

Re: Identifying grid transactions

2017-10-04 Thread Dmitriy Setrakyan
On Wed, Oct 4, 2017 at 3:01 PM, Konstantin Dudkov wrote: > Hi, > > .withTag maybe? > Agree, withTag() looks much better.

Re: Identifying grid transactions

2017-10-04 Thread Sergey Kozlov
No I meant just a string p.s. .withTag looks better On Wed, Oct 4, 2017 at 3:08 PM, Vladimir Ozerov wrote: > Sergey, > > Do you mean attaching something more than a single String? > > On Wed, Oct 4, 2017 at 3:01 PM, Konstantin Dudkov wrote: > > > Hi, > > > > .withTag maybe? > > > > 04/10/2017

Re: Identifying grid transactions

2017-10-04 Thread Vladimir Ozerov
Sergey, Do you mean attaching something more than a single String? On Wed, Oct 4, 2017 at 3:01 PM, Konstantin Dudkov wrote: > Hi, > > .withTag maybe? > > 04/10/2017 14:52, Sergey Kozlov пишет: > > Hi >> >> .withApplication and .withMetatData may narrow use case. Looks like . >> withDescription

Re: Identifying grid transactions

2017-10-04 Thread Konstantin Dudkov
Hi, .withTag maybe? 04/10/2017 14:52, Sergey Kozlov пишет: Hi .withApplication and .withMetatData may narrow use case. Looks like . withDescription can have more sense and allow use write any information valuable for further debugging. On Wed, Oct 4, 2017 at 2:47 PM, Dmitriy Setrakyan wrote:

Re: Identifying grid transactions

2017-10-04 Thread Sergey Kozlov
Hi .withApplication and .withMetatData may narrow use case. Looks like . withDescription can have more sense and allow use write any information valuable for further debugging. On Wed, Oct 4, 2017 at 2:47 PM, Dmitriy Setrakyan wrote: > I would rename to "withMetadata()". > > On Wed, Oct 4, 2017

Re: Identifying grid transactions

2017-10-04 Thread Dmitriy Setrakyan
I would rename to "withMetadata()". On Wed, Oct 4, 2017 at 2:31 PM, Vladimir Ozerov wrote: > Alex, > > I do not think we have such feature in the product at the moment. But this > could be very valuable addition. For example, we have somewhat similar task > for JDBC - to track applications that

Re: Identifying grid transactions

2017-10-04 Thread Vladimir Ozerov
Alex, I do not think we have such feature in the product at the moment. But this could be very valuable addition. For example, we have somewhat similar task for JDBC - to track applications that use the driver [1]. We can think of adding a single optional string to transaction protocol, so that we

Re: Identifying grid transactions

2017-10-04 Thread Alexey Inozemtsev
Alexey, thanks a lot! This requires a change in application code. Is there a way to do it without that? Alexey 2017-10-04 13:22 GMT+03:00 Alexei Scherbakov : > Alexey, > > Simplest way: wrap IgniteTransactions instance returned by > ignite.transactions() with delegate using advanced logging capa

Re: Identifying grid transactions

2017-10-04 Thread Alexei Scherbakov
Alexey, Simplest way: wrap IgniteTransactions instance returned by ignite.transactions() with delegate using advanced logging capabilities for tx* methods, like current thread and stack trace. There is no notion of transaction parameters. 2017-10-04 12:40 GMT+03:00 Alexey Inozemtsev : > Igniter

Identifying grid transactions

2017-10-04 Thread Alexey Inozemtsev
Igniters, A team I'm working with uses Apache Ignite massively. There are many application modules using the cluster. We've faced a problem on how to identify the external app modules which keep transactions open in the grid. Right now we have to restart client nodes to get reed of them. Is there