[jira] [Commented] (AMBARI-13876) Refactor Reassign step4 controller

[Oleg Nechiporenko (JIRA)]

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

Oleg Nechiporenko commented on AMBARI-13876:


 10301 tests complete (12 seconds)
  115 tests pending

> Refactor Reassign step4 controller
> --
>
> Key: AMBARI-13876
> URL: https://issues.apache.org/jira/browse/AMBARI-13876
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-web
>Affects Versions: 2.2.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 2.2.0
>
> Attachments: AMBARI-13876.patch
>
>
> Config initializing should be done using {{ConfigInitializer}}



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

[jira] [Updated] (AMBARI-13875) Support Impersonation for Hive

[Henning Kropp (JIRA)]

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

Henning Kropp updated AMBARI-13875:
---
Attachment: AMBARI-13875.patch

This patch introduces a {{hive.server2.proxy.user}} property that is set to the 
config of the Hive session.

To configure impersonation the {{authParam}} needs to look like the following:
{{auth=KERBEROS;principal=hive/_h...@mycorp.net;hive.server2.proxy.user=${username}
 }}

> Support Impersonation for Hive
> --
>
> Key: AMBARI-13875
> URL: https://issues.apache.org/jira/browse/AMBARI-13875
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: trunk
>Reporter: Henning Kropp
> Attachments: AMBARI-13875.patch
>
>
> Hive View does not support impersonation.



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

[jira] [Assigned] (AMBARI-13861) hdfs balancer via ambari fails to run after HDP upgrade with NN HA enabled

[Dmitry Lysnichenko (JIRA)]

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

Dmitry Lysnichenko reassigned AMBARI-13861:
---

Assignee: Dmitry Lysnichenko

> hdfs balancer via ambari fails to run after HDP upgrade with NN HA enabled
> --
>
> Key: AMBARI-13861
> URL: https://issues.apache.org/jira/browse/AMBARI-13861
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.3
>Reporter: Dmytro Grinenko
>Assignee: Dmitry Lysnichenko
>Priority: Critical
> Fix For: 2.1.3
>
>
> Ran hdfs balancer via ambari on a cluster that had HA enabled and it failed.
> {code}
> Starting balancer with threshold = 10
> Executing command ambari-sudo.sh su hdfs -l -s /bin/bash -c 'export  
> PATH='"'"'/usr/sbin:/sbin:/usr/lib/ambari-server/*:/usr/sbin:/sbin:/usr/lib/ambari-server/*:/usr/lib64/qt-3.3/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin:/var/lib/ambari-agent:/var/lib/ambari-agent:/usr/hdp/current/hadoop-client/bin'"'"'
>  ; hdfs --config /usr/hdp/current/hadoop-client/conf balancer -threshold 10'
> 2015-10-06 23:33:27,059 - Execute['ambari-sudo.sh su hdfs -l -s /bin/bash -c 
> 'export  
> PATH='"'"'/usr/sbin:/sbin:/usr/lib/ambari-server/*:/usr/sbin:/sbin:/usr/lib/ambari-server/*:/usr/lib64/qt-3.3/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin:/var/lib/ambari-agent:/var/lib/ambari-agent:/usr/hdp/current/hadoop-client/bin'"'"'
>  ; hdfs --config /usr/hdp/current/hadoop-client/conf balancer -threshold 
> 10''] {'logoutput': False, 'on_new_line': handle_new_line}
> [balancer] 15/10/06 23:33:29 INFO balancer.Balancer: Using a threshold of 10.0
> [balancer] 15/10/06 23:33:29 INFO balancer.Balancer: namenodes  = 
> [hdfs://pre-prod-poc-1.novalocal:8020, hdfs://pre-prod-hdp-2-3]
> [balancer] 15/10/06 23:33:29 INFO balancer.Balancer: parameters = 
> Balancer.Parameters [BalancingPolicy.Node, threshold = 10.0, max idle 
> iteration = 5, #excluded nodes = 0, #included nodes = 0, #source nodes = 0, 
> run during upgrade = false]
> [balancer] 15/10/06 23:33:29 INFO balancer.Balancer: included nodes = []
> [balancer] 15/10/06 23:33:29 INFO balancer.Balancer: excluded nodes = []
> [balancer] 15/10/06 23:33:29 INFO balancer.Balancer: source nodes = []
> [balancer] Time Stamp   Iteration#  Bytes Already Moved  Bytes 
> Left To Move  Bytes Being Moved[balancer] 
> [balancer] 
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.ipc.StandbyException):
>  Operation category READ is not supported in state standby
>   at 
> org.apache.hadoop.hdfs.server.namenode.ha.StandbyState.checkOperation(StandbyState.java:87)
>   at 
> org.apache.hadoop.hdfs.server.namenode.NameNode$NameNodeHAContext.checkOperation(NameNode.java:1872)
>   at 
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkOperation(FSNamesystem.java:1306)
>   at 
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getServerDefaults(FSNamesystem.java:1618)
>   at 
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.getServerDefaults(NameNodeRpcServer.java:595)
>   at 
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.getServerDefaults(ClientNamenodeProtocolServerSideTranslatorPB.java:383)
>   at 
> org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
>   at 
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(Proto[balancer]
>  bufRpcEngine.java:616)
>   at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:969)
>   at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2137)
>   at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2133)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at javax.security.auth.Subject.doAs(Subject.java:422)
>   at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1657)
>   at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2131)
> .  Exiting ...[balancer] 
> [balancer] Oct 6, 2015 11:33:31 PM [balancer]  [balancer] Balancing took 
> 2.281 seconds[balancer]
> {code}
> If you look at the log it looks like we are adding  a namenode to the list 
> which is in standby. Should we not be using just the name service?
> {code}
> [balancer] 15/10/06 23:33:29 INFO balancer.Balancer: namenodes  = 
> [hdfs://pre-prod-poc-1.novalocal:8020, hdfs://pre-prod-hdp-2-3]
> [balancer] 15/10/06 23:33:29 INFO balancer.Balancer: parameters = 
> Balancer.Parameters 
> {code}
> {code}
> [root@pre-prod-poc-1 hive-testbench]# ambari-server --hash
> 226dfd1c6136f859fc42dd18e7090a9346f0f745
> root@pre-prod-poc-1 

[jira] [Commented] (AMBARI-13877) RU/EU: host failure summary dialog usability changes

[Andrii Tkach (JIRA)]

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

Andrii Tkach commented on AMBARI-13877:
---

10182 tests complete (14 seconds)
  104 tests pending

> RU/EU: host failure summary dialog usability changes
> 
>
> Key: AMBARI-13877
> URL: https://issues.apache.org/jira/browse/AMBARI-13877
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.1.3
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13877.patch, ru-failure.pptx
>
>
> In cases where hosts are skipped during upgrade (RU or EU), need to provide 
> more information to the user about the hosts and what happened.
> This attached mock provide more detail on the hosts and the component 
> failures.



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

[jira] [Created] (AMBARI-13878) Incorrect calculating of task duration

[Oleg Nechiporenko (JIRA)]

Oleg Nechiporenko created AMBARI-13878:
--

 Summary: Incorrect calculating of task duration
 Key: AMBARI-13878
 URL: https://issues.apache.org/jira/browse/AMBARI-13878
 Project: Ambari
  Issue Type: Improvement
  Components: ambari-web
Affects Versions: 2.1.3
 Environment: ambari-server version: ambari-server-2.1.3.0-322.x86_64
ambari-server --hash: 84dfed9968ce8224d49540a7572cd90b6d4538c2
HDP Stack: 2.3
HDP Version: 2.3.4.0-3192
Ambari DB: :MySQL
Oozie/Hive DB: MySQL/MySQL
Security:no
Security Type:MIT/MIT
Blueprints: false
Umask: 027
JDK: default
HA: no
Repo URL: 
http://s3.amazonaws.com/dev.hortonworks.com/ambari/centos6/2.x/updates/2.1.3.0/ambariqe.repo
OS: CentOS 6
Gateway: 172.22.121.36:8080
Ambari User: slava
Agents User: agentslava
MOTD: false
Customized service users: false
Reporter: Oleg Nechiporenko
Assignee: Oleg Nechiporenko
Priority: Critical
 Fix For: 2.2.0


Steps:
# Go to any service (I tried with Fafka, HDFS, YARN).
# Select "Restart All" from Service Actions combobox.
# Go to another service.
# Select "Restart All" from Service Actions combobox too.

Result: Fist operation has duration more than 2 hours. Duration become correct 
after task completion.



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

[jira] [Updated] (AMBARI-13877) RU/EU: host failure summary dialog usability changes

[Andrii Tkach (JIRA)]

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

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

> RU/EU: host failure summary dialog usability changes
> 
>
> Key: AMBARI-13877
> URL: https://issues.apache.org/jira/browse/AMBARI-13877
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.1.3
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13877.patch, ru-failure.pptx
>
>
> In cases where hosts are skipped during upgrade (RU or EU), need to provide 
> more information to the user about the hosts and what happened.
> This attached mock provide more detail on the hosts and the component 
> failures.



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

[jira] [Commented] (AMBARI-13878) Incorrect calculating of task duration

[Andrii Babiichuk (JIRA)]

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

Andrii Babiichuk commented on AMBARI-13878:
---

+1 for the patch

> Incorrect calculating of task duration
> --
>
> Key: AMBARI-13878
> URL: https://issues.apache.org/jira/browse/AMBARI-13878
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.3
> Environment: ambari-server version: ambari-server-2.1.3.0-322.x86_64
> ambari-server --hash: 84dfed9968ce8224d49540a7572cd90b6d4538c2
> HDP Stack: 2.3
> HDP Version: 2.3.4.0-3192
> Ambari DB: :MySQL
> Oozie/Hive DB: MySQL/MySQL
> Security:no
> Security Type:MIT/MIT
> Blueprints: false
> Umask: 027
> JDK: default
> HA: no
> Repo URL: 
> http://s3.amazonaws.com/dev.hortonworks.com/ambari/centos6/2.x/updates/2.1.3.0/ambariqe.repo
> OS: CentOS 6
> Gateway: 172.22.121.36:8080
> Ambari User: slava
> Agents User: agentslava
> MOTD: false
> Customized service users: false
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.2.0
>
> Attachments: AMBARI-13878.patch, incorrectDuration.png
>
>
> Steps:
> # Go to any service (I tried with Fafka, HDFS, YARN).
> # Select "Restart All" from Service Actions combobox.
> # Go to another service.
> # Select "Restart All" from Service Actions combobox too.
> Result: Fist operation has duration more than 2 hours. Duration become 
> correct after task completion.



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

[jira] [Updated] (AMBARI-13877) RU/EU: host failure summary dialog usability changes

[Andrii Tkach (JIRA)]

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

Andrii Tkach updated AMBARI-13877:
--
Attachment: ru-failure.pptx

> RU/EU: host failure summary dialog usability changes
> 
>
> Key: AMBARI-13877
> URL: https://issues.apache.org/jira/browse/AMBARI-13877
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.1.3
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: ru-failure.pptx
>
>
> In cases where hosts are skipped during upgrade (RU or EU), need to provide 
> more information to the user about the hosts and what happened.
> This attached mock provide more detail on the hosts and the component 
> failures.



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

[jira] [Created] (AMBARI-13877) RU/EU: host failure summary dialog usability changes

[Andrii Tkach (JIRA)]

Andrii Tkach created AMBARI-13877:
-

 Summary: RU/EU: host failure summary dialog usability changes
 Key: AMBARI-13877
 URL: https://issues.apache.org/jira/browse/AMBARI-13877
 Project: Ambari
  Issue Type: Task
  Components: ambari-web
Affects Versions: 2.1.3
Reporter: Andrii Tkach
Assignee: Andrii Tkach
Priority: Critical
 Fix For: 2.1.3
 Attachments: ru-failure.pptx

In cases where hosts are skipped during upgrade (RU or EU), need to provide 
more information to the user about the hosts and what happened.

This attached mock provide more detail on the hosts and the component failures.



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

[jira] [Commented] (AMBARI-13877) RU/EU: host failure summary dialog usability changes

[Aleksandr Kovalenko (JIRA)]

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

Aleksandr Kovalenko commented on AMBARI-13877:
--

+1 for the patch

> RU/EU: host failure summary dialog usability changes
> 
>
> Key: AMBARI-13877
> URL: https://issues.apache.org/jira/browse/AMBARI-13877
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.1.3
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13877.patch, ru-failure.pptx
>
>
> In cases where hosts are skipped during upgrade (RU or EU), need to provide 
> more information to the user about the hosts and what happened.
> This attached mock provide more detail on the hosts and the component 
> failures.



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

[jira] [Updated] (AMBARI-13878) Incorrect calculating of task duration

[Oleg Nechiporenko (JIRA)]

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

Oleg Nechiporenko updated AMBARI-13878:
---
Issue Type: Bug  (was: Improvement)

> Incorrect calculating of task duration
> --
>
> Key: AMBARI-13878
> URL: https://issues.apache.org/jira/browse/AMBARI-13878
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.3
> Environment: ambari-server version: ambari-server-2.1.3.0-322.x86_64
> ambari-server --hash: 84dfed9968ce8224d49540a7572cd90b6d4538c2
> HDP Stack: 2.3
> HDP Version: 2.3.4.0-3192
> Ambari DB: :MySQL
> Oozie/Hive DB: MySQL/MySQL
> Security:no
> Security Type:MIT/MIT
> Blueprints: false
> Umask: 027
> JDK: default
> HA: no
> Repo URL: 
> http://s3.amazonaws.com/dev.hortonworks.com/ambari/centos6/2.x/updates/2.1.3.0/ambariqe.repo
> OS: CentOS 6
> Gateway: 172.22.121.36:8080
> Ambari User: slava
> Agents User: agentslava
> MOTD: false
> Customized service users: false
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.2.0
>
> Attachments: incorrectDuration.png
>
>
> Steps:
> # Go to any service (I tried with Fafka, HDFS, YARN).
> # Select "Restart All" from Service Actions combobox.
> # Go to another service.
> # Select "Restart All" from Service Actions combobox too.
> Result: Fist operation has duration more than 2 hours. Duration become 
> correct after task completion.



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

[jira] [Updated] (AMBARI-13878) Incorrect calculating of task duration

[Oleg Nechiporenko (JIRA)]

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

Oleg Nechiporenko updated AMBARI-13878:
---
Attachment: incorrectDuration.png

> Incorrect calculating of task duration
> --
>
> Key: AMBARI-13878
> URL: https://issues.apache.org/jira/browse/AMBARI-13878
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-web
>Affects Versions: 2.1.3
> Environment: ambari-server version: ambari-server-2.1.3.0-322.x86_64
> ambari-server --hash: 84dfed9968ce8224d49540a7572cd90b6d4538c2
> HDP Stack: 2.3
> HDP Version: 2.3.4.0-3192
> Ambari DB: :MySQL
> Oozie/Hive DB: MySQL/MySQL
> Security:no
> Security Type:MIT/MIT
> Blueprints: false
> Umask: 027
> JDK: default
> HA: no
> Repo URL: 
> http://s3.amazonaws.com/dev.hortonworks.com/ambari/centos6/2.x/updates/2.1.3.0/ambariqe.repo
> OS: CentOS 6
> Gateway: 172.22.121.36:8080
> Ambari User: slava
> Agents User: agentslava
> MOTD: false
> Customized service users: false
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.2.0
>
> Attachments: incorrectDuration.png
>
>
> Steps:
> # Go to any service (I tried with Fafka, HDFS, YARN).
> # Select "Restart All" from Service Actions combobox.
> # Go to another service.
> # Select "Restart All" from Service Actions combobox too.
> Result: Fist operation has duration more than 2 hours. Duration become 
> correct after task completion.



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

[jira] [Commented] (AMBARI-13873) During ranger plugins enabling warning about dependent properties is placed incorrectly.

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13873:
-

ABORTED: Integrated in Ambari-branch-2.1 #853 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/853/])
AMBARI-13873 During ranger plugins enabling warning about dependent 
(ababiichuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=52b8d02c52f16b684864d9340e5007f28c830875])
* ambari-web/app/views/main/service/info/configs.js


> During ranger plugins enabling warning about dependent properties is placed 
> incorrectly.
> 
>
> Key: AMBARI-13873
> URL: https://issues.apache.org/jira/browse/AMBARI-13873
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.3
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13873.patch
>
>
> Steps:
> Installed cluster with HDFS, YARN, ZooKeeper.
> Added Ranger.
> Go to Ranger's config Ranger Plugin tab.
> Change HDFS Ranger Plugin value (enable it).
> Disable HDFS Ranger Plugin.
> Enable it again.
> Result: warning about dependent properties is placed incorrectly.



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

[jira] [Commented] (AMBARI-13878) Incorrect calculating of task duration

[Oleg Nechiporenko (JIRA)]

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

Oleg Nechiporenko commented on AMBARI-13878:


  10150 tests complete (14 seconds)
  104 tests pending

