As 'hawq stop cluster --reload' didn't actually stop the cluster, so the next action 'hawq start cluster' will fail.
We should let the '--reload' option not available to the 'hawq restart' command. Another option is to re-write the 'hawq restart' command to make it cleaner. Regards, Radar On Fri, Mar 24, 2017 at 11:37 AM, Ma Hongxu <inte...@outlook.com> wrote: > hi all > does anyone know why this command failed? is it a bug? > 'reload' is a bit ambiguous, seems enter utility, refer: > http://hdb.docs.pivotal.io/212/hawq/reference/cli/ > admin_utilities/hawqrestart.html > > $ hawq restart cluster -a --reload > 20170324:11:31:05:026911 hawq_stop:interma-mbp:hma-[INFO]:-Prepare to do > 'hawq stop' > 20170324:11:31:05:026911 hawq_stop:interma-mbp:hma-[INFO]:-You can find > log in: > 20170324:11:31:05:026911 hawq_stop:interma-mbp:hma-[INFO]:-/Users/hma/ > hawqAdminLogs/hawq_stop_20170324.log > 20170324:11:31:05:026911 hawq_stop:interma-mbp:hma-[INFO]:-GPHOME is set > to: > 20170324:11:31:05:026911 hawq_stop:interma-mbp:hma-[ > INFO]:-/Users/hma/hawq/install > 20170324:11:31:05:026911 hawq_stop:interma-mbp:hma-[INFO]:-Reloading > configuration without restarting hawq cluster > 20170324:11:31:05:026911 hawq_stop:interma-mbp:hma-[INFO]:-No standby > host configured > 20170324:11:31:05:026911 hawq_stop:interma-mbp:hma-[INFO]:-Reload hawq > cluster > 20170324:11:31:05:026911 hawq_stop:interma-mbp:hma-[INFO]:-Reload hawq > master > 20170324:11:31:05:026911 hawq_stop:interma-mbp:hma-[INFO]:-Master > reloaded successfully > 20170324:11:31:05:026911 hawq_stop:interma-mbp:hma-[INFO]:-Reload hawq > segment > 20170324:11:31:05:026911 hawq_stop:interma-mbp:hma-[INFO]:-Reload > segments in list: ['localhost'] > 20170324:11:31:06:026911 hawq_stop:interma-mbp:hma-[INFO]:-Total segment > number is: 1 > .. > 20170324:11:31:08:026911 hawq_stop:interma-mbp:hma-[INFO]:-1 of 1 > segments reload successfully > 20170324:11:31:08:026911 hawq_stop:interma-mbp:hma-[INFO]:-Segments > reloaded successfully > 20170324:11:31:08:026911 hawq_stop:interma-mbp:hma-[INFO]:-Cluster > reloaded successfully > 20170324:11:31:08:026959 hawq_start:interma-mbp:hma-[INFO]:-Prepare to do > 'hawq start' > 20170324:11:31:08:026959 hawq_start:interma-mbp:hma-[INFO]:-You can find > log in: > 20170324:11:31:08:026959 hawq_start:interma-mbp:hma-[INFO]:-/Users/hma/ > hawqAdminLogs/hawq_start_20170324.log > 20170324:11:31:08:026959 hawq_start:interma-mbp:hma-[INFO]:-GPHOME is set > to: > 20170324:11:31:08:026959 hawq_start:interma-mbp:hma-[ > INFO]:-/Users/hma/hawq/install > 20170324:11:31:08:026959 hawq_start:interma-mbp:hma-[INFO]:-Reloading > configuration without restarting hawq cluster > 20170324:11:31:08:026959 hawq_start:interma-mbp:hma-[INFO]:-Gathering > information and validating the environment... > 20170324:11:31:08:026959 hawq_start:interma-mbp:hma-[INFO]:-No standby > host configured > 20170324:11:31:08:026959 hawq_start:interma-mbp:hma-[INFO]:-Start all the > nodes in hawq cluster > 20170324:11:31:08:026959 hawq_start:interma-mbp:hma-[INFO]:-Starting > master node 'localhost' > 20170324:11:31:08:026959 hawq_start:interma-mbp:hma-[INFO]:-Start master > service > 20170324:11:31:09:026959 hawq_start:interma-mbp:hma-[INFO]:-pg_ctl: > another server might be running; trying to start server anyway > pg_ctl: could not start server > Examine the log output. > 20170324:11:31:09:026959 hawq_start:interma-mbp:hma-[ERROR]:-Master start > failed, exit > > > -- > Regards, > Hongxu. >
