ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vladislav Pyatkov <vldpyat...@gmail.com>
Subject Re: need few clarification for some of our use cases
Date Wed, 16 Nov 2016 07:35:03 GMT
Hi Navneet,

Ignite supports various logging utilities (jul, log4j, slf4j etc.)[1]. I
used to log4j SocketAppender for issues like this.

Look at the Ignite transaction API[2], you got specific exception when
transaction was not commited.

Yes, you can use Cache Interceptor[3] for processing cache operation or
Continuous Queries[4] for tracking of cache entry updates.

[1]:
http://ignite.apache.org/releases/1.0.0/javadoc/org/apache/ignite/logger/log4j/Log4JLogger.html
[2]: https://apacheignite.readme.io/docs/transactions
[3]:
https://ignite.apache.org/releases/mobile/org/apache/ignite/cache/CacheInterceptor.html
[4]: https://apacheignite.readme.io/docs/continuous-queries

On Wed, Nov 16, 2016 at 10:10 AM, Navneet Kumar <
navneetkumar.india@gmail.com> wrote:

> Hi All,
> I need few clarification for some of our use cases:
> -       Can we redirect the apache ignite logs to remote server ?
> -       How LRTs(pending transactions not committed)  can be identified
> and acted
> upon ?
> -       Does Apache ignite support DB triggers when Cache is updated.
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/need-few-clarification-for-some-of-our-
> use-cases-tp9014.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>



-- 
Vladislav Pyatkov

Mime
View raw message