[Bug] incosistent state of pg_operator after init CB cluster

Offen
#2,169 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 2 Tagen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
45/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
c, postgresql
Bereich
databases

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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
Vorherrschende Sprache
C
Sterne
1.4k
Forks
273
Ø Merge
4 T. 6 Std.
Gemergte PRs (30 T.)
105

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus apache/cloudberry

Alle Issues in apache/cloudberry

Ähnliche Issues

Weitere Issues zu C

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.