apalan60 opened a new pull request, #20608:
URL: https://github.com/apache/kafka/pull/20608

   ## Purpose
   
   Allow running multiple Kafka System Test clusters on the same host without 
conflicts.
   
   ---
   
   ## Background
   
   - `ducker-ak up` creates `cluster.json` and binds debug port `5678:5678` on 
the first node.
   -  Only one cluster can run per host because a second attempt fails due to 
fixed names and a static debug port.
   
   ---
   
   ## Key Changes
   
   **Prefix isolation**
   - Usage: `--prefix <string>` CLI option or `DUCKER_PREFIX` environment 
variable to set a unique cluster prefix.
   - Effects when prefix is provided:
       - Network: `<prefix>-ducknet`
       - Containers: `<prefix>-ducker01`, `<prefix>-ducker02`, ...
       - Cluster file: `cluster.<prefix>.json`; tests read the matching file.
       - Debug port: with a prefix, the first node of the cluster is assigned a 
host port automatically when running `ducker-ak up` or `ducker-ak test`. In 
this auto-assigned mode, the chosen host port is written to 
`debug-port.<prefix>.txt`. If a specific port is required, it can be set using 
the `--debug-port` CLI option or the `DUCKER_DEBUGPY_PORT` environment variable.
   - Without prefix:  behavior remains (`5678:5678`, `cluster.json`, `ducknet`, 
`ducker...`).
   
   ---
   
   ## Compatibility
   
   | Case      | Host:Container | Cluster file            | Network            
| Names                                    | Debug Port file           |
   
|-----------|----------------|-------------------------|--------------------|------------------------------------------|---------------------------|
   | No prefix | `5678:5678`    | `cluster.json`          | `ducknet`          
| `ducker01`, `ducker02`                   | x                         |
   | Prefix    | `random:5678`  | `cluster.<prefix>.json` | `<prefix>-ducknet` 
| `<prefix>-ducker01`, `<prefix>-ducker02` | `debug-port.<prefix>.txt` |
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to