I am seeing

Question

I am seeing and also failing with the same error message in JDK 1 8 Quickstart JDK 11 13 Quickstart passes So this must be a generic build issue rather than something specific to changes in these PRs Error messages given below Any idea what has changed here ``` message BrokerResourceMissingError errorCode 410 Executing command StopProcess controller server broker zooKeeper 18885 + true 18886 + kill 0 3750 18887 github workflows scripts pinot quickstart sh line 71 kill 3750 No such process 18888 + break 18889 + rm rf tmp PinotAdmin zkData 18890 + 0 eq 0 18891 Batch Quickstart failed Cannot get correct result for count star query 18892 + echo Batch Quickstart failed Cannot get correct result for count star query 18893 + exit 1 18894 Error Process completed with exit code 1 ```

Mayank · Answer

Seems the quickstart test has become brittle recently Some JDK version keeps failing randomly and passes on rerun

Jackie · Answer

Github Actions test vm only provides 2 cores <https docs github com en actions using github hosted runners about github hosted runners supported runners and hardware resources>

Jackie · Answer

I suspect enabling the lead controller resources by default adds some extra workload on the controller which causes the issue

Jackie · Answer

Let s see if extending the setup time fixes the issue <https github com apache incubator pinot pull 6746>

Mayank · Answer

It was approved so I took the liberty to merge the PR

Mayank · Answer

< Jackie> ^^

Jackie · Answer

Was planning to run tests more times lol Let s see if the problem gone in master

Neha Pawar · Answer

doesnt look like it s helping

Jackie · Answer

Yeah same issue

Mayank · Answer

Argh

Xiang Fu · Answer

seems this time it s unit test failure

Xiang Fu · Answer

pinot spark stuck out tongue

Jackie · Answer

There is another quick start test failure <https github com apache incubator pinot pull 6745 checks check run id=2280618667>

Amrish Lal · Answer

`Pinot Quickstart on JDK 1 8` is still failing I am wondering what are the options here Should we consider removing this check Is someone still using JDK1 8

Neha Pawar · Answer

but its not just 1 8

Neha Pawar · Answer

it is randomly failing for all of the quickstart with the differnet jdk versions

Amrish Lal · Answer

I think the `BrokerResourceMissingError` exception means that Broker doesn t know about the `baseballStats` table Exception is thrown in `BrokerResponseNative java`

Amrish Lal · Answer

Maybe this step is failing looking at logs but I don t see any error messages associated with this ```Executing command AddTable tableConfigFile tmp 1617896415131 baseballStats 1617896415254 config schemaFile tmp 1617896375079 baseballStats baseballStats schema json controllerProtocol http controllerHost fv az201 716 controllerPort 9000 user null exec```

Jack · Answer

< Amrish Lal> can you try to rebase your code with latest master branch I think jackie has merged some PR to increase the setup time in the test

Neha Pawar · Answer

i dont think that is helping i rebased and still see the same issue

Jackie · Answer

The issue is still there Basically the controller rest endpoint is not responding thus the table is not created I m trying to dig into it

Jackie · Answer

We can ignore the quick start tests for now Please make sure the unit tests and integration tests pass before merging