vsbace opened a new issue, #1404:
URL: https://github.com/apache/cloudberry/issues/1404

   ### Apache Cloudberry version
   
   [apache-cloudberry-2.0.0-incubating]
   (https://github.com/apache/cloudberry/releases/tag/2.0.0-incubating)
   
   ### What happened
   
   By network problem some primary segments can not be avilable and switched to 
FAILED state.
   When network problem was sovled i can try to recover failed segment and 
happen the next problem:
   `
   Continue with segment recovery procedure Yy|Nn (default=N):
   > y
   20251017:10:58:19:792595 gprecoverseg:cbdb01:gpadmin-[INFO]:-Starting to 
create new pg_hba.conf on primary segments
   20251017:10:58:20:792595 gprecoverseg:cbdb01:gpadmin-[INFO]:-Successfully 
modified pg_hba.conf on primary segments to allow replication connections
   20251017:10:58:20:792595 gprecoverseg:cbdb01:gpadmin-[INFO]:-1 segment(s) to 
recover
   20251017:10:58:20:792595 gprecoverseg:cbdb01:gpadmin-[INFO]:-Ensuring 1 
failed segment(s) are stopped
   **20251017:10:58:21:792595 gprecoverseg:cbdb01:gpadmin-[WARNING]:-Unable to 
determine if /u00/cbdb/primary/gpseg7 is symlink. Assuming it is not symlink**
   **20251017:10:58:21:792595 
gprecoverseg:cbdb01:gpadmin-[CRITICAL]:-gprecoverseg failed. (Reason='invalid 
literal for int() with base 10:** "# 
--------------------------------------------------------------------\n# NOTICE 
from the Apache Cloudberry PPMC\n# 
--------------------------------------------------------------------\n# This 
file u') exiting...
   `
   Yarly i already happened this problem in Cloudberry 1.6 and found WA,
   first i need to delete data folder for segment and recover procedure 
processed successfully.
   But i think when i have 15 primary segments i can use WA, but on PRod we 
have more that segments and it will be a big problem.  
   
   ### What you think should happen instead
   
   _No response_
   
   ### How to reproduce
   
   - one or more primary segments was failed and switched to mirror segmets
   - we can try to recover segments by command "GPRECOVERSEG" or "GPRECOVERSEG 
-F" and catch the same problem
   
   ### Operating System
   
   Debian 12.0
   
   ### Anything else
   
   This problem occured every time, every run gprecoverseg.
   
   ### 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://github.com/apache/cloudberry/blob/main/CODE_OF_CONDUCT.md).
   


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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to