apache/incubator-seata

optimize channel availability thread log output

Open

#5,474 opened on Mar 30, 2023

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Java (25,960 stars) (8,878 forks)batch import
good first issuetask: help-wanted

Description

  • I have searched the issues of this repository and believe that this is not a duplicate.

Ⅰ. Issue Description

image 建议改为debug下输出堆栈，info下不输出堆栈，并且将所有失败的地址合并输出，而不是10个里面有5个地址不可用输出五次日志得形式

Ⅱ. Describe what happened

If there is an exception, please attach the exception trace:

Just paste your stack trace here!

Ⅲ. Describe what you expected to happen

Ⅳ. How to reproduce it (as minimally and precisely as possible)

  1. xxx
  2. xxx
  3. xxx

Ⅴ. Anything else we need to know?

Ⅵ. Environment:

  • JDK version :
  • Seata version:
  • OS :
  • Others:

Contributor guide

Tech stack
java
Domain
observability
Issue type
refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
JavaSLF4J
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85
Research direction
Locate the source code for channel availability thread logging in the Seata repository (likely in the RPC or transport module). Modify the log statements so that stack traces are only printed at DEBUG level, INFO level omits them, and all failed addresses are combined into a single log output. Refer to Seata's logging conventions using SLF4J and ensure consistency with existing patterns.