> Incorrect calculating of task duration
> --
>
> Key: AMBARI-13878
> URL: https://issues.apache.org/jira/browse/AMBARI-13878
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.3
> Environment: ambari-server version: ambari-server-2.1.3.0-322.x86_64
> ambari-server --hash: 84dfed9968ce8224d49540a7572cd90b6d4538c2
> HDP Stack: 2.3
> HDP Version: 2.3.4.0-3192
> Ambari DB: :MySQL
> Oozie/Hive DB: MySQL/MySQL
> Security:no
> Security Type:MIT/MIT
> Blueprints: false
> Umask: 027
> JDK: default
> HA: no
> Repo URL: 
> http://s3.amazonaws.com/dev.hortonworks.com/ambari/centos6/2.x/updates/2.1.3.0/ambariqe.repo
> OS: CentOS 6
> Gateway: 172.22.121.36:8080
> Ambari User: slava
> Agents User: agentslava
> MOTD: false
> Customized service users: false
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.2.0
>
> Attachments: AMBARI-13878.patch, incorrectDuration.png
>
>
> Steps:
> # Go to any service (I tried with Fafka, HDFS, YARN).
> # Select "Restart All" from Service Actions combobox.
> # Go to another service.
> # Select "Restart All" from Service Actions combobox too.
> Result: Fist operation has duration more than 2 hours. Duration become 
> correct after task completion.



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

[jira] [Updated] (AMBARI-13878) Incorrect calculating of task duration

[Oleg Nechiporenko (JIRA)]

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

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

> Incorrect calculating of task duration
> --
>
> Key: AMBARI-13878
> URL: https://issues.apache.org/jira/browse/AMBARI-13878
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.3
> Environment: ambari-server version: ambari-server-2.1.3.0-322.x86_64
> ambari-server --hash: 84dfed9968ce8224d49540a7572cd90b6d4538c2
> HDP Stack: 2.3
> HDP Version: 2.3.4.0-3192
> Ambari DB: :MySQL
> Oozie/Hive DB: MySQL/MySQL
> Security:no
> Security Type:MIT/MIT
> Blueprints: false
> Umask: 027
> JDK: default
> HA: no
> Repo URL: 
> http://s3.amazonaws.com/dev.hortonworks.com/ambari/centos6/2.x/updates/2.1.3.0/ambariqe.repo
> OS: CentOS 6
> Gateway: 172.22.121.36:8080
> Ambari User: slava
> Agents User: agentslava
> MOTD: false
> Customized service users: false
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.2.0
>
> Attachments: AMBARI-13878.patch, incorrectDuration.png
>
>
> Steps:
> # Go to any service (I tried with Fafka, HDFS, YARN).
> # Select "Restart All" from Service Actions combobox.
> # Go to another service.
> # Select "Restart All" from Service Actions combobox too.
> Result: Fist operation has duration more than 2 hours. Duration become 
> correct after task completion.



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

Re: Review Request 40221: AMS should not assume hdfs as the protocol

[Dmytro Sen]

> On Ноя. 12, 2015, 6:52 п.п., Sid Wagle wrote:
> > ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/hbase.py,
> >  line 189
> > 
> >
> > Thsi is good but if FS != HDFS we still need to try and create the 
> > hbase.rootdir on local FS.

We do this in elase branch

else:

  local_root_dir = params.hbase_root_dir
  #cut protocol name
  if local_root_dir.startswith("file://"):
local_root_dir = local_root_dir[7:]
#otherwise assume dir name is provided as is

  Directory(local_root_dir,
owner = params.hbase_user,
cd_access="a",
recursive = True
  )


- Dmytro


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


On Ноя. 12, 2015, 9:50 д.п., Dmytro Sen wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40221/
> ---
> 
> (Updated Ноя. 12, 2015, 9:50 д.п.)
> 
> 
> Review request for Ambari, Sumit Mohanty and Sid Wagle.
> 
> 
> Bugs: AMBARI-13851
> https://issues.apache.org/jira/browse/AMBARI-13851
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> AMS scripts should not assume that hdfs is the protocol.
> is_hbase_distributed = hbase_root_dir.startswith('hdfs://')
> 
> or 
> 
> is_hbase_distributed = 
> security_params['hbase-site']['hbase.rootdir'].startswith('hdfs://')
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams.py
>  50e363c 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/hbase.py
>  9e6f2fa 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py
>  00e4123 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py
>  1c6a49f 
>   ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py 
> 7181122 
>   
> ambari-server/src/test/python/stacks/2.0.6/AMBARI_METRICS/test_metrics_collector.py
>  b04e1d5 
> 
> Diff: https://reviews.apache.org/r/40221/diff/
> 
> 
> Testing
> ---
> 
> --
> Ran 249 tests in 8.115s
> 
> OK
> --
> Total run:831
> Total errors:0
> Total failures:0
> OK
> 
> 
> Thanks,
> 
> Dmytro Sen
> 
>

[jira] [Created] (AMBARI-13874) On Kerberos Service Config page "hull host" is shown in KDC category

[Andrii Babiichuk (JIRA)]

Andrii Babiichuk created AMBARI-13874:
-

 Summary: On Kerberos Service Config page "hull host" is shown in 
KDC category
 Key: AMBARI-13874
 URL: https://issues.apache.org/jira/browse/AMBARI-13874
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.2.0
Reporter: Andrii Babiichuk
Assignee: Andrii Babiichuk
 Fix For: 2.2.0


There in no KDC component in kerberos service, only KERBEROS_CLIENT, so there 
is no master/slave host property.



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

[jira] [Updated] (AMBARI-13874) On Kerberos Service Config page "hull host" is shown in KDC category

[Andrii Babiichuk (JIRA)]

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

Andrii Babiichuk updated AMBARI-13874:
--
Attachment: AMBARI-13874.patch

> On Kerberos Service Config page "hull host" is shown in KDC category
> 
>
> Key: AMBARI-13874
> URL: https://issues.apache.org/jira/browse/AMBARI-13874
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 2.2.0
>
> Attachments: AMBARI-13874.patch
>
>
> There in no KDC component in kerberos service, only KERBEROS_CLIENT, so there 
> is no master/slave host property.



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

[jira] [Assigned] (AMBARI-11825) Failure to add or install component defined with cardinality ALL

[Shantanu Mundkur (JIRA)]

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

Shantanu Mundkur reassigned AMBARI-11825:
-

Assignee: Shantanu Mundkur

> Failure to add or install component defined with cardinality ALL
> 
>
> Key: AMBARI-11825
> URL: https://issues.apache.org/jira/browse/AMBARI-11825
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 1.7.0
>Reporter: Shantanu Mundkur
>Assignee: Shantanu Mundkur
>
> A MASTER, SLAVE or CLIENT component defined with a cardinality of ALL results 
> in a failure while adding the service, upon clicking Deploy, with an error 
> like:
> org.apache.ambari.server.controller.spi.ResourceAlreadyExistsException: 
> Attempted to create host_component's which already exist: 
> [clusterName=CLUSTER1, hostName=node1.domain.com, 
> componentName=MYSERVICE_MASTER],[clusterName=CLUSTER1, 
> hostName=node1.domain.com, componentName=MYSERVICE_MASTER]
> or
> org.apache.ambari.server.controller.spi.ResourceAlreadyExistsException: 
> Attempted to create a host_component which already exists: 
> [clusterName=CLUSTER2, hostName=node10.domain.com, 
> componentName=MYSERVICE_SLAVE]



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

[jira] [Commented] (AMBARI-13738) Checking the vm.swappiness Kernel Parameter

[Canan Girgin (JIRA)]

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

Canan Girgin commented on AMBARI-13738:
---

+1 for patch

> Checking the vm.swappiness Kernel Parameter
> ---
>
> Key: AMBARI-13738
> URL: https://issues.apache.org/jira/browse/AMBARI-13738
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-agent, ambari-server, ambari-web
>Reporter: Canan Girgin
>Priority: Trivial
> Attachments: AMBARI-13738.patch
>
>
> Swappiness parameter is set to 60 by default. This is not suitable for Hadoop 
> clusters.  When installing new cluster,  Ambari should be check  if the 
> swappiness parameter is less than 10 .



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

Re: Review Request 40073: Checking selinux status on each host when creating new cluster

[Andrew Onischuk]

> On Nov. 12, 2015, 7:54 a.m., Andrew Onischuk wrote:
> > I don't think we need this feature. Anyways we force turing off selinux 
> > before installing on Ambari.
> > 
> >   Execute(("setenforce","0"),
> >   only_if="test -f /selinux/enforce",
> >   not_if="(! which getenforce ) || (which getenforce && getenforce 
> > | grep -q Disabled)",
> >   sudo=True,
> >   )
> 
> Mehmet Zahid Yuzuguldu wrote:
> i see that, but this can be happen if selinux is activated after 
> installed before adding new cluster.
> We got this senario in our hadoop ecosystem
> 
> Andrew Onischuk wrote:
> But adding new cluster will trigger INSTALL tasks which will trigger 
> "setenforce 0". Am I missing something?
> 
> Mehmet Zahid Yuzuguldu wrote:
> Ok, this is for manual installing ambari-agent and not adding new cluster 
> just after installing ambari-agent.
> 
> Andrew Onischuk wrote:
> anyway you should add the ambari-agent to cluster and install something 
> on it, to do anything on it.
> 
> Mehmet Zahid Yuzuguldu wrote:
> So, cancelling this pathc?

Unless there is any reasonable purpose for the change. Currently I don't see 
one, which is my main concern.


- Andrew


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


On Nov. 12, 2015, 7:29 a.m., Mehmet Zahid Yuzuguldu wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40073/
> ---
> 
> (Updated Nov. 12, 2015, 7:29 a.m.)
> 
> 
> Review request for Ambari, Andrew Onischuk and Dmitro Lisnichenko.
> 
> 
> Bugs: AMBARI-13733
> https://issues.apache.org/jira/browse/AMBARI-13733
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Adding checking selinux status mechanism on each host when creating new 
> cluster.
> 
> 
> Diffs
> -
> 
>   ambari-server/src/main/resources/custom_actions/scripts/check_host.py 
> 8b49725 
>   ambari-web/app/controllers/wizard/step3_controller.js cf1f1ae 
>   ambari-web/app/messages.js 78c439b 
>   ambari-web/app/views/wizard/step3/hostWarningPopupBody_view.js 9c6454e 
>   ambari-web/app/views/wizard/step3_view.js 6ecfb41 
>   ambari-web/test/views/wizard/step3/hostWarningPopupBody_view_test.js 
> 3cd53a0 
> 
> Diff: https://reviews.apache.org/r/40073/diff/
> 
> 
> Testing
> ---
> 
> Manual testing done.
> ==
> 
> Ambar-web
> mvn clean test
> 
> 10080 tests complete (11 seconds)
> 105 tests pending
> 
> 
> Thanks,
> 
> Mehmet Zahid Yuzuguldu
> 
>

[jira] [Updated] (AMBARI-13873) During ranger plugins enabling warning about dependent properties is placed incorrectly.

[Andrii Babiichuk (JIRA)]

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

Andrii Babiichuk updated AMBARI-13873:
--
Attachment: AMBARI-13873.patch

> During ranger plugins enabling warning about dependent properties is placed 
> incorrectly.
> 
>
> Key: AMBARI-13873
> URL: https://issues.apache.org/jira/browse/AMBARI-13873
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.3
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13873.patch
>
>
> Steps:
> Installed cluster with HDFS, YARN, ZooKeeper.
> Added Ranger.
> Go to Ranger's config Ranger Plugin tab.
> Change HDFS Ranger Plugin value (enable it).
> Disable HDFS Ranger Plugin.
> Enable it again.
> Result: warning about dependent properties is placed incorrectly.



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

Re: Review Request 40221: AMS should not assume hdfs as the protocol

[Dmytro Sen]

> On Ноя. 13, 2015, 1:51 д.п., Sumit Mohanty wrote:
> > ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/hbase.py,
> >  line 189
> > 
> >
> > Actually, all FS that I know of allow the creation of folder on them 
> > through this call. So we will have no problem creating the root dir even if 
> > the FS is not HDFS. We can skip this change.

We should check if it's hdfs rootdir, then create HdfsDirectory, otherwise 
create the local FS directory.
It handles pseudo-distributed mode, when 
config['hbase-site']['hbase.cluster.distributed'] == 'true' , but 
['hbase-site']['hbase.rootdir'] == 'file:///var/'


- Dmytro


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


On Ноя. 12, 2015, 9:50 д.п., Dmytro Sen wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40221/
> ---
> 
> (Updated Ноя. 12, 2015, 9:50 д.п.)
> 
> 
> Review request for Ambari, Sumit Mohanty and Sid Wagle.
> 
> 
> Bugs: AMBARI-13851
> https://issues.apache.org/jira/browse/AMBARI-13851
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> AMS scripts should not assume that hdfs is the protocol.
> is_hbase_distributed = hbase_root_dir.startswith('hdfs://')
> 
> or 
> 
> is_hbase_distributed = 
> security_params['hbase-site']['hbase.rootdir'].startswith('hdfs://')
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams.py
>  50e363c 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/hbase.py
>  9e6f2fa 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py
>  00e4123 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py
>  1c6a49f 
>   ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py 
> 7181122 
>   
> ambari-server/src/test/python/stacks/2.0.6/AMBARI_METRICS/test_metrics_collector.py
>  b04e1d5 
> 
> Diff: https://reviews.apache.org/r/40221/diff/
> 
> 
> Testing
> ---
> 
> --
> Ran 249 tests in 8.115s
> 
> OK
> --
> Total run:831
> Total errors:0
> Total failures:0
> OK
> 
> 
> Thanks,
> 
> Dmytro Sen
> 
>

[jira] [Commented] (AMBARI-13830) Bump the Ambari Spark definition to Spark 1.5.2

[Saisai Shao (JIRA)]

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

Saisai Shao commented on AMBARI-13830:
--

Is it getting merged, looks like not. Would you please help to merge this, this 
is pending for Spark version upgrade. Thanks a lot.

> Bump the Ambari Spark definition to Spark 1.5.2
> ---
>
> Key: AMBARI-13830
> URL: https://issues.apache.org/jira/browse/AMBARI-13830
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: trunk
>Reporter: Saisai Shao
> Fix For: trunk
>
> Attachments: AMBARI-13830.patch
>
>
> Change the Ambari Spark definition to version 1.5.2



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

[jira] [Created] (AMBARI-13873) During ranger plugins enabling warning about dependent properties is placed incorrectly.

[Andrii Babiichuk (JIRA)]

Andrii Babiichuk created AMBARI-13873:
-

 Summary: During ranger plugins enabling warning about dependent 
properties is placed incorrectly.
 Key: AMBARI-13873
 URL: https://issues.apache.org/jira/browse/AMBARI-13873
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.1.3
Reporter: Andrii Babiichuk
Assignee: Andrii Babiichuk
Priority: Critical
 Fix For: 2.1.3


Steps:
Installed cluster with HDFS, YARN, ZooKeeper.
Added Ranger.
Go to Ranger's config Ranger Plugin tab.
Change HDFS Ranger Plugin value (enable it).
Disable HDFS Ranger Plugin.
Enable it again.
Result: warning about dependent properties is placed incorrectly.



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

[jira] [Commented] (AMBARI-13869) AMS config validation issues

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-13869:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12772111/AMBARI-13869.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.orm.dao.AlertDefinitionDAOTest
  
org.apache.ambari.server.controller.BackgroundCustomCommandExecutionTest
  
org.apache.ambari.server.controller.AmbariCustomCommandExecutionHelperTest
  
org.apache.ambari.server.functionaltests.server.StartStopServerTest
  
org.apache.ambari.server.controller.AmbariManagementControllerTest
  org.apache.ambari.server.orm.dao.AlertDispatchDAOTest

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

This message is automatically generated.

> AMS config validation issues
> 
>
> Key: AMBARI-13869
> URL: https://issues.apache.org/jira/browse/AMBARI-13869
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13869.patch
>
>
> Issue 1 : AMS validation asks to set hbase_master_xmn_size to an unreasonable 
> value of 4123168640 MB
> Issue 2 : AMS stack-advisor validates 3 configs in 1 message



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

[jira] [Commented] (AMBARI-13873) During ranger plugins enabling warning about dependent properties is placed incorrectly.

[Oleg Nechiporenko (JIRA)]

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

Oleg Nechiporenko commented on AMBARI-13873:


+1 for patch

> During ranger plugins enabling warning about dependent properties is placed 
> incorrectly.
> 
>
> Key: AMBARI-13873
> URL: https://issues.apache.org/jira/browse/AMBARI-13873
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.3
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13873.patch
>
>
> Steps:
> Installed cluster with HDFS, YARN, ZooKeeper.
> Added Ranger.
> Go to Ranger's config Ranger Plugin tab.
> Change HDFS Ranger Plugin value (enable it).
> Disable HDFS Ranger Plugin.
> Enable it again.
> Result: warning about dependent properties is placed incorrectly.



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

Re: Review Request 40080: AMBARI-13748: Being able to clean repository cache before installing open source components

[Andrew Onischuk]

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

Ship it!



ambari-server/src/main/resources/custom_actions/scripts/clear_repocache.py 
(line 52)


I think 'apt-get clean' on Ubuntu cleans all the locally save deb files and 
etc.
While 'apt-get update' updates the repositories information.

I think you meant apt-get update here? No?


- Andrew Onischuk


