[Bug] incosistent state of pg_operator after init CB cluster

Aberta
#2,169 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 2 dias

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
45/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
c, postgresql
Domínio
databases

Direção de pesquisa

Start by reading the GPCHECKCAT output and the cluster initialization path that populates pg_operator catalogs across the coordinator and segments; the issue does not name source files or tests. Compare oprrest and oprjoin for the listed operator OIDs after creating a cluster and running GPCHECKCAT -O DBNAME. Done means those catalog values match on the coordinator and all segments.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

type: Bug
Apache Cloudberry version

PostgreSQL 14.4 (Apache Cloudberry 2.1.0-incubating build dev) on x86_64-pc-linux-gnu, compiled by gcc (Astra 1.8.2) , 64-bit compiled

What happened

After we are initialyzed CBDB cluster we found some inconsistent of PG catalog by checking by run GPCHECKCAT command on main database in online mode.
We catch the next errors:
`----------------------------------------------------
Object oid: 17472
Table name: pg_operator

Name of test which found this issue: inconsistent_pg_operator
         oprrest is '5040' on content -1 (qc1.local:5432)
         oprrest is '1302' on all other segments
         oprjoin is '5041' on content -1 (qc1.local:5432)
         oprjoin is '1303' on all other segments

Object oid: 17476
Table name: pg_operator

Name of test which found this issue: inconsistent_pg_operator
         oprrest is '5040' on content -1 (qc1.local:5432)
         oprrest is '1302' on all other segments
         oprjoin is '5041' on content -1 (qc1.local:5432)
         oprjoin is '1303' on all other segments

Object oid: 17534
Table name: pg_operator

Name of test which found this issue: inconsistent_pg_operator
         oprrest is '5040' on content -1 (qc1.local:5432)
         oprrest is '1302' on all other segments
         oprjoin is '5041' on content -1 (qc1.local:5432)
         oprjoin is '1303' on all other segments

Object oid: 17477
Table name: pg_operator

Name of test which found this issue: inconsistent_pg_operator
         oprrest is '5040' on content -1 (qc1.local:5432)
         oprrest is '1302' on all other segments
         oprjoin is '5041' on content -1 (qc1.local:5432)
         oprjoin is '1303' on all other segments

Object oid: 17535
Table name: pg_operator

Name of test which found this issue: inconsistent_pg_operator
         oprrest is '5040' on content -1 (qc1.local:5432)
         oprrest is '1302' on all other segments
         oprjoin is '5041' on content -1 (qc1.local:5432)
         oprjoin is '1303' on all other segments

`

This problem was repeated every time when we are try to create CB cluster again in many times.

What you think should happen instead

Possible is was in internal cluster creating logic.

How to reproduce

After creating new Cluster try to run GPCHECKCAT -O DBNAME

Operating System

Astra 1.8.2 analog Debain 12

Anything else

Some information from PG operator on problem DB

Image
Are you willing to submit PR?
  • Yes, I am willing to submit a PR!
Code of Conduct
Linguagem predominante
C
Estrelas
1.4k
Forks
273
Merge médio
4d 6h
PRs com merge (30d)
105

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de apache/cloudberry

Todas as issues de apache/cloudberry

Issues semelhantes

Mais issues de C

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.