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 <dsetrak...@apache.org>
wrote:
I would rename to "withMetadata()".
On Wed, Oct 4, 2017 at 2:31 PM, Vladimir Ozerov <voze...@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.scherbak...@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.inozemt...@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.
