[jira] [Updated] (AMBARI-25471) After node reboot autostart of components takes too much time.
[
https://issues.apache.org/jira/browse/AMBARI-25471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-25471:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> After node reboot autostart of components takes too much time.
> --
>
> Key: AMBARI-25471
> URL: https://issues.apache.org/jira/browse/AMBARI-25471
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.6
>
> Attachments: AMBARI-25471.patch
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The reason for this is because ambari-agent does not know start order. And so
> if INFRA_SOLR with timeout of 10 hours starts before ZOOKEEPER, which it
> requires, it’s a big problem. As well as it blocks agent queue for any other
> commands. The solution is to run the commands in parallel. Also for fast
> autostart users might want to disable retry_gap: {noformat}/var/lib/ambari-
> server/resources/scripts/configs.py -a set -l localhost -n cluster_name -u
> admin -p admin -c cluster-env -k retry_gap_in_sec -v 0{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (AMBARI-25471) After node reboot autostart of components takes too much time.
[
https://issues.apache.org/jira/browse/AMBARI-25471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-25471:
Labels: pull-request-available (was: )
> After node reboot autostart of components takes too much time.
> --
>
> Key: AMBARI-25471
> URL: https://issues.apache.org/jira/browse/AMBARI-25471
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.6
>
> Attachments: AMBARI-25471.patch
>
>
> The reason for this is because ambari-agent does not know start order. And so
> if INFRA_SOLR with timeout of 10 hours starts before ZOOKEEPER, which it
> requires, it’s a big problem. As well as it blocks agent queue for any other
> commands. The solution is to run the commands in parallel. Also for fast
> autostart users might want to disable retry_gap: {noformat}/var/lib/ambari-
> server/resources/scripts/configs.py -a set -l localhost -n cluster_name -u
> admin -p admin -c cluster-env -k retry_gap_in_sec -v 0{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (AMBARI-25471) After node reboot autostart of components takes too much time.
[
https://issues.apache.org/jira/browse/AMBARI-25471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-25471:
-
Attachment: AMBARI-25471.patch
> After node reboot autostart of components takes too much time.
> --
>
> Key: AMBARI-25471
> URL: https://issues.apache.org/jira/browse/AMBARI-25471
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Fix For: 2.7.6
>
> Attachments: AMBARI-25471.patch
>
>
> The reason for this is because ambari-agent does not know start order. And so
> if INFRA_SOLR with timeout of 10 hours starts before ZOOKEEPER, which it
> requires, it’s a big problem. As well as it blocks agent queue for any other
> commands. The solution is to run the commands in parallel. Also for fast
> autostart users might want to disable retry_gap: {noformat}/var/lib/ambari-
> server/resources/scripts/configs.py -a set -l localhost -n cluster_name -u
> admin -p admin -c cluster-env -k retry_gap_in_sec -v 0{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (AMBARI-25471) After node reboot autostart of components takes too much time.
[
https://issues.apache.org/jira/browse/AMBARI-25471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-25471:
-
Status: Patch Available (was: Open)
> After node reboot autostart of components takes too much time.
> --
>
> Key: AMBARI-25471
> URL: https://issues.apache.org/jira/browse/AMBARI-25471
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Fix For: 2.7.6
>
> Attachments: AMBARI-25471.patch
>
>
> The reason for this is because ambari-agent does not know start order. And so
> if INFRA_SOLR with timeout of 10 hours starts before ZOOKEEPER, which it
> requires, it’s a big problem. As well as it blocks agent queue for any other
> commands. The solution is to run the commands in parallel. Also for fast
> autostart users might want to disable retry_gap: {noformat}/var/lib/ambari-
> server/resources/scripts/configs.py -a set -l localhost -n cluster_name -u
> admin -p admin -c cluster-env -k retry_gap_in_sec -v 0{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
