[jira] [Updated] (AMBARI-18619) Optimize Service Checks to it picks a random host and prefers hosts with 0 active commands

2016-10-19 Thread Alejandro Fernandez (JIRA)

 [ 
https://issues.apache.org/jira/browse/AMBARI-18619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alejandro Fernandez updated AMBARI-18619:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Pushed to trunk, commit 365a5d638fb7edcd4ff5561b29f0efb66fa5b881
branch-2.5, commit 68d4da47b84301b4688fce5eef1360a779f1849a

> Optimize Service Checks to it picks a random host and prefers hosts with 0 
> active commands
> --
>
> Key: AMBARI-18619
> URL: https://issues.apache.org/jira/browse/AMBARI-18619
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18619.branch-2.5.patch, AMBARI-18619.trunk.patch
>
>
> STR:
> * Deploy a 3-node cluster with Ambari 2.4 and HDP 2.5 with clients on every 
> host.
> * Run multiple service checks in parallel, but notice that they typically run 
> on the same 1 or 2 hosts.
> Currently, Ambari relies on getting the list of candidate hosts from the DB 
> and excludes all hosts that are in maintenance mode. From that list, it picks 
> the first host that is healthy (i.e., heartbeating). This means that the 
> logic does not pick a random host.
> Instead, Ambari should always pick a random host and prefer to schedule on 
> hosts that have 0 in-progress commands.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (AMBARI-18619) Optimize Service Checks to it picks a random host and prefers hosts with 0 active commands

2016-10-19 Thread Alejandro Fernandez (JIRA)

 [ 
https://issues.apache.org/jira/browse/AMBARI-18619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alejandro Fernandez updated AMBARI-18619:
-
Attachment: (was: AMBARI-18619.trunk.patch)

> Optimize Service Checks to it picks a random host and prefers hosts with 0 
> active commands
> --
>
> Key: AMBARI-18619
> URL: https://issues.apache.org/jira/browse/AMBARI-18619
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18619.branch-2.5.patch, AMBARI-18619.trunk.patch
>
>
> STR:
> * Deploy a 3-node cluster with Ambari 2.4 and HDP 2.5 with clients on every 
> host.
> * Run multiple service checks in parallel, but notice that they typically run 
> on the same 1 or 2 hosts.
> Currently, Ambari relies on getting the list of candidate hosts from the DB 
> and excludes all hosts that are in maintenance mode. From that list, it picks 
> the first host that is healthy (i.e., heartbeating). This means that the 
> logic does not pick a random host.
> Instead, Ambari should always pick a random host and prefer to schedule on 
> hosts that have 0 in-progress commands.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (AMBARI-18619) Optimize Service Checks to it picks a random host and prefers hosts with 0 active commands

2016-10-19 Thread Alejandro Fernandez (JIRA)

 [ 
https://issues.apache.org/jira/browse/AMBARI-18619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alejandro Fernandez updated AMBARI-18619:
-
Attachment: AMBARI-18619.branch-2.5.patch
AMBARI-18619.trunk.patch

> Optimize Service Checks to it picks a random host and prefers hosts with 0 
> active commands
> --
>
> Key: AMBARI-18619
> URL: https://issues.apache.org/jira/browse/AMBARI-18619
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18619.branch-2.5.patch, AMBARI-18619.trunk.patch
>
>
> STR:
> * Deploy a 3-node cluster with Ambari 2.4 and HDP 2.5 with clients on every 
> host.
> * Run multiple service checks in parallel, but notice that they typically run 
> on the same 1 or 2 hosts.
> Currently, Ambari relies on getting the list of candidate hosts from the DB 
> and excludes all hosts that are in maintenance mode. From that list, it picks 
> the first host that is healthy (i.e., heartbeating). This means that the 
> logic does not pick a random host.
> Instead, Ambari should always pick a random host and prefer to schedule on 
> hosts that have 0 in-progress commands.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (AMBARI-18619) Optimize Service Checks to it picks a random host and prefers hosts with 0 active commands

2016-10-19 Thread Alejandro Fernandez (JIRA)

 [ 
https://issues.apache.org/jira/browse/AMBARI-18619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alejandro Fernandez updated AMBARI-18619:
-
Attachment: (was: AMBARI-18619.branch-2.5.patch)

> Optimize Service Checks to it picks a random host and prefers hosts with 0 
> active commands
> --
>
> Key: AMBARI-18619
> URL: https://issues.apache.org/jira/browse/AMBARI-18619
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18619.branch-2.5.patch, AMBARI-18619.trunk.patch
>
>
> STR:
> * Deploy a 3-node cluster with Ambari 2.4 and HDP 2.5 with clients on every 
> host.
> * Run multiple service checks in parallel, but notice that they typically run 
> on the same 1 or 2 hosts.
> Currently, Ambari relies on getting the list of candidate hosts from the DB 
> and excludes all hosts that are in maintenance mode. From that list, it picks 
> the first host that is healthy (i.e., heartbeating). This means that the 
> logic does not pick a random host.
> Instead, Ambari should always pick a random host and prefer to schedule on 
> hosts that have 0 in-progress commands.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (AMBARI-18619) Optimize Service Checks to it picks a random host and prefers hosts with 0 active commands

2016-10-19 Thread Alejandro Fernandez (JIRA)

 [ 
https://issues.apache.org/jira/browse/AMBARI-18619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alejandro Fernandez updated AMBARI-18619:
-
Attachment: AMBARI-18619.branch-2.5.patch
AMBARI-18619.trunk.patch

> Optimize Service Checks to it picks a random host and prefers hosts with 0 
> active commands
> --
>
> Key: AMBARI-18619
> URL: https://issues.apache.org/jira/browse/AMBARI-18619
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18619.branch-2.5.patch, AMBARI-18619.trunk.patch
>
>
> STR:
> * Deploy a 3-node cluster with Ambari 2.4 and HDP 2.5 with clients on every 
> host.
> * Run multiple service checks in parallel, but notice that they typically run 
> on the same 1 or 2 hosts.
> Currently, Ambari relies on getting the list of candidate hosts from the DB 
> and excludes all hosts that are in maintenance mode. From that list, it picks 
> the first host that is healthy (i.e., heartbeating). This means that the 
> logic does not pick a random host.
> Instead, Ambari should always pick a random host and prefer to schedule on 
> hosts that have 0 in-progress commands.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (AMBARI-18619) Optimize Service Checks to it picks a random host and prefers hosts with 0 active commands

2016-10-19 Thread Alejandro Fernandez (JIRA)

 [ 
https://issues.apache.org/jira/browse/AMBARI-18619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alejandro Fernandez updated AMBARI-18619:
-
Attachment: (was: AMBARI-18619.branch-2.5.patch)

> Optimize Service Checks to it picks a random host and prefers hosts with 0 
> active commands
> --
>
> Key: AMBARI-18619
> URL: https://issues.apache.org/jira/browse/AMBARI-18619
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18619.branch-2.5.patch, AMBARI-18619.trunk.patch
>
>
> STR:
> * Deploy a 3-node cluster with Ambari 2.4 and HDP 2.5 with clients on every 
> host.
> * Run multiple service checks in parallel, but notice that they typically run 
> on the same 1 or 2 hosts.
> Currently, Ambari relies on getting the list of candidate hosts from the DB 
> and excludes all hosts that are in maintenance mode. From that list, it picks 
> the first host that is healthy (i.e., heartbeating). This means that the 
> logic does not pick a random host.
> Instead, Ambari should always pick a random host and prefer to schedule on 
> hosts that have 0 in-progress commands.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (AMBARI-18619) Optimize Service Checks to it picks a random host and prefers hosts with 0 active commands

2016-10-18 Thread Alejandro Fernandez (JIRA)

 [ 
https://issues.apache.org/jira/browse/AMBARI-18619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alejandro Fernandez updated AMBARI-18619:
-
Attachment: (was: AMBARI-18619.branch-2.5.patch)

> Optimize Service Checks to it picks a random host and prefers hosts with 0 
> active commands
> --
>
> Key: AMBARI-18619
> URL: https://issues.apache.org/jira/browse/AMBARI-18619
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18619.branch-2.5.patch, AMBARI-18619.trunk.patch
>
>
> STR:
> * Deploy a 3-node cluster with Ambari 2.4 and HDP 2.5 with clients on every 
> host.
> * Run multiple service checks in parallel, but notice that they typically run 
> on the same 1 or 2 hosts.
> Currently, Ambari relies on getting the list of candidate hosts from the DB 
> and excludes all hosts that are in maintenance mode. From that list, it picks 
> the first host that is healthy (i.e., heartbeating). This means that the 
> logic does not pick a random host.
> Instead, Ambari should always pick a random host and prefer to schedule on 
> hosts that have 0 in-progress commands.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (AMBARI-18619) Optimize Service Checks to it picks a random host and prefers hosts with 0 active commands

2016-10-18 Thread Alejandro Fernandez (JIRA)

 [ 
https://issues.apache.org/jira/browse/AMBARI-18619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alejandro Fernandez updated AMBARI-18619:
-
Attachment: (was: AMBARI-18619.trunk.patch)

> Optimize Service Checks to it picks a random host and prefers hosts with 0 
> active commands
> --
>
> Key: AMBARI-18619
> URL: https://issues.apache.org/jira/browse/AMBARI-18619
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18619.branch-2.5.patch, AMBARI-18619.trunk.patch
>
>
> STR:
> * Deploy a 3-node cluster with Ambari 2.4 and HDP 2.5 with clients on every 
> host.
> * Run multiple service checks in parallel, but notice that they typically run 
> on the same 1 or 2 hosts.
> Currently, Ambari relies on getting the list of candidate hosts from the DB 
> and excludes all hosts that are in maintenance mode. From that list, it picks 
> the first host that is healthy (i.e., heartbeating). This means that the 
> logic does not pick a random host.
> Instead, Ambari should always pick a random host and prefer to schedule on 
> hosts that have 0 in-progress commands.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (AMBARI-18619) Optimize Service Checks to it picks a random host and prefers hosts with 0 active commands

2016-10-18 Thread Alejandro Fernandez (JIRA)

 [ 
https://issues.apache.org/jira/browse/AMBARI-18619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alejandro Fernandez updated AMBARI-18619:
-
Attachment: AMBARI-18619.branch-2.5.patch
AMBARI-18619.trunk.patch

> Optimize Service Checks to it picks a random host and prefers hosts with 0 
> active commands
> --
>
> Key: AMBARI-18619
> URL: https://issues.apache.org/jira/browse/AMBARI-18619
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18619.branch-2.5.patch, AMBARI-18619.trunk.patch
>
>
> STR:
> * Deploy a 3-node cluster with Ambari 2.4 and HDP 2.5 with clients on every 
> host.
> * Run multiple service checks in parallel, but notice that they typically run 
> on the same 1 or 2 hosts.
> Currently, Ambari relies on getting the list of candidate hosts from the DB 
> and excludes all hosts that are in maintenance mode. From that list, it picks 
> the first host that is healthy (i.e., heartbeating). This means that the 
> logic does not pick a random host.
> Instead, Ambari should always pick a random host and prefer to schedule on 
> hosts that have 0 in-progress commands.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (AMBARI-18619) Optimize Service Checks to it picks a random host and prefers hosts with 0 active commands

2016-10-18 Thread Alejandro Fernandez (JIRA)

 [ 
https://issues.apache.org/jira/browse/AMBARI-18619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alejandro Fernandez updated AMBARI-18619:
-
Attachment: AMBARI-18619.branch-2.5.patch
AMBARI-18619.trunk.patch

> Optimize Service Checks to it picks a random host and prefers hosts with 0 
> active commands
> --
>
> Key: AMBARI-18619
> URL: https://issues.apache.org/jira/browse/AMBARI-18619
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18619.branch-2.5.patch, AMBARI-18619.trunk.patch
>
>
> STR:
> * Deploy a 3-node cluster with Ambari 2.4 and HDP 2.5 with clients on every 
> host.
> * Run multiple service checks in parallel, but notice that they typically run 
> on the same 1 or 2 hosts.
> Currently, Ambari relies on getting the list of candidate hosts from the DB 
> and excludes all hosts that are in maintenance mode. From that list, it picks 
> the first host that is healthy (i.e., heartbeating). This means that the 
> logic does not pick a random host.
> Instead, Ambari should always pick a random host and prefer to schedule on 
> hosts that have 0 in-progress commands.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (AMBARI-18619) Optimize Service Checks to it picks a random host and prefers hosts with 0 active commands

2016-10-18 Thread Alejandro Fernandez (JIRA)

 [ 
https://issues.apache.org/jira/browse/AMBARI-18619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alejandro Fernandez updated AMBARI-18619:
-
Attachment: (was: AMBARI-18619.trunk.patch)

> Optimize Service Checks to it picks a random host and prefers hosts with 0 
> active commands
> --
>
> Key: AMBARI-18619
> URL: https://issues.apache.org/jira/browse/AMBARI-18619
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: 2.5.0
>
>
> STR:
> * Deploy a 3-node cluster with Ambari 2.4 and HDP 2.5 with clients on every 
> host.
> * Run multiple service checks in parallel, but notice that they typically run 
> on the same 1 or 2 hosts.
> Currently, Ambari relies on getting the list of candidate hosts from the DB 
> and excludes all hosts that are in maintenance mode. From that list, it picks 
> the first host that is healthy (i.e., heartbeating). This means that the 
> logic does not pick a random host.
> Instead, Ambari should always pick a random host and prefer to schedule on 
> hosts that have 0 in-progress commands.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (AMBARI-18619) Optimize Service Checks to it picks a random host and prefers hosts with 0 active commands

2016-10-18 Thread Alejandro Fernandez (JIRA)

 [ 
https://issues.apache.org/jira/browse/AMBARI-18619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alejandro Fernandez updated AMBARI-18619:
-
Attachment: (was: AMBARI-18619.branch-2.5.patch)

> Optimize Service Checks to it picks a random host and prefers hosts with 0 
> active commands
> --
>
> Key: AMBARI-18619
> URL: https://issues.apache.org/jira/browse/AMBARI-18619
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: 2.5.0
>
>
> STR:
> * Deploy a 3-node cluster with Ambari 2.4 and HDP 2.5 with clients on every 
> host.
> * Run multiple service checks in parallel, but notice that they typically run 
> on the same 1 or 2 hosts.
> Currently, Ambari relies on getting the list of candidate hosts from the DB 
> and excludes all hosts that are in maintenance mode. From that list, it picks 
> the first host that is healthy (i.e., heartbeating). This means that the 
> logic does not pick a random host.
> Instead, Ambari should always pick a random host and prefer to schedule on 
> hosts that have 0 in-progress commands.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (AMBARI-18619) Optimize Service Checks to it picks a random host and prefers hosts with 0 active commands

2016-10-17 Thread Alejandro Fernandez (JIRA)

 [ 
https://issues.apache.org/jira/browse/AMBARI-18619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alejandro Fernandez updated AMBARI-18619:
-
Attachment: AMBARI-18619.trunk.patch
AMBARI-18619.branch-2.5.patch

> Optimize Service Checks to it picks a random host and prefers hosts with 0 
> active commands
> --
>
> Key: AMBARI-18619
> URL: https://issues.apache.org/jira/browse/AMBARI-18619
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18619.branch-2.5.patch, AMBARI-18619.trunk.patch
>
>
> STR:
> * Deploy a 3-node cluster with Ambari 2.4 and HDP 2.5 with clients on every 
> host.
> * Run multiple service checks in parallel, but notice that they typically run 
> on the same 1 or 2 hosts.
> Currently, Ambari relies on getting the list of candidate hosts from the DB 
> and excludes all hosts that are in maintenance mode. From that list, it picks 
> the first host that is healthy (i.e., heartbeating). This means that the 
> logic does not pick a random host.
> Instead, Ambari should always pick a random host and prefer to schedule on 
> hosts that have 0 in-progress commands.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (AMBARI-18619) Optimize Service Checks to it picks a random host and prefers hosts with 0 active commands

2016-10-17 Thread Alejandro Fernandez (JIRA)

 [ 
https://issues.apache.org/jira/browse/AMBARI-18619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alejandro Fernandez updated AMBARI-18619:
-
Attachment: (was: AMBARI-18169.trunk.patch)

> Optimize Service Checks to it picks a random host and prefers hosts with 0 
> active commands
> --
>
> Key: AMBARI-18619
> URL: https://issues.apache.org/jira/browse/AMBARI-18619
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18619.branch-2.5.patch, AMBARI-18619.trunk.patch
>
>
> STR:
> * Deploy a 3-node cluster with Ambari 2.4 and HDP 2.5 with clients on every 
> host.
> * Run multiple service checks in parallel, but notice that they typically run 
> on the same 1 or 2 hosts.
> Currently, Ambari relies on getting the list of candidate hosts from the DB 
> and excludes all hosts that are in maintenance mode. From that list, it picks 
> the first host that is healthy (i.e., heartbeating). This means that the 
> logic does not pick a random host.
> Instead, Ambari should always pick a random host and prefer to schedule on 
> hosts that have 0 in-progress commands.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (AMBARI-18619) Optimize Service Checks to it picks a random host and prefers hosts with 0 active commands

2016-10-17 Thread Alejandro Fernandez (JIRA)

 [ 
https://issues.apache.org/jira/browse/AMBARI-18619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alejandro Fernandez updated AMBARI-18619:
-
Attachment: (was: AMBARI-18169.branch-2.5.patch)

> Optimize Service Checks to it picks a random host and prefers hosts with 0 
> active commands
> --
>
> Key: AMBARI-18619
> URL: https://issues.apache.org/jira/browse/AMBARI-18619
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18169.trunk.patch
>
>
> STR:
> * Deploy a 3-node cluster with Ambari 2.4 and HDP 2.5 with clients on every 
> host.
> * Run multiple service checks in parallel, but notice that they typically run 
> on the same 1 or 2 hosts.
> Currently, Ambari relies on getting the list of candidate hosts from the DB 
> and excludes all hosts that are in maintenance mode. From that list, it picks 
> the first host that is healthy (i.e., heartbeating). This means that the 
> logic does not pick a random host.
> Instead, Ambari should always pick a random host and prefer to schedule on 
> hosts that have 0 in-progress commands.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (AMBARI-18619) Optimize Service Checks to it picks a random host and prefers hosts with 0 active commands

2016-10-17 Thread Alejandro Fernandez (JIRA)

 [ 
https://issues.apache.org/jira/browse/AMBARI-18619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alejandro Fernandez updated AMBARI-18619:
-
Status: Patch Available  (was: Open)

> Optimize Service Checks to it picks a random host and prefers hosts with 0 
> active commands
> --
>
> Key: AMBARI-18619
> URL: https://issues.apache.org/jira/browse/AMBARI-18619
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18169.branch-2.5.patch, AMBARI-18169.trunk.patch
>
>
> STR:
> * Deploy a 3-node cluster with Ambari 2.4 and HDP 2.5 with clients on every 
> host.
> * Run multiple service checks in parallel, but notice that they typically run 
> on the same 1 or 2 hosts.
> Currently, Ambari relies on getting the list of candidate hosts from the DB 
> and excludes all hosts that are in maintenance mode. From that list, it picks 
> the first host that is healthy (i.e., heartbeating). This means that the 
> logic does not pick a random host.
> Instead, Ambari should always pick a random host and prefer to schedule on 
> hosts that have 0 in-progress commands.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (AMBARI-18619) Optimize Service Checks to it picks a random host and prefers hosts with 0 active commands

2016-10-17 Thread Alejandro Fernandez (JIRA)

 [ 
https://issues.apache.org/jira/browse/AMBARI-18619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alejandro Fernandez updated AMBARI-18619:
-
Attachment: AMBARI-18169.trunk.patch
AMBARI-18169.branch-2.5.patch

> Optimize Service Checks to it picks a random host and prefers hosts with 0 
> active commands
> --
>
> Key: AMBARI-18619
> URL: https://issues.apache.org/jira/browse/AMBARI-18619
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18169.branch-2.5.patch, AMBARI-18169.trunk.patch
>
>
> STR:
> * Deploy a 3-node cluster with Ambari 2.4 and HDP 2.5 with clients on every 
> host.
> * Run multiple service checks in parallel, but notice that they typically run 
> on the same 1 or 2 hosts.
> Currently, Ambari relies on getting the list of candidate hosts from the DB 
> and excludes all hosts that are in maintenance mode. From that list, it picks 
> the first host that is healthy (i.e., heartbeating). This means that the 
> logic does not pick a random host.
> Instead, Ambari should always pick a random host and prefer to schedule on 
> hosts that have 0 in-progress commands.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)