[
https://issues.apache.org/jira/browse/HAWQ-617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15225610#comment-15225610
]
ASF GitHub Bot commented on HAWQ-617:
-------------------------------------
Github user radarwave commented on the pull request:
https://github.com/apache/incubator-hawq/pull/546#issuecomment-205625040
@bhuvnesh2703 Now 'hawq stop' works just like '--ignore-bad-hosts' always
enabled. But 'hawq stop' should only check if hawq process is running on the
node, it should fail if the node is not available. We will fix that in another
jira.
It's ok to apply the 'option' to 'hawq stop' next time when we fixing above
hawq stop check issues. But if it convenience, please also apply it to 'hawq
stop' so we can keep the option works for both start and stop. Thanks.
> Add a flag to hawq config to allow skipping hosts on which ssh fails and
> continue with syncing configurations files
> -------------------------------------------------------------------------------------------------------------------
>
> Key: HAWQ-617
> URL: https://issues.apache.org/jira/browse/HAWQ-617
> Project: Apache HAWQ
> Issue Type: Bug
> Reporter: bhuvnesh chaudhary
> Assignee: Lei Chang
>
> Add a flag to hawq config to allow skipping hosts on which ssh fails and
> continue with syncing configurations files.
> Currently, if there is any one bad host, sync operations fails. Hawq activate
> standby uses hawq config to update hawq-site.xml configuration, however if
> the active master host is down, it fails.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
