GBase Database(GBase 8c): Why Three Deployment Layouts Have Different Configuration Fields

The three deployment layouts in GBase Database(GBase 8c) share a common configuration structure, but they do not use exactly the same fields, port assignments, or component counts.

That distinction is easy to overlook. A configuration file may look familiar enough to copy, but using the wrong deployment example can introduce unexpected topology and installation problems.

The key is understanding that the minimal, single-HA-group, and default distributed layouts are three independent configuration baselines, not three variations of one universal template.

1. Configuration Fields: What Exists and What Does Not?

Start with field presence.

The minimal and single-HA-group examples include:

• az for DN instances.
• proxy_port for CN and DN instances.

The official default distributed example includes neither field.

This is not necessarily an omission or an incomplete configuration. Each example is designed for its own deployment layout.

When adapting a GBase Database configuration, do not assume that every field in one example must also appear in another.

2. Port Assignments Are Layout-Specific

The differences are not limited to field presence. Port assignments also vary.

GTM agent_port:

• Single-HA-group example: 36667 and 46667.
• Default distributed example: 8001 and 8002.

DN port assignments:

In the default distributed example:

These values belong to their respective configuration examples. Do not blindly reuse port assignments when moving between deployment layouts. Always verify port availability and the actual configuration requirements for each host.

3. Compare the Three GBase Database Deployment Layouts

The component counts make the architectural differences easier to understand.

The pattern is clear:

• Minimal: One DN group with one instance, providing the smallest deployment configuration.
• Single HA Group: Adds DN replicas and more coordinator instances.
• Default Distributed: Expands the DN layer to two groups, each with three instances, while using different CN and gha_server counts.

These are architectural differences, not simply different numbers of machines.

4. Why Copying Between Layouts Is Risky

A common deployment shortcut is to take an existing gbase.yml, replace IP addresses and hostnames, and adjust component counts.

The problem is that changing counts does not automatically make the field structure correct.

For example:

• Keeping az or proxy_port when adapting a configuration to a layout whose official example does not include them.
• Removing fields without understanding their architectural purpose.
• Reusing GTM or DN port assignments from another deployment.
• Changing the number of DN instances without verifying the intended replica structure.

Missing fields can alter the declared topology. Extra fields should not be assumed to be harmless or automatically ignored.

GBase Database executes the configuration that is declared. Engineers remain responsible for ensuring that the configuration matches the intended deployment architecture.

5. The Better Approach: Start with the Correct Configuration Example

For GBase Database(GBase 8c), use this workflow:

1. Identify the target layout: minimal, single-HA-group, or default distributed.
2. Select the corresponding official gbase.yml example.
3. Replace IP addresses and hostnames section by section.
4. Update installation directories according to the target environment.
5. Verify component counts, field presence, and port assignments.
6. Review the final configuration before running gha_ctl install.

Avoid treating one deployment example as a universal template and adapting it by adding or deleting fields.

The three examples are designed for different scenarios. Each should be treated as a complete baseline for its intended layout.

6. Three Templates, One Simple Rule

The most important lesson is that GBase Database deployment configuration is layout-dependent.

The minimal layout, single-HA-group layout, and default distributed layout share a common structure, but their field sets and component arrangements are not interchangeable.

Remember three things:

• Field presence can differ between deployment layouts.
• Port assignments and component counts are layout-specific.
• The official example for the target architecture should always be the starting point.

Three deployment layouts, three configuration baselines. Pick the right one before changing a single IP address.