[jira] [Updated] (FLINK-24510) Fix the duplicate log output of libraries/connectors，when logback is used
[
https://issues.apache.org/jira/browse/FLINK-24510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-24510:
---
Labels: auto-deprioritized-major auto-deprioritized-minor
pull-request-available (was: auto-deprioritized-major pull-request-available
stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> Fix the duplicate log output of libraries/connectors，when logback is used
> -
>
> Key: FLINK-24510
> URL: https://issues.apache.org/jira/browse/FLINK-24510
> Project: Flink
> Issue Type: Bug
> Components: Deployment / Scripts
>Affects Versions: 1.14.0
>Reporter: xiangqiao
>Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor,
> pull-request-available
> Attachments: image-2021-10-12-10-52-22-389.png
>
>
> When logback is used, the logs of libraries / connectors are output
> repeatedly.
> !image-2021-10-12-10-52-22-389.png!
>
> By default, *appenders are cumulative*: a logger will log to the appenders
> attached to itself (if any) as well as all the appenders attached to its
> ancestors. Thus, attaching the same appender to multiple loggers will cause
> logging output to be duplicated.
> [http://logback.qos.ch/manual/configuration.html#cumulative]
>
> We can solve this problem in the following ways：
> {code:java}
>
>
>
>
>
>
>
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-24510) Fix the duplicate log output of libraries/connectors，when logback is used
[
https://issues.apache.org/jira/browse/FLINK-24510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-24510:
---
Labels: auto-deprioritized-major pull-request-available stale-minor (was:
auto-deprioritized-major pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Fix the duplicate log output of libraries/connectors，when logback is used
> -
>
> Key: FLINK-24510
> URL: https://issues.apache.org/jira/browse/FLINK-24510
> Project: Flink
> Issue Type: Bug
> Components: Deployment / Scripts
>Affects Versions: 1.14.0
>Reporter: xiangqiao
>Priority: Minor
> Labels: auto-deprioritized-major, pull-request-available,
> stale-minor
> Attachments: image-2021-10-12-10-52-22-389.png
>
>
> When logback is used, the logs of libraries / connectors are output
> repeatedly.
> !image-2021-10-12-10-52-22-389.png!
>
> By default, *appenders are cumulative*: a logger will log to the appenders
> attached to itself (if any) as well as all the appenders attached to its
> ancestors. Thus, attaching the same appender to multiple loggers will cause
> logging output to be duplicated.
> [http://logback.qos.ch/manual/configuration.html#cumulative]
>
> We can solve this problem in the following ways：
> {code:java}
>
>
>
>
>
>
>
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-24510) Fix the duplicate log output of libraries/connectors，when logback is used
[
https://issues.apache.org/jira/browse/FLINK-24510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-24510:
---
Labels: auto-deprioritized-major pull-request-available (was:
pull-request-available stale-major)
Priority: Minor (was: Major)
This issue was labeled "stale-major" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Major, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> Fix the duplicate log output of libraries/connectors，when logback is used
> -
>
> Key: FLINK-24510
> URL: https://issues.apache.org/jira/browse/FLINK-24510
> Project: Flink
> Issue Type: Bug
> Components: Deployment / Scripts
>Affects Versions: 1.14.0
>Reporter: xiangqiao
>Priority: Minor
> Labels: auto-deprioritized-major, pull-request-available
> Attachments: image-2021-10-12-10-52-22-389.png
>
>
> When logback is used, the logs of libraries / connectors are output
> repeatedly.
> !image-2021-10-12-10-52-22-389.png!
>
> By default, *appenders are cumulative*: a logger will log to the appenders
> attached to itself (if any) as well as all the appenders attached to its
> ancestors. Thus, attaching the same appender to multiple loggers will cause
> logging output to be duplicated.
> [http://logback.qos.ch/manual/configuration.html#cumulative]
>
> We can solve this problem in the following ways：
> {code:java}
>
>
>
>
>
>
>
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (FLINK-24510) Fix the duplicate log output of libraries/connectors，when logback is used
[
https://issues.apache.org/jira/browse/FLINK-24510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-24510:
---
Labels: pull-request-available stale-major (was: pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 60 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Fix the duplicate log output of libraries/connectors，when logback is used
> -
>
> Key: FLINK-24510
> URL: https://issues.apache.org/jira/browse/FLINK-24510
> Project: Flink
> Issue Type: Bug
> Components: Deployment / Scripts
>Affects Versions: 1.14.0
>Reporter: xiangqiao
>Priority: Major
> Labels: pull-request-available, stale-major
> Attachments: image-2021-10-12-10-52-22-389.png
>
>
> When logback is used, the logs of libraries / connectors are output
> repeatedly.
> !image-2021-10-12-10-52-22-389.png!
>
> By default, *appenders are cumulative*: a logger will log to the appenders
> attached to itself (if any) as well as all the appenders attached to its
> ancestors. Thus, attaching the same appender to multiple loggers will cause
> logging output to be duplicated.
> [http://logback.qos.ch/manual/configuration.html#cumulative]
>
> We can solve this problem in the following ways：
> {code:java}
>
>
>
>
>
>
>
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (FLINK-24510) Fix the duplicate log output of libraries/connectors，when logback is used
[
https://issues.apache.org/jira/browse/FLINK-24510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated FLINK-24510:
---
Labels: pull-request-available (was: )
> Fix the duplicate log output of libraries/connectors，when logback is used
> -
>
> Key: FLINK-24510
> URL: https://issues.apache.org/jira/browse/FLINK-24510
> Project: Flink
> Issue Type: Bug
> Components: Deployment / Scripts
>Affects Versions: 1.14.0
>Reporter: xiangqiao
>Priority: Major
> Labels: pull-request-available
> Attachments: image-2021-10-12-10-52-22-389.png
>
>
> When logback is used, the logs of libraries / connectors are output
> repeatedly.
> !image-2021-10-12-10-52-22-389.png!
>
> By default, *appenders are cumulative*: a logger will log to the appenders
> attached to itself (if any) as well as all the appenders attached to its
> ancestors. Thus, attaching the same appender to multiple loggers will cause
> logging output to be duplicated.
> [http://logback.qos.ch/manual/configuration.html#cumulative]
>
> We can solve this problem in the following ways：
> {code:java}
>
>
>
>
>
>
>
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
