You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Peter Schmitt <pe...@gmail.com> on 2017/03/02 21:52:30 UTC
Whole cache-entries in log-files found
Hello Ignite-Community!
I saw that Ignite sometimes logs whole cache-entries.
In addition to the whole content of an entry, such log entries contain e.g.
Ignite-details like extras=GridCachedObsoleteEntryExtras and messages like
"Value did not change, skip write swap entry".
Why does Ignite create such log-entries which consist of the
cache-entry-content and some Ignite-Metadata?
How can I disable it?
Any hint is appreciated,
Peter
Re: Whole cache-entries in log-files found
Posted by Peter Schmitt <pe...@gmail.com>.
Hi Val,
thank you for the answer!
Kind Regards,
Peter
2017-03-02 23:31 GMT+01:00 vkulichenko <va...@gmail.com>:
> Hi Peter,
>
> Starting with 1.9 (which is about to be released) it will be possible to
> avoid key-value printout by setting this system property:
>
> -DIGNITE_TO_STRING_INCLUDE_SENSITIVE=true
>
> -Val
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Whole-cache-entries-in-log-files-
> found-tp10999p11003.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
Re: Whole cache-entries in log-files found
Posted by vkulichenko <va...@gmail.com>.
Hi Peter,
Starting with 1.9 (which is about to be released) it will be possible to
avoid key-value printout by setting this system property:
-DIGNITE_TO_STRING_INCLUDE_SENSITIVE=true
-Val
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Whole-cache-entries-in-log-files-found-tp10999p11003.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.