date:20160212


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

Andrew Onischuk updated AMBARI-14842:
-
Fix Version/s: (was: 2.4.0)
   2.2.2

> ambari agent upstart support
> 
>
> Key: AMBARI-14842
> URL: https://issues.apache.org/jira/browse/AMBARI-14842
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.2.2
>
> Attachments: AMBARI-14842.patch
>
>
> Context:  
> It is critical that we have a service that can auto-restart during crashes and
> reboots. This is done via upstart on Ubuntu.  
> The issue is that Ambari-Agent scripts in the current state is not upstart-
> able due to some implementation issues.  
> So to make this upstart-able, we had to directly take a dependency into a
> helper script for Ambari-Agent (as per user1 recommendation). However, this
> dependency turned out to be fragile, since it broke in HDP 2.4. So this JIRA
> is about making ambari agent upstartable directly when we install Ambari, so
> users doesn’t have to resort to a fragile dependency. We made it work  
> Details:  
> The way to start ambari-agent and ambari-server are different for user1 and
> user2.  
> In the case for ambari-agent:  
> user1 calls "/etc/init.d/ambari-agent" (which invokes /usr/sbin/ambari-agent)
> to start ambari agent.  
> user2 uses "/etc/init/ambari-agent" (which directly calls /usr/lib/python2.6
> /site-packages/ambari_agent/main.py) to start ambari-agent.  
> user2 has to call ambari-agent/main.py directly is because we need upstart to
> re-start services when it crashes unexpectedly and upstart does not work if we
> configure it to call /usr/sbin/ambari-agent.  
> The reason is that upstart needs to track the process for the service (i.e.
> ambari-agent) that it needs to restart; however, /usr/sbin/ambari-agent
> executes lots of commands that would result in new processes being spawned and
> will confuse upstart the "main" process it should be tracking.  
> We need user1 to give us a upstart-compatible script otherwise HDP changes can
> break us unexpectedly.  
> We also have a upstart script for ambari-server for the same reason.  
> Attaching both scripts for user1 to take a look.



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

[jira] [Commented] (AMBARI-15016) Cover hosts views with unit tests


[ 
https://issues.apache.org/jira/browse/AMBARI-15016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144355#comment-15144355
 ] 

Andrii Tkach commented on AMBARI-15016:
---

committed to trunk

> Cover hosts views with unit tests
> -
>
> Key: AMBARI-15016
> URL: https://issues.apache.org/jira/browse/AMBARI-15016
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 2.4.0
>
> Attachments: AMBARI-15016.patch
>
>
> Cover following files with unit tests:
> ambari-web/app/views/main/host/add_view
> ambari-web/app/views/main/host/combo_search_box
> ambari-web/app/views/main/host/config_service_menu
> ambari-web/app/views/main/host/config_service
> ambari-web/app/views/main/host/menu
> ambari-web/app/views/main/host/summary



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

[jira] [Updated] (AMBARI-15025) Hosts page: Filtering works incorrectly with multiple filters applied


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

Oleg Nechiporenko updated AMBARI-15025:
---
Attachment: AMBARI-15025_branch-2.2.patch

