Skip to content

Conversation

gfphoenix78
Copy link
Contributor

When the reader process acquires a LOCK, it requires to get the writer PROC. For first time, the reader may not get the writer PROC. It's unknown why the reader can't find the writer. Wait a little more time for it.

+DETAIL:  connection to server at "172.18.0.2", port 7004 failed: FATAL:  reader could not find writer proc entry
+DETAIL:  lock [0,1260] AccessShareLock 0. Probably because writer gang is gone somehow. Maybe try rerunning.
+ERROR:  failed to acquire resources on one or more segments

Type of Change

  • Bug fix (non-breaking change)
  • New feature (non-breaking change)
  • Breaking change (fix or feature with breaking changes)
  • Documentation update

Test Plan

  • Unit tests added/updated
  • Integration tests added/updated
  • Passed make installcheck
  • Passed make -C src/test installcheck-cbdb-parallel

Impact

Performance:

User-facing changes:

Dependencies:

Checklist

Additional Context

CI Skip Instructions


When the reader process acquires a LOCK, it requires to get the writer
PROC. For first time, the reader may not get the writer PROC. It's unknown
why the reader can't find the writer. Wait a little more time for it.
volatile PGPROC * proc = FindProcByGpSessionId(gp_session_id);
int count = 0;
while(proc==NULL && count < 5)
while(proc==NULL && count < 200)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

which pipeline happened ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The internal pipeline that is not in github.

@avamingli
Copy link
Contributor

​​Isn't the root cause simply a lack of resources? ​`failed to acquire resources on one or more segments?

@gfphoenix78
Copy link
Contributor Author

​​Isn't the root cause simply a lack of resources? ​`failed to acquire resources on one or more segments?

Not a root cause.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants