From 8bff2302cbd0038657044b2ee7bbb94f849eadb3 Mon Sep 17 00:00:00 2001 From: Przemyslaw Gomulka Date: Fri, 29 May 2020 11:23:07 +0200 Subject: [PATCH 1/3] [Doc] 7.6.0 Known issue for slow loggers leaking log4j loggers --- docs/reference/release-notes/7.6.asciidoc | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/reference/release-notes/7.6.asciidoc b/docs/reference/release-notes/7.6.asciidoc index db68c6c7836b5..33955e2d5d740 100644 --- a/docs/reference/release-notes/7.6.asciidoc +++ b/docs/reference/release-notes/7.6.asciidoc @@ -168,6 +168,10 @@ that are incompatible with java.time patterns will cause parsing errors, incorre https://github.com/elastic/elasticsearch/pull/52555 This is fixed in {es} 7.7 and later versions. +* Slow loggers are causing log4j loggers to leak over time. When new index is created, new log4j logger was associated with it. +However when deleting an index it, log4j was keeping a reference internally to its loggers causing a memory leak. +https://github.com/elastic/elasticsearch/issues/56171 Fixed in 7.7.1 + [[breaking-7.6.0]] [float] === Breaking changes From 74adddef41eefca5b504f8bae9453307902a6c56 Mon Sep 17 00:00:00 2001 From: Przemyslaw Gomulka Date: Tue, 2 Jun 2020 14:15:08 +0200 Subject: [PATCH 2/3] Update docs/reference/release-notes/7.6.asciidoc Co-authored-by: Adam Locke --- docs/reference/release-notes/7.6.asciidoc | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/reference/release-notes/7.6.asciidoc b/docs/reference/release-notes/7.6.asciidoc index 33955e2d5d740..bbee36644c7e4 100644 --- a/docs/reference/release-notes/7.6.asciidoc +++ b/docs/reference/release-notes/7.6.asciidoc @@ -168,10 +168,9 @@ that are incompatible with java.time patterns will cause parsing errors, incorre https://github.com/elastic/elasticsearch/pull/52555 This is fixed in {es} 7.7 and later versions. -* Slow loggers are causing log4j loggers to leak over time. When new index is created, new log4j logger was associated with it. -However when deleting an index it, log4j was keeping a reference internally to its loggers causing a memory leak. -https://github.com/elastic/elasticsearch/issues/56171 Fixed in 7.7.1 +Slow loggers can cause Log4j loggers to leak over time. When a new index is created, a new Log4j logger is associated with it. However, when an index is deleted, Log4j keeps an internal reference to its loggers that results in a memory leak {pull}56171[#56171] +This issue is fixed in Elasticsearch 6.8.10 and 7.7.1. [[breaking-7.6.0]] [float] === Breaking changes From 24b4b2a9b66795b6b6b5b5004c6633aa09dce842 Mon Sep 17 00:00:00 2001 From: Przemyslaw Gomulka Date: Tue, 2 Jun 2020 15:39:19 +0200 Subject: [PATCH 3/3] Update docs/reference/release-notes/7.6.asciidoc Co-authored-by: Adam Locke --- docs/reference/release-notes/7.6.asciidoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/reference/release-notes/7.6.asciidoc b/docs/reference/release-notes/7.6.asciidoc index bbee36644c7e4..e2574024a201d 100644 --- a/docs/reference/release-notes/7.6.asciidoc +++ b/docs/reference/release-notes/7.6.asciidoc @@ -168,9 +168,9 @@ that are incompatible with java.time patterns will cause parsing errors, incorre https://github.com/elastic/elasticsearch/pull/52555 This is fixed in {es} 7.7 and later versions. -Slow loggers can cause Log4j loggers to leak over time. When a new index is created, a new Log4j logger is associated with it. However, when an index is deleted, Log4j keeps an internal reference to its loggers that results in a memory leak {pull}56171[#56171] - -This issue is fixed in Elasticsearch 6.8.10 and 7.7.1. +* Slow loggers can cause Log4j loggers to leak over time. When a new index is created, a new Log4j logger is associated with it. However, when an index is deleted, Log4j keeps an internal reference to its loggers that results in a memory leak (issue: {issue}56171[#56171]) ++ +This issue is fixed in {es} 6.8.10 and 7.7.1. [[breaking-7.6.0]] [float] === Breaking changes