Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Subject: Re: Identifying grid transactions
To: dev@ignite.apache.org
References: <CAKXNsOWNqKXob-k4QFfbhe656DHGte-1qQOZYOOzPyZPCDo85Q@mail.gmail.com>
 <CAMegbc+2eSHo8+2BexR-oT_t81pYtC8_psUt1SwFUwDXsva4dQ@mail.gmail.com>
 <CAGt6o8krxbk+stac9MoG0zfpb=4-Ux2BdqMkEFd3bUcJeT=XyQ@mail.gmail.com>
 <CA+0=VoXtg+zJcovY3S7kJhzpFw6Ep31-E3YUHU6TD=Fr7OTvwQ@mail.gmail.com>
 <CAMbfdjY_pZ9qDXSLR0reH12gVRYdNC-aWGbx+=ocRuzTD14O8A@mail.gmail.com>
From: Konstantin Dudkov <kdudkov@ya.ru>
Message-ID: <c1d5416e-f008-4187-3b05-3796a0920012@ya.ru>
Date: Wed, 4 Oct 2017 15:01:03 +0300
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0)
 Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <CAMbfdjY_pZ9qDXSLR0reH12gVRYdNC-aWGbx+=ocRuzTD14O8A@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
archived-at: Wed, 04 Oct 2017 12:01:15 -0000

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 <dsetrakyan@apache.org>
> wrote:
> 
>> I would rename to "withMetadata()".
>>
>> On Wed, Oct 4, 2017 at 2:31 PM, Vladimir Ozerov <vozerov@gridgain.com>
>> 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 use the driver [1]. We can think of
>>> adding a single optional string to transaction protocol, so that we can
>>> track application/module on any node. E.g.:
>>>
>>> IgniteTransactions transactions = ignite.transactions().
>> withApplication("
>>> *myApp:myModule*");
>>>
>>> And then all usages of this facade will propagate application to all
>> nodes.
>>>
>>> Thoughts?
>>>
>>> [1] https://issues.apache.org/jira/browse/IGNITE-5453
>>>
>>> On Wed, Oct 4, 2017 at 1:22 PM, Alexei Scherbakov <
>>> alexey.scherbakoff@gmail.com> wrote:
>>>
>>>> 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 <
>>> alexey.inozemtsev@gmail.com
>>>>> :
>>>>
>>>>> 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 a parameter on Ignite transaction to (ala MODULE in Oracle)
>>>> which
>>>>> can be set on a client side?
>>>>> Are there other ways to manage such a situation?
>>>>>
>>>>> Have a nice day,
>>>>> Alexey
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Best regards,
>>>> Alexei Scherbakov
>>>>
>>>
>>
> 
> 
> 

-- 
Regards, Konstantin.