Ken Krugler
09/22/2021, 12:03 AMbin/pinot-admin.sh
) wasn’t stopping when batch ingest failed. In looking at PinotAdministrator
, it seems like you have to set the pinot.admin.system.exit
System property to true
for this to work. Any reason why pinot-admin.sh
shouldn’t be setting this to true if JAVA_OPTS
isn’t specified? E.g. something like
if [ -z "$JAVA_OPTS" ] ; then
ALL_JAVA_OPTS="-Xms4G -Dlog4j2.configurationFile=conf/log4j2.xml -Dpinot.admin.system.exit=true"
else
ALL_JAVA_OPTS=$JAVA_OPTS
fi
Ken Krugler
09/22/2021, 12:06 AMLaunchDataIngestionJobCommand
has its own main()
method. Any reason why it needs a main method?Kishore G
Kishore G
Ken Krugler
09/22/2021, 12:15 AMpinot-admin.sh
, right?Kishore G
Mayank
Xiang Fu
Ken Krugler
09/24/2021, 9:28 PMpinot.admin.system.exit=true
(no change to the default setting in the PinotAdministrator Java code). Do you think that might still cause a problem? Asking because I did see quickstart test failed on the build machine. But I tried quick-start-batch.sh
on my Mac using a build with my change, and that worked.Xiang Fu
Xiang Fu
Xiang Fu
Ken Krugler
09/24/2021, 10:17 PMbin/pinot-admin.sh StartZookeeper
command used by the CI quickstart spun up, versus the regular return from PinotAdministrator will hang due to the thread. I’m thinking I should modify the CI quickstart to set JAVA_OPS to not enable the system exit (and use less memory for the JVM than the regular settings)Ken Krugler
09/24/2021, 10:28 PMXiang Fu
Ken Krugler
09/25/2021, 4:36 PM.github/workflows/scripts/.pinot_quickstart.sh
to set JAVA_OPTS
explicitly to something that didn’t set the pinot.admin.system.exit
System property to true
, and that seems to work (all tests now pass)