On Nov. 12, 2015, 9:44 p.m., Di Li wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40080/
> ---
> 
> (Updated Nov. 12, 2015, 9:44 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Andrew Onischuk, Jayush 
> Luniya, and Sid Wagle.
> 
> 
> Bugs: AMBARI-13748
> https://issues.apache.org/jira/browse/AMBARI-13748
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Need a way for Ambari to trigger a repository clean (yum clean expire-cache 
> on rhel, for example) when updating repository files during an Ambari update 
> as well as fresh installation of a cluster.
> 
> Currently, this must be done occasionally through a manual step, and if not 
> done will lead to problems during install.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/custom_action_definitions/system_action_definitions.xml
>  e725d68 
>   ambari-server/src/main/resources/custom_actions/scripts/clear_repocache.py 
> PRE-CREATION 
>   ambari-server/src/test/python/custom_actions/TestClearRepoCache.py 
> PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/40080/diff/
> 
> 
> Testing
> ---
> 
> New unit test. Patch cluster with the changes and run fresh install and 
> rolling upgrade to verify the repo clean up logic was run.
> 
> New unit test for custom action code change. Also test the custom action by 
> REST API call
> 
> 
> curl -u admin:admin -H "X-Requested-By: admin" -X POST 
> -d'{"RequestInfo":{"context":"clear repo cache test", "action" : 
> "clear_repocache"}, 
> "Requests/resource_filters":[{"hosts":"agent.mydomain.com"}]}' 
> http://server.mydomain.com:8080/api/v1/clusters/bi/requests
> 
> 
> Thanks,
> 
> Di Li
> 
>

[jira] [Commented] (AMBARI-13874) On Kerberos Service Config page "hull host" is shown in KDC category

[Oleg Nechiporenko (JIRA)]

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

Oleg Nechiporenko commented on AMBARI-13874:


+1 for patch

> On Kerberos Service Config page "hull host" is shown in KDC category
> 
>
> Key: AMBARI-13874
> URL: https://issues.apache.org/jira/browse/AMBARI-13874
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 2.2.0
>
> Attachments: AMBARI-13874.patch
>
>
> There in no KDC component in kerberos service, only KERBEROS_CLIENT, so there 
> is no master/slave host property.



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

[jira] [Created] (AMBARI-13875) Support Impersonation for Hive

[Henning Kropp (JIRA)]

Henning Kropp created AMBARI-13875:
--

 Summary: Support Impersonation for Hive
 Key: AMBARI-13875
 URL: https://issues.apache.org/jira/browse/AMBARI-13875
 Project: Ambari
  Issue Type: Bug
  Components: ambari-views
Affects Versions: trunk
Reporter: Henning Kropp


Hive View does not support impersonation.



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

[jira] [Created] (AMBARI-13876) Refactor Reassign step4 controller

[Oleg Nechiporenko (JIRA)]

Oleg Nechiporenko created AMBARI-13876:
--

 Summary: Refactor Reassign step4 controller
 Key: AMBARI-13876
 URL: https://issues.apache.org/jira/browse/AMBARI-13876
 Project: Ambari
  Issue Type: Improvement
  Components: ambari-web
Affects Versions: 2.2.0
Reporter: Oleg Nechiporenko
Assignee: Oleg Nechiporenko
 Fix For: 2.2.0


Config initializing should be done using {{ConfigInitializer}}



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

Review Request 40298: SmartSense install fails as archive.zip fails to download

[Dmitro Lisnichenko]

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

Review request for Ambari, Andrew Onischuk and Sumit Mohanty.


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


Repository: ambari


Description
---

Try to install Smart Sense when trying to deploy HDP 2.3 and the server and 
agent install fails

Caught an exception while executing custom service command: : 'Script 
/var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_agent.py
 does not exist'; 'Script 
/var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_agent.py
 does not exist'

Caught an exception while executing custom service command: : 'Script 
/var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_server.py
 does not exist'; 'Script 
/var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_server.py
 does not exist'

server is running under user slava:
slava23129  3.3  4.2 4768512 686808 ?  Sl   02:28  25:37 
/usr/jdk64/jdk1.8.0_45/bin/java -server -XX:NewRatio=3 -XX:+UseConcMarkSweepGC 
-XX:-UseGCOverheadLimit -XX:CMSInitiatingOccupancyFraction=60 
-Dsun.zip.disableMemoryMapping=true -Xms512m -Xmx2048m 
-Djava.security.auth.login.config=/etc/ambari-server/conf/krb5JAASLogin.conf 
-Djava.security.krb5.conf=/etc/krb5.conf 
-Djavax.security.auth.useSubjectCredsOnly=false -Xms512m -Xmx2048m 
-Djava.security.auth.login.config=/etc/ambari-server/conf/krb5JAASLogin.conf 
-Djava.security.krb5.conf=/etc/krb5.conf 
-Djavax.security.auth.useSubjectCredsOnly=false -cp 
/etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/mysql-connector-java.jar
 org.apache.ambari.server.controller.AmbariServer

Files generated by ambari-server script have wrong permissions:
[root@os-r6-stest-5 tmp]# ll 
/var/lib/ambari-server/resources/stacks/HDP/2.1/services/SMARTSENSE/package/
total 840
-rw-r-. 1 root  root  0 2015-11-13 02:27 abc.txt
-rw-r-. 1 root  root 850974 2015-11-12 22:26 archive.zip
drwxr-xr-x. 4 slava root   4096 2015-11-12 22:25 files
drwxr-xr-x. 2 slava root   4096 2015-11-12 22:25 scripts

[root@os-r6-stest-5 tmp]# umask
0027
And that's why file can not be read by server process.


Diffs
-

  ambari-server/src/main/python/ambari_server/resourceFilesKeeper.py fe80723 

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


Testing
---

mvn clean test


Thanks,

Dmitro Lisnichenko

Re: Review Request 40300: Ranger Usersync Moving From Seconds to Millis On Stack Upgrade

[Nate Cole]

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

Ship it!


Ship It!

- Nate Cole


On Nov. 13, 2015, 11:39 a.m., Jonathan Hurley wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40300/
> ---
> 
> (Updated Nov. 13, 2015, 11:39 a.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jayush Luniya, and Nate Cole.
> 
> 
> Bugs: AMBARI-13888
> https://issues.apache.org/jira/browse/AMBARI-13888
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> During upgrade, sync interval needs to be migrated properly.
> 
> In HDP 2.2, ranger treats this value in minutes 
> {{usersync-properties.xml/SYNC_INTERVAL}}. In HDP 2.3, the unit changed to 
> milliseconds 
> {{ranger-ugsync-site.xml/ranger.usersync.sleeptimeinmillisbetweensynccycle}}. 
> So upgrade should handle the transformation.
> 
> Yes, we _could_ write a Java class with performs "smart" checking and just 
> multiplies a modified value by 1000 - but that's a lot of work for really no 
> benefit. Let's just correct the value so that it doesn't hammer the server 
> and set it  back to the stock value.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/services/RANGER/configuration/ranger-ugsync-site.xml
>  d61cf20 
>   ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/config-upgrade.xml 
> 518132e 
>   
> ambari-server/src/main/resources/upgrade/catalog/UpgradeCatalog_2.2_to_2.3.json
>  40c345d 
> 
> Diff: https://reviews.apache.org/r/40300/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Jonathan Hurley
> 
>

Re: Review Request 40298: SmartSense install fails as archive.zip fails to download

[Mahadev Konar]

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

Ship it!


Ship It!

- Mahadev Konar


On Nov. 13, 2015, 4:20 p.m., Dmitro Lisnichenko wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40298/
> ---
> 
> (Updated Nov. 13, 2015, 4:20 p.m.)
> 
> 
> Review request for Ambari, Andrew Onischuk and Sumit Mohanty.
> 
> 
> Bugs: AMBARI-13887
> https://issues.apache.org/jira/browse/AMBARI-13887
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Try to install Smart Sense when trying to deploy HDP 2.3 and the server and 
> agent install fails
> 
> Caught an exception while executing custom service command:  'ambari_agent.AgentException.AgentException'>: 'Script 
> /var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_agent.py
>  does not exist'; 'Script 
> /var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_agent.py
>  does not exist'
> 
> Caught an exception while executing custom service command:  'ambari_agent.AgentException.AgentException'>: 'Script 
> /var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_server.py
>  does not exist'; 'Script 
> /var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_server.py
>  does not exist'
> 
> server is running under user slava:
> slava23129  3.3  4.2 4768512 686808 ?  Sl   02:28  25:37 
> /usr/jdk64/jdk1.8.0_45/bin/java -server -XX:NewRatio=3 
> -XX:+UseConcMarkSweepGC -XX:-UseGCOverheadLimit 
> -XX:CMSInitiatingOccupancyFraction=60 -Dsun.zip.disableMemoryMapping=true 
> -Xms512m -Xmx2048m 
> -Djava.security.auth.login.config=/etc/ambari-server/conf/krb5JAASLogin.conf 
> -Djava.security.krb5.conf=/etc/krb5.conf 
> -Djavax.security.auth.useSubjectCredsOnly=false -Xms512m -Xmx2048m 
> -Djava.security.auth.login.config=/etc/ambari-server/conf/krb5JAASLogin.conf 
> -Djava.security.krb5.conf=/etc/krb5.conf 
> -Djavax.security.auth.useSubjectCredsOnly=false -cp 
> /etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/mysql-connector-java.jar
>  org.apache.ambari.server.controller.AmbariServer
> 
> Files generated by ambari-server script have wrong permissions:
> [root@os-r6-stest-5 tmp]# ll 
> /var/lib/ambari-server/resources/stacks/HDP/2.1/services/SMARTSENSE/package/
> total 840
> -rw-r-. 1 root  root  0 2015-11-13 02:27 abc.txt
> -rw-r-. 1 root  root 850974 2015-11-12 22:26 archive.zip
> drwxr-xr-x. 4 slava root   4096 2015-11-12 22:25 files
> drwxr-xr-x. 2 slava root   4096 2015-11-12 22:25 scripts
> 
> [root@os-r6-stest-5 tmp]# umask
> 0027
> And that's why file can not be read by server process.
> 
> 
> Diffs
> -
> 
>   ambari-server/src/main/python/ambari_server/resourceFilesKeeper.py fe80723 
> 
> Diff: https://reviews.apache.org/r/40298/diff/
> 
> 
> Testing
> ---
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Dmitro Lisnichenko
> 
>

Re: Review Request 40236: Check status of RS process for AMS in embedded mode

[Dmytro Sen]

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

(Updated Ноя. 13, 2015, 3:28 п.п.)


Review request for Ambari and Sid Wagle.


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


Repository: ambari


Description
---

TimelineMetricStoreWatcher added, it checks TimelineMetricStore functionality 
by adding and getting a fake metric to/from HBase.


Diffs (updated)
-

  
ambari-metrics/ambari-metrics-timelineservice/conf/unix/ambari-metrics-collector
 0018bc2 
  
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/ApplicationHistoryServer.java
 d79ca68 
  
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/HBaseTimelineMetricStore.java
 aed5fed 
  
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/PhoenixHBaseAccessor.java
 be06650 
  
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/TimelineMetricConfiguration.java
 fd51f3d 
  
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/TimelineMetricStoreWatcher.java
 PRE-CREATION 
  
ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/TimelineMetricStoreWatcherTest.java
 PRE-CREATION 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-site.xml
 c73a401 

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


Testing
---

Unit tests passed


Thanks,

Dmytro Sen

[jira] [Assigned] (AMBARI-13860) NN HA Wizard does not repopulate the Nameservice value when user nav back from a later page to change its value

[Di Li (JIRA)]

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

Di Li reassigned AMBARI-13860:
--

Assignee: Di Li

> NN HA Wizard does not repopulate the Nameservice value when user nav back 
> from a later page to change its value
> ---
>
> Key: AMBARI-13860
> URL: https://issues.apache.org/jira/browse/AMBARI-13860
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.0
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
>
> On the NN HA Wizard page 1, type in "nnsrv" as the nameservice value, then go 
> to the next page. You will see the the value is used for a few property 
> changes. 
> If you then nav back to page 1 to change the nameservice value to something 
> different, say "mynamesrv", then Next to the next page, the UI still uses the 
> old nameservice value and the fields are read-only. Users then have to exit 
> the NN HA wizard, and reopen it.



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

[jira] [Resolved] (AMBARI-13860) NN HA Wizard does not repopulate the Nameservice value when user nav back from a later page to change its value

[Di Li (JIRA)]

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

Di Li resolved AMBARI-13860.

   Resolution: Cannot Reproduce
Fix Version/s: trunk

can't reproduce in trunk

> NN HA Wizard does not repopulate the Nameservice value when user nav back 
> from a later page to change its value
> ---
>
> Key: AMBARI-13860
> URL: https://issues.apache.org/jira/browse/AMBARI-13860
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.0
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
>
> On the NN HA Wizard page 1, type in "nnsrv" as the nameservice value, then go 
> to the next page. You will see the the value is used for a few property 
> changes. 
> If you then nav back to page 1 to change the nameservice value to something 
> different, say "mynamesrv", then Next to the next page, the UI still uses the 
> old nameservice value and the fields are read-only. Users then have to exit 
> the NN HA wizard, and reopen it.



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

[jira] [Commented] (AMBARI-13878) Incorrect calculating of task duration

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13878:
-

ABORTED: Integrated in Ambari-branch-2.1 #855 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/855/])
AMBARI-13878. Incorrect calculating of task duration (onechiporenko) 
(onechiporenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=203195cc7ec0f5197137314f7c1eafaf57cc13d0])
* ambari-web/test/utils/date/date_test.js
* ambari-web/app/utils/date/date.js
* ambari-web/app/controllers/global/background_operations_controller.js


> Incorrect calculating of task duration
> --
>
> Key: AMBARI-13878
> URL: https://issues.apache.org/jira/browse/AMBARI-13878
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.3
> Environment: ambari-server version: ambari-server-2.1.3.0-322.x86_64
> ambari-server --hash: 84dfed9968ce8224d49540a7572cd90b6d4538c2
> HDP Stack: 2.3
> HDP Version: 2.3.4.0-3192
> Ambari DB: :MySQL
> Oozie/Hive DB: MySQL/MySQL
> Security:no
> Security Type:MIT/MIT
> Blueprints: false
> Umask: 027
> JDK: default
> HA: no
> Repo URL: 
> http://s3.amazonaws.com/dev.hortonworks.com/ambari/centos6/2.x/updates/2.1.3.0/ambariqe.repo
> OS: CentOS 6
> Gateway: 172.22.121.36:8080
> Ambari User: slava
> Agents User: agentslava
> MOTD: false
> Customized service users: false
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.2.0
>
> Attachments: AMBARI-13878.patch, incorrectDuration.png
>
>
> Steps:
> # Go to any service (I tried with Fafka, HDFS, YARN).
> # Select "Restart All" from Service Actions combobox.
> # Go to another service.
> # Select "Restart All" from Service Actions combobox too.
> Result: Fist operation has duration more than 2 hours. Duration become 
> correct after task completion.



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

[jira] [Commented] (AMBARI-13861) hdfs balancer via ambari fails to run after HDP upgrade with NN HA enabled

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13861:
-

ABORTED: Integrated in Ambari-branch-2.1 #855 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/855/])
AMBARI-13861. hdfs balancer via ambari fails to run after HDP upgrade 
(dlysnichenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=55808eaf896f6df8ea99fbe72c58ca184bc8])
* ambari-server/src/test/resources/stacks/HDP/2.1.1/upgrades/config-upgrade.xml
* ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.3.xml
* 
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ConfigUpgradeChangeDefinition.java
* 
ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/nonrolling-upgrade-2.3.xml
* 
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ConfigureTask.java
* 
ambari-server/src/test/java/org/apache/ambari/server/state/UpgradeHelperTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/PropertyKeyState.java
* ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/config-upgrade.xml


> hdfs balancer via ambari fails to run after HDP upgrade with NN HA enabled
> --
>
> Key: AMBARI-13861
> URL: https://issues.apache.org/jira/browse/AMBARI-13861
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.3
>Reporter: Dmytro Grinenko
>Assignee: Dmitry Lysnichenko
>Priority: Critical
> Fix For: 2.1.3
>
>
> Ran hdfs balancer via ambari on a cluster that had HA enabled and it failed.
> {code}
> Starting balancer with threshold = 10
> Executing command ambari-sudo.sh su hdfs -l -s /bin/bash -c 'export  
> PATH='"'"'/usr/sbin:/sbin:/usr/lib/ambari-server/*:/usr/sbin:/sbin:/usr/lib/ambari-server/*:/usr/lib64/qt-3.3/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin:/var/lib/ambari-agent:/var/lib/ambari-agent:/usr/hdp/current/hadoop-client/bin'"'"'
>  ; hdfs --config /usr/hdp/current/hadoop-client/conf balancer -threshold 10'
> 2015-10-06 23:33:27,059 - Execute['ambari-sudo.sh su hdfs -l -s /bin/bash -c 
> 'export  
> PATH='"'"'/usr/sbin:/sbin:/usr/lib/ambari-server/*:/usr/sbin:/sbin:/usr/lib/ambari-server/*:/usr/lib64/qt-3.3/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin:/var/lib/ambari-agent:/var/lib/ambari-agent:/usr/hdp/current/hadoop-client/bin'"'"'
>  ; hdfs --config /usr/hdp/current/hadoop-client/conf balancer -threshold 
> 10''] {'logoutput': False, 'on_new_line': handle_new_line}
> [balancer] 15/10/06 23:33:29 INFO balancer.Balancer: Using a threshold of 10.0
> [balancer] 15/10/06 23:33:29 INFO balancer.Balancer: namenodes  = 
> [hdfs://pre-prod-poc-1.novalocal:8020, hdfs://pre-prod-hdp-2-3]
> [balancer] 15/10/06 23:33:29 INFO balancer.Balancer: parameters = 
> Balancer.Parameters [BalancingPolicy.Node, threshold = 10.0, max idle 
> iteration = 5, #excluded nodes = 0, #included nodes = 0, #source nodes = 0, 
> run during upgrade = false]
> [balancer] 15/10/06 23:33:29 INFO balancer.Balancer: included nodes = []
> [balancer] 15/10/06 23:33:29 INFO balancer.Balancer: excluded nodes = []
> [balancer] 15/10/06 23:33:29 INFO balancer.Balancer: source nodes = []
> [balancer] Time Stamp   Iteration#  Bytes Already Moved  Bytes 
> Left To Move  Bytes Being Moved[balancer] 
> [balancer] 
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.ipc.StandbyException):
>  Operation category READ is not supported in state standby
>   at 
> org.apache.hadoop.hdfs.server.namenode.ha.StandbyState.checkOperation(StandbyState.java:87)
>   at 
> org.apache.hadoop.hdfs.server.namenode.NameNode$NameNodeHAContext.checkOperation(NameNode.java:1872)
>   at 
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkOperation(FSNamesystem.java:1306)
>   at 
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getServerDefaults(FSNamesystem.java:1618)
>   at 
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.getServerDefaults(NameNodeRpcServer.java:595)
>   at 
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.getServerDefaults(ClientNamenodeProtocolServerSideTranslatorPB.java:383)
>   at 
> org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
>   at 
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(Proto[balancer]
>  bufRpcEngine.java:616)
>   at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:969)
>   at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2137)
>   at 

