-
Notifications
You must be signed in to change notification settings - Fork 175
Closed
Labels
good first issueGood for newcomersGood for newcomershelp wantedExtra attention is neededExtra attention is neededkind/easy
Description
According to feedback from @stulzq and @whalesongAndLittleFish ,when Layotto can not connect to the redis server(for example,you wrote a wrong redis port in the Layotto configuration file), the logs are not detailed and we can't find out why error happens.
Steps to reproduce:
- Start a Layotto with a redis lock component following the quickstart document ,but configurate a wrong redis port
- Use redis lock demo client to invoke Layotto. The client will panic,and the client logs are as follows:
But the server logs are not detailed,you can't find out why:
What would you like to be added:
Add detailed log when grpc API error
Chinese:
目前Layotto配置配错了、连接redis异常时,client调分布式锁API会报错,但是从日志中看不出来为啥报错
需要优化日志,连接redis异常时打印更详细的日志,方便排查。
Metadata
Metadata
Assignees
Labels
good first issueGood for newcomersGood for newcomershelp wantedExtra attention is neededExtra attention is neededkind/easy