> Hosts page: Filtering works incorrectly with multiple filters applied
> -
>
> Key: AMBARI-15025
> URL: https://issues.apache.org/jira/browse/AMBARI-15025
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15025.patch, AMBARI-15025_branch-2.2.patch
>
>
> On 1200 node cluster I enabled filter for alerts and then put in a hostname 
> filter... which showed hosts that did not match the filter. (video attached).
> POST request:
> URL: 
> {code:java}
> /api/v1/clusters/perf/hosts?fields=Hosts/rack_info,Hosts/host_name,Hosts/maintenance_state,Hosts/public_host_name,Hosts/cpu_count,Hosts/ph_cpu_count,alerts_summary,Hosts/host_status,Hosts/last_heartbeat_time,Hosts/ip,host_components/HostRoles/state,host_components/HostRoles/maintenance_state,host_components/HostRoles/stale_configs,host_components/HostRoles/service_name,host_components/HostRoles/desired_admin_state,Hosts/total_mem,stack_versions/HostStackVersions,stack_versions/repository_versions/RepositoryVersions/repository_version,stack_versions/repository_versions/RepositoryVersions/id,stack_versions/repository_versions/RepositoryVersions/display_name_response=true_size=10=0=Hosts/host_name.as
> {code}
> Data: 
> {code:java}
> {"RequestInfo":{"query":"page_size=10=0_summary/CRITICAL>0|alerts_summary/WARNING>0/host_name.matches(.*23.*)"}}
> {code}
> Response: 
> {code:java}
> {
>   "itemTotal" : "308",
>   "items" : [
> {
>   "Hosts" : {
> "cpu_count" : 4,
> "host_name" : "perf-b-1.c.pramod-thangali.internal",
> "host_status" : "HEALTHY",
> "ip" : "10.240.0.4",
> "last_heartbeat_time" : 1455013064276,
> "maintenance_state" : "OFF",
> "ph_cpu_count" : 4,
> "public_host_name" : "perf-b-1.c.pramod-thangali.internal",
> "rack_info" : "/default-rack",
> "total_mem" : 15301028
>   }...
> {code}



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

[jira] [Updated] (AMBARI-15025) Hosts page: Filtering works incorrectly with multiple filters applied


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

Oleg Nechiporenko updated AMBARI-15025:
---
Attachment: AMBARI-15025.patch

> Hosts page: Filtering works incorrectly with multiple filters applied
> -
>
> Key: AMBARI-15025
> URL: https://issues.apache.org/jira/browse/AMBARI-15025
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15025.patch
>
>
> On 1200 node cluster I enabled filter for alerts and then put in a hostname 
> filter... which showed hosts that did not match the filter. (video attached).
> POST request:
> URL: 
> {code:java}
> /api/v1/clusters/perf/hosts?fields=Hosts/rack_info,Hosts/host_name,Hosts/maintenance_state,Hosts/public_host_name,Hosts/cpu_count,Hosts/ph_cpu_count,alerts_summary,Hosts/host_status,Hosts/last_heartbeat_time,Hosts/ip,host_components/HostRoles/state,host_components/HostRoles/maintenance_state,host_components/HostRoles/stale_configs,host_components/HostRoles/service_name,host_components/HostRoles/desired_admin_state,Hosts/total_mem,stack_versions/HostStackVersions,stack_versions/repository_versions/RepositoryVersions/repository_version,stack_versions/repository_versions/RepositoryVersions/id,stack_versions/repository_versions/RepositoryVersions/display_name_response=true_size=10=0=Hosts/host_name.as
> {code}
> Data: 
> {code:java}
> {"RequestInfo":{"query":"page_size=10=0_summary/CRITICAL>0|alerts_summary/WARNING>0/host_name.matches(.*23.*)"}}
> {code}
> Response: 
> {code:java}
> {
>   "itemTotal" : "308",
>   "items" : [
> {
>   "Hosts" : {
> "cpu_count" : 4,
> "host_name" : "perf-b-1.c.pramod-thangali.internal",
> "host_status" : "HEALTHY",
> "ip" : "10.240.0.4",
> "last_heartbeat_time" : 1455013064276,
> "maintenance_state" : "OFF",
> "ph_cpu_count" : 4,
> "public_host_name" : "perf-b-1.c.pramod-thangali.internal",
> "rack_info" : "/default-rack",
> "total_mem" : 15301028
>   }...
> {code}



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

[jira] [Commented] (AMBARI-15025) Hosts page: Filtering works incorrectly with multiple filters applied


[ 
https://issues.apache.org/jira/browse/AMBARI-15025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144369#comment-15144369
 ] 

Oleg Nechiporenko commented on AMBARI-15025:


  24255 tests complete (23 seconds)
  156 tests pending

> Hosts page: Filtering works incorrectly with multiple filters applied
> -
>
> Key: AMBARI-15025
> URL: https://issues.apache.org/jira/browse/AMBARI-15025
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15025.patch
>
>
> On 1200 node cluster I enabled filter for alerts and then put in a hostname 
> filter... which showed hosts that did not match the filter. (video attached).
> POST request:
> URL: 
> {code:java}
> /api/v1/clusters/perf/hosts?fields=Hosts/rack_info,Hosts/host_name,Hosts/maintenance_state,Hosts/public_host_name,Hosts/cpu_count,Hosts/ph_cpu_count,alerts_summary,Hosts/host_status,Hosts/last_heartbeat_time,Hosts/ip,host_components/HostRoles/state,host_components/HostRoles/maintenance_state,host_components/HostRoles/stale_configs,host_components/HostRoles/service_name,host_components/HostRoles/desired_admin_state,Hosts/total_mem,stack_versions/HostStackVersions,stack_versions/repository_versions/RepositoryVersions/repository_version,stack_versions/repository_versions/RepositoryVersions/id,stack_versions/repository_versions/RepositoryVersions/display_name_response=true_size=10=0=Hosts/host_name.as
> {code}
> Data: 
> {code:java}
> {"RequestInfo":{"query":"page_size=10=0_summary/CRITICAL>0|alerts_summary/WARNING>0/host_name.matches(.*23.*)"}}
> {code}
> Response: 
> {code:java}
> {
>   "itemTotal" : "308",
>   "items" : [
> {
>   "Hosts" : {
> "cpu_count" : 4,
> "host_name" : "perf-b-1.c.pramod-thangali.internal",
> "host_status" : "HEALTHY",
> "ip" : "10.240.0.4",
> "last_heartbeat_time" : 1455013064276,
> "maintenance_state" : "OFF",
> "ph_cpu_count" : 4,
> "public_host_name" : "perf-b-1.c.pramod-thangali.internal",
> "rack_info" : "/default-rack",
> "total_mem" : 15301028
>   }...
> {code}



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

[jira] [Resolved] (AMBARI-15007) Make amazon2015 to be part of redhat6 family


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

Andrew Onischuk resolved AMBARI-15007.
--
Resolution: Fixed

My bad. Fixed the problem.
Committed to trunk and branch-2.2

> Make amazon2015 to be part of redhat6 family
> 
>
> Key: AMBARI-15007
> URL: https://issues.apache.org/jira/browse/AMBARI-15007
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.2.2
>
> Attachments: AMBARI-15007.patch
>
>
> We have discussed the solution for this with Sumit Mohanty.  
> We decided to avoid introducing new os family for amazon.  
> And to simply add aliases section to os_family.json like this:
> 
> 
>   "aliases": {
> "amazon2015": "amazon6"
>   }
> 
> The only disadvantage is that when choosing repo-url, user might be confused
> that centos6 url is for amazon 2015.  
> But that what initially what I was asked to do.
> Also this jira should include using /etc/system-release instead of /etc/issue
> to detect amazon os. (/etc/os-release seems to be absent on some centos
> distros, so I think it's not reliable)



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

[jira] [Commented] (AMBARI-15025) Hosts page: Filtering works incorrectly with multiple filters applied


[ 
https://issues.apache.org/jira/browse/AMBARI-15025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144377#comment-15144377
 ] 

Andrii Tkach commented on AMBARI-15025:
---

+1 for the patch

> Hosts page: Filtering works incorrectly with multiple filters applied
> -
>
> Key: AMBARI-15025
> URL: https://issues.apache.org/jira/browse/AMBARI-15025
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15025.patch, AMBARI-15025_branch-2.2.patch
>
>
> On 1200 node cluster I enabled filter for alerts and then put in a hostname 
> filter... which showed hosts that did not match the filter. (video attached).
> POST request:
> URL: 
> {code:java}
> /api/v1/clusters/perf/hosts?fields=Hosts/rack_info,Hosts/host_name,Hosts/maintenance_state,Hosts/public_host_name,Hosts/cpu_count,Hosts/ph_cpu_count,alerts_summary,Hosts/host_status,Hosts/last_heartbeat_time,Hosts/ip,host_components/HostRoles/state,host_components/HostRoles/maintenance_state,host_components/HostRoles/stale_configs,host_components/HostRoles/service_name,host_components/HostRoles/desired_admin_state,Hosts/total_mem,stack_versions/HostStackVersions,stack_versions/repository_versions/RepositoryVersions/repository_version,stack_versions/repository_versions/RepositoryVersions/id,stack_versions/repository_versions/RepositoryVersions/display_name_response=true_size=10=0=Hosts/host_name.as
> {code}
> Data: 
> {code:java}
> {"RequestInfo":{"query":"page_size=10=0_summary/CRITICAL>0|alerts_summary/WARNING>0/host_name.matches(.*23.*)"}}
> {code}
> Response: 
> {code:java}
> {
>   "itemTotal" : "308",
>   "items" : [
> {
>   "Hosts" : {
> "cpu_count" : 4,
> "host_name" : "perf-b-1.c.pramod-thangali.internal",
> "host_status" : "HEALTHY",
> "ip" : "10.240.0.4",
> "last_heartbeat_time" : 1455013064276,
> "maintenance_state" : "OFF",
> "ph_cpu_count" : 4,
> "public_host_name" : "perf-b-1.c.pramod-thangali.internal",
> "rack_info" : "/default-rack",
> "total_mem" : 15301028
>   }...
> {code}



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

[jira] [Commented] (AMBARI-15021) Set AMBARI_METRICS as the default datasource


[ 
https://issues.apache.org/jira/browse/AMBARI-15021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144352#comment-15144352
 ] 

Hudson commented on AMBARI-15021:
-

ABORTED: Integrated in Ambari-trunk-Commit #4317 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4317/])
AMBARI-15021. Set AMBARI_METRICS as the default datasource. (Prajwal Rao 
(yusaku: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c47fff3576382e0e4efcd9f8b952b7362cec4390])
* 
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/templates/metrics_grafana_datasource.json.j2


> Set AMBARI_METRICS as the default datasource
> 
>
> Key: AMBARI-15021
> URL: https://issues.apache.org/jira/browse/AMBARI-15021
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.2.2
>Reporter: Prajwal Rao
>Assignee: Prajwal Rao
> Fix For: 2.2.2
>
> Attachments: AMBARI-15021.patch
>
>
> When Grafana is deployed as a component, the auto created datasource 
> (AMBARI_METRICS) isn't set as default.



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

[jira] [Commented] (AMBARI-14715) TimelineServer configuration is missing in yarn-env.xml.


[ 
https://issues.apache.org/jira/browse/AMBARI-14715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144351#comment-15144351
 ] 

Hudson commented on AMBARI-14715:
-

ABORTED: Integrated in Ambari-trunk-Commit #4317 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4317/])
AMBARI-14715. TimelineServer configuration is missing in yarn-env.xml. (yusaku: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6eed33322291c90c03386b72806fc3be461df5ec])
* 
ambari-server/src/main/resources/stacks/HDP/2.3/services/YARN/configuration/yarn-env.xml


> TimelineServer configuration is missing in yarn-env.xml.
> 
>
> Key: AMBARI-14715
> URL: https://issues.apache.org/jira/browse/AMBARI-14715
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Reporter: Akira AJISAKA
>Assignee: Akira AJISAKA
>  Labels: newbie
> Fix For: 2.2.2
>
> Attachments: AMBARI-14715.001.patch
>
>
> In yarn-env.xml, {{YARN_HISTORYSERVER_OPTS}} and 
> {{YARN_HISTORYSERVER_HEAPSIZE}} are not valid for TimelineServer.
> {noformat:title=ambari-server/src/main/resources/stacks/HDP/2.3/services/YARN/configuration/yarn-env.xml}
>   # Specify the max Heapsize for the HistoryManager using a numerical 
> value
>   # in the scale of MB. For example, to specify an jvm option of 
> -Xmx1000m, set
>   # the value to 1024.
>   # This value will be overridden by an Xmx setting specified in either 
> YARN_OPTS
>   # and/or YARN_HISTORYSERVER_OPTS.
>   # If not specified, the default value will be picked from either 
> YARN_HEAPMAX
>   # or JAVA_HEAP_MAX with YARN_HEAPMAX as the preferred option of the two.
>   export YARN_HISTORYSERVER_HEAPSIZE={{apptimelineserver_heapsize}}
> {noformat}
> {{HISTORYSERVER}} should be {{TIMELINESERVER}}.



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

[jira] [Commented] (AMBARI-15025) Hosts page: Filtering works incorrectly with multiple filters applied


[ 
https://issues.apache.org/jira/browse/AMBARI-15025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144375#comment-15144375
 ] 

Oleg Nechiporenko commented on AMBARI-15025:


2.2:

  10367 tests complete (12 seconds)
  121 tests pending


> Hosts page: Filtering works incorrectly with multiple filters applied
> -
>
> Key: AMBARI-15025
> URL: https://issues.apache.org/jira/browse/AMBARI-15025
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15025.patch, AMBARI-15025_branch-2.2.patch
>
>
> On 1200 node cluster I enabled filter for alerts and then put in a hostname 
> filter... which showed hosts that did not match the filter. (video attached).
> POST request:
> URL: 
> {code:java}
> /api/v1/clusters/perf/hosts?fields=Hosts/rack_info,Hosts/host_name,Hosts/maintenance_state,Hosts/public_host_name,Hosts/cpu_count,Hosts/ph_cpu_count,alerts_summary,Hosts/host_status,Hosts/last_heartbeat_time,Hosts/ip,host_components/HostRoles/state,host_components/HostRoles/maintenance_state,host_components/HostRoles/stale_configs,host_components/HostRoles/service_name,host_components/HostRoles/desired_admin_state,Hosts/total_mem,stack_versions/HostStackVersions,stack_versions/repository_versions/RepositoryVersions/repository_version,stack_versions/repository_versions/RepositoryVersions/id,stack_versions/repository_versions/RepositoryVersions/display_name_response=true_size=10=0=Hosts/host_name.as
> {code}
> Data: 
> {code:java}
> {"RequestInfo":{"query":"page_size=10=0_summary/CRITICAL>0|alerts_summary/WARNING>0/host_name.matches(.*23.*)"}}
> {code}
> Response: 
> {code:java}
> {
>   "itemTotal" : "308",
>   "items" : [
> {
>   "Hosts" : {
> "cpu_count" : 4,
> "host_name" : "perf-b-1.c.pramod-thangali.internal",
> "host_status" : "HEALTHY",
> "ip" : "10.240.0.4",
> "last_heartbeat_time" : 1455013064276,
> "maintenance_state" : "OFF",
> "ph_cpu_count" : 4,
> "public_host_name" : "perf-b-1.c.pramod-thangali.internal",
> "rack_info" : "/default-rack",
> "total_mem" : 15301028
>   }...
> {code}



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

[jira] [Commented] (AMBARI-15025) Hosts page: Filtering works incorrectly with multiple filters applied


[ 
https://issues.apache.org/jira/browse/AMBARI-15025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144376#comment-15144376
 ] 

Oleg Nechiporenko commented on AMBARI-15025:


Patches for trunk and 2.2 are added.

> Hosts page: Filtering works incorrectly with multiple filters applied
> -
>
> Key: AMBARI-15025
> URL: https://issues.apache.org/jira/browse/AMBARI-15025
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15025.patch, AMBARI-15025_branch-2.2.patch
>
>
> On 1200 node cluster I enabled filter for alerts and then put in a hostname 
> filter... which showed hosts that did not match the filter. (video attached).
> POST request:
> URL: 
> {code:java}
> /api/v1/clusters/perf/hosts?fields=Hosts/rack_info,Hosts/host_name,Hosts/maintenance_state,Hosts/public_host_name,Hosts/cpu_count,Hosts/ph_cpu_count,alerts_summary,Hosts/host_status,Hosts/last_heartbeat_time,Hosts/ip,host_components/HostRoles/state,host_components/HostRoles/maintenance_state,host_components/HostRoles/stale_configs,host_components/HostRoles/service_name,host_components/HostRoles/desired_admin_state,Hosts/total_mem,stack_versions/HostStackVersions,stack_versions/repository_versions/RepositoryVersions/repository_version,stack_versions/repository_versions/RepositoryVersions/id,stack_versions/repository_versions/RepositoryVersions/display_name_response=true_size=10=0=Hosts/host_name.as
> {code}
> Data: 
> {code:java}
> {"RequestInfo":{"query":"page_size=10=0_summary/CRITICAL>0|alerts_summary/WARNING>0/host_name.matches(.*23.*)"}}
> {code}
> Response: 
> {code:java}
> {
>   "itemTotal" : "308",
>   "items" : [
> {
>   "Hosts" : {
> "cpu_count" : 4,
> "host_name" : "perf-b-1.c.pramod-thangali.internal",
> "host_status" : "HEALTHY",
> "ip" : "10.240.0.4",
> "last_heartbeat_time" : 1455013064276,
> "maintenance_state" : "OFF",
> "ph_cpu_count" : 4,
> "public_host_name" : "perf-b-1.c.pramod-thangali.internal",
> "rack_info" : "/default-rack",
> "total_mem" : 15301028
>   }...
> {code}



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

[jira] [Commented] (AMBARI-15025) Hosts page: Filtering works incorrectly with multiple filters applied


[ 
https://issues.apache.org/jira/browse/AMBARI-15025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144397#comment-15144397
 ] 

Hadoop QA commented on AMBARI-15025:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12787642/AMBARI-15025.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-web.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/5330//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/5330//console

This message is automatically generated.

> Hosts page: Filtering works incorrectly with multiple filters applied
> -
>
> Key: AMBARI-15025
> URL: https://issues.apache.org/jira/browse/AMBARI-15025
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15025.patch, AMBARI-15025_branch-2.2.patch
>
>
> On 1200 node cluster I enabled filter for alerts and then put in a hostname 
> filter... which showed hosts that did not match the filter. (video attached).
> POST request:
> URL: 
> {code:java}
> /api/v1/clusters/perf/hosts?fields=Hosts/rack_info,Hosts/host_name,Hosts/maintenance_state,Hosts/public_host_name,Hosts/cpu_count,Hosts/ph_cpu_count,alerts_summary,Hosts/host_status,Hosts/last_heartbeat_time,Hosts/ip,host_components/HostRoles/state,host_components/HostRoles/maintenance_state,host_components/HostRoles/stale_configs,host_components/HostRoles/service_name,host_components/HostRoles/desired_admin_state,Hosts/total_mem,stack_versions/HostStackVersions,stack_versions/repository_versions/RepositoryVersions/repository_version,stack_versions/repository_versions/RepositoryVersions/id,stack_versions/repository_versions/RepositoryVersions/display_name_response=true_size=10=0=Hosts/host_name.as
> {code}
> Data: 
> {code:java}
> {"RequestInfo":{"query":"page_size=10=0_summary/CRITICAL>0|alerts_summary/WARNING>0/host_name.matches(.*23.*)"}}
> {code}
> Response: 
> {code:java}
> {
>   "itemTotal" : "308",
>   "items" : [
> {
>   "Hosts" : {
> "cpu_count" : 4,
> "host_name" : "perf-b-1.c.pramod-thangali.internal",
> "host_status" : "HEALTHY",
> "ip" : "10.240.0.4",
> "last_heartbeat_time" : 1455013064276,
> "maintenance_state" : "OFF",
> "ph_cpu_count" : 4,
> "public_host_name" : "perf-b-1.c.pramod-thangali.internal",
> "rack_info" : "/default-rack",
> "total_mem" : 15301028
>   }...
> {code}



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

[jira] [Commented] (AMBARI-15025) Hosts page: Filtering works incorrectly with multiple filters applied


[ 
https://issues.apache.org/jira/browse/AMBARI-15025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144479#comment-15144479
 ] 

Oleg Nechiporenko commented on AMBARI-15025:


Patch for 2.2 was selected to test trunk.

> Hosts page: Filtering works incorrectly with multiple filters applied
> -
>
> Key: AMBARI-15025
> URL: https://issues.apache.org/jira/browse/AMBARI-15025
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15025.patch, AMBARI-15025_branch-2.2.patch
>
>
> On 1200 node cluster I enabled filter for alerts and then put in a hostname 
> filter... which showed hosts that did not match the filter. (video attached).
> POST request:
> URL: 
> {code:java}
> /api/v1/clusters/perf/hosts?fields=Hosts/rack_info,Hosts/host_name,Hosts/maintenance_state,Hosts/public_host_name,Hosts/cpu_count,Hosts/ph_cpu_count,alerts_summary,Hosts/host_status,Hosts/last_heartbeat_time,Hosts/ip,host_components/HostRoles/state,host_components/HostRoles/maintenance_state,host_components/HostRoles/stale_configs,host_components/HostRoles/service_name,host_components/HostRoles/desired_admin_state,Hosts/total_mem,stack_versions/HostStackVersions,stack_versions/repository_versions/RepositoryVersions/repository_version,stack_versions/repository_versions/RepositoryVersions/id,stack_versions/repository_versions/RepositoryVersions/display_name_response=true_size=10=0=Hosts/host_name.as
> {code}
> Data: 
> {code:java}
> {"RequestInfo":{"query":"page_size=10=0_summary/CRITICAL>0|alerts_summary/WARNING>0/host_name.matches(.*23.*)"}}
> {code}
> Response: 
> {code:java}
> {
>   "itemTotal" : "308",
>   "items" : [
> {
>   "Hosts" : {
> "cpu_count" : 4,
> "host_name" : "perf-b-1.c.pramod-thangali.internal",
> "host_status" : "HEALTHY",
> "ip" : "10.240.0.4",
> "last_heartbeat_time" : 1455013064276,
> "maintenance_state" : "OFF",
> "ph_cpu_count" : 4,
> "public_host_name" : "perf-b-1.c.pramod-thangali.internal",
> "rack_info" : "/default-rack",
> "total_mem" : 15301028
>   }...
> {code}



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

[jira] [Commented] (AMBARI-15016) Cover hosts views with unit tests


[ 
https://issues.apache.org/jira/browse/AMBARI-15016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144510#comment-15144510
 ] 

Hudson commented on AMBARI-15016:
-

FAILURE: Integrated in Ambari-trunk-Commit #4318 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4318/])
AMBARI-15016 Cover hosts views with unit tests. (atkach) (atkach: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=30438e9052d5782d8e2b5fe4b28c6adf9d78c5d7])
* ambari-web/app/utils/configs/rm_ha_config_initializer.js
* ambari-web/app/assets/test/tests.js
* ambari-web/test/views/main/host/add_view_test.js
* ambari-web/app/views/main/admin/highAvailability/progress_view.js
* ambari-web/app/views/main/host/summary.js
* ambari-web/app/views/main/host/add_view.js
* ambari-web/test/views/main/host/config_service_menu_test.js
* ambari-web/app/views/main/host/menu.js
* ambari-web/app/views/main/host/configs_service.js
* ambari-web/test/views/main/host/combo_search_box_test.js
* ambari-web/test/views/main/host/summary_test.js
* ambari-web/app/controllers/wizard/step7_controller.js
* ambari-web/test/views/main/host/host_alerts_view_test.js
* ambari-web/test/views/main/admin/highAvailability/progress_view_test.js
* ambari-web/test/views/main/host/config_service_test.js
* ambari-web/test/views/main/host/menu_test.js


> Cover hosts views with unit tests
> -
>
> Key: AMBARI-15016
> URL: https://issues.apache.org/jira/browse/AMBARI-15016
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 2.4.0
>
> Attachments: AMBARI-15016.patch
>
>
> Cover following files with unit tests:
> ambari-web/app/views/main/host/add_view
> ambari-web/app/views/main/host/combo_search_box
> ambari-web/app/views/main/host/config_service_menu
> ambari-web/app/views/main/host/config_service
> ambari-web/app/views/main/host/menu
> ambari-web/app/views/main/host/summary



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

[jira] [Created] (AMBARI-15026) Hadoop metrics emit interval seems to be 1 minute instead of 10 seconds default

Dmytro Sen created AMBARI-15026:
---

 Summary: Hadoop metrics emit interval seems to be 1 minute instead 
of 10 seconds default
 Key: AMBARI-15026
 URL: https://issues.apache.org/jira/browse/AMBARI-15026
 Project: Ambari
  Issue Type: Bug
  Components: ambari-metrics
Affects Versions: 2.2.0
Reporter: Dmytro Sen
Assignee: Dmytro Sen
Priority: Critical
 Fix For: 2.2.2


Noticed this after upgrade from 2.1.2 to 2.2.0.

Bug seems to have been introduced bu AMBARI-13037.

Need to ensure, send internal of 60 seconds and leaving the collection or 
sampling interval as default.

{code}
0: jdbc:phoenix:localhost:61181:/ams-hbase-un> select * from METRIC_RECORD 
where METRIC_NAME='rpc.rpc.RpcQueueTimeAvgTime' and APP_ID = 'namenode' order 
by SERVER_TIME desc limit 10;
+-++-++-++--++--++++
| METRIC_NAME |  HOSTNAME  | SERVER_TIME |   APP_ID   | INSTANCE_ID | 
START_TIME |UNITS | METRIC_SUM | METRIC_COUNT | METRIC_MAX | 
METRIC_MIN |  METRICS   |
+-++-++-++--++--++++
| rpc.rpc.RpcQueueTimeAvgTime | c6401.ambari.apache.org | 1455155926917 | 
namenode   | null| 1455155866867 | null | 0.0| 
2| 0.0| 0.0| 
{"1455155866867":0.0,"1455155926867":0.0} |
| rpc.rpc.RpcQueueTimeAvgTime | c6401.ambari.apache.org | 1455155806915 | 
namenode   | null| 1455155746868 | null | 0.5| 
2| 0.5| 0.0| 
{"1455155746868":0.5,"1455155806868":0.0} |
| rpc.rpc.RpcQueueTimeAvgTime | c6401.ambari.apache.org | 1455155686901 | 
namenode   | null| 1455155626867 | null | 2.0| 
2| 1.0| 1.0| 
{"1455155626867":1.0,"1455155686867":1.0} |
| rpc.rpc.RpcQueueTimeAvgTime | c6401.ambari.apache.org | 1455155566987 | 
namenode   | null| 1455155446868 | null | 1.5| 
3| 1.0| 0.0| 
{"1455155446868":0.0,"1455155506866":1.0,"1455155566872":0.5} |
| rpc.rpc.RpcQueueTimeAvgTime | c6401.ambari.apache.org | 1455155221565 | 
namenode   | null| 1455155101498 | null | 2.5| 
3| 1.0| 0.5| 
{"1455155101498":1.0,"1455155161496":1.0,"1455155221497":0.5} |
| rpc.rpc.RpcQueueTimeAvgTime | c6401.ambari.apache.org | 1455155041553 | 
namenode   | null| 1455154981496 | null | 2.5| 
2| 2.5| 0.0| 
{"1455154981496":0.0,"1455155041498":2.5} |
| rpc.rpc.RpcQueueTimeAvgTime | c6401.ambari.apache.org | 1455154921619 | 
namenode   | null| 1455154801501 | null | 
0.8334 | 3| 0.5| 0.0| 
{"1455154801501":0.5,"1455154861497":0.7,"1455154921497":0.0} |
| rpc.rpc.RpcQueueTimeAvgTime | c6401.ambari.apache.org | 1455154679870 | 
namenode   | null| 1455154619738 | null | 1.0| 
2| 1.0| 0.0| 
{"1455154619738":1.0,"1455154679738":0.0} |
| rpc.rpc.RpcQueueTimeAvgTime | c6401.ambari.apache.org | 1455154559985 | 
namenode   | null| 1455154439747 | null | 1.5| 
3| 1.0| 0.0| 
{"1455154439747":0.5,"1455154499738":0.0,"1455154559740":1.0} |
+-++-++-++--++--++++
9 rows selected (0.485 seconds)
{code}



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

Re: Review Request 43365: assign_master_components.js breaks next step in certain case


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43365/
---

(Updated Feb. 12, 2016, 5:22 a.m.)


Review request for Ambari, Alexander Denissov, Alejandro Fernandez, Aleksandr 
Kovalenko, Alexandr Antonenko, bhuvnesh chaudhary, Goutam Tadi, Jaimin Jetly, 
jun aoki, Lav Jain, Newton Alex, Oleksandr Diachenko, and Sumit Mohanty.


Bugs: AMBARI-14701
https://issues.apache.org/jira/browse/AMBARI-14701


Repository: ambari


Description
---

There was noAction onSecondary (Cancel button). Implemented onSecondary, and 
modified the callback for the same.


Diffs (updated)
-

  ambari-web/app/mixins/wizard/assign_master_components.js 7dc267e 

Diff: https://reviews.apache.org/r/43365/diff/


Testing (updated)
---

All unit tests passed:
  10401 tests complete (9 seconds)
  121 tests pending

[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 01:08 min
[INFO] Finished at: 2016-02-12T05:19:30-08:00
[INFO] Final Memory: 12M/311M
[INFO] 


Thanks,

Matt

[jira] [Commented] (AMBARI-15025) Hosts page: Filtering works incorrectly with multiple filters applied


[ 
https://issues.apache.org/jira/browse/AMBARI-15025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144407#comment-15144407
 ] 

Oleg Nechiporenko commented on AMBARI-15025:


Tested manually on the real cluster

> Hosts page: Filtering works incorrectly with multiple filters applied
> -
>
> Key: AMBARI-15025
> URL: https://issues.apache.org/jira/browse/AMBARI-15025
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15025.patch, AMBARI-15025_branch-2.2.patch
>
>
> On 1200 node cluster I enabled filter for alerts and then put in a hostname 
> filter... which showed hosts that did not match the filter. (video attached).
> POST request:
> URL: 
> {code:java}
> /api/v1/clusters/perf/hosts?fields=Hosts/rack_info,Hosts/host_name,Hosts/maintenance_state,Hosts/public_host_name,Hosts/cpu_count,Hosts/ph_cpu_count,alerts_summary,Hosts/host_status,Hosts/last_heartbeat_time,Hosts/ip,host_components/HostRoles/state,host_components/HostRoles/maintenance_state,host_components/HostRoles/stale_configs,host_components/HostRoles/service_name,host_components/HostRoles/desired_admin_state,Hosts/total_mem,stack_versions/HostStackVersions,stack_versions/repository_versions/RepositoryVersions/repository_version,stack_versions/repository_versions/RepositoryVersions/id,stack_versions/repository_versions/RepositoryVersions/display_name_response=true_size=10=0=Hosts/host_name.as
> {code}
> Data: 
> {code:java}
> {"RequestInfo":{"query":"page_size=10=0_summary/CRITICAL>0|alerts_summary/WARNING>0/host_name.matches(.*23.*)"}}
> {code}
> Response: 
> {code:java}
> {
>   "itemTotal" : "308",
>   "items" : [
> {
>   "Hosts" : {
> "cpu_count" : 4,
> "host_name" : "perf-b-1.c.pramod-thangali.internal",
> "host_status" : "HEALTHY",
> "ip" : "10.240.0.4",
> "last_heartbeat_time" : 1455013064276,
> "maintenance_state" : "OFF",
> "ph_cpu_count" : 4,
> "public_host_name" : "perf-b-1.c.pramod-thangali.internal",
> "rack_info" : "/default-rack",
> "total_mem" : 15301028
>   }...
> {code}



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

[jira] [Commented] (AMBARI-15025) Hosts page: Filtering works incorrectly with multiple filters applied


[ 
https://issues.apache.org/jira/browse/AMBARI-15025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144453#comment-15144453
 ] 

Hadoop QA commented on AMBARI-15025:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12787643/AMBARI-15025_branch-2.2.patch
  against trunk revision .

{color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/5331//console

This message is automatically generated.

> Hosts page: Filtering works incorrectly with multiple filters applied
> -
>
> Key: AMBARI-15025
> URL: https://issues.apache.org/jira/browse/AMBARI-15025
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15025.patch, AMBARI-15025_branch-2.2.patch
>
>
> On 1200 node cluster I enabled filter for alerts and then put in a hostname 
> filter... which showed hosts that did not match the filter. (video attached).
> POST request:
> URL: 
> {code:java}
> /api/v1/clusters/perf/hosts?fields=Hosts/rack_info,Hosts/host_name,Hosts/maintenance_state,Hosts/public_host_name,Hosts/cpu_count,Hosts/ph_cpu_count,alerts_summary,Hosts/host_status,Hosts/last_heartbeat_time,Hosts/ip,host_components/HostRoles/state,host_components/HostRoles/maintenance_state,host_components/HostRoles/stale_configs,host_components/HostRoles/service_name,host_components/HostRoles/desired_admin_state,Hosts/total_mem,stack_versions/HostStackVersions,stack_versions/repository_versions/RepositoryVersions/repository_version,stack_versions/repository_versions/RepositoryVersions/id,stack_versions/repository_versions/RepositoryVersions/display_name_response=true_size=10=0=Hosts/host_name.as
> {code}
> Data: 
> {code:java}
> {"RequestInfo":{"query":"page_size=10=0_summary/CRITICAL>0|alerts_summary/WARNING>0/host_name.matches(.*23.*)"}}
> {code}
> Response: 
> {code:java}
> {
>   "itemTotal" : "308",
>   "items" : [
> {
>   "Hosts" : {
> "cpu_count" : 4,
> "host_name" : "perf-b-1.c.pramod-thangali.internal",
> "host_status" : "HEALTHY",
> "ip" : "10.240.0.4",
> "last_heartbeat_time" : 1455013064276,
> "maintenance_state" : "OFF",
> "ph_cpu_count" : 4,
> "public_host_name" : "perf-b-1.c.pramod-thangali.internal",
> "rack_info" : "/default-rack",
> "total_mem" : 15301028
>   }...
> {code}



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

[jira] [Updated] (AMBARI-14936) Tweaks to reduce build time


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

Andrew Onischuk updated AMBARI-14936:
-
Attachment: AMBARI-14936.patch

> Tweaks to reduce build time
> ---
>
> Key: AMBARI-14936
> URL: https://issues.apache.org/jira/browse/AMBARI-14936
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-14936.patch
>
>
> 1\. Don't build common-services and stacks folder into ambari-server.jar. This
> reduces jar size from 20Mb to 7Mb. And also reduces its buildtime.  
> 2\. -DassemblyPhase=none option to skip building tarballs. Is useful when
> building simply a jar is needed.  
> 3\. -Dnodemodules.dir option to not redownload node_modules folder in ambari-
> web. This reduces ambari-web time from ~1.1 min. to ~15s. (unless it's a first
> build and node_modules is not there). However this may rearly result in npm
> cache issues, which is simply solved by 'rm -rf ambari-web/node_modules'



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

[jira] [Updated] (AMBARI-14936) Tweaks to reduce build time


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

Andrew Onischuk updated AMBARI-14936:
-
Attachment: (was: AMBARI-14936.patch)

> Tweaks to reduce build time
> ---
>
> Key: AMBARI-14936
> URL: https://issues.apache.org/jira/browse/AMBARI-14936
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-14936.patch
>
>
> 1\. Don't build common-services and stacks folder into ambari-server.jar. This
> reduces jar size from 20Mb to 7Mb. And also reduces its buildtime.  
> 2\. -DassemblyPhase=none option to skip building tarballs. Is useful when
> building simply a jar is needed.  
> 3\. -Dnodemodules.dir option to not redownload node_modules folder in ambari-
> web. This reduces ambari-web time from ~1.1 min. to ~15s. (unless it's a first
> build and node_modules is not there). However this may rearly result in npm
> cache issues, which is simply solved by 'rm -rf ambari-web/node_modules'



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

[jira] [Commented] (AMBARI-15022) Add Custom action to sync Standby with Master


[ 
https://issues.apache.org/jira/browse/AMBARI-15022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144488#comment-15144488
 ] 

Hadoop QA commented on AMBARI-15022:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12787603/AMBARI-15022-trunk.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-server ambari-web.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/5332//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/5332//console

This message is automatically generated.

> Add Custom action to sync Standby with Master
> -
>
> Key: AMBARI-15022
> URL: https://issues.apache.org/jira/browse/AMBARI-15022
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-web
>Affects Versions: trunk, 2.2.2
>Reporter: Goutam Tadi
>Assignee: Goutam Tadi
>Priority: Minor
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-15022-trunk.patch
>
>
> On the action page of the standby host ( screenshot2 ), there should add one 
> action that user can activate standby when master down and one action that 
> user can resync standby when the status of standby is "Not synchronized.". 
> Use "hawq init standby -n" to resync standby from master and use "hawq 
> activate standby [-option]"  to activate standby. 
> For more details, please reference to hawq doc about standby. 



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

[jira] [Created] (AMBARI-15027) Sometimes Yarn graphs,Heatmaps take longer to load

Andrii Tkach created AMBARI-15027:
-

 Summary: Sometimes Yarn graphs,Heatmaps take longer to load
 Key: AMBARI-15027
 URL: https://issues.apache.org/jira/browse/AMBARI-15027
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.2.1
 Environment: ambari-server version: ambari-server-2.2.1.0-66.x86_64
ambari-server --hash: a659e664cd8b4f05883d8a8a1412e68097bd2b85
HDP Stack: 2.4
HDP Version: 2.4.0.0-44
Ambari DB: :Oracle
Oozie/Hive DB: Oracle/Oracle
Security:no
Security Type:MIT/MIT
Reporter: Andrii Tkach
Assignee: Andrii Tkach
Priority: Critical
 Fix For: 2.2.2


Sometimes YARN graphs, (and summary panel elements sometimes) take long time to 
load. Please look at the videos of the test that failed because it could not 
find the yarn graphs,heatmaps in time.
I was able to reproduce this issue. STR:
1) Go to Yarn service page, but navigate away from it before the graphs are 
loaded
2) Try going back again to Yarn page
The graphs will not load. This was observed on Hbase page as well. Hitting F5 
or Signing back in solves the problem



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

[jira] [Commented] (AMBARI-15024) Ability for Ambari to determine java_vendor and pass it as hostLevelParam


[ 
https://issues.apache.org/jira/browse/AMBARI-15024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144570#comment-15144570
 ] 

Hadoop QA commented on AMBARI-15024:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12787623/AMBARI-15024.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:red}-1 core tests{color}.  The patch failed these unit tests in 
ambari-server:

  org.apache.ambari.server.stack.KerberosDescriptorTest
  org.apache.ambari.server.stack.StackManagerTest
  
org.apache.ambari.server.controller.AmbariManagementControllerImplTest
  
org.apache.ambari.server.controller.internal.ClientConfigResourceProviderTest

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/5333//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/5333//console

This message is automatically generated.

> Ability for Ambari to determine java_vendor and pass it as hostLevelParam
> -
>
> Key: AMBARI-15024
> URL: https://issues.apache.org/jira/browse/AMBARI-15024
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Reporter: Greg Senia
>  Labels: ibm-jdk
> Fix For: 2.3.0, 2.2.2
>
> Attachments: AMBARI-15024.patch
>
>
> Adding the ability to pass java_vendor down to ambari-agent as a 
> hostLevelParam will allow other JDKs to be put into place such as the IBM JDK 
> which has different tuning params when it comes to hadoop-env.



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

[jira] [Commented] (AMBARI-15025) Hosts page: Filtering works incorrectly with multiple filters applied


[ 
https://issues.apache.org/jira/browse/AMBARI-15025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144410#comment-15144410
 ] 

Oleg Nechiporenko commented on AMBARI-15025:


Committed to trunk and 2.2

> Hosts page: Filtering works incorrectly with multiple filters applied
> -
>
> Key: AMBARI-15025
> URL: https://issues.apache.org/jira/browse/AMBARI-15025
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15025.patch, AMBARI-15025_branch-2.2.patch
>
>
> On 1200 node cluster I enabled filter for alerts and then put in a hostname 
> filter... which showed hosts that did not match the filter. (video attached).
> POST request:
> URL: 
> {code:java}
> /api/v1/clusters/perf/hosts?fields=Hosts/rack_info,Hosts/host_name,Hosts/maintenance_state,Hosts/public_host_name,Hosts/cpu_count,Hosts/ph_cpu_count,alerts_summary,Hosts/host_status,Hosts/last_heartbeat_time,Hosts/ip,host_components/HostRoles/state,host_components/HostRoles/maintenance_state,host_components/HostRoles/stale_configs,host_components/HostRoles/service_name,host_components/HostRoles/desired_admin_state,Hosts/total_mem,stack_versions/HostStackVersions,stack_versions/repository_versions/RepositoryVersions/repository_version,stack_versions/repository_versions/RepositoryVersions/id,stack_versions/repository_versions/RepositoryVersions/display_name_response=true_size=10=0=Hosts/host_name.as
> {code}
> Data: 
> {code:java}
> {"RequestInfo":{"query":"page_size=10=0_summary/CRITICAL>0|alerts_summary/WARNING>0/host_name.matches(.*23.*)"}}
> {code}
> Response: 
> {code:java}
> {
>   "itemTotal" : "308",
>   "items" : [
> {
>   "Hosts" : {
> "cpu_count" : 4,
> "host_name" : "perf-b-1.c.pramod-thangali.internal",
> "host_status" : "HEALTHY",
> "ip" : "10.240.0.4",
> "last_heartbeat_time" : 1455013064276,
> "maintenance_state" : "OFF",
> "ph_cpu_count" : 4,
> "public_host_name" : "perf-b-1.c.pramod-thangali.internal",
> "rack_info" : "/default-rack",
> "total_mem" : 15301028
>   }...
> {code}



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

[jira] [Commented] (AMBARI-14842) ambari agent upstart support


[ 
https://issues.apache.org/jira/browse/AMBARI-14842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144500#comment-15144500
 ] 

Hudson commented on AMBARI-14842:
-

FAILURE: Integrated in Ambari-branch-2.2 #327 (See 
[https://builds.apache.org/job/Ambari-branch-2.2/327/])
AMBARI-14842. ambari agent upstart support (aonishuk) (aonishuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=3c0c22c17bc759b676282b551fe69598b59c08ba])
* ambari-agent/pom.xml
* ambari-agent/etc/init/ambari-agent.conf
* ambari-agent/conf/unix/ambari-agent


> ambari agent upstart support
> 
>
> Key: AMBARI-14842
> URL: https://issues.apache.org/jira/browse/AMBARI-14842
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.2.2
>
> Attachments: AMBARI-14842.patch
>
>
> Context:  
> It is critical that we have a service that can auto-restart during crashes and
> reboots. This is done via upstart on Ubuntu.  
> The issue is that Ambari-Agent scripts in the current state is not upstart-
> able due to some implementation issues.  
> So to make this upstart-able, we had to directly take a dependency into a
> helper script for Ambari-Agent (as per user1 recommendation). However, this
> dependency turned out to be fragile, since it broke in HDP 2.4. So this JIRA
> is about making ambari agent upstartable directly when we install Ambari, so
> users doesn’t have to resort to a fragile dependency. We made it work  
> Details:  
> The way to start ambari-agent and ambari-server are different for user1 and
> user2.  
> In the case for ambari-agent:  
> user1 calls "/etc/init.d/ambari-agent" (which invokes /usr/sbin/ambari-agent)
> to start ambari agent.  
> user2 uses "/etc/init/ambari-agent" (which directly calls /usr/lib/python2.6
> /site-packages/ambari_agent/main.py) to start ambari-agent.  
> user2 has to call ambari-agent/main.py directly is because we need upstart to
> re-start services when it crashes unexpectedly and upstart does not work if we
> configure it to call /usr/sbin/ambari-agent.  
> The reason is that upstart needs to track the process for the service (i.e.
> ambari-agent) that it needs to restart; however, /usr/sbin/ambari-agent
> executes lots of commands that would result in new processes being spawned and
> will confuse upstart the "main" process it should be tracking.  
> We need user1 to give us a upstart-compatible script otherwise HDP changes can
> break us unexpectedly.  
> We also have a upstart script for ambari-server for the same reason.  
> Attaching both scripts for user1 to take a look.



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

[jira] [Updated] (AMBARI-15026) Hadoop metrics emit interval seems to be 1 minute instead of 10 seconds default


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

Dmytro Sen updated AMBARI-15026:

Attachment: AMBARI-15026-trunk.patch

> Hadoop metrics emit interval seems to be 1 minute instead of 10 seconds 
> default
> ---
>
> Key: AMBARI-15026
> URL: https://issues.apache.org/jira/browse/AMBARI-15026
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.2.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15026-trunk.patch
>
>
> Noticed this after upgrade from 2.1.2 to 2.2.0.
> Bug seems to have been introduced bu AMBARI-13037.
> Need to ensure, send internal of 60 seconds and leaving the collection or 
> sampling interval as default.
> {code}
> 0: jdbc:phoenix:localhost:61181:/ams-hbase-un> select * from METRIC_RECORD 
> where METRIC_NAME='rpc.rpc.RpcQueueTimeAvgTime' and APP_ID = 'namenode' order 
> by SERVER_TIME desc limit 10;
> +-++-++-++--++--++++
> | METRIC_NAME |  HOSTNAME  | SERVER_TIME |   APP_ID   | INSTANCE_ID | 
> START_TIME |UNITS | METRIC_SUM | METRIC_COUNT | METRIC_MAX | 
> METRIC_MIN |  METRICS   |
> +-++-++-++--++--++++
> | rpc.rpc.RpcQueueTimeAvgTime | c6401.ambari.apache.org | 1455155926917 | 
> namenode   | null| 1455155866867 | null | 0.0
> | 2| 0.0| 0.0| 
> {"1455155866867":0.0,"1455155926867":0.0} |
> | rpc.rpc.RpcQueueTimeAvgTime | c6401.ambari.apache.org | 1455155806915 | 
> namenode   | null| 1455155746868 | null | 0.5
> | 2| 0.5| 0.0| 
> {"1455155746868":0.5,"1455155806868":0.0} |
> | rpc.rpc.RpcQueueTimeAvgTime | c6401.ambari.apache.org | 1455155686901 | 
> namenode   | null| 1455155626867 | null | 2.0
> | 2| 1.0| 1.0| 
> {"1455155626867":1.0,"1455155686867":1.0} |
> | rpc.rpc.RpcQueueTimeAvgTime | c6401.ambari.apache.org | 1455155566987 | 
> namenode   | null| 1455155446868 | null | 1.5
> | 3| 1.0| 0.0| 
> {"1455155446868":0.0,"1455155506866":1.0,"1455155566872":0.5} |
> | rpc.rpc.RpcQueueTimeAvgTime | c6401.ambari.apache.org | 1455155221565 | 
> namenode   | null| 1455155101498 | null | 2.5
> | 3| 1.0| 0.5| 
> {"1455155101498":1.0,"1455155161496":1.0,"1455155221497":0.5} |
> | rpc.rpc.RpcQueueTimeAvgTime | c6401.ambari.apache.org | 1455155041553 | 
> namenode   | null| 1455154981496 | null | 2.5
> | 2| 2.5| 0.0| 
> {"1455154981496":0.0,"1455155041498":2.5} |
> | rpc.rpc.RpcQueueTimeAvgTime | c6401.ambari.apache.org | 1455154921619 | 
> namenode   | null| 1455154801501 | null | 
> 0.8334 | 3| 0.5| 0.0| 
> {"1455154801501":0.5,"1455154861497":0.7,"1455154921497":0.0} 
> |
> | rpc.rpc.RpcQueueTimeAvgTime | c6401.ambari.apache.org | 1455154679870 | 
> namenode   | null| 1455154619738 | null | 1.0
> | 2| 1.0| 0.0| 
> {"1455154619738":1.0,"1455154679738":0.0} |
> | rpc.rpc.RpcQueueTimeAvgTime | c6401.ambari.apache.org | 1455154559985 | 
> namenode   | null| 1455154439747 | null | 1.5
> | 3| 1.0| 0.0| 
> {"1455154439747":0.5,"1455154499738":0.0,"1455154559740":1.0} |
> +-++-++-++--++--++++
> 9 rows selected (0.485 seconds)
> {code}



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

Review Request 43526: Hadoop metrics emit interval seems to be 1 minute instead of 10 seconds default

2016-02-12 Thread Dmytro Sen


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43526/
---

Review request for Ambari, Aravindan Vijayan and Sid Wagle.


Bugs: AMBARI-15026
https://issues.apache.org/jira/browse/AMBARI-15026


Repository: ambari


Description
---

Noticed this after upgrade from 2.1.2 to 2.2.0.
Bug seems to have been introduced bu AMBARI-13037.
Need to ensure, send internal of 60 seconds and leaving the collection or 
sampling interval as default.


Diffs
-

  
ambari-server/src/main/resources/common-services/ACCUMULO/1.6.1.2.2.0/package/scripts/params.py
 c415f6e 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-site.xml
 180b43b 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py
 8193737 
  
ambari-server/src/main/resources/common-services/FLUME/1.4.0.2.0/package/scripts/params.py
 d2f2d02 
  
ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/package/scripts/params_linux.py
 337f09d 
  
ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/package/scripts/params_linux.py
 f186a89 
  
ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-START/scripts/params.py
 426237c 

Diff: https://reviews.apache.org/r/43526/diff/


Testing
---

--
Ran 255 tests in 8.465s

OK
--
Total run:902
Total errors:0
Total failures:0
OK


Thanks,

Dmytro Sen

[jira] [Commented] (AMBARI-15023) Agents should not ask for auto-start command details if it has the details


[ 
https://issues.apache.org/jira/browse/AMBARI-15023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144580#comment-15144580
 ] 

Hadoop QA commented on AMBARI-15023:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12787619/AMBARI-15023.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:red}-1 javac{color:red}.  The patch appears to cause the build to 
fail.

Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/5334//console

This message is automatically generated.

> Agents should not ask for auto-start command details if it has the details
> --
>
> Key: AMBARI-15023
> URL: https://issues.apache.org/jira/browse/AMBARI-15023
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.2.1
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15023.patch
>
>
> agent keeps on asking for the details for auto execution commands even if it 
> has the details. this results in server unnecessarily computing START command 
> details when its not needed.



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

[jira] [Commented] (AMBARI-15008) Use force_toggle_kerberos directive when retrying enable Kerberos on failure


[ 
https://issues.apache.org/jira/browse/AMBARI-15008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144583#comment-15144583
 ] 

Hadoop QA commented on AMBARI-15008:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12787446/AMBARI-15008.patch
  against trunk revision .

{color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/5335//console

This message is automatically generated.

> Use force_toggle_kerberos directive when retrying enable Kerberos on failure
> 
>
> Key: AMBARI-15008
> URL: https://issues.apache.org/jira/browse/AMBARI-15008
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.2.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.2.2
>
> Attachments: AMBARI-15008.patch
>
>
> Use {{force_toggle_kerberos directive}} when retrying enable Kerberos on 
> failure rather than disabling and then re-enabling Kerberos.
> This occurs in the _Enable Kerberos Wizard_ if a failure occurs on the 
> "Enable Kerberos" page and the _retry_ button_ is clicked. 
> *Note*: to simulate an error condition on this step, stop the KDC (krb5kdc) 
> and admin (kadmin) servers before transitioning to the "Enable Kerberos" page 
> from the "Configure Identities" page in the "Enable Kerberos" wizard. 
> To force a retry of enabling Kerberos, the following API call should be made:
> {code}
> PUT /api/v1/clusters/CLUSTER_NAME?force_toggle_kerberos=true
> {
>   "Clusters" : {
> "security_type" : "KERBEROS"
> }
> }
> {code}



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

[jira] [Updated] (AMBARI-14701) assign_master_components.js breaks next step in certain case

2016-02-12 Thread Matt (JIRA)


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

Matt updated AMBARI-14701:
--
Attachment: AMBARI-14701-trunk-v3.patch

> assign_master_components.js breaks next step in certain case
> 
>
> Key: AMBARI-14701
> URL: https://issues.apache.org/jira/browse/AMBARI-14701
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Reporter: jun aoki
>Assignee: Matt
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-14701-branch-2.2-v1.patch, 
> AMBARI-14701-branch-2.2-v2.patch, AMBARI-14701-branch-2.2-v3.patch, 
> AMBARI-14701-branch-2.2-v4.patch, AMBARI-14701-branch-2.2.patch, 
> AMBARI-14701-trunk-v1.patch, AMBARI-14701-trunk-v2.patch, 
> AMBARI-14701-trunk-v3.patch, AMBARI-14701-trunk.patch, screenshot-1.png, 
> screenshot-2.png
>
>
> We have a custom wizard with AssignMasterComponents mixin and 
> useServerValidation is set true.
> Select Host page shows a confirmation when there is a validation error 
> validated on the server side, which is good.
> However, if you cancel the confirmation, you can no longer go to Next page by 
> clicking Next button.



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

[jira] [Commented] (AMBARI-14936) Tweaks to reduce build time


[ 
https://issues.apache.org/jira/browse/AMBARI-14936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144612#comment-15144612
 ] 

Hadoop QA commented on AMBARI-14936:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12787655/AMBARI-14936.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-server ambari-web.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/5337//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/5337//console

This message is automatically generated.

> Tweaks to reduce build time
> ---
>
> Key: AMBARI-14936
> URL: https://issues.apache.org/jira/browse/AMBARI-14936
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-14936.patch
>
>
> 1\. Don't build common-services and stacks folder into ambari-server.jar. This
> reduces jar size from 20Mb to 7Mb. And also reduces its buildtime.  
> 2\. -DassemblyPhase=none option to skip building tarballs. Is useful when
> building simply a jar is needed.  
> 3\. -Dnodemodules.dir option to not redownload node_modules folder in ambari-
> web. This reduces ambari-web time from ~1.1 min. to ~15s. (unless it's a first
> build and node_modules is not there). However this may rearly result in npm
> cache issues, which is simply solved by 'rm -rf ambari-web/node_modules'



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

[jira] [Updated] (AMBARI-15027) Sometimes Yarn graphs,Heatmaps take longer to load


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

Andrii Tkach updated AMBARI-15027:
--
Attachment: AMBARI-15027.patch

> Sometimes Yarn graphs,Heatmaps take longer to load
> --
>
> Key: AMBARI-15027
> URL: https://issues.apache.org/jira/browse/AMBARI-15027
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.1
> Environment: ambari-server version: ambari-server-2.2.1.0-66.x86_64
> ambari-server --hash: a659e664cd8b4f05883d8a8a1412e68097bd2b85
> HDP Stack: 2.4
> HDP Version: 2.4.0.0-44
> Ambari DB: :Oracle
> Oozie/Hive DB: Oracle/Oracle
> Security:no
> Security Type:MIT/MIT
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15027.patch, yarnGraphsNotLoading.flv
>
>
> Sometimes YARN graphs, (and summary panel elements sometimes) take long time 
> to load. Please look at the videos of the test that failed because it could 
> not find the yarn graphs,heatmaps in time.
> I was able to reproduce this issue. STR:
> 1) Go to Yarn service page, but navigate away from it before the graphs are 
> loaded
> 2) Try going back again to Yarn page
> The graphs will not load. This was observed on Hbase page as well. Hitting F5 
> or Signing back in solves the problem



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

Re: Review Request 43465: Hdfs keytab for hawq service check on secured cluster

2016-02-12 Thread Robert Levas



> On Feb. 10, 2016, 8:15 p.m., Robert Levas wrote:
> > ambari-server/src/main/resources/common-services/HAWQ/2.0.0/kerberos.json, 
> > lines 5-8
> > 
> >
> > Is this identity used by both the `HAWKMASTER` and `HAWQSTANDBY` 
> > components?  If not, this block should be moved into the appropriate 
> > component since we want to use it sparingly.  Esentially the 
> > `/HDFS/NAMENODE/hdfs` is the _root_ user for HDFS.  So we need to becareful 
> > where it gets put.
> 
> jun aoki wrote:
> @robert Levas, thank you for your comment and sharing the knowledge. hdfs 
> identity is indeed used by both HAWQMASTER and HAWQSTANDBY, thus I drop this 
> issue.

Thanks for the clarification.


> On Feb. 10, 2016, 8:15 p.m., Robert Levas wrote:
> > ambari-server/src/main/resources/common-services/HAWQ/2.0.0/kerberos.json, 
> > lines 27-53
> > 
> >
> > This identitiy seems to be duplicated in both components.  You should 
> > probably move this to the service level and reference it in the component 
> > if component-specific changes need to be made.
> 
> jun aoki wrote:
> Robert, thank you for telling me this. I saw the duplicate but had no 
> idea I could define once and refers to it. 
> 
> https://cwiki.apache.org/confluence/display/AMBARI/Automated+Kerberizaton#AutomatedKerberizaton-Service-levelIdentities
>  for anybody who wants to know the detail of this.

Essentially you used the same mechanism when including the HDFS identity. :)


> On Feb. 10, 2016, 8:15 p.m., Robert Levas wrote:
> > ambari-server/src/main/resources/common-services/HAWQ/2.0.0/kerberos.json, 
> > line 31
> > 
> >
> > This is an interesting principal name choice.  Why not use a principal 
> > name that helps to identify is use.  Like, `hawq@${realm}` or better yet 
> > something like `${hawq-env/hawk_user}@${realm}`.
> 
> jun aoki wrote:
> I agree Robert. this should've been hawq/_HOST${realm}. Currently this is 
> a HAWQ limitation (it won't take any other principal name) 
> https://issues.apache.org/jira/browse/HAWQ-406

Thanks for clarification, hopefully HAWQ is fixed soon since using `postgres` 
can be confusing an potentally problematic.  My big issue with this is how the 
auth-to-local rules get generated.  In this case, since no `local_username` 
property is set for the identity, a specific auth-to-local rule will not be 
created.  Thus, the mapping will fall to the default rule with does a 
one-for-one mapping and will associate this identity with the local `postgres` 
account - which may or may not exist.  This scenario happens with HDFS when it 
maps a Kerberos identity to a local user account. So maybe if there is a local 
user created for HAWQ (`hawq-env/hawq-user` maybe?) use that as the 
`local_username` for the identity. For example:

```
{
  ...,
  "principal": {
"value": "postgres@${realm}",
"type" : "service",
"local_username" : "${hawq-env/hawq-user}"
  },
  ...
}

```


- Robert


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43465/#review118794
---


On Feb. 10, 2016, 8 p.m., jun aoki wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43465/
> ---
> 
> (Updated Feb. 10, 2016, 8 p.m.)
> 
> 
> Review request for Ambari.
> 
> 
> Bugs: AMBARI-15001
> https://issues.apache.org/jira/browse/AMBARI-15001
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> This is to add hdfs keytab for hawq nodes.
> Currently HAWQ's service check fails due to data clean up after service check 
> is completed and causes a false negative.
> 
> 
> Diffs
> -
> 
>   ambari-server/src/main/resources/common-services/HAWQ/2.0.0/kerberos.json 
> cc11c15 
> 
> Diff: https://reviews.apache.org/r/43465/diff/
> 
> 
> Testing
> ---
> 
> Locally teted.
> 
> 
> Thanks,
> 
> jun aoki
> 
>

Re: Review Request 30862: AMBARI-9098 Cannot install new secure services to existing secure HDFS cluster


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/30862/#review119019
---



Please close this review: it's over a year old.

- Nate Cole


On Feb. 10, 2015, 8:43 p.m., Rishi Pidva wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/30862/
> ---
> 
> (Updated Feb. 10, 2015, 8:43 p.m.)
> 
> 
> Review request for Ambari, Jaimin Jetly, jun aoki, Nate Cole, and Vitthal 
> Gogate.
> 
> 
> Bugs: AMBARI-9098
> https://issues.apache.org/jira/browse/AMBARI-9098
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Add service fails to update the configuration properly due to missing 
> properties in controller. Also noticed there was issue in loading kerberos 
> domain on Add service screen.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/stacks/HDP/2.0.6/services/OOZIE/package/scripts/oozie_service.py
>  ac4280a 
>   ambari-web/app/controllers/main/admin/security/add/step2.js 8ccd301 
>   ambari-web/app/data/HDP2/secure_mapping.js f4a17d9 
>   ambari-web/app/data/HDP2/secure_properties.js 7760dd2 
>   ambari-web/app/data/secure_mapping.js cfca947 
>   ambari-web/app/mixins/wizard/addSecurityConfigs.js 659f9cc 
> 
> Diff: https://reviews.apache.org/r/30862/diff/
> 
> 
> Testing
> ---
> 
> Manual testing for the following use cases:
> - Adding security to a basic cluster deployed via blueprint with HDFS, YARN, 
> Mapred, Zookeeper and Knox.
> - Adding Oozie service to secure cluster
> - Adding Hive service to secure cluster.
> - Removing security
> - Adding security back.
> 
> 
> Thanks,
> 
> Rishi Pidva
> 
>

[jira] [Commented] (AMBARI-15025) Hosts page: Filtering works incorrectly with multiple filters applied


[ 
https://issues.apache.org/jira/browse/AMBARI-15025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144646#comment-15144646
 ] 

Hudson commented on AMBARI-15025:
-

FAILURE: Integrated in Ambari-branch-2.2 #328 (See 
[https://builds.apache.org/job/Ambari-branch-2.2/328/])
AMBARI-15025. Hosts page: Filtering works incorrectly with multiple 
(onechiporenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b75cc8d3a83cb61318bb7f9261cb56ec22fb4a48])
* ambari-web/app/controllers/main/host.js


> Hosts page: Filtering works incorrectly with multiple filters applied
> -
>
> Key: AMBARI-15025
> URL: https://issues.apache.org/jira/browse/AMBARI-15025
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15025.patch, AMBARI-15025_branch-2.2.patch
>
>
> On 1200 node cluster I enabled filter for alerts and then put in a hostname 
> filter... which showed hosts that did not match the filter. (video attached).
> POST request:
> URL: 
> {code:java}
> /api/v1/clusters/perf/hosts?fields=Hosts/rack_info,Hosts/host_name,Hosts/maintenance_state,Hosts/public_host_name,Hosts/cpu_count,Hosts/ph_cpu_count,alerts_summary,Hosts/host_status,Hosts/last_heartbeat_time,Hosts/ip,host_components/HostRoles/state,host_components/HostRoles/maintenance_state,host_components/HostRoles/stale_configs,host_components/HostRoles/service_name,host_components/HostRoles/desired_admin_state,Hosts/total_mem,stack_versions/HostStackVersions,stack_versions/repository_versions/RepositoryVersions/repository_version,stack_versions/repository_versions/RepositoryVersions/id,stack_versions/repository_versions/RepositoryVersions/display_name_response=true_size=10=0=Hosts/host_name.as
> {code}
> Data: 
> {code:java}
> {"RequestInfo":{"query":"page_size=10=0_summary/CRITICAL>0|alerts_summary/WARNING>0/host_name.matches(.*23.*)"}}
> {code}
> Response: 
> {code:java}
> {
>   "itemTotal" : "308",
>   "items" : [
> {
>   "Hosts" : {
> "cpu_count" : 4,
> "host_name" : "perf-b-1.c.pramod-thangali.internal",
> "host_status" : "HEALTHY",
> "ip" : "10.240.0.4",
> "last_heartbeat_time" : 1455013064276,
> "maintenance_state" : "OFF",
> "ph_cpu_count" : 4,
> "public_host_name" : "perf-b-1.c.pramod-thangali.internal",
> "rack_info" : "/default-rack",
> "total_mem" : 15301028
>   }...
> {code}



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

[jira] [Commented] (AMBARI-15007) Make amazon2015 to be part of redhat6 family


[ 
https://issues.apache.org/jira/browse/AMBARI-15007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144645#comment-15144645
 ] 

Hudson commented on AMBARI-15007:
-

FAILURE: Integrated in Ambari-branch-2.2 #328 (See 
[https://builds.apache.org/job/Ambari-branch-2.2/328/])
AMBARI-15007. Make amazon2015 to be part of redhat6 family (aonishuk) 
(aonishuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6ed6758e620da2315107075eb76e26a1272040b1])
* ambari-server/src/main/resources/stacks/HDP/2.4/repos/repoinfo.xml
* ambari-server/src/main/resources/stacks/HDP/2.2/repos/repoinfo.xml
* ambari-server/src/main/resources/stacks/HDP/2.3/repos/repoinfo.xml
* 
ambari-server/src/main/java/org/apache/ambari/server/state/stack/JsonOsFamilyRoot.java
* ambari-common/src/main/python/ambari_commons/resources/os_family.json
* ambari-server/src/main/java/org/apache/ambari/server/state/stack/OsFamily.java
* ambari-common/src/main/python/ambari_commons/os_check.py
* ambari-server/src/test/resources/os_family.json
* ambari-server/src/test/python/TestOSCheck.py


> Make amazon2015 to be part of redhat6 family
> 
>
> Key: AMBARI-15007
> URL: https://issues.apache.org/jira/browse/AMBARI-15007
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.2.2
>
> Attachments: AMBARI-15007.patch
>
>
> We have discussed the solution for this with Sumit Mohanty.  
> We decided to avoid introducing new os family for amazon.  
> And to simply add aliases section to os_family.json like this:
> 
> 
>   "aliases": {
> "amazon2015": "amazon6"
>   }
> 
> The only disadvantage is that when choosing repo-url, user might be confused
> that centos6 url is for amazon 2015.  
> But that what initially what I was asked to do.
> Also this jira should include using /etc/system-release instead of /etc/issue
> to detect amazon os. (/etc/os-release seems to be absent on some centos
> distros, so I think it's not reliable)



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

Re: Review Request 43527: Critical alert for Kafka when using custom port(stack 2.3 and higher)

2016-02-12 Thread Jonathan Hurley


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43527/#review119030
---


Ship it!





ambari-agent/src/main/python/ambari_agent/alerts/port_alert.py (line 105)


Should we also do 0.0.0.0 as well, similar to what the other alerts do?


- Jonathan Hurley


On Feb. 12, 2016, 9:37 a.m., Vitalyi Brodetskyi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43527/
> ---
> 
> (Updated Feb. 12, 2016, 9:37 a.m.)
> 
> 
> Review request for Ambari, Dmytro Sen and Jonathan Hurley.
> 
> 
> Bugs: AMBARI-15028
> https://issues.apache.org/jira/browse/AMBARI-15028
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> .
> 
> 
> Diffs
> -
> 
>   ambari-agent/src/main/python/ambari_agent/alerts/port_alert.py 848da65 
>   ambari-server/src/main/resources/stacks/HDP/2.3/services/KAFKA/alerts.json 
> PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/43527/diff/
> 
> 
> Testing
> ---
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Vitalyi Brodetskyi
> 
>

Re: Review Request 43248: Tweaks to reduce build time

2016-02-12 Thread Dmitro Lisnichenko


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43248/#review119011
---


Ship it!




Ship It!

- Dmitro Lisnichenko


On Feb. 12, 2016, 4:13 p.m., Andrew Onischuk wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43248/
> ---
> 
> (Updated Feb. 12, 2016, 4:13 p.m.)
> 
> 
> Review request for Ambari and Dmitro Lisnichenko.
> 
> 
> Bugs: AMBARI-14936
> https://issues.apache.org/jira/browse/AMBARI-14936
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> 1\. Don't build common-services and stacks folder into ambari-server.jar. This
> reduces jar size from 20Mb to 7Mb. And also reduces its buildtime.  
> 2\. -DassemblyPhase=none option to skip building tarballs. Is useful when
> building simply a jar is needed.  
> 3\. -Dnodemodules.dir option to not redownload node_modules folder in ambari-
> web. This reduces ambari-web time from ~1.1 min. to ~15s. (unless it's a first
> build and node_modules is not there). However this may rearly result in npm
> cache issues, which is simply solved by 'rm -rf ambari-web/node_modules'
> 
> 
> Diffs
> -
> 
>   ambari-agent/pom.xml bb7cc34 
>   ambari-server/pom.xml 33b5501 
>   ambari-web/pom.xml 761a3f0 
>   pom.xml 57c6de7 
> 
> Diff: https://reviews.apache.org/r/43248/diff/
> 
> 
> Testing
> ---
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Andrew Onischuk
> 
>

[jira] [Commented] (AMBARI-15027) Sometimes Yarn graphs,Heatmaps take longer to load


[ 
https://issues.apache.org/jira/browse/AMBARI-15027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144616#comment-15144616
 ] 

Andrii Tkach commented on AMBARI-15027:
---

24292 tests complete (31 seconds)
  156 tests pending

> Sometimes Yarn graphs,Heatmaps take longer to load
> --
>
> Key: AMBARI-15027
> URL: https://issues.apache.org/jira/browse/AMBARI-15027
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.1
> Environment: ambari-server version: ambari-server-2.2.1.0-66.x86_64
> ambari-server --hash: a659e664cd8b4f05883d8a8a1412e68097bd2b85
> HDP Stack: 2.4
> HDP Version: 2.4.0.0-44
> Ambari DB: :Oracle
> Oozie/Hive DB: Oracle/Oracle
> Security:no
> Security Type:MIT/MIT
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15027.patch, yarnGraphsNotLoading.flv
>
>
> Sometimes YARN graphs, (and summary panel elements sometimes) take long time 
> to load. Please look at the videos of the test that failed because it could 
> not find the yarn graphs,heatmaps in time.
> I was able to reproduce this issue. STR:
> 1) Go to Yarn service page, but navigate away from it before the graphs are 
> loaded
> 2) Try going back again to Yarn page
> The graphs will not load. This was observed on Hbase page as well. Hitting F5 
> or Signing back in solves the problem



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

Re: Review Request 43465: Hdfs keytab for hawq service check on secured cluster

2016-02-12 Thread Robert Levas


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43465/#review119016
---




ambari-server/src/main/resources/common-services/HAWQ/2.0.0/kerberos.json 
(lines 30 - 31)


The principal is declared as a *service*, however the princial name does 
not include the FQDN of the host the service. This is typically a bad practice. 
So if this identitiy is really a service-level identitiy, the principal name 
should be changed to `postgres/_HOST@@{realm}` or the `type` should be changed 
to `user`.



ambari-server/src/main/resources/common-services/HAWQ/2.0.0/kerberos.json 
(lines 52 - 53)


Same service vs user identity issues mentioned above.


- Robert Levas


On Feb. 10, 2016, 8 p.m., jun aoki wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43465/
> ---
> 
> (Updated Feb. 10, 2016, 8 p.m.)
> 
> 
> Review request for Ambari.
> 
> 
> Bugs: AMBARI-15001
> https://issues.apache.org/jira/browse/AMBARI-15001
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> This is to add hdfs keytab for hawq nodes.
> Currently HAWQ's service check fails due to data clean up after service check 
> is completed and causes a false negative.
> 
> 
> Diffs
> -
> 
>   ambari-server/src/main/resources/common-services/HAWQ/2.0.0/kerberos.json 
> cc11c15 
> 
> Diff: https://reviews.apache.org/r/43465/diff/
> 
> 
> Testing
> ---
> 
> Locally teted.
> 
> 
> Thanks,
> 
> jun aoki
> 
>

[jira] [Created] (AMBARI-15029) Adding a Service results in deleting Config Group mappings (more than 1 CG present)

Aleksandr Kovalenko created AMBARI-15029:


 Summary: Adding a Service results in deleting Config Group 
mappings (more than 1 CG present)
 Key: AMBARI-15029
 URL: https://issues.apache.org/jira/browse/AMBARI-15029
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.2.0, 2.2.1
Reporter: Aleksandr Kovalenko
Assignee: Aleksandr Kovalenko
Priority: Critical
 Fix For: 2.2.2


If we add new service and have some config group with custom property (it is 
absent in default group and is present only in custom config group), this 
property disappears.



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

[jira] [Commented] (AMBARI-15029) Adding a Service results in deleting Config Group mappings (more than 1 CG present)


[ 
https://issues.apache.org/jira/browse/AMBARI-15029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144666#comment-15144666
 ] 

Aleksandr Kovalenko commented on AMBARI-15029:
--

24292 tests complete (22 seconds)
  156 tests pending


> Adding a Service results in deleting Config Group mappings (more than 1 CG 
> present)
> ---
>
> Key: AMBARI-15029
> URL: https://issues.apache.org/jira/browse/AMBARI-15029
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.0, 2.2.1
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15029.patch, AMBARI-15029_branch-2.2.patch
>
>
> If we add new service and have some config group with custom property (it is 
> absent in default group and is present only in custom config group), this 
> property disappears.



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

[jira] [Updated] (AMBARI-15024) Ability for Ambari to determine java_vendor and pass it as hostLevelParam

2016-02-12 Thread Greg Senia (JIRA)


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

Greg Senia updated AMBARI-15024:

Attachment: (was: AMBARI-15024.patch)

> Ability for Ambari to determine java_vendor and pass it as hostLevelParam
> -
>
> Key: AMBARI-15024
> URL: https://issues.apache.org/jira/browse/AMBARI-15024
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Reporter: Greg Senia
>  Labels: ibm-jdk
> Fix For: 2.3.0, 2.2.2
>
> Attachments: AMBARI-15024.patch
>
>
> Adding the ability to pass java_vendor down to ambari-agent as a 
> hostLevelParam will allow other JDKs to be put into place such as the IBM JDK 
> which has different tuning params when it comes to hadoop-env.



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

[jira] [Commented] (AMBARI-15024) Ability for Ambari to determine java_vendor and pass it as hostLevelParam

2016-02-12 Thread Greg Senia (JIRA)


[ 
https://issues.apache.org/jira/browse/AMBARI-15024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144673#comment-15144673
 ] 

Greg Senia commented on AMBARI-15024:
-

Updated test cases to test for java_vendor and for 14 objects in hostLevelParams

> Ability for Ambari to determine java_vendor and pass it as hostLevelParam
> -
>
> Key: AMBARI-15024
> URL: https://issues.apache.org/jira/browse/AMBARI-15024
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Reporter: Greg Senia
>  Labels: ibm-jdk
> Fix For: 2.3.0, 2.2.2
>
> Attachments: AMBARI-15024.patch
>
>
> Adding the ability to pass java_vendor down to ambari-agent as a 
> hostLevelParam will allow other JDKs to be put into place such as the IBM JDK 
> which has different tuning params when it comes to hadoop-env.



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

Re: Review Request 43368: assign_master_components.js breaks next step in certain case


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43368/
---

(Updated Feb. 12, 2016, 5:46 a.m.)


Review request for Ambari, Alexander Denissov, Alejandro Fernandez, Aleksandr 
Kovalenko, Alexandr Antonenko, bhuvnesh chaudhary, Goutam Tadi, Jaimin Jetly, 
jun aoki, Lav Jain, Newton Alex, Oleksandr Diachenko, and Sumit Mohanty.


Bugs: AMBARI-14701
https://issues.apache.org/jira/browse/AMBARI-14701


Repository: ambari


Description
---

There was noAction onSecondary (Cancel button). Implemented onSecondary, and 
modified the callback for the same.


Diffs (updated)
-

  ambari-web/app/mixins/wizard/assign_master_components.js 0693507 

Diff: https://reviews.apache.org/r/43368/diff/


Testing (updated)
---

Unit tests passed.
  24292 tests complete (19 seconds)
  156 tests pending

[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 01:15 min
[INFO] Finished at: 2016-02-12T05:45:05-08:00
[INFO] Final Memory: 12M/311M
[INFO] 


Thanks,

Matt

[jira] [Commented] (AMBARI-15008) Use force_toggle_kerberos directive when retrying enable Kerberos on failure

2016-02-12 Thread Antonenko Alexander (JIRA)


[ 
https://issues.apache.org/jira/browse/AMBARI-15008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144591#comment-15144591
 ] 

Antonenko Alexander commented on AMBARI-15008:
--

Patch does not apply to trunk because it was accidentally committed with 
AMBARI-15009. So it only needs to be committed to branch-2.2

> Use force_toggle_kerberos directive when retrying enable Kerberos on failure
> 
>
> Key: AMBARI-15008
> URL: https://issues.apache.org/jira/browse/AMBARI-15008
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.2.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.2.2
>
> Attachments: AMBARI-15008.patch
>
>
> Use {{force_toggle_kerberos directive}} when retrying enable Kerberos on 
> failure rather than disabling and then re-enabling Kerberos.
> This occurs in the _Enable Kerberos Wizard_ if a failure occurs on the 
> "Enable Kerberos" page and the _retry_ button_ is clicked. 
> *Note*: to simulate an error condition on this step, stop the KDC (krb5kdc) 
> and admin (kadmin) servers before transitioning to the "Enable Kerberos" page 
> from the "Configure Identities" page in the "Enable Kerberos" wizard. 
> To force a retry of enabling Kerberos, the following API call should be made:
> {code}
> PUT /api/v1/clusters/CLUSTER_NAME?force_toggle_kerberos=true
> {
>   "Clusters" : {
> "security_type" : "KERBEROS"
> }
> }
> {code}



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

[jira] [Commented] (AMBARI-15027) Sometimes Yarn graphs,Heatmaps take longer to load


[ 
https://issues.apache.org/jira/browse/AMBARI-15027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144618#comment-15144618
 ] 

Aleksandr Kovalenko commented on AMBARI-15027:
--

+1 for the patch

> Sometimes Yarn graphs,Heatmaps take longer to load
> --
>
> Key: AMBARI-15027
> URL: https://issues.apache.org/jira/browse/AMBARI-15027
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.1
> Environment: ambari-server version: ambari-server-2.2.1.0-66.x86_64
> ambari-server --hash: a659e664cd8b4f05883d8a8a1412e68097bd2b85
> HDP Stack: 2.4
> HDP Version: 2.4.0.0-44
> Ambari DB: :Oracle
> Oozie/Hive DB: Oracle/Oracle
> Security:no
> Security Type:MIT/MIT
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15027.patch, yarnGraphsNotLoading.flv
>
>
> Sometimes YARN graphs, (and summary panel elements sometimes) take long time 
> to load. Please look at the videos of the test that failed because it could 
> not find the yarn graphs,heatmaps in time.
> I was able to reproduce this issue. STR:
> 1) Go to Yarn service page, but navigate away from it before the graphs are 
> loaded
> 2) Try going back again to Yarn page
> The graphs will not load. This was observed on Hbase page as well. Hitting F5 
> or Signing back in solves the problem



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

Re: Review Request 42818: Register Version: add ability to load new version definition file


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/42818/#review119017
---



If this change is pushed, please close this review.

- Nate Cole


On Jan. 26, 2016, 2:45 p.m., Xi Wang wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/42818/
> ---
> 
> (Updated Jan. 26, 2016, 2:45 p.m.)
> 
> 
> Review request for Ambari, Nate Cole and Yusaku Sako.
> 
> 
> Bugs: AMBARI-14795
> https://issues.apache.org/jira/browse/AMBARI-14795
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> This one belongs to UI work of Patch Upgrade ( Provide ability to apply 
> single patches on top of RU release), and is the first part to implement" 
> Manage Ambari > Register Version" page.
> Should generate a new "Register Version" page, and add the ability to load 
> new version definition file through two options:
> 1. Browse local files and then Upload file,
> 2. Enter the Url then click on "Read Version File" button,
> After either option, the Version File (a .xml file) should be POST to server, 
> then loaded (GET call) to the page content.
> 
> Be sure to load the mock data, will integrate API later.
> 
> 
> Diffs
> -
> 
>   
> ambari-admin/src/main/resources/ui/admin-web/app/assets/data/version/version.json
>  7c604f1 
>   
> ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/stackVersions/StackVersionsCreateCtrl.js
>  a817d88 
>   ambari-admin/src/main/resources/ui/admin-web/app/scripts/i18n.config.js 
> 04485c6 
>   ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/Stack.js 
> ffed3cc 
>   ambari-admin/src/main/resources/ui/admin-web/app/styles/main.css 895a28f 
>   
> ambari-admin/src/main/resources/ui/admin-web/app/views/stackVersions/stackVersionPage.html
>  9b7e032 
> 
> Diff: https://reviews.apache.org/r/42818/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Xi Wang
> 
>

[jira] [Created] (AMBARI-15028) Critical alert for Kafka when using custom port(stack 2.3 and higher)

2016-02-12 Thread Vitaly Brodetskyi (JIRA)

Vitaly Brodetskyi created AMBARI-15028:
--

 Summary: Critical alert for Kafka when using custom port(stack 2.3 
and higher)
 Key: AMBARI-15028
 URL: https://issues.apache.org/jira/browse/AMBARI-15028
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Reporter: Vitaly Brodetskyi
Assignee: Vitaly Brodetskyi
Priority: Critical
 Fix For: 2.2.2






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

[jira] [Updated] (AMBARI-15028) Critical alert for Kafka when using custom port(stack 2.3 and higher)

2016-02-12 Thread Vitaly Brodetskyi (JIRA)


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

Vitaly Brodetskyi updated AMBARI-15028:
---
Attachment: AMBARI-15028.patch

> Critical alert for Kafka when using custom port(stack 2.3 and higher)
> -
>
> Key: AMBARI-15028
> URL: https://issues.apache.org/jira/browse/AMBARI-15028
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15028.patch
>
>




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

[jira] [Commented] (AMBARI-15029) Adding a Service results in deleting Config Group mappings (more than 1 CG present)

2016-02-12 Thread Andrii Babiichuk (JIRA)


[ 
https://issues.apache.org/jira/browse/AMBARI-15029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144678#comment-15144678
 ] 

Andrii Babiichuk commented on AMBARI-15029:
---

+1 for the patches

> Adding a Service results in deleting Config Group mappings (more than 1 CG 
> present)
> ---
>
> Key: AMBARI-15029
> URL: https://issues.apache.org/jira/browse/AMBARI-15029
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.0, 2.2.1
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15029.patch, AMBARI-15029_branch-2.2.patch
>
>
> If we add new service and have some config group with custom property (it is 
> absent in default group and is present only in custom config group), this 
> property disappears.



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

[jira] [Updated] (AMBARI-15029) Adding a Service results in deleting Config Group mappings (more than 1 CG present)


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

Aleksandr Kovalenko updated AMBARI-15029:
-
Attachment: AMBARI-15029_branch-2.2.patch

> Adding a Service results in deleting Config Group mappings (more than 1 CG 
> present)
> ---
>
> Key: AMBARI-15029
> URL: https://issues.apache.org/jira/browse/AMBARI-15029
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.0, 2.2.1
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15029.patch, AMBARI-15029_branch-2.2.patch
>
>
> If we add new service and have some config group with custom property (it is 
> absent in default group and is present only in custom config group), this 
> property disappears.



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

Re: Review Request 43527: Critical alert for Kafka when using custom port(stack 2.3 and higher)


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43527/#review119029
---


Ship it!




Ship It!

- Matt


On Feb. 12, 2016, 6:37 a.m., Vitalyi Brodetskyi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43527/
> ---
> 
> (Updated Feb. 12, 2016, 6:37 a.m.)
> 
> 
> Review request for Ambari, Dmytro Sen and Jonathan Hurley.
> 
> 
> Bugs: AMBARI-15028
> https://issues.apache.org/jira/browse/AMBARI-15028
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> .
> 
> 
> Diffs
> -
> 
>   ambari-agent/src/main/python/ambari_agent/alerts/port_alert.py 848da65 
>   ambari-server/src/main/resources/stacks/HDP/2.3/services/KAFKA/alerts.json 
> PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/43527/diff/
> 
> 
> Testing
> ---
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Vitalyi Brodetskyi
> 
>

Re: Review Request 41397: AMBARI-14383 Add support for Ranger TagSync process as a component under RANGER


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/41397/#review119018
---



What's the status of this review?  If it's pushed, please close.  You can abort 
the review if it's not going to happen.  Thanks.

- Nate Cole


On Dec. 15, 2015, 11:46 a.m., Gautam Borad wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/41397/
> ---
> 
> (Updated Dec. 15, 2015, 11:46 a.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jaimin Jetly, Madhan 
> Neethiraj, Mahadev Konar, Nate Cole, Sumit Mohanty, Selvamohan Neethiraj, and 
> Velmurugan Periasamy.
> 
> 
> Bugs: AMBARI-14383
> https://issues.apache.org/jira/browse/AMBARI-14383
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Ranger TagSync is a separate component that will be responsible for 
> synchronizing the tags from Apache Atlas into Apache Ranger (db).
> 
> Add Ranger TagSync component under existing RANGER service.
> The component will be a master component
> Ability to start/stop the component independently of Ranger Admin.
> Ability to install the component on any host of the cluster
> Support should be available only from HDP 2.3
> 
> 
> Diffs
> -
> 
>   
> ambari-common/src/main/python/resource_management/libraries/functions/conf_select.py
>  fd83c53 
>   
> ambari-common/src/main/python/resource_management/libraries/functions/hdp_select.py
>  5628f33 
>   
> ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/params.py
>  b6e5ee9 
>   
> ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/ranger_service.py
>  4f711c3 
>   
> ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/ranger_tagsync.py
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/setup_ranger_xml.py
>  8de0d80 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/services/RANGER/configuration/ranger-tagsync-site.xml
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/services/RANGER/metainfo.xml 
> 2fb8a9a 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.3.xml
>  cf3afbe 
>   ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.3.xml 
> cce20be 
> 
> Diff: https://reviews.apache.org/r/41397/diff/
> 
> 
> Testing
> ---
> 
> Installed Ranger on centos 6 and enabled Ranger TagSync module.
> 
> Tested minor upgrade from 2.3.x to 2.3.xx
> 
> 
> Thanks,
> 
> Gautam Borad
> 
>

Review Request 43527: Critical alert for Kafka when using custom port(stack 2.3 and higher)

2016-02-12 Thread Vitalyi Brodetskyi


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43527/
---

Review request for Ambari, Dmytro Sen and Jonathan Hurley.


Bugs: AMBARI-15028
https://issues.apache.org/jira/browse/AMBARI-15028


Repository: ambari


Description
---

.


Diffs
-

  ambari-agent/src/main/python/ambari_agent/alerts/port_alert.py 848da65 
  ambari-server/src/main/resources/stacks/HDP/2.3/services/KAFKA/alerts.json 
PRE-CREATION 

Diff: https://reviews.apache.org/r/43527/diff/


Testing
---

mvn clean test


Thanks,

Vitalyi Brodetskyi

Re: Review Request 43527: Critical alert for Kafka when using custom port(stack 2.3 and higher)

2016-02-12 Thread Dmytro Sen


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43527/#review119021
---


Ship it!




Ship It!

- Dmytro Sen


On Фев. 12, 2016, 2:37 п.п., Vitalyi Brodetskyi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43527/
> ---
> 
> (Updated Фев. 12, 2016, 2:37 п.п.)
> 
> 
> Review request for Ambari, Dmytro Sen and Jonathan Hurley.
> 
> 
> Bugs: AMBARI-15028
> https://issues.apache.org/jira/browse/AMBARI-15028
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> .
> 
> 
> Diffs
> -
> 
>   ambari-agent/src/main/python/ambari_agent/alerts/port_alert.py 848da65 
>   ambari-server/src/main/resources/stacks/HDP/2.3/services/KAFKA/alerts.json 
> PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/43527/diff/
> 
> 
> Testing
> ---
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Vitalyi Brodetskyi
> 
>

[jira] [Updated] (AMBARI-15029) Adding a Service results in deleting Config Group mappings (more than 1 CG present)


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

Aleksandr Kovalenko updated AMBARI-15029:
-
Attachment: AMBARI-15029.patch

> Adding a Service results in deleting Config Group mappings (more than 1 CG 
> present)
> ---
>
> Key: AMBARI-15029
> URL: https://issues.apache.org/jira/browse/AMBARI-15029
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.0, 2.2.1
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15029.patch, AMBARI-15029_branch-2.2.patch
>
>
> If we add new service and have some config group with custom property (it is 
> absent in default group and is present only in custom config group), this 
> property disappears.



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

Debugging Views

2016-02-12 Thread Harp, Michael

Anyone have a technique for debugging view issues? For instance I am not seeing 
any job records displayed in the stock Tez view(ambari-2.2.2.0-64) and so far 
have not found any clues in ambari-server.log or javascript errors on the 
frontend.
Thanks,
Mike

[jira] [Updated] (AMBARI-14701) assign_master_components.js breaks next step in certain case

2016-02-12 Thread Matt (JIRA)


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

Matt updated AMBARI-14701:
--
Attachment: AMBARI-14701-branch-2.2-v4.patch

> assign_master_components.js breaks next step in certain case
> 
>
> Key: AMBARI-14701
> URL: https://issues.apache.org/jira/browse/AMBARI-14701
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Reporter: jun aoki
>Assignee: Matt
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-14701-branch-2.2-v1.patch, 
> AMBARI-14701-branch-2.2-v2.patch, AMBARI-14701-branch-2.2-v3.patch, 
> AMBARI-14701-branch-2.2-v4.patch, AMBARI-14701-branch-2.2.patch, 
> AMBARI-14701-trunk-v1.patch, AMBARI-14701-trunk-v2.patch, 
> AMBARI-14701-trunk.patch, screenshot-1.png, screenshot-2.png
>
>
> We have a custom wizard with AssignMasterComponents mixin and 
> useServerValidation is set true.
> Select Host page shows a confirmation when there is a validation error 
> validated on the server side, which is good.
> However, if you cancel the confirmation, you can no longer go to Next page by 
> clicking Next button.



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

[jira] [Commented] (AMBARI-15008) Use force_toggle_kerberos directive when retrying enable Kerberos on failure

2016-02-12 Thread Antonenko Alexander (JIRA)


[ 
https://issues.apache.org/jira/browse/AMBARI-15008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144594#comment-15144594
 ] 

Antonenko Alexander commented on AMBARI-15008:
--

committed to branch-2.2, as this changes are already in trunk

> Use force_toggle_kerberos directive when retrying enable Kerberos on failure
> 
>
> Key: AMBARI-15008
> URL: https://issues.apache.org/jira/browse/AMBARI-15008
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.2.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.2.2
>
> Attachments: AMBARI-15008.patch
>
>
> Use {{force_toggle_kerberos directive}} when retrying enable Kerberos on 
> failure rather than disabling and then re-enabling Kerberos.
> This occurs in the _Enable Kerberos Wizard_ if a failure occurs on the 
> "Enable Kerberos" page and the _retry_ button_ is clicked. 
> *Note*: to simulate an error condition on this step, stop the KDC (krb5kdc) 
> and admin (kadmin) servers before transitioning to the "Enable Kerberos" page 
> from the "Configure Identities" page in the "Enable Kerberos" wizard. 
> To force a retry of enabling Kerberos, the following API call should be made:
> {code}
> PUT /api/v1/clusters/CLUSTER_NAME?force_toggle_kerberos=true
> {
>   "Clusters" : {
> "security_type" : "KERBEROS"
> }
> }
> {code}



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

[jira] [Commented] (AMBARI-14936) Tweaks to reduce build time


[ 
https://issues.apache.org/jira/browse/AMBARI-14936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144614#comment-15144614
 ] 

Andrew Onischuk commented on AMBARI-14936:
--

The patch changes pom.xml files only which are not covered with tests, that's 
why 'no tests were included'

> Tweaks to reduce build time
> ---
>
> Key: AMBARI-14936
> URL: https://issues.apache.org/jira/browse/AMBARI-14936
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-14936.patch
>
>
> 1\. Don't build common-services and stacks folder into ambari-server.jar. This
> reduces jar size from 20Mb to 7Mb. And also reduces its buildtime.  
> 2\. -DassemblyPhase=none option to skip building tarballs. Is useful when
> building simply a jar is needed.  
> 3\. -Dnodemodules.dir option to not redownload node_modules folder in ambari-
> web. This reduces ambari-web time from ~1.1 min. to ~15s. (unless it's a first
> build and node_modules is not there). However this may rearly result in npm
> cache issues, which is simply solved by 'rm -rf ambari-web/node_modules'



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

[jira] [Updated] (AMBARI-15027) Sometimes Yarn graphs,Heatmaps take longer to load


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

Andrii Tkach updated AMBARI-15027:
--
Attachment: yarnGraphsNotLoading.flv

> Sometimes Yarn graphs,Heatmaps take longer to load
> --
>
> Key: AMBARI-15027
> URL: https://issues.apache.org/jira/browse/AMBARI-15027
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.1
> Environment: ambari-server version: ambari-server-2.2.1.0-66.x86_64
> ambari-server --hash: a659e664cd8b4f05883d8a8a1412e68097bd2b85
> HDP Stack: 2.4
> HDP Version: 2.4.0.0-44
> Ambari DB: :Oracle
> Oozie/Hive DB: Oracle/Oracle
> Security:no
> Security Type:MIT/MIT
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15027.patch, yarnGraphsNotLoading.flv
>
>
> Sometimes YARN graphs, (and summary panel elements sometimes) take long time 
> to load. Please look at the videos of the test that failed because it could 
> not find the yarn graphs,heatmaps in time.
> I was able to reproduce this issue. STR:
> 1) Go to Yarn service page, but navigate away from it before the graphs are 
> loaded
> 2) Try going back again to Yarn page
> The graphs will not load. This was observed on Hbase page as well. Hitting F5 
> or Signing back in solves the problem



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

Re: Review Request 43248: Tweaks to reduce build time

2016-02-12 Thread Andrew Onischuk


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43248/
---

(Updated Feb. 12, 2016, 2:13 p.m.)


Review request for Ambari and Dmitro Lisnichenko.


Bugs: AMBARI-14936
https://issues.apache.org/jira/browse/AMBARI-14936


Repository: ambari


Description
---

1\. Don't build common-services and stacks folder into ambari-server.jar. This
reduces jar size from 20Mb to 7Mb. And also reduces its buildtime.  
2\. -DassemblyPhase=none option to skip building tarballs. Is useful when
building simply a jar is needed.  
3\. -Dnodemodules.dir option to not redownload node_modules folder in ambari-
web. This reduces ambari-web time from ~1.1 min. to ~15s. (unless it's a first
build and node_modules is not there). However this may rearly result in npm
cache issues, which is simply solved by 'rm -rf ambari-web/node_modules'


Diffs (updated)
-

  ambari-agent/pom.xml bb7cc34 
  ambari-server/pom.xml 33b5501 
  ambari-web/pom.xml 761a3f0 
  pom.xml 57c6de7 

Diff: https://reviews.apache.org/r/43248/diff/


Testing
---

mvn clean test


Thanks,

Andrew Onischuk

Re: Review Request 43465: Hdfs keytab for hawq service check on secured cluster

2016-02-12 Thread Robert Levas



> On Feb. 10, 2016, 8:15 p.m., Robert Levas wrote:
> > ambari-server/src/main/resources/common-services/HAWQ/2.0.0/kerberos.json, 
> > line 31
> > 
> >
> > This is an interesting principal name choice.  Why not use a principal 
> > name that helps to identify is use.  Like, `hawq@${realm}` or better yet 
> > something like `${hawq-env/hawk_user}@${realm}`.
> 
> jun aoki wrote:
> I agree Robert. this should've been hawq/_HOST${realm}. Currently this is 
> a HAWQ limitation (it won't take any other principal name) 
> https://issues.apache.org/jira/browse/HAWQ-406
> 
> Robert Levas wrote:
> Thanks for clarification, hopefully HAWQ is fixed soon since using 
> `postgres` can be confusing an potentally problematic.  My big issue with 
> this is how the auth-to-local rules get generated.  In this case, since no 
> `local_username` property is set for the identity, a specific auth-to-local 
> rule will not be created.  Thus, the mapping will fall to the default rule 
> with does a one-for-one mapping and will associate this identity with the 
> local `postgres` account - which may or may not exist.  This scenario happens 
> with HDFS when it maps a Kerberos identity to a local user account. So maybe 
> if there is a local user created for HAWQ (`hawq-env/hawq-user` maybe?) use 
> that as the `local_username` for the identity. For example:
> 
> ```
> {
>   ...,
>   "principal": {
> "value": "postgres@${realm}",
> "type" : "service",
> "local_username" : "${hawq-env/hawq-user}"
>   },
>   ...
> }
> 
> ```

Note: While creating the example. I noticed the descrepancy in the principal 
name. Technically the value should have been `postgres/_HOST@${realm}` or the 
type should have been `user`.  This is noted in issues I just added to the 
review.


- Robert


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43465/#review118794
---


On Feb. 10, 2016, 8 p.m., jun aoki wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43465/
> ---
> 
> (Updated Feb. 10, 2016, 8 p.m.)
> 
> 
> Review request for Ambari.
> 
> 
> Bugs: AMBARI-15001
> https://issues.apache.org/jira/browse/AMBARI-15001
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> This is to add hdfs keytab for hawq nodes.
> Currently HAWQ's service check fails due to data clean up after service check 
> is completed and causes a false negative.
> 
> 
> Diffs
> -
> 
>   ambari-server/src/main/resources/common-services/HAWQ/2.0.0/kerberos.json 
> cc11c15 
> 
> Diff: https://reviews.apache.org/r/43465/diff/
> 
> 
> Testing
> ---
> 
> Locally teted.
> 
> 
> Thanks,
> 
> jun aoki
> 
>

[jira] [Updated] (AMBARI-15024) Ability for Ambari to determine java_vendor and pass it as hostLevelParam

2016-02-12 Thread Greg Senia (JIRA)


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

Greg Senia updated AMBARI-15024:

Attachment: AMBARI-15024.patch

> Ability for Ambari to determine java_vendor and pass it as hostLevelParam
> -
>
> Key: AMBARI-15024
> URL: https://issues.apache.org/jira/browse/AMBARI-15024
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Reporter: Greg Senia
>  Labels: ibm-jdk
> Fix For: 2.3.0, 2.2.2
>
> Attachments: AMBARI-15024.patch
>
>
> Adding the ability to pass java_vendor down to ambari-agent as a 
> hostLevelParam will allow other JDKs to be put into place such as the IBM JDK 
> which has different tuning params when it comes to hadoop-env.



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

Re: Review Request 43463: AMBARI-15002. HiveServerInteractive. Adding skelton code for Hive Server Interactive component support.

2016-02-12 Thread Jaimin Jetly


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43463/#review119026
---


Ship it!




Ship It!

- Jaimin Jetly


On Feb. 11, 2016, 9:07 p.m., Swapan Shridhar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43463/
> ---
> 
> (Updated Feb. 11, 2016, 9:07 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jaimin Jetly, and Sumit Gupta.
> 
> 
> Bugs: AMBARI-15002
> https://issues.apache.org/jira/browse/AMBARI-15002
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> - Added skelton code for "Hive Server Interactive" component support.
> - A dummy Hive component "Hive Server2 Interactive" will show up on UI, but 
> will not have any backing start, stop etc. code. (next in line in terms of 
> checkin).
> - Along with that, added the "hive-interactive-site.xml" for configs.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/metainfo.xml 
> dfa20a5 
>   
> ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/stacks/HDP/2.4/services/HIVE/configuration/hive-interactive-site.xml
>  PRE-CREATION 
>   ambari-server/src/main/resources/stacks/HDP/2.4/services/HIVE/metainfo.xml 
> 82bdc92 
> 
> Diff: https://reviews.apache.org/r/43463/diff/
> 
> 
> Testing
> ---
> 
> - Using HDP 2.4 stack : Component shows up on UI using HDP 2.4. Screenshot : 
> ""HiveServer2 Interactive" component"
> - Using HDP 2.3 stack : Isolated from my changes and "HiveServer2 
> Interactive" component doesn't show up.
> - Python tests pass.
> 
> 
> File Attachments
> 
> 
> "HiveServer2 Interactive" component
>   
> https://reviews.apache.org/media/uploaded/files/2016/02/11/d260200a-505a-400a-a012-53d61101d024__Screen_Shot_2016-02-10_at_5.20.25_PM.png
> 
> 
> Thanks,
> 
> Swapan Shridhar
> 
>

[jira] [Commented] (AMBARI-15021) Set AMBARI_METRICS as the default datasource


[ 
https://issues.apache.org/jira/browse/AMBARI-15021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144244#comment-15144244
 ] 

Hudson commented on AMBARI-15021:
-

SUCCESS: Integrated in Ambari-branch-2.2 #326 (See 
[https://builds.apache.org/job/Ambari-branch-2.2/326/])
AMBARI-15021. Set AMBARI_METRICS as the default datasource. (Prajwal Rao 
(yusaku: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=bf8ecffedb07d59cf2ed10c0d57fd26fc2a68e4d])
* 
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/templates/metrics_grafana_datasource.json.j2


> Set AMBARI_METRICS as the default datasource
> 
>
> Key: AMBARI-15021
> URL: https://issues.apache.org/jira/browse/AMBARI-15021
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.2.2
>Reporter: Prajwal Rao
>Assignee: Prajwal Rao
> Fix For: 2.2.2
>
> Attachments: AMBARI-15021.patch
>
>
> When Grafana is deployed as a component, the auto created datasource 
> (AMBARI_METRICS) isn't set as default.



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

[jira] [Commented] (AMBARI-14715) TimelineServer configuration is missing in yarn-env.xml.


[ 
https://issues.apache.org/jira/browse/AMBARI-14715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144243#comment-15144243
 ] 

Hudson commented on AMBARI-14715:
-

SUCCESS: Integrated in Ambari-branch-2.2 #326 (See 
[https://builds.apache.org/job/Ambari-branch-2.2/326/])
AMBARI-14715. TimelineServer configuration is missing in yarn-env.xml. (yusaku: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4d61fa1b1a004ed34c06209fa5fd1ba69b6b78c9])
* 
ambari-server/src/main/resources/stacks/HDP/2.3/services/YARN/configuration/yarn-env.xml


> TimelineServer configuration is missing in yarn-env.xml.
> 
>
> Key: AMBARI-14715
> URL: https://issues.apache.org/jira/browse/AMBARI-14715
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Reporter: Akira AJISAKA
>Assignee: Akira AJISAKA
>  Labels: newbie
> Fix For: 2.2.2
>
> Attachments: AMBARI-14715.001.patch
>
>
> In yarn-env.xml, {{YARN_HISTORYSERVER_OPTS}} and 
> {{YARN_HISTORYSERVER_HEAPSIZE}} are not valid for TimelineServer.
> {noformat:title=ambari-server/src/main/resources/stacks/HDP/2.3/services/YARN/configuration/yarn-env.xml}
>   # Specify the max Heapsize for the HistoryManager using a numerical 
> value
>   # in the scale of MB. For example, to specify an jvm option of 
> -Xmx1000m, set
>   # the value to 1024.
>   # This value will be overridden by an Xmx setting specified in either 
> YARN_OPTS
>   # and/or YARN_HISTORYSERVER_OPTS.
>   # If not specified, the default value will be picked from either 
> YARN_HEAPMAX
>   # or JAVA_HEAP_MAX with YARN_HEAPMAX as the preferred option of the two.
>   export YARN_HISTORYSERVER_HEAPSIZE={{apptimelineserver_heapsize}}
> {noformat}
> {{HISTORYSERVER}} should be {{TIMELINESERVER}}.



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

[jira] [Commented] (AMBARI-14800) Alerts: HDFS alerts based on AMS metrics


[ 
https://issues.apache.org/jira/browse/AMBARI-14800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144248#comment-15144248
 ] 

Dmytro Sen commented on AMBARI-14800:
-

The failure is not related to this jira

> Alerts: HDFS alerts based on AMS metrics
> 
>
> Key: AMBARI-14800
> URL: https://issues.apache.org/jira/browse/AMBARI-14800
> Project: Ambari
>  Issue Type: Task
>  Components: alerts, ambari-metrics, stacks
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14800.patch, AMBARI-14800_2-trunk.patch
>
>
> - Define a script based alert that is run by the Ambari agent for HDFS
> - The alert definition captures the metrics to query, optionally a AMS appId 
> / instanceId along with the percentage thresholds to alert on.
> - The alert should support thresholds on variance in the data. This is time 
> window based so the alert definitions will be per day / per week / per month 
> or per quarter.



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

[jira] [Commented] (AMBARI-15010) YARN metrics not written due to permissions on metrics properties file


[ 
https://issues.apache.org/jira/browse/AMBARI-15010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144255#comment-15144255
 ] 

Dmytro Sen commented on AMBARI-15010:
-

The failure is not related to this jira.

> YARN metrics not written due to permissions on metrics properties file
> --
>
> Key: AMBARI-15010
> URL: https://issues.apache.org/jira/browse/AMBARI-15010
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics, stacks
>Affects Versions: 2.2.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
> Fix For: 2.2.2
>
> Attachments: AMBARI-15010-trunk.patch
>
>
> If env had umask setting of 027.
> The hadoop-metrics2.properties was owned by "hdfs:root" with 640 permissions.
> The ownership group needs to be "hadoop" so all hadoop daemons can read the 
> properties file.



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

[jira] [Created] (AMBARI-15025) Hosts page: Filtering works incorrectly with multiple filters applied

Oleg Nechiporenko created AMBARI-15025:
--

 Summary: Hosts page: Filtering works incorrectly with multiple 
filters applied
 Key: AMBARI-15025
 URL: https://issues.apache.org/jira/browse/AMBARI-15025
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.2.2
Reporter: Oleg Nechiporenko
Assignee: Oleg Nechiporenko
Priority: Critical
 Fix For: 2.2.2


On 1200 node cluster I enabled filter for alerts and then put in a hostname 
filter... which showed hosts that did not match the filter. (video attached).
POST request:
URL: 
{code:java}
/api/v1/clusters/perf/hosts?fields=Hosts/rack_info,Hosts/host_name,Hosts/maintenance_state,Hosts/public_host_name,Hosts/cpu_count,Hosts/ph_cpu_count,alerts_summary,Hosts/host_status,Hosts/last_heartbeat_time,Hosts/ip,host_components/HostRoles/state,host_components/HostRoles/maintenance_state,host_components/HostRoles/stale_configs,host_components/HostRoles/service_name,host_components/HostRoles/desired_admin_state,Hosts/total_mem,stack_versions/HostStackVersions,stack_versions/repository_versions/RepositoryVersions/repository_version,stack_versions/repository_versions/RepositoryVersions/id,stack_versions/repository_versions/RepositoryVersions/display_name_response=true_size=10=0=Hosts/host_name.as
{code}
Data: 
{code:java}
{"RequestInfo":{"query":"page_size=10=0_summary/CRITICAL>0|alerts_summary/WARNING>0/host_name.matches(.*23.*)"}}
{code}
Response: 
{code:java}
{
  "itemTotal" : "308",
  "items" : [
{
  "Hosts" : {
"cpu_count" : 4,
"host_name" : "perf-b-1.c.pramod-thangali.internal",
"host_status" : "HEALTHY",
"ip" : "10.240.0.4",
"last_heartbeat_time" : 1455013064276,
"maintenance_state" : "OFF",
"ph_cpu_count" : 4,
"public_host_name" : "perf-b-1.c.pramod-thangali.internal",
"rack_info" : "/default-rack",
"total_mem" : 15301028
  }...
{code}



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

[jira] [Updated] (AMBARI-15030) Fix unreasonable default heap settings for AMS HBase heapsize and xmn size.


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

Aravindan Vijayan updated AMBARI-15030:
---
Description: 
Default values from the stack (Not stack advisor)

regionserver_heapsize : 512MB
regionserver_xmn_size : 256MB

xmn is 50% of rs heapsize which is unreasonable. Changing to 756MB and 128MB 
respectively.

  was:
Default values from the stack (Not stack advisor)
regionserver_heapsize : 512MB
regionserver_xmn_size : 256MB

xmn is 50% of rs heapsize which is unreasonable. Changing to 756MB and 128MB 
respectively.


> Fix unreasonable default heap settings for AMS HBase heapsize and xmn size.
> ---
>
> Key: AMBARI-15030
> URL: https://issues.apache.org/jira/browse/AMBARI-15030
> Project: Ambari
>  Issue Type: Bug
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
>
> Default values from the stack (Not stack advisor)
> regionserver_heapsize : 512MB
> regionserver_xmn_size : 256MB
> xmn is 50% of rs heapsize which is unreasonable. Changing to 756MB and 128MB 
> respectively.



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

[jira] [Created] (AMBARI-15031) Duplicate key violation syncing groups when performing ldap-sync with --all option

2016-02-12 Thread JIRA

Olivér Szabó created AMBARI-15031:
-

 Summary: Duplicate key violation syncing groups when performing 
ldap-sync with --all option
 Key: AMBARI-15031
 URL: https://issues.apache.org/jira/browse/AMBARI-15031
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.2.0
Reporter: Olivér Szabó
Assignee: Olivér Szabó
 Fix For: 2.2.2


While performing an ldap-sync using the {{--all}} option, when groups imported 
from a previous ldap-sync already exist, a duplicate key violation is 
encountered on the previously existing groups. The duplicate key violation 
occurs on the {{UNQ_groups_0}} constraint. 

{noformat}
Syncing all...ERROR: 
Exiting with exit code 1. 
REASON: Caught exception running LDAP sync. Exception EclipseLink-4002 (Eclipse 
Persistence Services - 2.5.2.v20140319-9ad6abd): 
org.eclipse.persistence.exceptions.DatabaseException 
Internal Exception: java.sql.BatchUpdateException: Duplicate entry 'mygroup1' 
for key 'UNQ_groups_0' 
Error Code: 1062
{noformat}

This does not seem of happen when performing an ldap-sync with the {{--groups}} 
option. 




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

[jira] [Commented] (AMBARI-14701) assign_master_components.js breaks next step in certain case


[ 
https://issues.apache.org/jira/browse/AMBARI-14701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144881#comment-15144881
 ] 

Hadoop QA commented on AMBARI-14701:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12787658/AMBARI-14701-trunk-v3.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-web.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/5341//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/5341//console

This message is automatically generated.

> assign_master_components.js breaks next step in certain case
> 
>
> Key: AMBARI-14701
> URL: https://issues.apache.org/jira/browse/AMBARI-14701
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Reporter: jun aoki
>Assignee: Matt
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-14701-branch-2.2-v1.patch, 
> AMBARI-14701-branch-2.2-v2.patch, AMBARI-14701-branch-2.2-v3.patch, 
> AMBARI-14701-branch-2.2-v4.patch, AMBARI-14701-branch-2.2.patch, 
> AMBARI-14701-trunk-v1.patch, AMBARI-14701-trunk-v2.patch, 
> AMBARI-14701-trunk-v3.patch, AMBARI-14701-trunk.patch, screenshot-1.png, 
> screenshot-2.png
>
>
> We have a custom wizard with AssignMasterComponents mixin and 
> useServerValidation is set true.
> Select Host page shows a confirmation when there is a validation error 
> validated on the server side, which is good.
> However, if you cancel the confirmation, you can no longer go to Next page by 
> clicking Next button.



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

Re: Review Request 43508: AMBARI-14932: "download zip" does not work

2016-02-12 Thread Keta Patel

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43508/
---

(Updated Feb. 12, 2016, 5:34 p.m.)

Review request for Ambari, Di Li, DIPAYAN BHOWMICK, Pallav Kulshreshtha, and
Srimanth Gunturi.

Summary (updated)
-

AMBARI-14932: "download zip" does not work

Bugs: AMBARI-14932
https://issues.apache.org/jira/browse/AMBARI-14932

Repository: ambari

Description
---

Steps to Reproduce:
1. go to "View" - "FILES" - " Create Instance"
2. go to hdfs file view
3. click "download zip" icon
The click doesn't download any file. The REST call returns 200 OK status.

Detailed steps on configuring Views can be found in the link below:
http://docs.hortonworks.com/HDPDocuments/Ambari-2.1.0.0/bk_ambari_views_guide/bk_ambari_views_guide-20150721.pdf

Diffs
-

contrib/views/files/src/main/java/org/apache/ambari/view/filebrowser/DownloadService.java
749174a
contrib/views/files/src/main/resources/ui/app/controllers/file.js 88fa5fb

Diff: https://reviews.apache.org/r/43508/diff/

Testing
---

FIX:
The check for "allowed" in the controller, from the response of
zipByRequestId() ("/zip" API call for downloading zip file) resulted in no
action after clicking the download zip button. This was because there was no
"allowed" paramter in the response of zip download. This "allowed" property was
added in the response of browse() ("/browse" API call for downloading
individual file) to check if the user had permissions for the file or not. This
was verified by opening the file. If that operation didn't throw an error, then
it would mean that the user had the required permissions to download the
individual file. But the fact that the point of execution reaches past the
statement of opening the file verifies that the user has the permission. The
check with "checkperm" and setting the response with "allowed" attribute in the
response is not necessary.
So, for the fix I simply removed the check for "allowed" from the controller
and also removed the check for "checkperm" which sets the "allowed" attribute
in the response.

TESTS:
There are already exisitng tests for DownloadService, so I haven't added any
new ones.

Thanks,

Keta Patel

[jira] [Created] (AMBARI-15030) Fix unreasonable default heap settings for AMS HBase heapsize and xmn size.

Aravindan Vijayan created AMBARI-15030:
--

 Summary: Fix unreasonable default heap settings for AMS HBase 
heapsize and xmn size.
 Key: AMBARI-15030
 URL: https://issues.apache.org/jira/browse/AMBARI-15030
 Project: Ambari
  Issue Type: Bug
Reporter: Aravindan Vijayan
Assignee: Aravindan Vijayan
Priority: Critical


Actual
regionserver_heapsize : 512MB
regionserver_xmn_size : 256MB

xmn is 50% of rs heapsize which is unreasonable. Changing to 756MB and 128MB 
respectively.



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

[jira] [Commented] (AMBARI-14932) "download zip" does not work

2016-02-12 Thread DIPAYAN BHOWMICK (JIRA)


[ 
https://issues.apache.org/jira/browse/AMBARI-14932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144845#comment-15144845
 ] 

DIPAYAN BHOWMICK commented on AMBARI-14932:
---

Hi [~patel...@us.ibm.com], can you please create a review request in 
https://reviews.apache.org and add the review link to this bug. Add, me and 
[~pallavkul] as the reviewers. I am sorry, I was not able to check the patch, 
but I will definitely try out the patch this weekend.

Thanks.

> "download zip"  does not work
> -
>
> Key: AMBARI-14932
> URL: https://issues.apache.org/jira/browse/AMBARI-14932
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views, contrib
>Affects Versions: trunk
>Reporter: Keta Patel
>Assignee: Keta Patel
> Attachments: AMBARI-14932_Feb10_fix1.patch, AMBARI-14932_Feb11.patch, 
> DownloadService.tiff, adapter.tiff, error_after_file_open.tiff, file_1.tiff, 
> file_2.tiff, screenshot.tiff
>
>
> Steps to Reproduce:
> 1. go to "View" - "FILES" - " Create Instance"
> 2. go to hdfs file view
> 3. click "download zip" icon
> The click doesn't download any file. The REST call returns 200 OK status.
> Detailed steps on configuring Views can be found in the link below:
> http://docs.hortonworks.com/HDPDocuments/Ambari-2.1.0.0/bk_ambari_views_guide/bk_ambari_views_guide-20150721.pdf



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

[jira] [Commented] (AMBARI-15008) Use force_toggle_kerberos directive when retrying enable Kerberos on failure


[ 
https://issues.apache.org/jira/browse/AMBARI-15008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144849#comment-15144849
 ] 

Hudson commented on AMBARI-15008:
-

SUCCESS: Integrated in Ambari-branch-2.2 #329 (See 
[https://builds.apache.org/job/Ambari-branch-2.2/329/])
AMBARI-15008. Use force_toggle_kerberos directive when retrying enable (hiveww: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d5412a54f6b2e153ed0a12f88d4428a5ca13bc81])
* ambari-web/app/utils/ajax/ajax.js
* ambari-web/app/controllers/main/admin/kerberos/step7_controller.js


> Use force_toggle_kerberos directive when retrying enable Kerberos on failure
> 
>
> Key: AMBARI-15008
> URL: https://issues.apache.org/jira/browse/AMBARI-15008
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.2.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.2.2
>
> Attachments: AMBARI-15008.patch
>
>
> Use {{force_toggle_kerberos directive}} when retrying enable Kerberos on 
> failure rather than disabling and then re-enabling Kerberos.
> This occurs in the _Enable Kerberos Wizard_ if a failure occurs on the 
> "Enable Kerberos" page and the _retry_ button_ is clicked. 
> *Note*: to simulate an error condition on this step, stop the KDC (krb5kdc) 
> and admin (kadmin) servers before transitioning to the "Enable Kerberos" page 
> from the "Configure Identities" page in the "Enable Kerberos" wizard. 
> To force a retry of enabling Kerberos, the following API call should be made:
> {code}
> PUT /api/v1/clusters/CLUSTER_NAME?force_toggle_kerberos=true
> {
>   "Clusters" : {
> "security_type" : "KERBEROS"
> }
> }
> {code}



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

[jira] [Commented] (AMBARI-15027) Sometimes Yarn graphs,Heatmaps take longer to load


[ 
https://issues.apache.org/jira/browse/AMBARI-15027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144854#comment-15144854
 ] 

Hadoop QA commented on AMBARI-15027:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12787661/AMBARI-15027.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-web.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/5340//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/5340//console

This message is automatically generated.

> Sometimes Yarn graphs,Heatmaps take longer to load
> --
>
> Key: AMBARI-15027
> URL: https://issues.apache.org/jira/browse/AMBARI-15027
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.1
> Environment: ambari-server version: ambari-server-2.2.1.0-66.x86_64
> ambari-server --hash: a659e664cd8b4f05883d8a8a1412e68097bd2b85
> HDP Stack: 2.4
> HDP Version: 2.4.0.0-44
> Ambari DB: :Oracle
> Oozie/Hive DB: Oracle/Oracle
> Security:no
> Security Type:MIT/MIT
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15027.patch, yarnGraphsNotLoading.flv
>
>
> Sometimes YARN graphs, (and summary panel elements sometimes) take long time 
> to load. Please look at the videos of the test that failed because it could 
> not find the yarn graphs,heatmaps in time.
> I was able to reproduce this issue. STR:
> 1) Go to Yarn service page, but navigate away from it before the graphs are 
> loaded
> 2) Try going back again to Yarn page
> The graphs will not load. This was observed on Hbase page as well. Hitting F5 
> or Signing back in solves the problem



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

[jira] [Commented] (AMBARI-13951) Service install will fail if the property-type attribute of any service config property has a value in a stack not known to ambari-server

2016-02-12 Thread Christopher Jackson (JIRA)


[ 
https://issues.apache.org/jira/browse/AMBARI-13951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144894#comment-15144894
 ] 

Christopher Jackson commented on AMBARI-13951:
--

Just ran into this issue when migrating to Ambari 2.2 from 2.1. Is there a list 
somewhere of valid Property Types?

> Service install will fail if the property-type attribute of any service 
> config property has a value in a stack not known to ambari-server
> -
>
> Key: AMBARI-13951
> URL: https://issues.apache.org/jira/browse/AMBARI-13951
> Project: Ambari
>  Issue Type: Bug
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
> Fix For: 2.3.0
>
> Attachments: AMBARI-13951.v1.patch
>
>
> If any property in stack definition has a random property-type , then create 
> configuration API fails with the runtime exception as shown below and request 
> never comes back with any response.
> {code}
> java.lang.RuntimeException: Unable to serialize to json: 
> org.codehaus.jackson.JsonGenerationException: Null key for a Map not allowed 
> in JSON (use a converting NullKeySerializer?)
> at 
> org.apache.ambari.server.api.services.serializers.JsonSerializer.serialize(JsonSerializer.java:71)
> at 
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:113)
> at 
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:74)
> at 
> org.apache.ambari.server.api.services.ClusterService.updateCluster(ClusterService.java:151)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at 
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:540)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:715)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
> at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1496)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
> at 
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118)
> Caused by: org.codehaus.jackson.JsonGenerationException: Null key for a Map 
> not allowed in JSON (use a converting NullKeySerializer?)
> at 
> org.codehaus.jackson.map.ser.impl.FailingSerializer.serialize(FailingSerializer.java:34)
> at 
> org.codehaus.jackson.map.ser.std.MapSerializer.serializeFields(MapSerializer.java:237)
> at 
> org.codehaus.jackson.map.ser.std.MapSerializer.serialize(MapSerializer.java:186)
> at 
> org.codehaus.jackson.map.ser.std.MapSerializer.serialize(MapSerializer.java:23)
> at 
>

[jira] [Commented] (AMBARI-15026) Hadoop metrics emit interval seems to be 1 minute instead of 10 seconds default


[ 
https://issues.apache.org/jira/browse/AMBARI-15026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144914#comment-15144914
 ] 

Hadoop QA commented on AMBARI-15026:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12787652/AMBARI-15026-trunk.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-server.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/5342//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/5342//console

This message is automatically generated.

> Hadoop metrics emit interval seems to be 1 minute instead of 10 seconds 
> default
> ---
>
> Key: AMBARI-15026
> URL: https://issues.apache.org/jira/browse/AMBARI-15026
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.2.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15026-trunk.patch
>
>
> Noticed this after upgrade from 2.1.2 to 2.2.0.
> Bug seems to have been introduced bu AMBARI-13037.
> Need to ensure, send internal of 60 seconds and leaving the collection or 
> sampling interval as default.
> {code}
> 0: jdbc:phoenix:localhost:61181:/ams-hbase-un> select * from METRIC_RECORD 
> where METRIC_NAME='rpc.rpc.RpcQueueTimeAvgTime' and APP_ID = 'namenode' order 
> by SERVER_TIME desc limit 10;
> +-++-++-++--++--++++
> | METRIC_NAME |  HOSTNAME  | SERVER_TIME |   APP_ID   | INSTANCE_ID | 
> START_TIME |UNITS | METRIC_SUM | METRIC_COUNT | METRIC_MAX | 
> METRIC_MIN |  METRICS   |
> +-++-++-++--++--++++
> | rpc.rpc.RpcQueueTimeAvgTime | c6401.ambari.apache.org | 1455155926917 | 
> namenode   | null| 1455155866867 | null | 0.0
> | 2| 0.0| 0.0| 
> {"1455155866867":0.0,"1455155926867":0.0} |
> | rpc.rpc.RpcQueueTimeAvgTime | c6401.ambari.apache.org | 1455155806915 | 
> namenode   | null| 1455155746868 | null | 0.5
> | 2| 0.5| 0.0| 
> {"1455155746868":0.5,"1455155806868":0.0} |
> | rpc.rpc.RpcQueueTimeAvgTime | c6401.ambari.apache.org | 1455155686901 | 
> namenode   | null| 1455155626867 | null | 2.0
> | 2| 1.0| 1.0| 
> {"1455155626867":1.0,"1455155686867":1.0} |
> | rpc.rpc.RpcQueueTimeAvgTime | c6401.ambari.apache.org | 1455155566987 | 
> namenode   | null| 1455155446868 | null | 1.5
> | 3| 1.0| 0.0| 
> {"1455155446868":0.0,"1455155506866":1.0,"1455155566872":0.5} |
> | rpc.rpc.RpcQueueTimeAvgTime | c6401.ambari.apache.org | 1455155221565 | 
> namenode   | null| 1455155101498 | null | 2.5
> | 3| 1.0| 0.5| 
> {"1455155101498":1.0,"1455155161496":1.0,"1455155221497":0.5} |
> | rpc.rpc.RpcQueueTimeAvgTime | c6401.ambari.apache.org | 1455155041553 | 
> namenode   | null| 1455154981496 | null | 2.5
> | 2| 2.5| 0.0| 
> {"1455154981496":0.0,"1455155041498":2.5} |
> | rpc.rpc.RpcQueueTimeAvgTime | c6401.ambari.apache.org | 1455154921619 | 
> namenode   | null| 1455154801501 | null | 
> 0.8334 | 3| 0.5| 0.0| 
> {"1455154801501":0.5,"1455154861497":0.7,"1455154921497":0.0} 
> |
> | rpc.rpc.RpcQueueTimeAvgTime | c6401.ambari.apache.org | 1455154679870 | 
> namenode   | null| 1455154619738 | null | 1.0
> | 2| 1.0| 0.0| 
> {"1455154619738":1.0,"1455154679738":0.0} |
> | rpc.rpc.RpcQueueTimeAvgTime |

[jira] [Updated] (AMBARI-15030) Fix unreasonable default heap settings for AMS HBase heapsize and xmn size.


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

Aravindan Vijayan updated AMBARI-15030:
---
Description: 
Default values from the stack (Not stack advisor)
regionserver_heapsize : 512MB
regionserver_xmn_size : 256MB

xmn is 50% of rs heapsize which is unreasonable. Changing to 756MB and 128MB 
respectively.

  was:
Actual
regionserver_heapsize : 512MB
regionserver_xmn_size : 256MB

xmn is 50% of rs heapsize which is unreasonable. Changing to 756MB and 128MB 
respectively.


> Fix unreasonable default heap settings for AMS HBase heapsize and xmn size.
> ---
>
> Key: AMBARI-15030
> URL: https://issues.apache.org/jira/browse/AMBARI-15030
> Project: Ambari
>  Issue Type: Bug
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
>
> Default values from the stack (Not stack advisor)
> regionserver_heapsize : 512MB
> regionserver_xmn_size : 256MB
> xmn is 50% of rs heapsize which is unreasonable. Changing to 756MB and 128MB 
> respectively.



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

Review Request 43528: AMBARI-15030 : Fix unreasonable default heap settings for AMS HBase heapsize and xmn size.

2016-02-12 Thread Aravindan Vijayan


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43528/
---

Review request for Ambari, Dmytro Sen, Sumit Mohanty, and Sid Wagle.


Bugs: AMBARI-15030
https://issues.apache.org/jira/browse/AMBARI-15030


Repository: ambari


Description
---

Default values from the stack (Not stack advisor)
regionserver_heapsize : 512MB
regionserver_xmn_size : 256MB

xmn is 50% of rs heapsize which is unreasonable. Changing to 756MB and 128MB 
respectively.

Made the changes in stack_Advisor and UpgradeCatalog too.


Diffs
-

  
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog222.java
 88b3151 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-hbase-env.xml
 191e8b2 
  ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py 
af21008 
  
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog222Test.java
 6061e06 

Diff: https://reviews.apache.org/r/43528/diff/


Testing
---

UpgradeCatalog tests pass.
Python unit tests pass.


Thanks,

Aravindan Vijayan

[jira] [Updated] (AMBARI-15030) Fix unreasonable default heap settings for AMS HBase heapsize and xmn size.


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

Aravindan Vijayan updated AMBARI-15030:
---
Attachment: AMBARI-15030.patch

> Fix unreasonable default heap settings for AMS HBase heapsize and xmn size.
> ---
>
> Key: AMBARI-15030
> URL: https://issues.apache.org/jira/browse/AMBARI-15030
> Project: Ambari
>  Issue Type: Bug
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Attachments: AMBARI-15030.patch
>
>
> Default values from the stack (Not stack advisor)
> regionserver_heapsize : 512MB
> regionserver_xmn_size : 256MB
> xmn is 50% of rs heapsize which is unreasonable. Changing to 756MB and 128MB 
> respectively.



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

Re: Review Request 43528: AMBARI-15030 : Fix unreasonable default heap settings for AMS HBase heapsize and xmn size.

2016-02-12 Thread Aravindan Vijayan


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43528/
---

(Updated Feb. 12, 2016, 5:29 p.m.)


Review request for Ambari, Dmytro Sen, Sumit Mohanty, and Sid Wagle.


Bugs: AMBARI-15030
https://issues.apache.org/jira/browse/AMBARI-15030


Repository: ambari


Description
---

Default values from the stack (Not stack advisor)
regionserver_heapsize : 512MB
regionserver_xmn_size : 256MB

xmn is 50% of rs heapsize which is unreasonable. Changing to 756MB and 128MB 
respectively.

Made the changes in stack_Advisor and UpgradeCatalog too.


Diffs
-

  
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog222.java
 88b3151 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-hbase-env.xml
 191e8b2 
  ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py 
af21008 
  
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog222Test.java
 6061e06 

Diff: https://reviews.apache.org/r/43528/diff/


Testing
---

UpgradeCatalog tests pass.
Python unit tests pass.


Thanks,

Aravindan Vijayan

[jira] [Commented] (AMBARI-14932) "download zip" does not work

2016-02-12 Thread Keta Patel (JIRA)


[ 
https://issues.apache.org/jira/browse/AMBARI-14932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144919#comment-15144919
 ] 

Keta Patel commented on AMBARI-14932:
-

Hello [~dipayanb], 
I have created the following review request for this Jira and have added you 
and [~pallavkul] as the reviewers:
https://reviews.apache.org/r/43508/

Thanks

> "download zip"  does not work
> -
>
> Key: AMBARI-14932
> URL: https://issues.apache.org/jira/browse/AMBARI-14932
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views, contrib
>Affects Versions: trunk
>Reporter: Keta Patel
>Assignee: Keta Patel
> Attachments: AMBARI-14932_Feb10_fix1.patch, AMBARI-14932_Feb11.patch, 
> DownloadService.tiff, adapter.tiff, error_after_file_open.tiff, file_1.tiff, 
> file_2.tiff, screenshot.tiff
>
>
> Steps to Reproduce:
> 1. go to "View" - "FILES" - " Create Instance"
> 2. go to hdfs file view
> 3. click "download zip" icon
> The click doesn't download any file. The REST call returns 200 OK status.
> Detailed steps on configuring Views can be found in the link below:
> http://docs.hortonworks.com/HDPDocuments/Ambari-2.1.0.0/bk_ambari_views_guide/bk_ambari_views_guide-20150721.pdf



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

[jira] [Commented] (AMBARI-15002) Adding skelton code for Hive Server Interactive component support.

2016-02-12 Thread Jaimin D Jetly (JIRA)


[ 
https://issues.apache.org/jira/browse/AMBARI-15002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144694#comment-15144694
 ] 

Jaimin D Jetly commented on AMBARI-15002:
-

+1 for the patch.
I was able to apply the patch on current trunk bits.
Ran ambari-server python unit tests and found them to pass successfully:

--
Ran 255 tests in 7.158s

OK
--
Total run:902
Total errors:0
Total failures:0
OK


> Adding skelton code for Hive Server Interactive component support.
> --
>
> Key: AMBARI-15002
> URL: https://issues.apache.org/jira/browse/AMBARI-15002
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.4.0
>
> Attachments: AMBARI-15002.patch
>
>
> Adding skelton code for Hive Server Interactive component support.



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

Re: Review Request 43427: Update gpcheck.cnf to hawq_check.cnf file


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43427/#review119033
---


Ship it!




Ship It!


ambari-web/app/models/stack_service.js (line 360)


May be capitalize 'c' in display name 'Advanced HAWQ check' if the other 
display names are shown the same way, since this is a user facing part?


- Matt


On Feb. 10, 2016, 11:06 a.m., bhuvnesh chaudhary wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43427/
> ---
> 
> (Updated Feb. 10, 2016, 11:06 a.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, jun aoki, Jayush Luniya, 
> Oleksandr Diachenko, Richard Zang, Sumit Mohanty, and Yusaku Sako.
> 
> 
> Bugs: AMBARI-14997
> https://issues.apache.org/jira/browse/AMBARI-14997
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Populate hawq_check.cnf instead of gpcheck.cnf. Hawq documentation suggests 
> using hawq_check.cnf config file to run hawq check on clusters.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0/configuration/gpcheck-env.xml
>  309a0c7 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0/configuration/hawq-check-env.xml
>  PRE-CREATION 
>   ambari-server/src/main/resources/common-services/HAWQ/2.0.0/metainfo.xml 
> 21ab445 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/hawq_constants.py
>  01de99a 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/master_helper.py
>  2e0b6da 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/params.py
>  add3c63 
>   ambari-server/src/test/python/stacks/2.3/common/services-hawq-1-host.json 
> 09e305f 
>   ambari-server/src/test/python/stacks/2.3/common/services-hawq-3-hosts.json 
> 09e305f 
>   ambari-server/src/test/python/stacks/2.3/common/services-hawq-pxf-hdfs.json 
> 4cd2d4d 
>   
> ambari-server/src/test/python/stacks/2.3/common/services-master_ambari_colo-3-hosts.json
>  560e1db 
>   
> ambari-server/src/test/python/stacks/2.3/common/services-master_standby_colo-3-hosts.json
>  93d6ec1 
>   
> ambari-server/src/test/python/stacks/2.3/common/services-normal-hawq-3-hosts.json
>  d10a976 
>   
> ambari-server/src/test/python/stacks/2.3/common/services-standby_ambari_colo-3-hosts.json
>  170c740 
>   ambari-web/app/data/HDP2.3/site_properties.js 61cbe88 
>   ambari-web/app/models/stack_service.js 5814386 
> 
> Diff: https://reviews.apache.org/r/43427/diff/
> 
> 
> Testing
> ---
> 
> yes. manual.
> mvn test - passes.
> 
> 
> Thanks,
> 
> bhuvnesh chaudhary
> 
>

[jira] [Commented] (AMBARI-15025) Hosts page: Filtering works incorrectly with multiple filters applied


[ 
https://issues.apache.org/jira/browse/AMBARI-15025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144704#comment-15144704
 ] 

Oleg Nechiporenko commented on AMBARI-15025:


{noformat}
[INFO] Ambari Web  SUCCESS [01:10 min]
[INFO] Ambari Server . FAILURE [  02:40 h]
{noformat}

> Hosts page: Filtering works incorrectly with multiple filters applied
> -
>
> Key: AMBARI-15025
> URL: https://issues.apache.org/jira/browse/AMBARI-15025
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15025.patch, AMBARI-15025_branch-2.2.patch
>
>
> On 1200 node cluster I enabled filter for alerts and then put in a hostname 
> filter... which showed hosts that did not match the filter. (video attached).
> POST request:
> URL: 
> {code:java}
> /api/v1/clusters/perf/hosts?fields=Hosts/rack_info,Hosts/host_name,Hosts/maintenance_state,Hosts/public_host_name,Hosts/cpu_count,Hosts/ph_cpu_count,alerts_summary,Hosts/host_status,Hosts/last_heartbeat_time,Hosts/ip,host_components/HostRoles/state,host_components/HostRoles/maintenance_state,host_components/HostRoles/stale_configs,host_components/HostRoles/service_name,host_components/HostRoles/desired_admin_state,Hosts/total_mem,stack_versions/HostStackVersions,stack_versions/repository_versions/RepositoryVersions/repository_version,stack_versions/repository_versions/RepositoryVersions/id,stack_versions/repository_versions/RepositoryVersions/display_name_response=true_size=10=0=Hosts/host_name.as
> {code}
> Data: 
> {code:java}
> {"RequestInfo":{"query":"page_size=10=0_summary/CRITICAL>0|alerts_summary/WARNING>0/host_name.matches(.*23.*)"}}
> {code}
> Response: 
> {code:java}
> {
>   "itemTotal" : "308",
>   "items" : [
> {
>   "Hosts" : {
> "cpu_count" : 4,
> "host_name" : "perf-b-1.c.pramod-thangali.internal",
> "host_status" : "HEALTHY",
> "ip" : "10.240.0.4",
> "last_heartbeat_time" : 1455013064276,
> "maintenance_state" : "OFF",
> "ph_cpu_count" : 4,
> "public_host_name" : "perf-b-1.c.pramod-thangali.internal",
> "rack_info" : "/default-rack",
> "total_mem" : 15301028
>   }...
> {code}



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

[jira] [Commented] (AMBARI-15025) Hosts page: Filtering works incorrectly with multiple filters applied


[ 
https://issues.apache.org/jira/browse/AMBARI-15025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15144749#comment-15144749
 ] 

Hudson commented on AMBARI-15025:
-

ABORTED: Integrated in Ambari-trunk-Commit #4319 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4319/])
AMBARI-15025. Hosts page: Filtering works incorrectly with multiple 
(onechiporenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ddba3c5d4e2dbd7f0edf07429df4fa24bbaa2d21])
* ambari-web/app/controllers/main/host.js


> Hosts page: Filtering works incorrectly with multiple filters applied
> -
>
> Key: AMBARI-15025
> URL: https://issues.apache.org/jira/browse/AMBARI-15025
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15025.patch, AMBARI-15025_branch-2.2.patch
>
>
> On 1200 node cluster I enabled filter for alerts and then put in a hostname 
> filter... which showed hosts that did not match the filter. (video attached).
> POST request:
> URL: 
> {code:java}
> /api/v1/clusters/perf/hosts?fields=Hosts/rack_info,Hosts/host_name,Hosts/maintenance_state,Hosts/public_host_name,Hosts/cpu_count,Hosts/ph_cpu_count,alerts_summary,Hosts/host_status,Hosts/last_heartbeat_time,Hosts/ip,host_components/HostRoles/state,host_components/HostRoles/maintenance_state,host_components/HostRoles/stale_configs,host_components/HostRoles/service_name,host_components/HostRoles/desired_admin_state,Hosts/total_mem,stack_versions/HostStackVersions,stack_versions/repository_versions/RepositoryVersions/repository_version,stack_versions/repository_versions/RepositoryVersions/id,stack_versions/repository_versions/RepositoryVersions/display_name_response=true_size=10=0=Hosts/host_name.as
> {code}
> Data: 
> {code:java}
> {"RequestInfo":{"query":"page_size=10=0_summary/CRITICAL>0|alerts_summary/WARNING>0/host_name.matches(.*23.*)"}}
> {code}
> Response: 
> {code:java}
> {
>   "itemTotal" : "308",
>   "items" : [
> {
>   "Hosts" : {
> "cpu_count" : 4,
> "host_name" : "perf-b-1.c.pramod-thangali.internal",
> "host_status" : "HEALTHY",
> "ip" : "10.240.0.4",
> "last_heartbeat_time" : 1455013064276,
> "maintenance_state" : "OFF",
> "ph_cpu_count" : 4,
> "public_host_name" : "perf-b-1.c.pramod-thangali.internal",
> "rack_info" : "/default-rack",
> "total_mem" : 15301028
>   }...
> {code}



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

Re: Review Request 41397: AMBARI-14383 Add support for Ranger TagSync process as a component under RANGER



> On Feb. 12, 2016, 9:28 a.m., Nate Cole wrote:
> > What's the status of this review?  If it's pushed, please close.  You can 
> > abort the review if it's not going to happen.  Thanks.
> 
> Velmurugan Periasamy wrote:
> Most likely, tagsync will need to be supported from 2.6 stack (this could 
> change). So my suggestion is to close this review and open a new one when the 
> new patch is ready.

Sounds good.  I can't close it myself since I'm not the opener.


- Nate


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/41397/#review119018
---


On Dec. 15, 2015, 11:46 a.m., Gautam Borad wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/41397/
> ---
> 
> (Updated Dec. 15, 2015, 11:46 a.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jaimin Jetly, Madhan 
> Neethiraj, Mahadev Konar, Nate Cole, Sumit Mohanty, Selvamohan Neethiraj, and 
> Velmurugan Periasamy.
> 
> 
> Bugs: AMBARI-14383
> https://issues.apache.org/jira/browse/AMBARI-14383
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Ranger TagSync is a separate component that will be responsible for 
> synchronizing the tags from Apache Atlas into Apache Ranger (db).
> 
> Add Ranger TagSync component under existing RANGER service.
> The component will be a master component
> Ability to start/stop the component independently of Ranger Admin.
> Ability to install the component on any host of the cluster
> Support should be available only from HDP 2.3
> 
> 
> Diffs
> -
> 
>   
> ambari-common/src/main/python/resource_management/libraries/functions/conf_select.py
>  fd83c53 
>   
> ambari-common/src/main/python/resource_management/libraries/functions/hdp_select.py
>  5628f33 
>   
> ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/params.py
>  b6e5ee9 
>   
> ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/ranger_service.py
>  4f711c3 
>   
> ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/ranger_tagsync.py
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/setup_ranger_xml.py
>  8de0d80 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/services/RANGER/configuration/ranger-tagsync-site.xml
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/services/RANGER/metainfo.xml 
> 2fb8a9a 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.3.xml
>  cf3afbe 
>   ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.3.xml 
> cce20be 
> 
> Diff: https://reviews.apache.org/r/41397/diff/
> 
> 
> Testing
> ---
> 
> Installed Ranger on centos 6 and enabled Ranger TagSync module.
> 
> Tested minor upgrade from 2.3.x to 2.3.xx
> 
> 
> Thanks,
> 
> Gautam Borad
> 
>

Re: Review Request 41397: AMBARI-14383 Add support for Ranger TagSync process as a component under RANGER

2016-02-12 Thread Velmurugan Periasamy



> On Feb. 12, 2016, 2:28 p.m., Nate Cole wrote:
> > What's the status of this review?  If it's pushed, please close.  You can 
> > abort the review if it's not going to happen.  Thanks.

Most likely, tagsync will need to be supported from 2.6 stack (this could 
change). So my suggestion is to close this review and open a new one when the 
new patch is ready.


- Velmurugan


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/41397/#review119018
---


On Dec. 15, 2015, 4:46 p.m., Gautam Borad wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/41397/
> ---
> 
> (Updated Dec. 15, 2015, 4:46 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jaimin Jetly, Madhan 
> Neethiraj, Mahadev Konar, Nate Cole, Sumit Mohanty, Selvamohan Neethiraj, and 
> Velmurugan Periasamy.
> 
> 
> Bugs: AMBARI-14383
> https://issues.apache.org/jira/browse/AMBARI-14383
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Ranger TagSync is a separate component that will be responsible for 
> synchronizing the tags from Apache Atlas into Apache Ranger (db).
> 
> Add Ranger TagSync component under existing RANGER service.
> The component will be a master component
> Ability to start/stop the component independently of Ranger Admin.
> Ability to install the component on any host of the cluster
> Support should be available only from HDP 2.3
> 
> 
> Diffs
> -
> 
>   
> ambari-common/src/main/python/resource_management/libraries/functions/conf_select.py
>  fd83c53 
>   
> ambari-common/src/main/python/resource_management/libraries/functions/hdp_select.py
>  5628f33 
>   
> ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/params.py
>  b6e5ee9 
>   
> ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/ranger_service.py
>  4f711c3 
>   
> ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/ranger_tagsync.py
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/setup_ranger_xml.py
>  8de0d80 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/services/RANGER/configuration/ranger-tagsync-site.xml
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/services/RANGER/metainfo.xml 
> 2fb8a9a 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.3.xml
>  cf3afbe 
>   ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.3.xml 
> cce20be 
> 
> Diff: https://reviews.apache.org/r/41397/diff/
> 
> 
> Testing
> ---
> 
> Installed Ranger on centos 6 and enabled Ranger TagSync module.
> 
> Tested minor upgrade from 2.3.x to 2.3.xx
> 
> 
> Thanks,
> 
> Gautam Borad
> 
>

Re: Review Request 43527: Critical alert for Kafka when using custom port(stack 2.3 and higher)

2016-02-12 Thread Vitalyi Brodetskyi



> On Лют. 12, 2016, 3:21 після полудня, Jonathan Hurley wrote:
> > ambari-agent/src/main/python/ambari_agent/alerts/port_alert.py, line 105
> > 
> >
> > Should we also do 0.0.0.0 as well, similar to what the other alerts do?

Sure, will add this condition too.


- Vitalyi


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43527/#review119030
---


On Лют. 12, 2016, 2:37 після полудня, Vitalyi Brodetskyi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43527/
> ---
> 
> (Updated Лют. 12, 2016, 2:37 після полудня)
> 
> 
> Review request for Ambari, Dmytro Sen and Jonathan Hurley.
> 
> 
> Bugs: AMBARI-15028
> https://issues.apache.org/jira/browse/AMBARI-15028
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> .
> 
> 
> Diffs
> -
> 
>   ambari-agent/src/main/python/ambari_agent/alerts/port_alert.py 848da65 
>   ambari-server/src/main/resources/stacks/HDP/2.3/services/KAFKA/alerts.json 
> PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/43527/diff/
> 
> 
> Testing
> ---
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Vitalyi Brodetskyi
> 
>

Re: Review Request 43528: AMBARI-15030 : Fix unreasonable default heap settings for AMS HBase heapsize and xmn size.

2016-02-12 Thread Dmytro Sen


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43528/#review119048
---




ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog222.java
 (line 287)


I think value can be 512m as well as 512, but I'm not sure


- Dmytro Sen


On Фев. 12, 2016, 5:29 п.п., Aravindan Vijayan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43528/
> ---
> 
> (Updated Фев. 12, 2016, 5:29 п.п.)
> 
> 
> Review request for Ambari, Dmytro Sen, Sumit Mohanty, and Sid Wagle.
> 
> 
> Bugs: AMBARI-15030
> https://issues.apache.org/jira/browse/AMBARI-15030
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Default values from the stack (Not stack advisor)
> regionserver_heapsize : 512MB
> regionserver_xmn_size : 256MB
> 
> xmn is 50% of rs heapsize which is unreasonable. Changing to 756MB and 128MB 
> respectively.
> 
> Made the changes in stack_Advisor and UpgradeCatalog too.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog222.java
>  88b3151 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-hbase-env.xml
>  191e8b2 
>   ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py 
> af21008 
>   
> ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog222Test.java
>  6061e06 
> 
> Diff: https://reviews.apache.org/r/43528/diff/
> 
> 
> Testing
> ---
> 
> UpgradeCatalog tests pass.
> Python unit tests pass.
> 
> 
> Thanks,
> 
> Aravindan Vijayan
> 
>

Re: Review Request 43528: AMBARI-15030 : Fix unreasonable default heap settings for AMS HBase heapsize and xmn size.

2016-02-12 Thread Sumit Mohanty


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43528/#review119050
---




ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog222.java
 (line 281)


Is this necessary? I am making a defensive argument. Ambari upgrade, 
without any basic change to AMS code base should not ned to modify AMS config. 
But yes, if we decide to do it then lets allow both with and without "m"


- Sumit Mohanty


On Feb. 12, 2016, 5:29 p.m., Aravindan Vijayan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43528/
> ---
> 
> (Updated Feb. 12, 2016, 5:29 p.m.)
> 
> 
> Review request for Ambari, Dmytro Sen, Sumit Mohanty, and Sid Wagle.
> 
> 
> Bugs: AMBARI-15030
> https://issues.apache.org/jira/browse/AMBARI-15030
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Default values from the stack (Not stack advisor)
> regionserver_heapsize : 512MB
> regionserver_xmn_size : 256MB
> 
> xmn is 50% of rs heapsize which is unreasonable. Changing to 756MB and 128MB 
> respectively.
> 
> Made the changes in stack_Advisor and UpgradeCatalog too.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog222.java
>  88b3151 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-hbase-env.xml
>  191e8b2 
>   ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py 
> af21008 
>   
> ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog222Test.java
>  6061e06 
> 
> Diff: https://reviews.apache.org/r/43528/diff/
> 
> 
> Testing
> ---
> 
> UpgradeCatalog tests pass.
> Python unit tests pass.
> 
> 
> Thanks,
> 
> Aravindan Vijayan
> 
>

[jira] [Updated] (AMBARI-15031) Duplicate key violation syncing groups when performing ldap-sync with --all option

2016-02-12 Thread JIRA


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

Olivér Szabó updated AMBARI-15031:
--
Attachment: AMBARI-15031.patch

> Duplicate key violation syncing groups when performing ldap-sync with --all 
> option
> --
>
> Key: AMBARI-15031
> URL: https://issues.apache.org/jira/browse/AMBARI-15031
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.2.2
>
> Attachments: AMBARI-15031.patch
>
>
> While performing an ldap-sync using the {{--all}} option, when groups 
> imported from a previous ldap-sync already exist, a duplicate key violation 
> is encountered on the previously existing groups. The duplicate key violation 
> occurs on the {{UNQ_groups_0}} constraint. 
> {noformat}
> Syncing all...ERROR: 
> Exiting with exit code 1. 
> REASON: Caught exception running LDAP sync. Exception EclipseLink-4002 
> (Eclipse Persistence Services - 2.5.2.v20140319-9ad6abd): 
> org.eclipse.persistence.exceptions.DatabaseException 
> Internal Exception: java.sql.BatchUpdateException: Duplicate entry 'mygroup1' 
> for key 'UNQ_groups_0' 
> Error Code: 1062
> {noformat}
> This does not seem of happen when performing an ldap-sync with the 
> {{--groups}} option. 



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

Review Request 43532: AMBARI-15031 - Duplicate key violation during ldap sync

2016-02-12 Thread Oliver Szabo


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43532/
---

Review request for Ambari, Laszlo Puskas, Robert Levas, and Robert Nettleton.


Bugs: AMBARI-15031
https://issues.apache.org/jira/browse/AMBARI-15031


Repository: ambari


Description
---

Duplicate key violation syncing groups when performing ldap-sync with --all 
option.


Diffs
-

  
ambari-server/src/main/java/org/apache/ambari/server/security/ldap/AmbariLdapDataPopulator.java
 3d2685e 
  
ambari-server/src/main/java/org/apache/ambari/server/security/ldap/LdapBatchDto.java
 9247f38 
  
ambari-server/src/test/java/org/apache/ambari/server/security/ldap/AmbariLdapDataPopulatorTest.java
 be92871 

Diff: https://reviews.apache.org/r/43532/diff/


Testing
---

Testing is in progress ...


Thanks,

Oliver Szabo

[jira] [Commented] (AMBARI-15029) Adding a Service results in deleting Config Group mappings (more than 1 CG present)