foxbei opened a new issue, #9110:
URL: https://github.com/apache/seatunnel/issues/9110

   ### Search before asking
   
   - [x] I had searched in the 
[issues](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22bug%22)
 and found no similar issues.
   
   
   ### What happened
   
   升级2.3.10后Metrices 地址打不开,之前2.3.9是正常可以访问的
   
   ### SeaTunnel Version
   
   2.3.10
   
   ### SeaTunnel Config
   
   ```conf
   seatunnel:
     engine:
       classloader-cache-mode: true
       history-job-expire-minutes: 1440
       backup-count: 1
       queue-type: blockingqueue
       print-execution-info-interval: 60
       print-job-metrics-info-interval: 60
       slot-service:
         dynamic-slot: true
       checkpoint:
         interval: 10000
         timeout: 60000
         storage:
           type: hdfs
           max-retained: 3
           plugin-config:
             namespace: /tmp/seatunnel/checkpoint_snapshot
             storage.type: hdfs
             fs.defaultFS: file:///
       telemetry:
         metric:
           enabled: true
         log:
           scheduled-deletion-enable: true
       http:
         enable-http: true
         port: 8080
         enable-dynamic-port: false
   ```
   
   ### Running Command
   
   ```shell
   curl http://{instanceHost}:5801/hazelcast/rest/instance/metrics
   ```
   
   ### Error Exception
   
   ```log
   curl: (56) Recv failure: Connection reset by peer
   ```
   
   ### Zeta or Flink or Spark Version
   
   _No response_
   
   ### Java or Scala Version
   
   _No response_
   
   ### Screenshots
   
   
![Image](https://github.com/user-attachments/assets/e381c7ab-5b3f-4f33-a170-48525d439200)
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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]

Reply via email to