[jira] [Commented] (AMBARI-13877) RU/EU: host failure summary dialog usability changes

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13877:
-

ABORTED: Integrated in Ambari-branch-2.1 #855 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/855/])
AMBARI-13877 RU/EU: host failure summary dialog usability changes. (atkach: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=21983a7585d5e9c36136c826d5e29fde1c2adec8])
* ambari-web/app/templates/main/admin/stack_upgrade/stack_upgrade_wizard.hbs
* ambari-web/test/views/main/admin/stack_upgrade/failed_hosts_modal_view_test.js
* ambari-web/app/views.js
* ambari-web/app/messages.js
* ambari-web/app/views/main/admin/stack_upgrade/failed_hosts_modal_view.js
* ambari-web/test/views/main/admin/stack_upgrade/upgrade_wizard_view_test.js
* ambari-web/app/views/main/admin/stack_upgrade/upgrade_wizard_view.js
* ambari-web/app/assets/test/tests.js
* ambari-web/test/controllers/main/admin/stack_and_upgrade_controller_test.js
* ambari-web/app/templates/main/admin/stack_upgrade/failed_hosts_modal.hbs
* ambari-web/app/styles/stack_versions.less
* ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js


> RU/EU: host failure summary dialog usability changes
> 
>
> Key: AMBARI-13877
> URL: https://issues.apache.org/jira/browse/AMBARI-13877
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.1.3
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13877.patch, AMBARI-13877_branch-2.1.patch, 
> ru-failure.pptx
>
>
> In cases where hosts are skipped during upgrade (RU or EU), need to provide 
> more information to the user about the hosts and what happened.
> This attached mock provide more detail on the hosts and the component 
> failures.



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

[jira] [Commented] (AMBARI-13881) Devdeploy: YARN,Mahout service checks fail on all OSes

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13881:
-

ABORTED: Integrated in Ambari-branch-2.1 #855 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/855/])
AMBARI-13881. Devdeploy: YARN,Mahout service checks fail on all OSes (aonishuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=994133826c47b1371240e8235c5bf3a86beccd58])
* 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/yarn.py
* ambari-server/src/test/python/stacks/2.0.6/YARN/test_historyserver.py
* 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py


> Devdeploy: YARN,Mahout service checks fail on all OSes
> --
>
> Key: AMBARI-13881
> URL: https://issues.apache.org/jira/browse/AMBARI-13881
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.1.3
>
>
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/MAHOUT/1.0.0.2.3/package/scripts/service_check.py",
>  line 79, in 
> MahoutServiceCheck().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 218, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/MAHOUT/1.0.0.2.3/package/scripts/service_check.py",
>  line 66, in service_check
> user = params.smokeuser
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line 
> 154, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 156, in run
> self.run_action(resource, action)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 119, in run_action
> provider_action()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
>  line 238, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 70, in inner
> result = function(command, **kwargs)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 92, in checked_call
> tries=tries, try_sleep=try_sleep)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 140, in _call_wrapper
> result = _call(command, **kwargs_copy)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 291, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'mahout 
> seqdirectory --input /user/ambari-qa/mahoutsmokeinput/sample-mahout-test.txt 
> --output /user/ambari-qa/mahoutsmokeoutput/ --charset utf-8' returned 1. 
> MAHOUT_LOCAL is not set; adding HADOOP_CONF_DIR to classpath.
> Running on hadoop, using /usr/hdp/current/hadoop-client/bin/hadoop and 
> HADOOP_CONF_DIR=/usr/hdp/current/hadoop-client/conf
> MAHOUT-JOB: 
> /usr/hdp/2.3.4.0-3235/mahout/mahout-examples-0.9.0.2.3.4.0-3235-job.jar
> WARNING: Use "yarn jar" to launch YARN applications.
> 15/11/13 12:17:46 WARN driver.MahoutDriver: No seqdirectory.props found 
> on classpath, will use command-line arguments only
> 15/11/13 12:17:47 INFO common.AbstractJob: Command line arguments: 
> {--charset=[utf-8], --chunkSize=[64], --endPhase=[2147483647], 
> --fileFilterClass=[org.apache.mahout.text.PrefixAdditionFilter], 
> --input=[/user/ambari-qa/mahoutsmokeinput/sample-mahout-test.txt], 
> --keyPrefix=[], --method=[mapreduce], 
> --output=[/user/ambari-qa/mahoutsmokeoutput/], --startPhase=[0], 
> --tempDir=[temp]}
> 15/11/13 12:17:49 INFO impl.TimelineClientImpl: Timeline service address: 
> http://os-u14-fxhqus-devdeploy-1.novalocal:8188/ws/v1/timeline/
> 15/11/13 12:17:49 INFO client.RMProxy: Connecting to ResourceManager at 
> os-u14-fxhqus-devdeploy-2.novalocal/172.22.82.23:8050
> 15/11/13 12:17:49 INFO service.AbstractService: Service 
> org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl failed in state 
> STARTED; cause: java.io.IOException: /tmp/entity-file-history/active does not 
> exist
> java.io.IOException: /tmp/entity-file-history/active does not exist
>   at 
> org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl.serviceStart(TimelineClientImpl.java:366)
>   at 
> org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
>   at 
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.serviceStart(YarnClientImpl.java:194)
>   at 
> 

[jira] [Commented] (AMBARI-13883) Upgrade: when out of sync, should default to Install Packages button

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13883:
-

ABORTED: Integrated in Ambari-branch-2.1 #855 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/855/])
AMBARI-13883 Upgrade: when out of sync, should default to Install (atkach: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ae3ce8b9898875fcaa1d5a08b75f9b002c1a4edb])
* ambari-web/app/views/main/admin/stack_upgrade/upgrade_version_box_view.js
* 
ambari-web/test/views/main/admin/stack_upgrade/upgrade_version_box_view_test.js


> Upgrade: when out of sync, should default to Install Packages button
> 
>
> Key: AMBARI-13883
> URL: https://issues.apache.org/jira/browse/AMBARI-13883
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.3
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13883.patch, reinstall.tiff
>
>
> 1) Install cluster with HDP 2.3.0 + HDFS, yarn,zk
> 2) installed hdp 2.3.2
> 3) before upgrading, went to add service hive. I was then out of sync 
> (correct)
> 4) Versions shows out of sync icon (correct) but the button defaulted to 
> Perform Upgrade.
> Should have defaulted to re-install packages button.
> See attached



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

[jira] [Commented] (AMBARI-13843) Create a script to setup an Ambari deployment for non-root

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13843:
-

FAILURE: Integrated in Ambari-trunk-Commit #3830 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3830/])
AMBARI-13843. Create a script to setup an Ambari deployment for non-root 
(aonishuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2d03c6d00224eeb974416345c804bc0cbb732c46])
* b/contrib/utils/non_root/setup_and_start_non_root_agent.sh
* b/contrib/utils/non_root/setup_and_start_non_root_server.sh


> Create a script to setup an Ambari deployment for non-root
> --
>
> Key: AMBARI-13843
> URL: https://issues.apache.org/jira/browse/AMBARI-13843
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.1.3
>
>
> Create a script to setup the hosts for non-root deployment of Ambari Server
> and Agent. Next week we plan to have a bug-bash for upgrades. This script will
> be useful to hand it off to the bug-bash participants.



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

[jira] [Commented] (AMBARI-13882) Flume agent does not display metrics

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13882:
-

FAILURE: Integrated in Ambari-trunk-Commit #3830 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3830/])
AMBARI-13882 Flume agent does not display metrics (dsen) (dsen: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=52346faba7af51f326ff7c35f0942019fe6c137d])
* 
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/webapp/TimelineWebServices.java
* 
ambari-metrics/ambari-metrics-storm-sink/src/main/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsSink.java
* 
ambari-metrics/ambari-metrics-kafka-sink/src/main/java/org/apache/hadoop/metrics2/sink/kafka/KafkaTimelineMetricsReporter.java
* 
ambari-metrics/ambari-metrics-flume-sink/src/main/java/org/apache/hadoop/metrics2/sink/flume/FlumeTimelineMetricsSink.java
* 
ambari-metrics/ambari-metrics-flume-sink/src/test/java/org/apache/hadoop/metrics2/sink/flume/FlumeTimelineMetricsSinkTest.java
* 
ambari-metrics/ambari-metrics-storm-sink/src/main/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsReporter.java
* 
ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/AbstractTimelineMetricsSink.java


> Flume agent does not display metrics
> 
>
> Key: AMBARI-13882
> URL: https://issues.apache.org/jira/browse/AMBARI-13882
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.1.3
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13882.patch
>
>
> Flume,Storm,Kafka sink report short hostnames instead of fqdn in some 
> enviroments



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

[jira] [Commented] (AMBARI-13880) DataNode Data Directories Which Contain Meta Information Tags Trigger Alerts

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13880:
-

FAILURE: Integrated in Ambari-trunk-Commit #3830 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3830/])
AMBARI-13880. DataNode Data Directories Which Contain Meta Information 
(vbrodetskyi: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=77d0fc15880e286ccd147dd77a15641ef91d6fd3])
* 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/alerts/alert_datanode_unmounted_data_dir.py


> DataNode Data Directories Which Contain Meta Information Tags Trigger Alerts
> 
>
> Key: AMBARI-13880
> URL: https://issues.apache.org/jira/browse/AMBARI-13880
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent, ambari-server
>Affects Versions: 2.1.2
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13880.patch
>
>
> HDFS allows the ability to tag DataNode data directories with meta 
> information:
> https://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-hdfs/ArchivalStorage.html
> Which results in paths that look like:
> [DISK]/hadoop/hdfs/data,[SSD]/hadoop/hdfs/ssd
> Many of our scripts assume that directories specified in 
> hdfs-site/dfs.datanode.data.dir are actual paths and perform operations like 
> os.path.isdir which will fail with meta data.



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

Re: Review Request 40221: AMS should not assume hdfs as the protocol

[Sid Wagle]

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

Ship it!


Ship It!

- Sid Wagle


On Nov. 12, 2015, 9:50 a.m., Dmytro Sen wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40221/
> ---
> 
> (Updated Nov. 12, 2015, 9:50 a.m.)
> 
> 
> Review request for Ambari, Sumit Mohanty and Sid Wagle.
> 
> 
> Bugs: AMBARI-13851
> https://issues.apache.org/jira/browse/AMBARI-13851
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> AMS scripts should not assume that hdfs is the protocol.
> is_hbase_distributed = hbase_root_dir.startswith('hdfs://')
> 
> or 
> 
> is_hbase_distributed = 
> security_params['hbase-site']['hbase.rootdir'].startswith('hdfs://')
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams.py
>  50e363c 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/hbase.py
>  9e6f2fa 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py
>  00e4123 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py
>  1c6a49f 
>   ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py 
> 7181122 
>   
> ambari-server/src/test/python/stacks/2.0.6/AMBARI_METRICS/test_metrics_collector.py
>  b04e1d5 
> 
> Diff: https://reviews.apache.org/r/40221/diff/
> 
> 
> Testing
> ---
> 
> --
> Ran 249 tests in 8.115s
> 
> OK
> --
> Total run:831
> Total errors:0
> Total failures:0
> OK
> 
> 
> Thanks,
> 
> Dmytro Sen
> 
>

[jira] [Commented] (AMBARI-13861) hdfs balancer via ambari fails to run after HDP upgrade with NN HA enabled

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13861:
-

FAILURE: Integrated in Ambari-trunk-Commit #3829 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3829/])
AMBARI-13861. hdfs balancer via ambari fails to run after HDP upgrade 
(dlysnichenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a2aa69ec183f1880deb91de8d7126db61dea1abf])
* ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/config-upgrade.xml
* 
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ConfigUpgradeChangeDefinition.java
* 
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ConfigureTask.java
* ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.3.xml
* 
ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/nonrolling-upgrade-2.3.xml
* 
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/PropertyKeyState.java
* ambari-server/src/test/resources/stacks/HDP/2.1.1/upgrades/config-upgrade.xml
* 
ambari-server/src/test/java/org/apache/ambari/server/state/UpgradeHelperTest.java


> hdfs balancer via ambari fails to run after HDP upgrade with NN HA enabled
> --
>
> Key: AMBARI-13861
> URL: https://issues.apache.org/jira/browse/AMBARI-13861
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.3
>Reporter: Dmytro Grinenko
>Assignee: Dmitry Lysnichenko
>Priority: Critical
> Fix For: 2.1.3
>
>
> Ran hdfs balancer via ambari on a cluster that had HA enabled and it failed.
> {code}
> Starting balancer with threshold = 10
> Executing command ambari-sudo.sh su hdfs -l -s /bin/bash -c 'export  
> PATH='"'"'/usr/sbin:/sbin:/usr/lib/ambari-server/*:/usr/sbin:/sbin:/usr/lib/ambari-server/*:/usr/lib64/qt-3.3/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin:/var/lib/ambari-agent:/var/lib/ambari-agent:/usr/hdp/current/hadoop-client/bin'"'"'
>  ; hdfs --config /usr/hdp/current/hadoop-client/conf balancer -threshold 10'
> 2015-10-06 23:33:27,059 - Execute['ambari-sudo.sh su hdfs -l -s /bin/bash -c 
> 'export  
> PATH='"'"'/usr/sbin:/sbin:/usr/lib/ambari-server/*:/usr/sbin:/sbin:/usr/lib/ambari-server/*:/usr/lib64/qt-3.3/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin:/var/lib/ambari-agent:/var/lib/ambari-agent:/usr/hdp/current/hadoop-client/bin'"'"'
>  ; hdfs --config /usr/hdp/current/hadoop-client/conf balancer -threshold 
> 10''] {'logoutput': False, 'on_new_line': handle_new_line}
> [balancer] 15/10/06 23:33:29 INFO balancer.Balancer: Using a threshold of 10.0
> [balancer] 15/10/06 23:33:29 INFO balancer.Balancer: namenodes  = 
> [hdfs://pre-prod-poc-1.novalocal:8020, hdfs://pre-prod-hdp-2-3]
> [balancer] 15/10/06 23:33:29 INFO balancer.Balancer: parameters = 
> Balancer.Parameters [BalancingPolicy.Node, threshold = 10.0, max idle 
> iteration = 5, #excluded nodes = 0, #included nodes = 0, #source nodes = 0, 
> run during upgrade = false]
> [balancer] 15/10/06 23:33:29 INFO balancer.Balancer: included nodes = []
> [balancer] 15/10/06 23:33:29 INFO balancer.Balancer: excluded nodes = []
> [balancer] 15/10/06 23:33:29 INFO balancer.Balancer: source nodes = []
> [balancer] Time Stamp   Iteration#  Bytes Already Moved  Bytes 
> Left To Move  Bytes Being Moved[balancer] 
> [balancer] 
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.ipc.StandbyException):
>  Operation category READ is not supported in state standby
>   at 
> org.apache.hadoop.hdfs.server.namenode.ha.StandbyState.checkOperation(StandbyState.java:87)
>   at 
> org.apache.hadoop.hdfs.server.namenode.NameNode$NameNodeHAContext.checkOperation(NameNode.java:1872)
>   at 
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkOperation(FSNamesystem.java:1306)
>   at 
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getServerDefaults(FSNamesystem.java:1618)
>   at 
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.getServerDefaults(NameNodeRpcServer.java:595)
>   at 
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.getServerDefaults(ClientNamenodeProtocolServerSideTranslatorPB.java:383)
>   at 
> org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
>   at 
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(Proto[balancer]
>  bufRpcEngine.java:616)
>   at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:969)
>   at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2137)
>   at 

[jira] [Commented] (AMBARI-13878) Incorrect calculating of task duration

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13878:
-

FAILURE: Integrated in Ambari-trunk-Commit #3829 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3829/])
AMBARI-13878. Incorrect calculating of task duration (onechiporenko) 
(onechiporenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e85822db638c10a8c29e480fb48f24b51994d46a])
* ambari-web/app/controllers/global/background_operations_controller.js
* ambari-web/test/utils/date/date_test.js
* ambari-web/app/utils/date/date.js


