a large number of akka remote logs
- Dominant language
- Scala
- Stars
- 6.8k
- Forks
- 1.2k
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 2
Description
## Environment details:
centeos docker1.17
## Provide the expected results and outputs:
```
after the Controller starts, it prints a large number of logs related to akka remote.
consider adjusting the relevant log level?
```
## Provide the actual results and outputs:
```
Discoverd [1] contact points , confimed[1],which is less than the required[2] ,retrying
```
Contributor guide
Research direction
Start by reproducing Controller startup in the stated CentOS and Docker 1.17 environment and trace the `Discoverd [1] contact points` message associated with Akka remote. Identify where that message is emitted and determine the appropriate log-level change; done means startup no longer produces the excessive Akka remote logs while retaining useful diagnostics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, scala
- Domain
- distributed-systems, observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100