happyfish100 / happyfish100/fastdfs-client-java
fastdfs集群部署了两个tracker，手动停止一个tracker，使用客户端上传文件10个，5个成功，5个失败
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.6k
- Forks
- 891
- PR merge metrics
- No merged PRs in 30d
Description
org.csource.common.MyException: connect to server 172.xxx.xxx.xxx:22122 fail, emsg:Connection refused: connect
at org.csource.fastdfs.pool.ConnectionFactory.create(ConnectionFactory.java:26) ~[fastdfs-client-java-1.29.jar:?]
at org.csource.fastdfs.pool.ConnectionManager.getConnection(ConnectionManager.java:76) ~[fastdfs-client-java-1.29.jar:?]
at org.csource.fastdfs.pool.ConnectionPool.getConnection(ConnectionPool.java:32) ~[fastdfs-client-java-1.29.jar:?]
at org.csource.fastdfs.TrackerServer.getConnection(TrackerServer.java:36) ~[fastdfs-client-java-1.29.jar:?]
at org.csource.fastdfs.TrackerClient.listGroups(TrackerClient.java:485) ~[fastdfs-client-java-1.29.jar:?]
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the two-tracker setup and stop one tracker while uploading multiple files. Start with ConnectionFactory.java, ConnectionManager.java, ConnectionPool.java, TrackerServer.java, and TrackerClient.listGroups(), then trace how a refused connection is handled. Done means the expected behavior when one tracker is unavailable is documented and covered by a reproducible test or confirmed fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100