> Incorrect calculating of task duration
> --
>
> Key: AMBARI-13878
> URL: https://issues.apache.org/jira/browse/AMBARI-13878
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.3
> Environment: ambari-server version: ambari-server-2.1.3.0-322.x86_64
> ambari-server --hash: 84dfed9968ce8224d49540a7572cd90b6d4538c2
> HDP Stack: 2.3
> HDP Version: 2.3.4.0-3192
> Ambari DB: :MySQL
> Oozie/Hive DB: MySQL/MySQL
> Security:no
> Security Type:MIT/MIT
> Blueprints: false
> Umask: 027
> JDK: default
> HA: no
> Repo URL: 
> http://s3.amazonaws.com/dev.hortonworks.com/ambari/centos6/2.x/updates/2.1.3.0/ambariqe.repo
> OS: CentOS 6
> Gateway: 172.22.121.36:8080
> Ambari User: slava
> Agents User: agentslava
> MOTD: false
> Customized service users: false
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.2.0
>
> Attachments: AMBARI-13878.patch, incorrectDuration.png
>
>
> Steps:
> # Go to any service (I tried with Fafka, HDFS, YARN).
> # Select "Restart All" from Service Actions combobox.
> # Go to another service.
> # Select "Restart All" from Service Actions combobox too.
> Result: Fist operation has duration more than 2 hours. Duration become 
> correct after task completion.



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

[jira] [Updated] (AMBARI-13887) SmartSense install fails as archive.zip fails to download

[Dmitry Lysnichenko (JIRA)]

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

Dmitry Lysnichenko updated AMBARI-13887:

Component/s: ambari-server

> SmartSense install fails as archive.zip fails to download
> -
>
> Key: AMBARI-13887
> URL: https://issues.apache.org/jira/browse/AMBARI-13887
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Attachments: AMBARI-13887.patch
>
>
> Try to install Smart Sense when trying to deploy HDP 2.3 and the server and 
> agent install fails
> Caught an exception while executing custom service command:  'ambari_agent.AgentException.AgentException'>: 'Script 
> /var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_agent.py
>  does not exist'; 'Script 
> /var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_agent.py
>  does not exist'
> Caught an exception while executing custom service command:  'ambari_agent.AgentException.AgentException'>: 'Script 
> /var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_server.py
>  does not exist'; 'Script 
> /var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_server.py
>  does not exist'



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

[jira] [Updated] (AMBARI-13887) SmartSense install fails as archive.zip fails to download

[Dmitry Lysnichenko (JIRA)]

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

Dmitry Lysnichenko updated AMBARI-13887:

Attachment: AMBARI-13887.patch

> SmartSense install fails as archive.zip fails to download
> -
>
> Key: AMBARI-13887
> URL: https://issues.apache.org/jira/browse/AMBARI-13887
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Attachments: AMBARI-13887.patch
>
>
> Try to install Smart Sense when trying to deploy HDP 2.3 and the server and 
> agent install fails
> Caught an exception while executing custom service command:  'ambari_agent.AgentException.AgentException'>: 'Script 
> /var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_agent.py
>  does not exist'; 'Script 
> /var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_agent.py
>  does not exist'
> Caught an exception while executing custom service command:  'ambari_agent.AgentException.AgentException'>: 'Script 
> /var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_server.py
>  does not exist'; 'Script 
> /var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_server.py
>  does not exist'



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

[jira] [Created] (AMBARI-13887) SmartSense install fails as archive.zip fails to download

[Dmitry Lysnichenko (JIRA)]

Dmitry Lysnichenko created AMBARI-13887:
---

 Summary: SmartSense install fails as archive.zip fails to download
 Key: AMBARI-13887
 URL: https://issues.apache.org/jira/browse/AMBARI-13887
 Project: Ambari
  Issue Type: Bug
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko
 Attachments: AMBARI-13887.patch


Try to install Smart Sense when trying to deploy HDP 2.3 and the server and 
agent install fails

Caught an exception while executing custom service command: : 'Script 
/var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_agent.py
 does not exist'; 'Script 
/var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_agent.py
 does not exist'

Caught an exception while executing custom service command: : 'Script 
/var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_server.py
 does not exist'; 'Script 
/var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_server.py
 does not exist'





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

Review Request 40300: Ranger Usersync Moving From Seconds to Millis On Stack Upgrade

[Jonathan Hurley]

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

Review request for Ambari, Alejandro Fernandez, Jayush Luniya, and Nate Cole.


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


Repository: ambari


Description
---

During upgrade, sync interval needs to be migrated properly.

In HDP 2.2, ranger treats this value in minutes 
{{usersync-properties.xml/SYNC_INTERVAL}}. In HDP 2.3, the unit changed to 
milliseconds 
{{ranger-ugsync-site.xml/ranger.usersync.sleeptimeinmillisbetweensynccycle}}. 
So upgrade should handle the transformation.

Yes, we _could_ write a Java class with performs "smart" checking and just 
multiplies a modified value by 1000 - but that's a lot of work for really no 
benefit. Let's just correct the value so that it doesn't hammer the server and 
set it  back to the stock value.


Diffs
-

  
ambari-server/src/main/resources/stacks/HDP/2.3/services/RANGER/configuration/ranger-ugsync-site.xml
 d61cf20 
  ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/config-upgrade.xml 
518132e 
  
ambari-server/src/main/resources/upgrade/catalog/UpgradeCatalog_2.2_to_2.3.json 
40c345d 

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


Testing
---


Thanks,

Jonathan Hurley

Re: Review Request 40294: Flume agent does not display metrics

[Dmytro Sen]

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

(Updated Ноя. 13, 2015, 2:56 п.п.)


Review request for Ambari, Myroslav Papirkovskyy, Sid Wagle, and Vitalyi 
Brodetskyi.


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


Repository: ambari


Description
---

Flume,Storm,Kafka sink report short hostnames instead of fqdn in some 
enviroments


Diffs (updated)
-

  
ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/AbstractTimelineMetricsSink.java
 5aba016 
  
ambari-metrics/ambari-metrics-flume-sink/src/main/java/org/apache/hadoop/metrics2/sink/flume/FlumeTimelineMetricsSink.java
 530c8c1 
  
ambari-metrics/ambari-metrics-flume-sink/src/test/java/org/apache/hadoop/metrics2/sink/flume/FlumeTimelineMetricsSinkTest.java
 fa1ca21 
  
ambari-metrics/ambari-metrics-kafka-sink/src/main/java/org/apache/hadoop/metrics2/sink/kafka/KafkaTimelineMetricsReporter.java
 dd7604b 
  
ambari-metrics/ambari-metrics-storm-sink/src/main/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsReporter.java
 5e27cf8 
  
ambari-metrics/ambari-metrics-storm-sink/src/main/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsSink.java
 3a49e0a 
  
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/webapp/TimelineWebServices.java
 ecfbe78 

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


Testing
---

Unit tests passed


Thanks,

Dmytro Sen

Re: Review Request 40294: Flume agent does not display metrics

[Myroslav Papirkovskyy]

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

Ship it!


Ship It!

- Myroslav Papirkovskyy


On Лис. 13, 2015, 4:56 після полудня, Dmytro Sen wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40294/
> ---
> 
> (Updated Лис. 13, 2015, 4:56 після полудня)
> 
> 
> Review request for Ambari, Myroslav Papirkovskyy, Sid Wagle, and Vitalyi 
> Brodetskyi.
> 
> 
> Bugs: AMBARI-13882
> https://issues.apache.org/jira/browse/AMBARI-13882
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Flume,Storm,Kafka sink report short hostnames instead of fqdn in some 
> enviroments
> 
> 
> Diffs
> -
> 
>   
> ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/AbstractTimelineMetricsSink.java
>  5aba016 
>   
> ambari-metrics/ambari-metrics-flume-sink/src/main/java/org/apache/hadoop/metrics2/sink/flume/FlumeTimelineMetricsSink.java
>  530c8c1 
>   
> ambari-metrics/ambari-metrics-flume-sink/src/test/java/org/apache/hadoop/metrics2/sink/flume/FlumeTimelineMetricsSinkTest.java
>  fa1ca21 
>   
> ambari-metrics/ambari-metrics-kafka-sink/src/main/java/org/apache/hadoop/metrics2/sink/kafka/KafkaTimelineMetricsReporter.java
>  dd7604b 
>   
> ambari-metrics/ambari-metrics-storm-sink/src/main/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsReporter.java
>  5e27cf8 
>   
> ambari-metrics/ambari-metrics-storm-sink/src/main/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsSink.java
>  3a49e0a 
>   
> ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/webapp/TimelineWebServices.java
>  ecfbe78 
> 
> Diff: https://reviews.apache.org/r/40294/diff/
> 
> 
> Testing
> ---
> 
> Unit tests passed
> 
> 
> Thanks,
> 
> Dmytro Sen
> 
>

[jira] [Resolved] (AMBARI-13705) Metrics Cache sizing test failing on trunk

[Dmytro Sen (JIRA)]

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

Dmytro Sen resolved AMBARI-13705.
-
Resolution: Fixed

Committed to trunk and branch-2.1

> Metrics Cache sizing test failing on trunk
> --
>
> Key: AMBARI-13705
> URL: https://issues.apache.org/jira/browse/AMBARI-13705
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.3
>Reporter: Siddharth Wagle
>Assignee: Aravindan Vijayan
> Fix For: 2.1.3
>
> Attachments: AMBARI-13705-trunk.patch
>
>
> org.apache.ambari.server.controller.metrics.timeline.cache.TimelineMetricCacheSizingTest#testTimelineMetricCacheSizing
>  fails on apache infra only.



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

[jira] [Created] (AMBARI-13888) Ranger Usersync Moving From Seconds to Millis On HDP Upgrade

[Jonathan Hurley (JIRA)]

Jonathan Hurley created AMBARI-13888:


 Summary: Ranger Usersync Moving From Seconds to Millis On HDP 
Upgrade
 Key: AMBARI-13888
 URL: https://issues.apache.org/jira/browse/AMBARI-13888
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.1.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
 Fix For: 2.1.3


During upgrade, sync interval needs to be migrated properly.

In HDP 2.2, ranger treats this value in minutes 
{{usersync-properties.xml/SYNC_INTERVAL}}. In HDP 2.3, the unit changed to 
milliseconds 
{{ranger-ugsync-site.xml/ranger.usersync.sleeptimeinmillisbetweensynccycle}}. 
So upgrade should handle the transformation.



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

[jira] [Updated] (AMBARI-13888) Ranger Usersync Moving From Seconds to Millis On Stack Upgrade

[Jonathan Hurley (JIRA)]

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

Jonathan Hurley updated AMBARI-13888:
-
Attachment: AMBARI-13888.patch

> Ranger Usersync Moving From Seconds to Millis On Stack Upgrade
> --
>
> Key: AMBARI-13888
> URL: https://issues.apache.org/jira/browse/AMBARI-13888
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
> Fix For: 2.1.3
>
> Attachments: AMBARI-13888.patch
>
>
> During upgrade, sync interval needs to be migrated properly.
> In HDP 2.2, ranger treats this value in minutes 
> {{usersync-properties.xml/SYNC_INTERVAL}}. In HDP 2.3, the unit changed to 
> milliseconds 
> {{ranger-ugsync-site.xml/ranger.usersync.sleeptimeinmillisbetweensynccycle}}. 
> So upgrade should handle the transformation.



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

Re: Review Request 40236: Check status of RS process for AMS in embedded mode

[Sid Wagle]

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

Ship it!


Ship It!

- Sid Wagle


On Nov. 13, 2015, 3:28 p.m., Dmytro Sen wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40236/
> ---
> 
> (Updated Nov. 13, 2015, 3:28 p.m.)
> 
> 
> Review request for Ambari and Sid Wagle.
> 
> 
> Bugs: AMBARI-13862
> https://issues.apache.org/jira/browse/AMBARI-13862
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> TimelineMetricStoreWatcher added, it checks TimelineMetricStore functionality 
> by adding and getting a fake metric to/from HBase.
> 
> 
> Diffs
> -
> 
>   
> ambari-metrics/ambari-metrics-timelineservice/conf/unix/ambari-metrics-collector
>  0018bc2 
>   
> ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/ApplicationHistoryServer.java
>  d79ca68 
>   
> ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/HBaseTimelineMetricStore.java
>  aed5fed 
>   
> ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/PhoenixHBaseAccessor.java
>  be06650 
>   
> ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/TimelineMetricConfiguration.java
>  fd51f3d 
>   
> ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/TimelineMetricStoreWatcher.java
>  PRE-CREATION 
>   
> ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/TimelineMetricStoreWatcherTest.java
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-site.xml
>  c73a401 
> 
> Diff: https://reviews.apache.org/r/40236/diff/
> 
> 
> Testing
> ---
> 
> Unit tests passed
> 
> 
> Thanks,
> 
> Dmytro Sen
> 
>

[jira] [Commented] (AMBARI-13880) DataNode Data Directories Which Contain Meta Information Tags Trigger Alerts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-13880:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12772184/AMBARI-13880.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.orm.dao.AlertDefinitionDAOTest
  
org.apache.ambari.server.controller.BackgroundCustomCommandExecutionTest
  
org.apache.ambari.server.controller.AmbariCustomCommandExecutionHelperTest
  
org.apache.ambari.server.functionaltests.server.StartStopServerTest
  
org.apache.ambari.server.controller.AmbariManagementControllerTest
  org.apache.ambari.server.orm.dao.AlertDispatchDAOTest

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

This message is automatically generated.

> DataNode Data Directories Which Contain Meta Information Tags Trigger Alerts
> 
>
> Key: AMBARI-13880
> URL: https://issues.apache.org/jira/browse/AMBARI-13880
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent, ambari-server
>Affects Versions: 2.1.2
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13880.patch
>
>
> HDFS allows the ability to tag DataNode data directories with meta 
> information:
> https://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-hdfs/ArchivalStorage.html
> Which results in paths that look like:
> [DISK]/hadoop/hdfs/data,[SSD]/hadoop/hdfs/ssd
> Many of our scripts assume that directories specified in 
> hdfs-site/dfs.datanode.data.dir are actual paths and perform operations like 
> os.path.isdir which will fail with meta data.



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

[jira] [Updated] (AMBARI-13887) SmartSense install fails as archive.zip fails to download

[Dmitry Lysnichenko (JIRA)]

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

Dmitry Lysnichenko updated AMBARI-13887:

Fix Version/s: 2.1.3

> SmartSense install fails as archive.zip fails to download
> -
>
> Key: AMBARI-13887
> URL: https://issues.apache.org/jira/browse/AMBARI-13887
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.3
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.1.3
>
> Attachments: AMBARI-13887.patch
>
>
> Try to install Smart Sense when trying to deploy HDP 2.3 and the server and 
> agent install fails
> Caught an exception while executing custom service command:  'ambari_agent.AgentException.AgentException'>: 'Script 
> /var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_agent.py
>  does not exist'; 'Script 
> /var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_agent.py
>  does not exist'
> Caught an exception while executing custom service command:  'ambari_agent.AgentException.AgentException'>: 'Script 
> /var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_server.py
>  does not exist'; 'Script 
> /var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_server.py
>  does not exist'



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

[jira] [Updated] (AMBARI-13887) SmartSense install fails as archive.zip fails to download

[Dmitry Lysnichenko (JIRA)]

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

Dmitry Lysnichenko updated AMBARI-13887:

Affects Version/s: 2.1.3

> SmartSense install fails as archive.zip fails to download
> -
>
> Key: AMBARI-13887
> URL: https://issues.apache.org/jira/browse/AMBARI-13887
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.3
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.1.3
>
> Attachments: AMBARI-13887.patch
>
>
> Try to install Smart Sense when trying to deploy HDP 2.3 and the server and 
> agent install fails
> Caught an exception while executing custom service command:  'ambari_agent.AgentException.AgentException'>: 'Script 
> /var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_agent.py
>  does not exist'; 'Script 
> /var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_agent.py
>  does not exist'
> Caught an exception while executing custom service command:  'ambari_agent.AgentException.AgentException'>: 'Script 
> /var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_server.py
>  does not exist'; 'Script 
> /var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_server.py
>  does not exist'



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

Re: Review Request 40298: SmartSense install fails as archive.zip fails to download

[Andrew Onischuk]

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

Ship it!


Ship It!

- Andrew Onischuk


