zabetak commented on PR #5546: URL: https://github.com/apache/hive/pull/5546#issuecomment-2698205850
I checked the errors on the JDBC storage handler and it seems that there is a port conflict. ``` docker: Error response from daemon: driver failed programming external connectivity on endpoint qtestExternalDB-PostgresExternalDB (ca2805ffc433805e46089f6b59ef9568ff600690166dbc78d4f8b03b75c5b342): Bind for 0.0.0.0:5432 failed: port is already allocated. 2025-02-18T20:36:05,092 INFO [main] externalDB.AbstractExternalDB: Going to run: docker events --since 24h --until 0s 2025-02-18T20:36:05,193 INFO [main] externalDB.AbstractExternalDB: Result lines#: 1745(stdout);0(stderr) 2025-02-18T20:36:05,193 INFO [main] externalDB.AbstractExternalDB: Stdout from proc: 2025-02-18T20:10:26.071854311-08:00 image pull zabetak/postgres-tpcds-metastore:1.3 (name=zabetak/postgres-tpcds-metastore) 2025-02-18T20:10:28.026788933-08:00 volume create 05d298163781df71069780ee94ceab6aacc4b2836e4bbf7a74580fa0cf0e2545 (driver=local) 2025-02-18T20:10:28.318006782-08:00 container create e5c318c04c2201b1000e2067cee5d602717efb83c207bd5eb9a85c72802fb9cd (image=zabetak/postgres-tpcds-metastore:1.3, name=metastore-test-postgres-install) 2025-02-18T20:10:28.447482168-08:00 network connect d1bc6735d79946310965b8826c3660eca26da542190ad7cf24fee937729708c5 (container=e5c318c04c2201b1000e2067cee5d602717efb83c207bd5eb9a85c72802fb9cd, name=bridge, type=bridge) 2025-02-18T20:10:28.450456682-08:00 volume mount 05d298163781df71069780ee94ceab6aacc4b2836e4bbf7a74580fa0cf0e2545 (container=e5c318c04c2201b1000e2067cee5d602717efb83c207bd5eb9a85c72802fb9cd, destination=/var/lib/postgresql/data, driver=local, propagation=, read/write=true) 2025-02-18T20:10:28.889087924-08:00 container start e5c318c04c2201b1000e2067cee5d602717efb83c207bd5eb9a85c72802fb9cd (image=zabetak/postgres-tpcds-metastore:1.3, name=metastore-test-postgres-install) 2025-02-18T20:10:28.905748246-08:00 container kill e5c318c04c2201b1000e2067cee5d602717efb83c207bd5eb9a85c72802fb9cd (image=zabetak/postgres-tpcds-metastore:1.3, name=metastore-test-postgres-install, signal=23) 2025-02-18T20:36:02.864436672-08:00 image pull postgres:9.3 (name=postgres) 2025-02-18T20:36:04.888710014-08:00 volume create 214bbd27000e8750f8c0e8fd19719f272fc0fbe06983e65783a429d57d498c76 (driver=local) 2025-02-18T20:36:04.927049756-08:00 container create cf1646e815381ee1117f9e25dce4e7fe7d25824c2e266615e384be637d815e82 (image=postgres:9.3, name=qtestExternalDB-PostgresExternalDB) ``` The creation of the Postgres container `ca2805ffc433805e46089f6b59ef9568ff600690166dbc78d4f8b03b75c5b342` fails cause there is another Postgres container already running in another split and occupies the port 5432. If my understanding is correct the problem is not specific to the changes here but can technically appear anytime if we happen to run two tests that are using a dockerized Postgres (or another DB) at the same time in different splits. Unfortunately, at the moment we don't have a mechanism to assign ports in a more dynamic way. My theory has some gaps though cause I would expect the chances to hit this race condition to be rather low. -- 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: gitbox-unsubscr...@hive.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: gitbox-unsubscr...@hive.apache.org For additional commands, e-mail: gitbox-h...@hive.apache.org
