h2o cluster names are not unique enough in gradle builds, to avoid unexpected cluster formations

Description

Since we have many-many simultaneous builds done by jenkins, I started getting worried about whether I accidentally got a cross-site cloud build

Looking at a gradlew build it looks like it uses a common prefix like "junit_cluster_" and then pid number local to the machine.

This is not unique enough to guarantee no unexpected cloud building from other machines or sites doesn't happen

should be simple to change this to a larger random number, or add the hostname in there. Username is not useful, since they are all jenkins

any cloud building should worry about this...for instance run.py. I didn't check a run.py cloud build

Using a flatfile doesn't guarantee that only those guys connect? (I think?) we require cluster name uniqueness

this shows ps -aux that shows some cluster names (junit_cluster_15584) for instance

jenkins 13964 159 1.4 13818240 1958476 ? SNl 22:31 1:38 java -ea -Xmx2g -Xms2g -cp build/libs/h2o-algos-test.jar:build/libs/h2o-algos.jar:../h2o-core/build/libs/h2o-core-test.jar:../h2o-core/build/libs/h2o-core.jar:../h2o-genmodel/build/libs/h2o-genmodel.jar:../lib/* water.H2O -name junit_cluster_13948 -baseport 44000
jenkins 13965 159 1.0 13234584 1375212 ? SNl 22:31 1:38 java -ea -Xmx2g -Xms2g -cp build/libs/h2o-algos-test.jar:build/libs/h2o-algos.jar:../h2o-core/build/libs/h2o-core-test.jar:../h2o-core/build/libs/h2o-core.jar:../h2o-genmodel/build/libs/h2o-genmodel.jar:../lib/* water.H2O -name junit_cluster_13948 -baseport 44000
jenkins 13966 137 0.8 12455348 1069884 ? SNl 22:31 1:24 java -ea -Xmx2g -Xms2g -cp build/libs/h2o-algos-test.jar:build/libs/h2o-algos.jar:../h2o-core/build/libs/h2o-core-test.jar:../h2o-core/build/libs/h2o-core.jar:../h2o-genmodel/build/libs/h2o-genmodel.jar:../lib/* water.H2O -name junit_cluster_13948 -baseport 44000
jenkins 13967 175 1.6 14210428 2235500 ? SNl 22:31 1:48 java -ea -Xmx2g -Xms2g -cp build/libs/h2o-algos-test.jar:build/libs/h2o-algos.jar:../h2o-core/build/libs/h2o-core-test.jar:../h2o-core/build/libs/h2o-core.jar:../h2o-genmodel/build/libs/h2o-genmodel.jar:../lib/* water.H2O -name junit_cluster_13948 -baseport 44000
jenkins 13970 207 1.8 12580724 2407684 ? SNl 22:31 2:08 java -ea -Xmx2g -Xms2g -cp build/libs/h2o-algos-test.jar:build/libs/h2o-algos.jar:../h2o-core/build/libs/h2o-core-test.jar:../h2o-core/build/libs/h2o-core.jar:../h2o-genmodel/build/libs/h2o-genmodel.jar:../lib/* -Dai.h2o.name=junit_cluster_13948 -Dai.h2o.baseport=44000 4000

Activity

Show:
Bill Gallmeister
December 10, 2016, 12:15 AM

I resolved these.

Won't Fix
Your pinned fields
Click on the next to a field label to start pinning.

Assignee

Bill Gallmeister

Reporter

Kevin Normoyle

CustomerVisible

No