On Nov. 13, 2015, 4:20 p.m., Dmitro Lisnichenko wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40298/
> ---
> 
> (Updated Nov. 13, 2015, 4:20 p.m.)
> 
> 
> Review request for Ambari, Andrew Onischuk and Sumit Mohanty.
> 
> 
> Bugs: AMBARI-13887
> https://issues.apache.org/jira/browse/AMBARI-13887
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Try to install Smart Sense when trying to deploy HDP 2.3 and the server and 
> agent install fails
> 
> Caught an exception while executing custom service command:  'ambari_agent.AgentException.AgentException'>: 'Script 
> /var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_agent.py
>  does not exist'; 'Script 
> /var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_agent.py
>  does not exist'
> 
> Caught an exception while executing custom service command:  'ambari_agent.AgentException.AgentException'>: 'Script 
> /var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_server.py
>  does not exist'; 'Script 
> /var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_server.py
>  does not exist'
> 
> server is running under user slava:
> slava23129  3.3  4.2 4768512 686808 ?  Sl   02:28  25:37 
> /usr/jdk64/jdk1.8.0_45/bin/java -server -XX:NewRatio=3 
> -XX:+UseConcMarkSweepGC -XX:-UseGCOverheadLimit 
> -XX:CMSInitiatingOccupancyFraction=60 -Dsun.zip.disableMemoryMapping=true 
> -Xms512m -Xmx2048m 
> -Djava.security.auth.login.config=/etc/ambari-server/conf/krb5JAASLogin.conf 
> -Djava.security.krb5.conf=/etc/krb5.conf 
> -Djavax.security.auth.useSubjectCredsOnly=false -Xms512m -Xmx2048m 
> -Djava.security.auth.login.config=/etc/ambari-server/conf/krb5JAASLogin.conf 
> -Djava.security.krb5.conf=/etc/krb5.conf 
> -Djavax.security.auth.useSubjectCredsOnly=false -cp 
> /etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/mysql-connector-java.jar
>  org.apache.ambari.server.controller.AmbariServer
> 
> Files generated by ambari-server script have wrong permissions:
> [root@os-r6-stest-5 tmp]# ll 
> /var/lib/ambari-server/resources/stacks/HDP/2.1/services/SMARTSENSE/package/
> total 840
> -rw-r-. 1 root  root  0 2015-11-13 02:27 abc.txt
> -rw-r-. 1 root  root 850974 2015-11-12 22:26 archive.zip
> drwxr-xr-x. 4 slava root   4096 2015-11-12 22:25 files
> drwxr-xr-x. 2 slava root   4096 2015-11-12 22:25 scripts
> 
> [root@os-r6-stest-5 tmp]# umask
> 0027
> And that's why file can not be read by server process.
> 
> 
> Diffs
> -
> 
>   ambari-server/src/main/python/ambari_server/resourceFilesKeeper.py fe80723 
> 
> Diff: https://reviews.apache.org/r/40298/diff/
> 
> 
> Testing
> ---
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Dmitro Lisnichenko
> 
>

[jira] [Commented] (AMBARI-13881) Devdeploy: YARN,Mahout service checks fail on all OSes

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13881:
-

FAILURE: Integrated in Ambari-trunk-Commit #3829 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3829/])
AMBARI-13881. Devdeploy: YARN,Mahout service checks fail on all OSes (aonishuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a05e5b6b55f400cbda163ceec385f07a4d670328])
* 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py
* 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/yarn.py
* ambari-server/src/test/python/stacks/2.0.6/YARN/test_historyserver.py


> Devdeploy: YARN,Mahout service checks fail on all OSes
> --
>
> Key: AMBARI-13881
> URL: https://issues.apache.org/jira/browse/AMBARI-13881
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.1.3
>
>
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/MAHOUT/1.0.0.2.3/package/scripts/service_check.py",
>  line 79, in 
> MahoutServiceCheck().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 218, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/MAHOUT/1.0.0.2.3/package/scripts/service_check.py",
>  line 66, in service_check
> user = params.smokeuser
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line 
> 154, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 156, in run
> self.run_action(resource, action)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 119, in run_action
> provider_action()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
>  line 238, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 70, in inner
> result = function(command, **kwargs)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 92, in checked_call
> tries=tries, try_sleep=try_sleep)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 140, in _call_wrapper
> result = _call(command, **kwargs_copy)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 291, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'mahout 
> seqdirectory --input /user/ambari-qa/mahoutsmokeinput/sample-mahout-test.txt 
> --output /user/ambari-qa/mahoutsmokeoutput/ --charset utf-8' returned 1. 
> MAHOUT_LOCAL is not set; adding HADOOP_CONF_DIR to classpath.
> Running on hadoop, using /usr/hdp/current/hadoop-client/bin/hadoop and 
> HADOOP_CONF_DIR=/usr/hdp/current/hadoop-client/conf
> MAHOUT-JOB: 
> /usr/hdp/2.3.4.0-3235/mahout/mahout-examples-0.9.0.2.3.4.0-3235-job.jar
> WARNING: Use "yarn jar" to launch YARN applications.
> 15/11/13 12:17:46 WARN driver.MahoutDriver: No seqdirectory.props found 
> on classpath, will use command-line arguments only
> 15/11/13 12:17:47 INFO common.AbstractJob: Command line arguments: 
> {--charset=[utf-8], --chunkSize=[64], --endPhase=[2147483647], 
> --fileFilterClass=[org.apache.mahout.text.PrefixAdditionFilter], 
> --input=[/user/ambari-qa/mahoutsmokeinput/sample-mahout-test.txt], 
> --keyPrefix=[], --method=[mapreduce], 
> --output=[/user/ambari-qa/mahoutsmokeoutput/], --startPhase=[0], 
> --tempDir=[temp]}
> 15/11/13 12:17:49 INFO impl.TimelineClientImpl: Timeline service address: 
> http://os-u14-fxhqus-devdeploy-1.novalocal:8188/ws/v1/timeline/
> 15/11/13 12:17:49 INFO client.RMProxy: Connecting to ResourceManager at 
> os-u14-fxhqus-devdeploy-2.novalocal/172.22.82.23:8050
> 15/11/13 12:17:49 INFO service.AbstractService: Service 
> org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl failed in state 
> STARTED; cause: java.io.IOException: /tmp/entity-file-history/active does not 
> exist
> java.io.IOException: /tmp/entity-file-history/active does not exist
>   at 
> org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl.serviceStart(TimelineClientImpl.java:366)
>   at 
> org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
>   at 
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.serviceStart(YarnClientImpl.java:194)
>   at 
> 

[jira] [Commented] (AMBARI-13877) RU/EU: host failure summary dialog usability changes

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13877:
-

FAILURE: Integrated in Ambari-trunk-Commit #3829 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3829/])
AMBARI-13877 RU/EU: host failure summary dialog usability changes. (atkach: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=18e595aeb960c4cc08bc5d55f0d8c251d894bf5f])
* ambari-web/app/templates/main/admin/stack_upgrade/failed_hosts_modal.hbs
* ambari-web/app/messages.js
* ambari-web/app/assets/test/tests.js
* ambari-web/app/templates/main/admin/stack_upgrade/stack_upgrade_wizard.hbs
* ambari-web/app/styles/stack_versions.less
* ambari-web/app/views/main/admin/stack_upgrade/failed_hosts_modal_view.js
* ambari-web/test/views/main/admin/stack_upgrade/failed_hosts_modal_view_test.js
* ambari-web/app/views.js
* ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js
* ambari-web/test/controllers/main/admin/stack_and_upgrade_controller_test.js
* ambari-web/app/views/main/admin/stack_upgrade/upgrade_wizard_view.js
* ambari-web/test/views/main/admin/stack_upgrade/upgrade_wizard_view_test.js


> RU/EU: host failure summary dialog usability changes
> 
>
> Key: AMBARI-13877
> URL: https://issues.apache.org/jira/browse/AMBARI-13877
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.1.3
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13877.patch, AMBARI-13877_branch-2.1.patch, 
> ru-failure.pptx
>
>
> In cases where hosts are skipped during upgrade (RU or EU), need to provide 
> more information to the user about the hosts and what happened.
> This attached mock provide more detail on the hosts and the component 
> failures.



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

[jira] [Commented] (AMBARI-13856) Sometimes when HA is enabled NameNode does not wait to leave safe mode on start

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13856:
-

FAILURE: Integrated in Ambari-trunk-Commit #3829 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3829/])
Revert "AMBARI-13856. Sometimes when HA is enabled NameNode does not (aonishuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=59ee076e6edba88a714343f6fccca8d46c13288b])
* 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py
* ambari-server/src/test/python/stacks/2.0.6/HDFS/test_namenode.py


> Sometimes when HA is enabled NameNode does not wait to leave safe mode on 
> start
> ---
>
> Key: AMBARI-13856
> URL: https://issues.apache.org/jira/browse/AMBARI-13856
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.1.3
>
>
> STR:  
> 1) Enable NN HA  
> 2) Run Stop All, Start All
> Active NameNode can be in the Safe Mode and start of some services (Falcon
> server) starts can fail.



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

[jira] [Updated] (AMBARI-13888) Ranger Usersync Moving From Seconds to Millis On Stack Upgrade

[Jonathan Hurley (JIRA)]

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

Jonathan Hurley updated AMBARI-13888:
-
Summary: Ranger Usersync Moving From Seconds to Millis On Stack Upgrade  
(was: Ranger Usersync Moving From Seconds to Millis On HDP Upgrade)

> Ranger Usersync Moving From Seconds to Millis On Stack Upgrade
> --
>
> Key: AMBARI-13888
> URL: https://issues.apache.org/jira/browse/AMBARI-13888
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
> Fix For: 2.1.3
>
>
> During upgrade, sync interval needs to be migrated properly.
> In HDP 2.2, ranger treats this value in minutes 
> {{usersync-properties.xml/SYNC_INTERVAL}}. In HDP 2.3, the unit changed to 
> milliseconds 
> {{ranger-ugsync-site.xml/ranger.usersync.sleeptimeinmillisbetweensynccycle}}. 
> So upgrade should handle the transformation.



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

[jira] [Commented] (AMBARI-13884) Devdeploy: Knox service check have started before the knox start action

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13884:
-

FAILURE: Integrated in Ambari-trunk-Commit #3830 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3830/])
AMBARI-13884. Devdeploy: Knox service check have started before the knox 
(aonishuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=090905be3d2706e701d6f1a3455af37cd3982953])
* ambari-server/src/main/resources/stacks/HDP/2.2/role_command_order.json


> Devdeploy: Knox service check have started before the knox start action
> ---
>
> Key: AMBARI-13884
> URL: https://issues.apache.org/jira/browse/AMBARI-13884
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.1.3
>
>
> Impact: -  
> Artifacts: [s11](http://linux-jenkins.qe.hortonworks.com/home/jenkins/qe-
> artifacts/os-u14-plytvs-devdeploy)  
> OS Type: debian7  
> Cluster: 
> Issue occurs on enabling Kerberos, during starting of all services. r6 & r7
> builds passed ok, so it's possibly a flaky issue.
> 
> 
> 
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/KNOX/0.5.0.2.2/package/scripts/service_check.py",
>  line 93, in 
> KnoxServiceCheck().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 218, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/KNOX/0.5.0.2.2/package/scripts/service_check.py",
>  line 88, in service_check
> logoutput=True
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line 
> 154, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 156, in run
> self.run_action(resource, action)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 119, in run_action
> provider_action()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
>  line 238, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 70, in inner
> result = function(command, **kwargs)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 92, in checked_call
> tries=tries, try_sleep=try_sleep)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 140, in _call_wrapper
> result = _call(command, **kwargs_copy)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 291, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of '/usr/bin/kinit 
> -kt /etc/security/keytabs/smokeuser.headless.keytab 
> smk_rndo78izjxmcqt5krlw5e88...@hwqe.hortonworks.com; /usr/bin/python2.6 
> /var/lib/ambari-agent/tmp/validateKnoxStatus.py -p 8443 -n 
> os-s11-3-ulepts-devdeploy-4.novalocal' returned 1. Connection to 
> os-s11-3-ulepts-devdeploy-4.novalocal on port 8443 failed: [Errno 111] 
> Connection refused
> 



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

[jira] [Commented] (AMBARI-13883) Upgrade: when out of sync, should default to Install Packages button

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13883:
-

FAILURE: Integrated in Ambari-trunk-Commit #3830 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3830/])
AMBARI-13883 Upgrade: when out of sync, should default to Install (atkach: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=92720011524bcad716868d865debba8540dae6ae])
* 
ambari-web/test/views/main/admin/stack_upgrade/upgrade_version_box_view_test.js
* ambari-web/app/views/main/admin/stack_upgrade/upgrade_version_box_view.js


> Upgrade: when out of sync, should default to Install Packages button
> 
>
> Key: AMBARI-13883
> URL: https://issues.apache.org/jira/browse/AMBARI-13883
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.3
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13883.patch, reinstall.tiff
>
>
> 1) Install cluster with HDP 2.3.0 + HDFS, yarn,zk
> 2) installed hdp 2.3.2
> 3) before upgrading, went to add service hive. I was then out of sync 
> (correct)
> 4) Versions shows out of sync icon (correct) but the button defaulted to 
> Perform Upgrade.
> Should have defaulted to re-install packages button.
> See attached



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

[jira] [Resolved] (AMBARI-13884) Devdeploy: Knox service check have started before the knox start action

[Andrew Onischuk (JIRA)]

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

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

Committed to trunk and branch-2.1

> Devdeploy: Knox service check have started before the knox start action
> ---
>
> Key: AMBARI-13884
> URL: https://issues.apache.org/jira/browse/AMBARI-13884
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.1.3
>
>
> Impact: -  
> Artifacts: [s11](http://linux-jenkins.qe.hortonworks.com/home/jenkins/qe-
> artifacts/os-u14-plytvs-devdeploy)  
> OS Type: debian7  
> Cluster: 
> Issue occurs on enabling Kerberos, during starting of all services. r6 & r7
> builds passed ok, so it's possibly a flaky issue.
> 
> 
> 
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/KNOX/0.5.0.2.2/package/scripts/service_check.py",
>  line 93, in 
> KnoxServiceCheck().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 218, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/KNOX/0.5.0.2.2/package/scripts/service_check.py",
>  line 88, in service_check
> logoutput=True
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line 
> 154, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 156, in run
> self.run_action(resource, action)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 119, in run_action
> provider_action()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
>  line 238, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 70, in inner
> result = function(command, **kwargs)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 92, in checked_call
> tries=tries, try_sleep=try_sleep)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 140, in _call_wrapper
> result = _call(command, **kwargs_copy)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 291, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of '/usr/bin/kinit 
> -kt /etc/security/keytabs/smokeuser.headless.keytab 
> smk_rndo78izjxmcqt5krlw5e88...@hwqe.hortonworks.com; /usr/bin/python2.6 
> /var/lib/ambari-agent/tmp/validateKnoxStatus.py -p 8443 -n 
> os-s11-3-ulepts-devdeploy-4.novalocal' returned 1. Connection to 
> os-s11-3-ulepts-devdeploy-4.novalocal on port 8443 failed: [Errno 111] 
> Connection refused
> 



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

Re: Review Request 40236: Check status of RS process for AMS in embedded mode

[Dmytro Sen]

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

(Updated Ноя. 13, 2015, 3:27 п.п.)


Review request for Ambari and Sid Wagle.


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


Repository: ambari


Description
---

TimelineMetricStoreWatcher added, it checks TimelineMetricStore functionality 
by adding and getting a fake metric to/from HBase.


Diffs (updated)
-

  
ambari-metrics/ambari-metrics-timelineservice/conf/unix/ambari-metrics-collector
 0018bc2 
  
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/ApplicationHistoryServer.java
 d79ca68 
  
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/HBaseTimelineMetricStore.java
 aed5fed 
  
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/PhoenixHBaseAccessor.java
 be06650 
  
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/TimelineMetricConfiguration.java
 fd51f3d 
  
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/TimelineMetricStoreWatcher.java
 PRE-CREATION 
  
ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/TimelineMetricStoreWatcherTest.java
 PRE-CREATION 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-site.xml
 c73a401 

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


Testing
---

Unit tests passed


Thanks,

Dmytro Sen

[jira] [Created] (AMBARI-13886) Stop-and-Start Upgrade: Fix unit tests that were ignored/missing on server

[Dmytro Grinenko (JIRA)]

Dmytro Grinenko created AMBARI-13886:


 Summary: Stop-and-Start Upgrade: Fix unit tests that were 
ignored/missing on server
 Key: AMBARI-13886
 URL: https://issues.apache.org/jira/browse/AMBARI-13886
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: trunk, 2.1.3
Reporter: Dmytro Grinenko
Priority: Critical
 Fix For: trunk, 2.1.3


Enable and fix server side unit-tests, previously disabled during feature merge.



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

[jira] [Created] (AMBARI-13889) Upgrade from 2.1.2 to 2.1.3 fails with Security enabled due to missing Accumulo configuration

[Josh Elser (JIRA)]

Josh Elser created AMBARI-13889:
---

 Summary: Upgrade from 2.1.2 to 2.1.3 fails with Security enabled 
due to missing Accumulo configuration
 Key: AMBARI-13889
 URL: https://issues.apache.org/jira/browse/AMBARI-13889
 Project: Ambari
  Issue Type: Bug
  Components: ambari-upgrade
Reporter: Josh Elser
Priority: Critical
 Fix For: 2.1.3


AMBARI-13295 fixed an issue where, with custom usernames/principals, the 
Accumulo client was using the default principal to try to authenticate with the 
Accumulo services with Kerberos enabled. This failed as the client had 
incorrect information to complete the authentication handshake.

This issue still exists in 2.1.2, however, which causes an upgrade from 2.1.2 
to 2.1.3-SNAPSHOT to fail because the incorrect configuration is never 
corrected.

[~rlevas] has kindly pointed that the UpgradeCatalog needs to be changed to 
ensure that the configuration is updated in the upgrade path out of 2.1.2.



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

Re: Review Request 40221: AMS should not assume hdfs as the protocol

[Aravindan Vijayan]

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



ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py 
(line 889)


I think there are other places in this file where the check if 
hbase_rootdir.startswith("hdfs://") is used. Dont we need to change the logic 
at those places as well?


- Aravindan Vijayan


