Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

cbcopy migration from Greenplum 6.21.0 to Apache Cloudberry 2.1.0 fails with COPY errors

Offen
  • Stimmt etwas nicht?
#2,213 4 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
35/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
c, postgresql
Bereich
databases

Rechercherichtung

Start by reviewing the cbcopy migration logs and the COPY failures reported for affected tables; the issue does not name source files or tests. Compare the source and target row counts and investigate the Broken pipe errors using the provided Greenplum 6.21.0 and Cloudberry 2.1.0 environment details. Done means identifying a reproducible cause and documenting a resolution or retry approach; detailed logs and commands are still needed.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Hi Apache Cloudberry Team,

We are migrating a large database from Greenplum Database 6.21.0 to Apache Cloudberry 2.1.0-incubating using the cbcopy utility.

During the migration, we encountered multiple table copy failures. The migration process reports errors such as:

could not write to COPY program: Broken pipe

Copy to affected rows X are not equal to copy from affected rows 0

Several tables failed to copy successfully.

We would appreciate your help in identifying the root cause and recommended resolution.

Environment:

Source database: Greenplum 6.21.0
Source os: CentOS 7

Target database: Apache Cloudberry 2.1.0-incubating

Source database size: Approximately 2 TB

Target OS: Oracle Linux 9.8

Migration utility: cbcopy

Steps to reproduce:

Configure the source Greenplum and target Cloudberry clusters.

Configure the required network connectivity and authentication.

Execute the cbcopy migration utility.

Observe the migration logs.

Expected behavior:

The cbcopy utility should copy all supported database objects and data successfully from Greenplum to Cloudberry.

Actual behavior:

Multiple tables fail during the COPY operation. Some tables report a mismatch between the number of rows copied from the source and the number of rows inserted into the target.

Questions:

What are the possible causes of the Broken pipe errors during cbcopy?

Is there a known issue with cbcopy in Cloudberry 2.1.0-incubating?

Are there any recommended configuration changes or patches?

Is there a recommended way to resume or retry failed table copies without restarting the entire migration?

We can provide the detailed logs, configuration files, and migration commands for further investigation.

Thank you.

Vorherrschende Sprache
C
Sterne
1.4k
Forks
265
Ø Merge
3 T. 17 Std.
Gemergte PRs (30 T.)
68

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.