Repository navigation
[Docs]: requested timeline 2 is not a child of this server's history #7268
Description
Is there an existing issue already for your request/idea?
- I have searched for an existing issue, and could not find anything. I believe this is a new documentation enhancement to be evaluated.
What problem in the existing documentation this issue aims to solve?
Hi!
What to do in such a situation ? The replicas don't start, they write this error
{"level":"info","ts":"2025-03-31T14:03:01Z","logger":"postgres","msg":"record","logging_pod":"prod-psp-db-7","record":{"log_time":"2025-03-31 14:03:01.105 UTC","process_id":"31","session_id":"67eaa088.1f","session_line_num":"8","session_start_time":"2025-03-31 14:02:48 UTC","transaction_id":"0","error_severity":"FATAL","sql_state_code":"XX000","message":"requested timeline 2 is not a child of this server's history","detail":"Latest checkpoint is at 104/60806880 on timeline 1, but in the history of the requested timeline, the server forked off from that timeline at 100/890F6D08.","backend_type":"startup","query_id":"0"}}
Describe what additions need to be done to the documentation
No response
Describe what pages need to change in the documentation, if any
No response
Describe what pages need to be removed from the documentation, if any
No response
Additional context
No response
Backport?
Yes
Code of Conduct
- I agree to follow this project's Code of Conduct
Activity
soulaw-mkii commentedon Apr 12, 2025
I faced the same issue on the replica node 2 and node 3 after I hibernate/rehydrate the cluster, while node 1 as the master is running fine.
sbidoul commentedon Jun 7, 2025
I'm facing this after an in place major upgrade from 16 to 17 using cnpg 1.26.
The upgrade went fine, the primary is up, the first replica join job works fine, but this error happens when starting the replica pod.
sbidoul commentedon Jun 7, 2025
I think my issue was due to the upgraded cluster being on timeline 1, while the backup had wals of the previous version cluster on timeline 5. I updated my backup configuration to use a different
serverNamewhich resolved the issue.derTobsch commentedon Jun 17, 2025
I am facing the same error. Thanks, @sbidoul, I did the same and it also resolved my problem. Should I have made something different while upgrading? I stopped all application pods, then changed the image. Where the cluster not in sync?
github-actions commentedon Aug 17, 2025
This issue is stale because it has been open for 60 days with no activity.
github-actions commentedon Sep 3, 2025
This issue was closed because it has been inactive for 14 days since being marked as stale.