On Nov. 12, 2015, 9:50 a.m., Dmytro Sen wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40221/
> ---
> 
> (Updated Nov. 12, 2015, 9:50 a.m.)
> 
> 
> Review request for Ambari, Sumit Mohanty and Sid Wagle.
> 
> 
> Bugs: AMBARI-13851
> https://issues.apache.org/jira/browse/AMBARI-13851
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> AMS scripts should not assume that hdfs is the protocol.
> is_hbase_distributed = hbase_root_dir.startswith('hdfs://')
> 
> or 
> 
> is_hbase_distributed = 
> security_params['hbase-site']['hbase.rootdir'].startswith('hdfs://')
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams.py
>  50e363c 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/hbase.py
>  9e6f2fa 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py
>  00e4123 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py
>  1c6a49f 
>   ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py 
> 7181122 
>   
> ambari-server/src/test/python/stacks/2.0.6/AMBARI_METRICS/test_metrics_collector.py
>  b04e1d5 
> 
> Diff: https://reviews.apache.org/r/40221/diff/
> 
> 
> Testing
> ---
> 
> --
> Ran 249 tests in 8.115s
> 
> OK
> --
> Total run:831
> Total errors:0
> Total failures:0
> OK
> 
> 
> Thanks,
> 
> Dmytro Sen
> 
>

[jira] [Commented] (AMBARI-13342) Allow access to callers with valid Knox authorization cookie

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13342:
-

FAILURE: Integrated in Ambari-trunk-Commit #3831 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3831/])
AMBARI-13342. Allow access to callers with valid Knox authorization 
(mpapyrkovskyy: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9fae285c60f48489ed6a521d3c2c5742092fda25])
* 
ambari-server/src/main/java/org/apache/ambari/server/api/AmbariErrorHandler.java
* ambari-server/src/main/python/ambari_server/setupSso.py
* ambari-server/src/main/windows/ambari-server.ps1
* ambari-server/src/main/python/ambari_server/userInput.py
* ambari-server/sbin/ambari-server


> Allow access to callers with valid Knox authorization cookie
> 
>
> Key: AMBARI-13342
> URL: https://issues.apache.org/jira/browse/AMBARI-13342
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Myroslav Papirkovskyy
>Assignee: Myroslav Papirkovskyy
>Priority: Critical
> Fix For: 2.2.0
>
>
> Implement security filter to allow authentication with valid JWT token.
> Provide info about authentication provider URL with every 403 error if 
> configured.



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

[jira] [Created] (AMBARI-13890) Configs: Values/units for HiveServer2 Heap Size overlapping on slider

[Antonenko Alexander (JIRA)]

Antonenko Alexander created AMBARI-13890:


 Summary: Configs: Values/units for HiveServer2 Heap Size 
overlapping on slider
 Key: AMBARI-13890
 URL: https://issues.apache.org/jira/browse/AMBARI-13890
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.1.2
Reporter: Antonenko Alexander
Assignee: Antonenko Alexander
Priority: Critical
 Fix For: 2.1.3


Please see the screenshot attached. At the install wizard, the values and units 
on the slider for property HiveServer2 Heap Size under Hive tab is overlapping.




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

[jira] [Created] (AMBARI-13891) Scrolls on the configs comparison

[Antonenko Alexander (JIRA)]

Antonenko Alexander created AMBARI-13891:


 Summary: Scrolls on the configs comparison
 Key: AMBARI-13891
 URL: https://issues.apache.org/jira/browse/AMBARI-13891
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.1.0
Reporter: Antonenko Alexander
Assignee: Antonenko Alexander
Priority: Critical
 Fix For: 2.2.0


See screenshot attached
Browser: Chrome Version 43.0.2357.124 m
Windows 7



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

[jira] [Updated] (AMBARI-13869) AMS validation asks to set hbase_master_xmn_size to 4123168640 MB

[Aravindan Vijayan (JIRA)]

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

Aravindan Vijayan updated AMBARI-13869:
---
Summary: AMS validation asks to set hbase_master_xmn_size to 4123168640 MB  
(was: AMS config validation issues)

> AMS validation asks to set hbase_master_xmn_size to 4123168640 MB
> -
>
> Key: AMBARI-13869
> URL: https://issues.apache.org/jira/browse/AMBARI-13869
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13869.patch
>
>
> Issue 1 : AMS validation asks to set hbase_master_xmn_size to an unreasonable 
> value of 4123168640 MB
> Issue 2 : AMS stack-advisor validates 3 configs in 1 message



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

[jira] [Commented] (AMBARI-13890) Configs: Values/units for HiveServer2 Heap Size overlapping on slider

[Aleksandr Kovalenko (JIRA)]

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

Aleksandr Kovalenko commented on AMBARI-13890:
--

+1 for the patch

> Configs: Values/units for HiveServer2 Heap Size overlapping on slider
> -
>
> Key: AMBARI-13890
> URL: https://issues.apache.org/jira/browse/AMBARI-13890
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.2
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13890.patch, Screen Shot 2015-09-22 at 2.37.52 
> PM.png, config-slider-rotate.jpg, config-slider-wrap.jpg
>
>
> Please see the screenshot attached. At the install wizard, the values and 
> units on the slider for property HiveServer2 Heap Size under Hive tab is 
> overlapping.



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

[jira] [Created] (AMBARI-13892) SLAVE component with cardinality 0+ gets auto-selected

[Antonenko Alexander (JIRA)]

Antonenko Alexander created AMBARI-13892:


 Summary: SLAVE component with cardinality 0+ gets auto-selected
 Key: AMBARI-13892
 URL: https://issues.apache.org/jira/browse/AMBARI-13892
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.1.3
Reporter: Antonenko Alexander
Assignee: Antonenko Alexander
Priority: Blocker
 Fix For: 2.1.3


An easy way to test it would be to do an Add Service of HBase and you will see 
PQS getting auto-selected 



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

Re: Review Request 40289: DataNode Data Directories Which Contain Meta Information Tags Trigger Alerts

[Vitalyi Brodetskyi]

> On Лис. 13, 2015, 6:37 після полудня, Alejandro Fernandez wrote:
> > We also need a similar check in dfs_datanode_helper.py

ok, will create jira for this.


- Vitalyi


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


On Лис. 13, 2015, 12:36 після полудня, Vitalyi Brodetskyi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40289/
> ---
> 
> (Updated Лис. 13, 2015, 12:36 після полудня)
> 
> 
> Review request for Ambari, Andrew Onischuk, Dmitro Lisnichenko, and Jonathan 
> Hurley.
> 
> 
> Bugs: AMBARI-13880
> https://issues.apache.org/jira/browse/AMBARI-13880
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> HDFS allows the ability to tag DataNode data directories with meta 
> information:
> https://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-hdfs/ArchivalStorage.html
> Which results in paths that look like:
> [DISK]/hadoop/hdfs/data,[SSD]/hadoop/hdfs/ssd
> Many of our scripts assume that directories specified in 
> hdfs-site/dfs.datanode.data.dir are actual paths and perform operations like 
> os.path.isdir which will fail with meta data.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/alerts/alert_datanode_unmounted_data_dir.py
>  f95daac 
> 
> Diff: https://reviews.apache.org/r/40289/diff/
> 
> 
> Testing
> ---
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Vitalyi Brodetskyi
> 
>

[jira] [Commented] (AMBARI-13705) Metrics Cache sizing test failing on trunk

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13705:
-

FAILURE: Integrated in Ambari-trunk-Commit #3831 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3831/])
AMBARI-13705 Metrics Cache sizing test failing on trunk (dsen) (dsen: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b6a3476c78588ba6d3841f495ca9b87dbe4418a6])
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/timeline/cache/TimelineMetricCacheSizingTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/timeline/cache/TimelineMetricsCacheSizeOfEngine.java


> Metrics Cache sizing test failing on trunk
> --
>
> Key: AMBARI-13705
> URL: https://issues.apache.org/jira/browse/AMBARI-13705
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.3
>Reporter: Siddharth Wagle
>Assignee: Aravindan Vijayan
> Fix For: 2.1.3
>
> Attachments: AMBARI-13705-trunk.patch
>
>
> org.apache.ambari.server.controller.metrics.timeline.cache.TimelineMetricCacheSizingTest#testTimelineMetricCacheSizing
>  fails on apache infra only.



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

[jira] [Updated] (AMBARI-13802) Update message content for Finalize Upgrade Pre-Check

[Xi Wang (JIRA)]

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

Xi Wang updated AMBARI-13802:
-
Attachment: AMBARI-13802-2-branch-2.1.patch

> Update message content for Finalize Upgrade Pre-Check
> -
>
> Key: AMBARI-13802
> URL: https://issues.apache.org/jira/browse/AMBARI-13802
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.1.3
>Reporter: Xi Wang
>Assignee: Xi Wang
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13802-2-branch-2.1.patch, 
> AMBARI-13802-branch-2.1.patch, AMBARI-13802-trunk.patch, new content 1.png, 
> new content 2 hosts.png, new content 2.png, new content 3.png
>
>




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

[jira] [Updated] (AMBARI-13869) AMS validation asks to set hbase_master_xmn_size to 4123168640 MB

[Aravindan Vijayan (JIRA)]

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

Aravindan Vijayan updated AMBARI-13869:
---
Description: 
Problem
AMS validation asks to set hbase_master_xmn_size to an unreasonable value of 
4123168640 MB

Bug
hbase_master_xmn_size recommended value returned in Bytes.

Fix
Change to MB.



  was:
Issue 1 : AMS validation asks to set hbase_master_xmn_size to an unreasonable 
value of 4123168640 MB

Issue 2 : AMS stack-advisor validates 3 configs in 1 message




> AMS validation asks to set hbase_master_xmn_size to 4123168640 MB
> -
>
> Key: AMBARI-13869
> URL: https://issues.apache.org/jira/browse/AMBARI-13869
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13869.patch
>
>
> Problem
> AMS validation asks to set hbase_master_xmn_size to an unreasonable value of 
> 4123168640 MB
> Bug
> hbase_master_xmn_size recommended value returned in Bytes.
> Fix
> Change to MB.



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

[jira] [Commented] (AMBARI-13882) Flume agent does not display metrics

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13882:
-

ABORTED: Integrated in Ambari-branch-2.1 #856 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/856/])
AMBARI-13882 Flume agent does not display metrics (dsen) (dsen: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e355770c22c355edc3e033e0f624d8d2a6483224])
* 
ambari-metrics/ambari-metrics-storm-sink/src/main/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsSink.java
* 
ambari-metrics/ambari-metrics-storm-sink/src/main/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsReporter.java
* 
ambari-metrics/ambari-metrics-flume-sink/src/main/java/org/apache/hadoop/metrics2/sink/flume/FlumeTimelineMetricsSink.java
* 
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/webapp/TimelineWebServices.java
* 
ambari-metrics/ambari-metrics-flume-sink/src/test/java/org/apache/hadoop/metrics2/sink/flume/FlumeTimelineMetricsSinkTest.java
* 
ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/AbstractTimelineMetricsSink.java
* 
ambari-metrics/ambari-metrics-kafka-sink/src/main/java/org/apache/hadoop/metrics2/sink/kafka/KafkaTimelineMetricsReporter.java


> Flume agent does not display metrics
> 
>
> Key: AMBARI-13882
> URL: https://issues.apache.org/jira/browse/AMBARI-13882
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.1.3
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13882.patch
>
>
> Flume,Storm,Kafka sink report short hostnames instead of fqdn in some 
> enviroments



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

[jira] [Commented] (AMBARI-13665) Enable HAWQ/PXF services in Ambari 2.1.3

[Jayush Luniya (JIRA)]

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

Jayush Luniya commented on AMBARI-13665:


[~mithmatt] [~adenisso] [~jaoki]
I see following unit test failures in ambari-web after applying the latest 
patch to 2.1 branch. Please update the patch to resolve these issues, run mvn 
clean test in branch-2.1 and paste the output to the JIRA along with the 
updated patch.

{noformat}
  ✖ 8 of 10212 tests failed:

  1) Ambari Web Unit tests test/data/HDP2.3/site_properties_test 
hdp2SiteProperties Check attributes of 
"hawq-site.xml/hawq_master_address_host". Display type value masterHost should 
be described in stack :
 AssertionError: expected 'masterHost' to match 
/undefined|supportTextConnection|radio button/
  at 
file:///Users/jluniya/release/2.1/ambari/ambari-web/node_modules/chai/chai.js:925
  at 
file:///Users/jluniya/release/2.1/ambari/ambari-web/node_modules/chai/chai.js:1896
  at 
file:///Users/jluniya/release/2.1/ambari/ambari-web/node_modules/chai/chai.js:3638
  at 
file:///Users/jluniya/release/2.1/ambari/ambari-web/public/test/javascripts/test.js:41391
  at 
file:///Users/jluniya/release/2.1/ambari/ambari-web/node_modules/mocha/mocha.js:4039
  at 
file:///Users/jluniya/release/2.1/ambari/ambari-web/node_modules/mocha/mocha.js:4404
  at 
file:///Users/jluniya/release/2.1/ambari/ambari-web/node_modules/mocha/mocha.js:4463
  at next 
