You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Kirk Lund (JIRA)" <ji...@apache.org> on 2018/10/31 20:04:00 UTC

[jira] [Assigned] (GEODE-5963) Client destroy log statement should be logged at debug level

     [ https://issues.apache.org/jira/browse/GEODE-5963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kirk Lund reassigned GEODE-5963:
--------------------------------

    Assignee: Kirk Lund

> Client destroy log statement should be logged at debug level
> ------------------------------------------------------------
>
>                 Key: GEODE-5963
>                 URL: https://issues.apache.org/jira/browse/GEODE-5963
>             Project: Geode
>          Issue Type: Wish
>          Components: client/server, logging
>            Reporter: Kirk Lund
>            Assignee: Kirk Lund
>            Priority: Major
>
> Usage patterns that include a lot of lookups for keys that aren't there may result in an abundance of this log statement in the log file:
> {noformat}
> [info 2018/10/31 13:01:20.909 PDT <main> tid=0x1] Server connection from foo: during entry destroy no entry was found for key key1
> {noformat}
> This log statement is in:
> {noformat}
> geode-core/src/main/java/org/apache/geode/internal/cache/tier/sockets/command/Destroy.java:156:      logger.info("{}: during entry destroy no entry was found for key {}",
> geode-core/src/main/java/org/apache/geode/internal/cache/tier/sockets/command/Destroy65.java:284:      logger.info("{}: during entry destroy no entry was found for key {}",
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)