Xuanwo opened a new issue, #1783: URL: https://github.com/apache/kvrocks/issues/1783
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/kvrocks/issues) and found no similar issues. ### Version 2.6.0 ### Minimal reproduce step Fork https://github.com/apache/incubator-opendal and running it's kvrocks test ```yaml kvrocks: runs-on: ubuntu-latest services: redis: image: apache/kvrocks ports: - 6379:6666 steps: - uses: actions/checkout@v3 - name: Setup Rust toolchain uses: ./.github/actions/setup with: need-nextest: true - name: Test shell: bash working-directory: core run: cargo nextest run redis --features services-redis env: OPENDAL_REDIS_TEST: on OPENDAL_REDIS_ENDPOINT: tcp://127.0.0.1:6379 OPENDAL_REDIS_ROOT: / OPENDAL_REDIS_DB: 0 ``` ### What did you expect to see? Test pass (this test is stable until today) ### What did you see instead? All operations returns `Broken Pipe`. ```shell running 1 test 2023-09-26T08:38:31.776841Z DEBUG opendal::services: service=redis operation=write path=bd4f0ac5-f137-43b5-a6fb-5a7f56993d1b -> started at core/src/layers/logging.rs:332 2023-09-26T08:38:31.777030Z DEBUG opendal::services: service=redis operation=write path=bd4f0ac5-f137-43b5-a6fb-5a7f56993d1b -> start writing at core/src/layers/logging.rs:344 2023-09-26T08:38:31.847986Z ERROR opendal::services: service=redis operation=Writer::close path=bd4f0ac5-f137-43b5-a6fb-5a7f56993d1b written=1870076B -> data close failed: Unexpected (temporary) at Writer::close => I/O error Context: service: redis path: bd4f0ac5-f137-43b5-a6fb-5a7f56993d1b Source: Broken pipe (os error 32) ```  https://github.com/apache/incubator-opendal/actions/runs/6309725180/job/17131514618 ### Anything Else? _No response_ ### Are you willing to submit a PR? - [ ] I'm willing to submit a PR! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