(file:///Users/jluniya/release/2.1/ambari/ambari-web/node_modules/mocha/mocha.js:4330)
  at 
file:///Users/jluniya/release/2.1/ambari/ambari-web/node_modules/mocha/mocha.js:4339
  at next 
(file:///Users/jluniya/release/2.1/ambari/ambari-web/node_modules/mocha/mocha.js:4287)
  at 
file:///Users/jluniya/release/2.1/ambari/ambari-web/node_modules/mocha/mocha.js:4307
  at timeslice 
(file:///Users/jluniya/release/2.1/ambari/ambari-web/node_modules/mocha/mocha.js:5279)

  2) Ambari Web Unit tests test/data/HDP2.3/site_properties_test 
hdp2SiteProperties Check attributes of 
"hawq-site.xml/hawq_standby_address_host". Display type value masterHost should 
be described in stack :
 AssertionError: expected 'masterHost' to match 
/undefined|supportTextConnection|radio button/
  at 
file:///Users/jluniya/release/2.1/ambari/ambari-web/node_modules/chai/chai.js:925
  at 
file:///Users/jluniya/release/2.1/ambari/ambari-web/node_modules/chai/chai.js:1896
  at 
file:///Users/jluniya/release/2.1/ambari/ambari-web/node_modules/chai/chai.js:3638
  at 
file:///Users/jluniya/release/2.1/ambari/ambari-web/public/test/javascripts/test.js:41391
  at 
file:///Users/jluniya/release/2.1/ambari/ambari-web/node_modules/mocha/mocha.js:4039
  at 
file:///Users/jluniya/release/2.1/ambari/ambari-web/node_modules/mocha/mocha.js:4404
  at 
file:///Users/jluniya/release/2.1/ambari/ambari-web/node_modules/mocha/mocha.js:4463
  at next 
(file:///Users/jluniya/release/2.1/ambari/ambari-web/node_modules/mocha/mocha.js:4330)
  at 
file:///Users/jluniya/release/2.1/ambari/ambari-web/node_modules/mocha/mocha.js:4339
  at next 
(file:///Users/jluniya/release/2.1/ambari/ambari-web/node_modules/mocha/mocha.js:4287)
  at 
file:///Users/jluniya/release/2.1/ambari/ambari-web/node_modules/mocha/mocha.js:4307
  at timeslice 
(file:///Users/jluniya/release/2.1/ambari/ambari-web/node_modules/mocha/mocha.js:5279)

  3) Ambari Web Unit tests test/data/HDP2.3/site_properties_test 
hdp2SiteProperties Check attributes of 
"hawq-site.xml/hawq_master_address_port". Display type value int should be 
described in stack :
 AssertionError: expected 'int' to match 
/undefined|supportTextConnection|radio button/
  at 
file:///Users/jluniya/release/2.1/ambari/ambari-web/node_modules/chai/chai.js:925
  at 
file:///Users/jluniya/release/2.1/ambari/ambari-web/node_modules/chai/chai.js:1896
  at 
file:///Users/jluniya/release/2.1/ambari/ambari-web/node_modules/chai/chai.js:3638
  at 
file:///Users/jluniya/release/2.1/ambari/ambari-web/public/test/javascripts/test.js:41391
  at 
file:///Users/jluniya/release/2.1/ambari/ambari-web/node_modules/mocha/mocha.js:4039
  at 
file:///Users/jluniya/release/2.1/ambari/ambari-web/node_modules/mocha/mocha.js:4404
  at 
file:///Users/jluniya/release/2.1/ambari/ambari-web/node_modules/mocha/mocha.js:4463
  at next 
(file:///Users/jluniya/release/2.1/ambari/ambari-web/node_modules/mocha/mocha.js:4330)
  at 
file:///Users/jluniya/release/2.1/ambari/ambari-web/node_modules/mocha/mocha.js:4339
  at next 
(file:///Users/jluniya/release/2.1/ambari/ambari-web/node_modules/mocha/mocha.js:4287)
  at 
file:///Users/jluniya/release/2.1/ambari/ambari-web/node_modules/mocha/mocha.js:4307
  at timeslice 
(file:///Users/jluniya/release/2.1/ambari/ambari-web/node_modules/mocha/mocha.js:5279)

  4) Ambari Web Unit 

[jira] [Commented] (AMBARI-13767) LDAP - Group Membership not pulled in with FreeIPA/RHELIDM

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-13767:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12772183/AMBARI-13767_v4.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:red}-1 core tests{color}.  The patch failed these unit tests in 
ambari-server:

  org.apache.ambari.server.orm.dao.AlertDefinitionDAOTest
  
org.apache.ambari.server.controller.BackgroundCustomCommandExecutionTest
  
org.apache.ambari.server.controller.AmbariCustomCommandExecutionHelperTest
  
org.apache.ambari.server.functionaltests.server.StartStopServerTest
  
org.apache.ambari.server.controller.AmbariManagementControllerTest
  org.apache.ambari.server.orm.dao.AlertDispatchDAOTest

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

This message is automatically generated.

> LDAP - Group Membership not pulled in with FreeIPA/RHELIDM
> --
>
> Key: AMBARI-13767
> URL: https://issues.apache.org/jira/browse/AMBARI-13767
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.2
> Environment: All OS
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13767_v4.patch
>
>
> When troubleshooting why the group members are not being sync'd with FreeIPA, 
> a packet trace helped identify the issue.  With ActiveDirectory the user's DN 
> is exposed as an attribute: "distinguishedName", this is not the case 
> inFreeIPA/RHEL IDM (using 389 DS for the directory server implementation).  
> The DN is not an attribute on the user, and cannot be used in a filter like 
> this:
> {noformat}
> (&(objectClass=posixaccount)(|(dn=uid=dstreev,cn=users,cn=accounts,dc=hdp,dc=local)(uid=uid=dstreev,cn=users,cn=accounts,dc=hdp,dc=local)))
> {noformat}



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

[jira] [Updated] (AMBARI-13891) Scrolls on the configs comparison

[Antonenko Alexander (JIRA)]

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

Antonenko Alexander updated AMBARI-13891:
-
Attachment: scrolls.png

> Scrolls on the configs comparison
> -
>
> Key: AMBARI-13891
> URL: https://issues.apache.org/jira/browse/AMBARI-13891
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.2.0
>
> Attachments: scrolls.png
>
>
> See screenshot attached
> Browser: Chrome Version 43.0.2357.124 m
> Windows 7



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

[jira] [Updated] (AMBARI-13890) Configs: Values/units for HiveServer2 Heap Size overlapping on slider

[Antonenko Alexander (JIRA)]

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

Antonenko Alexander updated AMBARI-13890:
-
Attachment: AMBARI-13890.patch

> Configs: Values/units for HiveServer2 Heap Size overlapping on slider
> -
>
> Key: AMBARI-13890
> URL: https://issues.apache.org/jira/browse/AMBARI-13890
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.2
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13890.patch, Screen Shot 2015-09-22 at 2.37.52 
> PM.png, config-slider-rotate.jpg, config-slider-wrap.jpg
>
>
> Please see the screenshot attached. At the install wizard, the values and 
> units on the slider for property HiveServer2 Heap Size under Hive tab is 
> overlapping.



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

[jira] [Updated] (AMBARI-13891) Scrolls on the configs comparison

[Antonenko Alexander (JIRA)]

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

Antonenko Alexander updated AMBARI-13891:
-
Attachment: AMBARI-13891.patch

> Scrolls on the configs comparison
> -
>
> Key: AMBARI-13891
> URL: https://issues.apache.org/jira/browse/AMBARI-13891
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.2.0
>
> Attachments: AMBARI-13891.patch, scrolls.png
>
>
> See screenshot attached
> Browser: Chrome Version 43.0.2357.124 m
> Windows 7



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

Re: Review Request 38748: AMBARI-11967: Oozie db password appears in clear text in client config downloaded from Ambari UI

[Andrew Onischuk]

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

Ship it!


Ship It!

- Andrew Onischuk


On Sept. 27, 2015, 6:08 p.m., Sangeeta Ravindran wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/38748/
> ---
> 
> (Updated Sept. 27, 2015, 6:08 p.m.)
> 
> 
> Review request for Ambari and Andrew Onischuk.
> 
> 
> Bugs: AMBARI-11967
> https://issues.apache.org/jira/browse/AMBARI-11967
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> When Oozie Client Configs are downloaded from the Ambari UI, the 
> oozie-site.xml included in the tar.gz file contains the value of the 
> oozie.service.JPAService.jdbc.password field.
> 
> The password should not be included in the downloaded client config file.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClientConfigResourceProvider.java
>  dea0362 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/ConfigHelper.java 
> 62c3b61 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClientConfigResourceProviderTest.java
>  7643abb 
> 
> Diff: https://reviews.apache.org/r/38748/diff/
> 
> 
> Testing
> ---
> 
> Manual testing. Updated JUnit test case. Ran mvn clean test.
> 
> 
> Thanks,
> 
> Sangeeta Ravindran
> 
>

[jira] [Commented] (AMBARI-13880) DataNode Data Directories Which Contain Meta Information Tags Trigger Alerts

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13880:
-

ABORTED: Integrated in Ambari-branch-2.1 #856 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/856/])
AMBARI-13880. DataNode Data Directories Which Contain Meta Information 
(vbrodetskyi: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7084e4bbcefc05451cc907ae2caaa70515ccd46a])
* 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/alerts/alert_datanode_unmounted_data_dir.py


> DataNode Data Directories Which Contain Meta Information Tags Trigger Alerts
> 
>
> Key: AMBARI-13880
> URL: https://issues.apache.org/jira/browse/AMBARI-13880
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent, ambari-server
>Affects Versions: 2.1.2
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13880.patch
>
>
> HDFS allows the ability to tag DataNode data directories with meta 
> information:
> https://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-hdfs/ArchivalStorage.html
> Which results in paths that look like:
> [DISK]/hadoop/hdfs/data,[SSD]/hadoop/hdfs/ssd
> Many of our scripts assume that directories specified in 
> hdfs-site/dfs.datanode.data.dir are actual paths and perform operations like 
> os.path.isdir which will fail with meta data.



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

[jira] [Commented] (AMBARI-13872) Rolling Upgrade: Configuration Groups not applied for upgrades across stack versions

[Jayush Luniya (JIRA)]

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

Jayush Luniya commented on AMBARI-13872:


No new test cases required. Failures are not related to this change.


Trunk:
commit 3a84d5f4a87b8de68685fdfde242e782c9e1e07f
Author: Jayush Luniya 
Date:   Fri Nov 13 11:23:15 2015 -0800

AMBARI-13872: Rolling Upgrade: Configuration Groups not applied for 
upgrades across stack versions (jluniya)

Branch-2.1:
commit a4bab22df39f4d790d955055a08c9fe72082ca71
Author: Jayush Luniya 
Date:   Fri Nov 13 11:23:15 2015 -0800

AMBARI-13872: Rolling Upgrade: Configuration Groups not applied for 
upgrades across stack versions (jluniya)



> Rolling Upgrade: Configuration Groups not applied for upgrades across stack 
> versions
> 
>
> Key: AMBARI-13872
> URL: https://issues.apache.org/jira/browse/AMBARI-13872
> Project: Ambari
>  Issue Type: Bug
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Attachments: AMBARI-13872.patch
>
>
> 1. RU is underway
> 2. Datanodes are upgraded.
> 3 When DN is started, it comes online with default config group , thereby 
> losing its other data mount points.



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

[jira] [Reopened] (AMBARI-13824) Stop-and-Start Upgrade: Fix for Oozie Express upgrade issues from HDP 2.1 to 2.3

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez reopened AMBARI-13824:
--

Reverted

> Stop-and-Start Upgrade: Fix for Oozie Express upgrade issues from HDP 2.1 to 
> 2.3
> 
>
> Key: AMBARI-13824
> URL: https://issues.apache.org/jira/browse/AMBARI-13824
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0, 2.1.3
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.2.0, 2.1.3
>
> Attachments: AMBARI-13824.additional-fix.patch, AMBARI-13824.patch
>
>
> Problem : Unable to start Ozzie server while on upgrade from HDP 2.1 -> 2.3.
> Reason :  As 2.3 has symlinks instead of directory structure for 
> "/etc/oozie/conf" and "usr/hdp/current/oozie-*/conf". 
> * -> "server" or "client"
> The symlinks are not properly set for Ozzie Server and client after the 
> upgrade. 
> Resolution : Added a new class and comamnd "CONFIGURE_FUNCTION" to get the 
> sym links working.
> After the upgrade, the symlinks are :
> 
> /etc/oozie/conf -> /etc/oozie/2.3.4.0-3204/0
> /usr/hdp/current/oozie-server/conf -> /etc/oozie/2.3.4.0-3204/0
> 
> P.S. The changes are generic in "conf_select" for setting the sym links. 
> Thus, other services also should be having their symlinks working in 2.1->2.3 
> upgrade path.



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

Re: Review Request 40080: AMBARI-13748: Being able to clean repository cache before installing open source components

[Di Li]

> On Nov. 13, 2015, 6:40 p.m., Alejandro Fernandez wrote:
> > ambari-server/src/main/resources/custom_actions/scripts/clear_repocache.py, 
> > line 22
> > 
> >
> > Let's avoid import * since it's been known to cause issues.

hello Alejandro,

I just updated the python script to have explicit imports. 

Thanks.


- Di


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


On Nov. 13, 2015, 1:56 p.m., Di Li wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40080/
> ---
> 
> (Updated Nov. 13, 2015, 1:56 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Andrew Onischuk, Jayush 
> Luniya, and Sid Wagle.
> 
> 
> Bugs: AMBARI-13748
> https://issues.apache.org/jira/browse/AMBARI-13748
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Need a way for Ambari to trigger a repository clean (yum clean expire-cache 
> on rhel, for example) when updating repository files during an Ambari update 
> as well as fresh installation of a cluster.
> 
> Currently, this must be done occasionally through a manual step, and if not 
> done will lead to problems during install.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/custom_action_definitions/system_action_definitions.xml
>  e725d68 
>   ambari-server/src/main/resources/custom_actions/scripts/clear_repocache.py 
> PRE-CREATION 
>   ambari-server/src/test/python/custom_actions/TestClearRepoCache.py 
> PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/40080/diff/
> 
> 
> Testing
> ---
> 
> New unit test. Patch cluster with the changes and run fresh install and 
> rolling upgrade to verify the repo clean up logic was run.
> 
> New unit test for custom action code change. Also test the custom action by 
> REST API call
> 
> 
> curl -u admin:admin -H "X-Requested-By: admin" -X POST 
> -d'{"RequestInfo":{"context":"clear repo cache test", "action" : 
> "clear_repocache"}, 
> "Requests/resource_filters":[{"hosts":"agent.mydomain.com"}]}' 
> http://server.mydomain.com:8080/api/v1/clusters/bi/requests
> 
> 
> Thanks,
> 
> Di Li
> 
>

[jira] [Updated] (AMBARI-13890) Configs: Values/units for HiveServer2 Heap Size overlapping on slider

[Antonenko Alexander (JIRA)]

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

Antonenko Alexander updated AMBARI-13890:
-
Attachment: config-slider-rotate.jpg
config-slider-wrap.jpg
Screen Shot 2015-09-22 at 2.37.52 PM.png

> Configs: Values/units for HiveServer2 Heap Size overlapping on slider
> -
>
> Key: AMBARI-13890
> URL: https://issues.apache.org/jira/browse/AMBARI-13890
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.2
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: Screen Shot 2015-09-22 at 2.37.52 PM.png, 
> config-slider-rotate.jpg, config-slider-wrap.jpg
>
>
> Please see the screenshot attached. At the install wizard, the values and 
> units on the slider for property HiveServer2 Heap Size under Hive tab is 
> overlapping.



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

Re: Review Request 38748: AMBARI-11967: Oozie db password appears in clear text in client config downloaded from Ambari UI

[Sangeeta Ravindran]

> On Sept. 29, 2015, 7:42 a.m., Andrew Onischuk wrote:
> > The code LGTM. The only thing I want to ask is are you sure that oozie 
> > client works fine without password in configurations? Can you give some 
> > references or results of what you want tried?
> 
> Sangeeta Ravindran wrote:
> Hi Andrew,
> 
> Sorry for not getting back to you earlier. The Oozie client will work 
> fine without db password as it depends mainly on RESTful APIs. Testcase 
> org.apache.ooze.client.TestOozieCLI.
> 
> Thanks,
> Sangeeta

Hi Andrew, Yusaku,

Can you please let me know if any further changes are needed in this jira?

Thanks,
Sangeeta


- Sangeeta


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


On Sept. 27, 2015, 6:08 p.m., Sangeeta Ravindran wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/38748/
> ---
> 
> (Updated Sept. 27, 2015, 6:08 p.m.)
> 
> 
> Review request for Ambari and Andrew Onischuk.
> 
> 
> Bugs: AMBARI-11967
> https://issues.apache.org/jira/browse/AMBARI-11967
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> When Oozie Client Configs are downloaded from the Ambari UI, the 
> oozie-site.xml included in the tar.gz file contains the value of the 
> oozie.service.JPAService.jdbc.password field.
> 
> The password should not be included in the downloaded client config file.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClientConfigResourceProvider.java
>  dea0362 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/ConfigHelper.java 
> 62c3b61 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClientConfigResourceProviderTest.java
>  7643abb 
> 
> Diff: https://reviews.apache.org/r/38748/diff/
> 
> 
> Testing
> ---
> 
> Manual testing. Updated JUnit test case. Ran mvn clean test.
> 
> 
> Thanks,
> 
> Sangeeta Ravindran
> 
>

Review Request 40303: AMBARI-13869 AMS validation asks to set hbase_master_xmn_size to 4123168640 MB

[Aravindan Vijayan]

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

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


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


Repository: ambari


Description
---

Problem
AMS validation asks to set hbase_master_xmn_size to an unreasonable value of 
4123168640 MB

Bug
hbase_master_xmn_size recommended value returned in Bytes.

Fix
Change to MB.


Diffs
-

  ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py 
878b2cd 

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


Testing
---

Tested against a big cluster to trigger the recommendation message.


Thanks,

Aravindan Vijayan

[jira] [Updated] (AMBARI-13892) SLAVE component with cardinality 0+ gets auto-selected

[Antonenko Alexander (JIRA)]

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

Antonenko Alexander updated AMBARI-13892:
-
Attachment: AMBARI-13892.patch

> SLAVE component with cardinality 0+ gets auto-selected
> --
>
> Key: AMBARI-13892
> URL: https://issues.apache.org/jira/browse/AMBARI-13892
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.3
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Blocker
> Fix For: 2.1.3
>
> Attachments: AMBARI-13892.patch
>
>
> An easy way to test it would be to do an Add Service of HBase and you will 
> see PQS getting auto-selected 



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

[jira] [Updated] (AMBARI-13889) Upgrade from 2.1.2 to 2.1.3 fails with Security enabled due to missing Accumulo configuration

[Josh Elser (JIRA)]

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

Josh Elser updated AMBARI-13889:

Attachment: AMBARI-13889.001.patch

[~rlevas], any chance you could take a look at this? I haven't run a full suite 
of tests, but UpgradeCatalog213Test is passing with the new addition.

> Upgrade from 2.1.2 to 2.1.3 fails with Security enabled due to missing 
> Accumulo configuration
> -
>
> Key: AMBARI-13889
> URL: https://issues.apache.org/jira/browse/AMBARI-13889
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-upgrade
>Reporter: Josh Elser
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13889.001.patch
>
>
> AMBARI-13295 fixed an issue where, with custom usernames/principals, the 
> Accumulo client was using the default principal to try to authenticate with 
> the Accumulo services with Kerberos enabled. This failed as the client had 
> incorrect information to complete the authentication handshake.
> This issue still exists in 2.1.2, however, which causes an upgrade from 2.1.2 
> to 2.1.3-SNAPSHOT to fail because the incorrect configuration is never 
> corrected.
> [~rlevas] has kindly pointed that the UpgradeCatalog needs to be changed to 
> ensure that the configuration is updated in the upgrade path out of 2.1.2.



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

Re: Review Request 40080: AMBARI-13748: Being able to clean repository cache before installing open source components

[Alejandro Fernandez]

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

Ship it!



ambari-server/src/main/resources/custom_actions/scripts/clear_repocache.py 
(line 22)


Let's avoid import * since it's been known to cause issues.


- Alejandro Fernandez


On Nov. 13, 2015, 1:56 p.m., Di Li wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40080/
> ---
> 
> (Updated Nov. 13, 2015, 1:56 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Andrew Onischuk, Jayush 
> Luniya, and Sid Wagle.
> 
> 
> Bugs: AMBARI-13748
> https://issues.apache.org/jira/browse/AMBARI-13748
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Need a way for Ambari to trigger a repository clean (yum clean expire-cache 
> on rhel, for example) when updating repository files during an Ambari update 
> as well as fresh installation of a cluster.
> 
> Currently, this must be done occasionally through a manual step, and if not 
> done will lead to problems during install.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/custom_action_definitions/system_action_definitions.xml
>  e725d68 
>   ambari-server/src/main/resources/custom_actions/scripts/clear_repocache.py 
> PRE-CREATION 
>   ambari-server/src/test/python/custom_actions/TestClearRepoCache.py 
> PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/40080/diff/
> 
> 
> Testing
> ---
> 
> New unit test. Patch cluster with the changes and run fresh install and 
> rolling upgrade to verify the repo clean up logic was run.
> 
> New unit test for custom action code change. Also test the custom action by 
> REST API call
> 
> 
> curl -u admin:admin -H "X-Requested-By: admin" -X POST 
> -d'{"RequestInfo":{"context":"clear repo cache test", "action" : 
> "clear_repocache"}, 
> "Requests/resource_filters":[{"hosts":"agent.mydomain.com"}]}' 
> http://server.mydomain.com:8080/api/v1/clusters/bi/requests
> 
> 
> Thanks,
> 
> Di Li
> 
>