[jira] [Created] (AMBARI-13730) Express Upgrade: Add max degree of parallelism to control number of tasks run in parallel

[Jayush Luniya (JIRA)]

Jayush Luniya created AMBARI-13730:
--

 Summary: Express Upgrade: Add max degree of parallelism to control 
number of tasks run in parallel
 Key: AMBARI-13730
 URL: https://issues.apache.org/jira/browse/AMBARI-13730
 Project: Ambari
  Issue Type: Task
  Components: ambari-server
Affects Versions: 2.2.0, 2.1.3
Reporter: Jayush Luniya
Assignee: Jayush Luniya
Priority: Critical
 Fix For: 2.1.3






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

Re: Review Request 39955: AMBARI-13723. Express Upgrade: HDP 2.1->2.3 must uninstall 2.1 bits before starting on 2.3

[Dmitro Lisnichenko]

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

Ship it!


Ship It!

- Dmitro Lisnichenko


On Nov. 5, 2015, 1:25 a.m., Alejandro Fernandez wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39955/
> ---
> 
> (Updated Nov. 5, 2015, 1:25 a.m.)
> 
> 
> Review request for Ambari, Dmytro Grinenko, Dmitro Lisnichenko, Jayush 
> Luniya, Nate Cole, and Swapan Shridhar.
> 
> 
> Bugs: AMBARI-13723
> https://issues.apache.org/jira/browse/AMBARI-13723
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> We found a major flaw in the Express Upgrade from 2.1->2.3. Basically, 
> "hadoop" bin still points to the old binary because we had to install HDP 2.3 
> while 2.1 bits still existed.
> 
> **Manual Upgrade Instructions:**
> 
> * Stop all services using 2.1
> * yum erase hadoop hdfs hive … (this will remove scripts /usr/bin/hadoop, 
> /usr/bin/hdfs, /usr/bin/hive, etc/)
> * yum install hadoop_2_3_* hdfs_2_3_* hive_2_3_* (rpm should point 
> /usr/bin/hadoop -> /usr/hdp/current/hadoop-client/bin/hadoop)
> * Change the version to 2.3 (hdp-select, conf-select, etc.)
> * Start all services, and hence MR Service Check passes with "hadoop" command
> 
> **Express Upgrade:**
> 
> * Install HDP 2.3 bits. We reused the RU framework that relies on a 2 step 
> process: install bits, perform upgrade. Hence, /usr/bin/hadoop is still using 
> 2.1 bits
> * Stop all services using 2.1
> * Change the version to 2.3 (hdp-select, conf-select, etc.)
> * Start all services, will fail on MR Service Check because ExecuteHadoop() 
> resource calls "hadoop" command, which is still pointing to 2.1 bits!
> 
> One solution is for the orchestration to remove the 2.1 bits before starting 
> using 2.3.
> Uninstalling the 2.1 bits will remove /usr/bin/hadoop, but when we call 
> "hdp-select set hadoop-client " it will create the symlink 
> /usr/bin/hadoop -> /usr/hdp/current/hadoop-client/bin/hadoop
> 
> 
> Diffs
> -
> 
>   ambari-server/src/main/resources/custom_actions/scripts/remove_bits.py 
> PRE-CREATION 
>   
> ambari-server/src/main/resources/stacks/HDP/2.1/upgrades/nonrolling-upgrade-2.3.xml
>  91d4f64 
> 
> Diff: https://reviews.apache.org/r/39955/diff/
> 
> 
> Testing
> ---
> 
> Verified during Express Upgrade from HDP 2.1->2.3
> 
> 
> Thanks,
> 
> Alejandro Fernandez
> 
>

[jira] [Updated] (AMBARI-13740) Corrupt 'spark-log4j-properties' for Spark service

[Drazen Zubovic (JIRA)]

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

Drazen Zubovic updated AMBARI-13740:

Description: 
It seems like the 'spark-log4j-properties' configuration passed from Ambari | 
Services | Spark | Configs is getting corrupt and reformatted into one line 
without LF. The log4j config file is getting compressed into a field, with all 
LF characters dropped out. This configuration apparently cannot be changed into 
normal/standard multi line configuration that would be meaningful to Spark. 
This way it seems like the whole log4j configuration is being ignored 
completely. If not due to the syntactical sanity, then at least due to the 
first character is '#', which applies to the whole line. The default Spark 
loglevel is set to INFO, so consequently console prints whole number of INFO 
messages for each statement passed to the console. Consequently further, the 
loglevel cannot be changed to WARN or ERROR and INFO lines cannot be suppressed 
from the console.  

--> The log4j.properties.template configuration looks like this: 

# Set everything to be logged to the console
log4j.rootCategory=INFO, console
log4j.appender.console=org.apache.log4j.ConsoleAppender
log4j.appender.console.target=System.err
log4j.appender.console.layout=org.apache.log4j.PatternLayout
log4j.appender.console.layout.ConversionPattern=%d{yy/MM/dd HH:mm:ss} %p %c{1}: 
%m%n

# Settings to quiet third party logs that are too verbose
log4j.logger.org.eclipse.jetty=WARN
log4j.logger.org.eclipse.jetty.util.component.AbstractLifeCycle=ERROR
log4j.logger.org.apache.spark.repl.SparkIMain$exprTyper=INFO
log4j.logger.org.apache.spark.repl.SparkILoop$SparkILoopInterpreter=INFO

--> The log4j.properties configuration looks like this: 

# Set everything to be logged to the consolelog4j.rootCategory=WARN, 
consolelog4j.appender.console=org.apache.log4j.ConsoleAppenderlog4j.appender.console.target=System.errlog4j.appender.console.layout=org.apache.log4j.PatternLayoutlog4j.appender.console.layout.ConversionPattern=%d{yy/MM/dd
 HH:mm:ss} %p %c{1}: %m%n# Settings to quiet third party logs that are too 
verboselog4j.logger.org.eclipse.jetty=WARNlog4j.logger.org.eclipse.jetty.util.component.AbstractLifeCycle=ERRORlog4j.logger.org.apache.spark.repl.SparkIMain$exprTyper=INFOlog4j.logger.org.apache.spark.repl.SparkILoop$SparkILoopInterpreter=INFO


--> This issue leads to the ### INFO messages that log4j prints in Spark 
console, without possibility to change the loglevel:

[root@sandbox ~]# spark-shell --master yarn-client --driver-memory 512m 
--executor-memory 512m
log4j:WARN No appenders could be found for logger 
(org.apache.hadoop.metrics2.lib.MutableMetricsFactory).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
info.
Using Spark's default log4j profile: org/apache/spark/log4j-defaults.properties
15/11/05 12:34:41 INFO SecurityManager: Changing view acls to: root
15/11/05 12:34:41 INFO SecurityManager: Changing modify acls to: root
15/11/05 12:34:41 INFO SecurityManager: SecurityManager: authentication 
disabled; ui acls disabled; users with view permissions: Set(root); users with 
modify permissions: Set(root)
15/11/05 12:34:41 INFO HttpServer: Starting HTTP Server
15/11/05 12:34:41 INFO Server: jetty-8.y.z-SNAPSHOT
15/11/05 12:34:41 INFO AbstractConnector: Started SocketConnector@0.0.0.0:54564
15/11/05 12:34:41 INFO Utils: Successfully started service 'HTTP class server' 
on port 54564.
Welcome to
    __
 / __/__  ___ _/ /__
_\ \/ _ \/ _ `/ __/  '_/
   /___/ .__/\_,_/_/ /_/\_\   version 1.3.1
  /_/

Using Scala version 2.10.4 (OpenJDK 64-Bit Server VM, Java 1.7.0_85)
Type in expressions to have them evaluated.
Type :help for more information.
15/11/05 12:34:44 INFO SparkContext: Running Spark version 1.3.1
15/11/05 12:34:44 INFO SecurityManager: Changing view acls to: root
15/11/05 12:34:44 INFO SecurityManager: Changing modify acls to: root
15/11/05 12:34:44 INFO SecurityManager: SecurityManager: authentication 
disabled; ui acls disabled; users with view permissions: Set(root); users with 
modify permissions: Set(root)
15/11/05 12:34:44 INFO Slf4jLogger: Slf4jLogger started
15/11/05 12:34:44 INFO Remoting: Starting remoting
15/11/05 12:34:44 INFO Remoting: Remoting started; listening on addresses 
:[akka.tcp://sparkdri...@sandbox.hortonworks.com:35020]
15/11/05 12:34:44 INFO Utils: Successfully started service 'sparkDriver' on 
port 35020.
15/11/05 12:34:44 INFO SparkEnv: Registering MapOutputTracker
15/11/05 12:34:44 INFO SparkEnv: Registering BlockManagerMaster
15/11/05 12:34:44 INFO DiskBlockManager: Created local directory at 
/tmp/spark-3b14e9fc-73b1-45e7-96f3-f0ee48f3a238/blockmgr-ffd0619a-5fbc-4ccc-bcef-ce8560e03cd7
15/11/05 12:34:44 INFO MemoryStore: MemoryStore started with capacity 265.4 MB

[jira] [Updated] (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:all-tabpanel
 ]

Canan Girgin updated AMBARI-13738:
--
Attachment: AMBARI-13738.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)

Review Request 39971: Checking the vm.swappiness Kernel Parameter

[Canan Girgin]

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

Review request for Ambari, Aleksandr Kovalenko, Andrew Onischuk, and Dmitro 
Lisnichenko.


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


Repository: ambari


Description
---

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 .


Diffs
-

  ambari-agent/src/main/python/ambari_agent/HostInfo.py 9460256 
  ambari-agent/src/test/python/ambari_agent/TestHostInfo.py 4a1f5f4 
  ambari-server/src/main/java/org/apache/ambari/server/agent/AgentEnv.java 
ede3965 
  ambari-server/src/main/resources/custom_actions/scripts/check_host.py 8b49725 
  
ambari-server/src/test/java/org/apache/ambari/server/agent/AgentResourceTest.java
 273158f 
  ambari-server/src/test/python/custom_actions/TestCheckHost.py 1e45927 
  ambari-server/src/test/python/stacks/2.1/common/hosts.json b8f8610 
  ambari-server/src/test/python/stacks/2.2/common/2/hosts.json a549312 
  ambari-web/app/controllers/wizard/step3_controller.js cf1f1ae 
  ambari-web/app/messages.js 377ed7d 
  ambari-web/app/views/wizard/step3/hostWarningPopupBody_view.js 9c6454e 
  ambari-web/app/views/wizard/step3_view.js 6ecfb41 

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


Testing
---


Thanks,

Canan Girgin

[jira] [Updated] (AMBARI-13739) RESTART ZOOKEEPER_SERVER failed after Upgrade from 1.6.1 to 2.1.3

[Vitaly Brodetskyi (JIRA)]

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

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

> RESTART ZOOKEEPER_SERVER failed after Upgrade from 1.6.1 to 2.1.3
> -
>
> Key: AMBARI-13739
> URL: https://issues.apache.org/jira/browse/AMBARI-13739
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.3
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.1.3
>
> Attachments: AMBARI-13739.patch
>
>
> STR:
> 1)Deploy old version 1.6.1
> 2)Enable/Disable security (MIT)
> 3)Make Ambari only upgrade to 2.1.3
> Actual results:
> RESTART ZOOKEEPER_SERVER failed after Upgrade from 1.6.1 to 2.1.3
> {code}
>   {
>   "href" : 
> "http://172.22.87.177:8080/api/v1/clusters/cl1/requests/11/tasks/501;,
>   "Tasks" : {
> "attempt_cnt" : 1,
> "cluster_name" : "cl1",
> "command" : "CUSTOM_COMMAND",
> "command_detail" : "RESTART ZOOKEEPER/ZOOKEEPER_SERVER",
> "custom_command_name" : "RESTART",
> "end_time" : 1446626534832,
> "error_log" : "/var/lib/ambari-agent/data/errors-501.txt",
> "exit_code" : 1,
> "host_name" : "amb-upg161-rhel6mysql1446600673-3.novalocal",
> "id" : 501,
> "output_log" : "/var/lib/ambari-agent/data/output-501.txt",
> "request_id" : 11,
> "role" : "ZOOKEEPER_SERVER",
> "stage_id" : 0,
> "start_time" : 1446626531540,
> "status" : "FAILED",
> "stderr" : "Traceback (most recent call last):\n  File 
> \"/var/lib/ambari-agent/cache/common-services/ZOOKEEPER/3.4.5.2.0/package/scripts/zookeeper_server.py\",
>  line 179, in \nZookeeperServer().execute()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
>  line 218, in execute\nmethod(env)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
>  line 486, in restart\nself.stop(env, upgrade_type=upgrade_type)\n  File 
> \"/var/lib/ambari-agent/cache/common-services/ZOOKEEPER/3.4.5.2.0/package/scripts/zookeeper_server.py\",
>  line 60, in stop\nzookeeper_service(action='stop', 
> upgrade_type=upgrade_type)\n  File 
> \"/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py\", line 
> 89, in thunk\nreturn fn(*args, **kwargs)\n  File 
> \"/var/lib/ambari-agent/cache/common-services/ZOOKEEPER/3.4.5.2.0/package/scripts/zookeeper_service.py\",
>  line 36, in zookeeper_service\nhdp_select.select(\"zookeeper-server\", 
> params.version)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/hdp_select.py\",
>  line 116, in select\nExecute(command, sudo=True)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line 
> 154, in __init__\nself.env.run()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", 
> line 156, in run\nself.run_action(resource, action)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", 
> line 119, in run_action\nprovider_action()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
>  line 238, in action_run\ntries=self.resource.tries, 
> try_sleep=self.resource.try_sleep)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 70, in inner\nresult = function(command, **kwargs)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 92, in checked_call\ntries=tries, try_sleep=try_sleep)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 140, in _call_wrapper\nresult = _call(command, **kwargs_copy)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 291, in _call\nraise 
> Fail(err_msg)\nresource_management.core.exceptions.Fail: Execution of 
> 'hdp-select set zookeeper-server 2.1.0.0-0001' returned 127. 
> /var/lib/ambari-agent/ambari-sudo.sh: line 50: hdp-select: command not found",
> "stdout" : "2015-11-04 08:42:14,133 - Group['hadoop'] {}\n2015-11-04 
> 08:42:14,135 - Group['nobody'] {}\n2015-11-04 08:42:14,135 - Group['users'] 
> {}\n2015-11-04 08:42:14,135 - User['hive'] {'gid': 'hadoop', 'groups': 
> ['hadoop']}\n2015-11-04 08:42:14,137 - User['oozie'] {'gid': 'hadoop', 
> 'groups': ['users']}\n2015-11-04 08:42:14,138 - User['nobody'] {'gid': 
> 'hadoop', 'groups': ['nobody']}\n2015-11-04 08:42:14,139 - User['ambari-qa'] 
> {'gid': 'hadoop', 'groups': ['users']}\n2015-11-04 08:42:14,140 - 
> User['hdfs'] {'gid': 'hadoop', 'groups': ['hadoop']}\n2015-11-04 08:42:14,142 
> - User['storm'] {'gid': 

[jira] [Created] (AMBARI-13740) Corrupt 'spark-log4j-properties' for Spark service

[Drazen Zubovic (JIRA)]

Drazen Zubovic created AMBARI-13740:
---

 Summary: Corrupt 'spark-log4j-properties' for Spark service
 Key: AMBARI-13740
 URL: https://issues.apache.org/jira/browse/AMBARI-13740
 Project: Ambari
  Issue Type: Bug
  Components: ambari-admin, ambari-client
Affects Versions: 2.1.0
 Environment: Hortonworks sandbox 2.3.1; HDP-2.3.0.0-2557
Reporter: Drazen Zubovic
Priority: Minor


It seems like spark-log4j-properties is getting corrupt and reformatted into 
one line without LF. Like the log4j config is field with LF chars masked out. 
The configuration cannot be changed into multi line configuration meaningful to 
Spark. Consequently console prints INFO messages for each statement. 

The log4j.properties.template configuration looks like this: 

# Set everything to be logged to the console
log4j.rootCategory=INFO, console
log4j.appender.console=org.apache.log4j.ConsoleAppender
log4j.appender.console.target=System.err
log4j.appender.console.layout=org.apache.log4j.PatternLayout
log4j.appender.console.layout.ConversionPattern=%d{yy/MM/dd HH:mm:ss} %p %c{1}: 
%m%n

# Settings to quiet third party logs that are too verbose
log4j.logger.org.eclipse.jetty=WARN
log4j.logger.org.eclipse.jetty.util.component.AbstractLifeCycle=ERROR
log4j.logger.org.apache.spark.repl.SparkIMain$exprTyper=INFO
log4j.logger.org.apache.spark.repl.SparkILoop$SparkILoopInterpreter=INFO

The log4j.properties configuration looks like this: 

# Set everything to be logged to the consolelog4j.rootCategory=WARN, 
consolelog4j.appender.console=org.apache.log4j.ConsoleAppenderlog4j.appender.console.target=System.errlog4j.appender.console.layout=org.apache.log4j.PatternLayoutlog4j.appender.console.layout.ConversionPattern=%d{yy/MM/dd
 HH:mm:ss} %p %c{1}: %m%n# Settings to quiet third party logs that are too 
verboselog4j.logger.org.eclipse.jetty=WARNlog4j.logger.org.eclipse.jetty.util.component.AbstractLifeCycle=ERRORlog4j.logger.org.apache.spark.repl.SparkIMain$exprTyper=INFOlog4j.logger.org.apache.spark.repl.SparkILoop$SparkILoopInterpreter=INFO


This issue leads to the ### INFO messages that log4j prints in Spark console:
[root@sandbox ~]# spark-shell --master yarn-client --driver-memory 512m 
--executor-memory 512m
log4j:WARN No appenders could be found for logger 
(org.apache.hadoop.metrics2.lib.MutableMetricsFactory).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
info.
Using Spark's default log4j profile: org/apache/spark/log4j-defaults.properties
15/11/05 12:34:41 INFO SecurityManager: Changing view acls to: root
15/11/05 12:34:41 INFO SecurityManager: Changing modify acls to: root
15/11/05 12:34:41 INFO SecurityManager: SecurityManager: authentication 
disabled; ui acls disabled; users with view permissions: Set(root); users with 
modify permissions: Set(root)
15/11/05 12:34:41 INFO HttpServer: Starting HTTP Server
15/11/05 12:34:41 INFO Server: jetty-8.y.z-SNAPSHOT
15/11/05 12:34:41 INFO AbstractConnector: Started SocketConnector@0.0.0.0:54564
15/11/05 12:34:41 INFO Utils: Successfully started service 'HTTP class server' 
on port 54564.
Welcome to
    __
 / __/__  ___ _/ /__
_\ \/ _ \/ _ `/ __/  '_/
   /___/ .__/\_,_/_/ /_/\_\   version 1.3.1
  /_/

Using Scala version 2.10.4 (OpenJDK 64-Bit Server VM, Java 1.7.0_85)
Type in expressions to have them evaluated.
Type :help for more information.
15/11/05 12:34:44 INFO SparkContext: Running Spark version 1.3.1
15/11/05 12:34:44 INFO SecurityManager: Changing view acls to: root
15/11/05 12:34:44 INFO SecurityManager: Changing modify acls to: root
15/11/05 12:34:44 INFO SecurityManager: SecurityManager: authentication 
disabled; ui acls disabled; users with view permissions: Set(root); users with 
modify permissions: Set(root)
15/11/05 12:34:44 INFO Slf4jLogger: Slf4jLogger started
15/11/05 12:34:44 INFO Remoting: Starting remoting
15/11/05 12:34:44 INFO Remoting: Remoting started; listening on addresses 
:[akka.tcp://sparkdri...@sandbox.hortonworks.com:35020]
15/11/05 12:34:44 INFO Utils: Successfully started service 'sparkDriver' on 
port 35020.
15/11/05 12:34:44 INFO SparkEnv: Registering MapOutputTracker
15/11/05 12:34:44 INFO SparkEnv: Registering BlockManagerMaster
15/11/05 12:34:44 INFO DiskBlockManager: Created local directory at 
/tmp/spark-3b14e9fc-73b1-45e7-96f3-f0ee48f3a238/blockmgr-ffd0619a-5fbc-4ccc-bcef-ce8560e03cd7
15/11/05 12:34:44 INFO MemoryStore: MemoryStore started with capacity 265.4 MB
15/11/05 12:34:45 INFO HttpFileServer: HTTP File server directory is 
/tmp/spark-7648f575-a8e3-4b25-945f-b4ded8631592/httpd-ec5526bb-4de6-42d6-83aa-a1ba0a2ca5dd
15/11/05 12:34:45 INFO HttpServer: Starting HTTP Server
15/11/05 12:34:45 INFO Server: jetty-8.y.z-SNAPSHOT
15/11/05 12:34:45 INFO AbstractConnector: Started 

[jira] [Updated] (AMBARI-13731) Ambari fails to install packages python-devel, mysql-connector-java and netcat-openbsd on SLES

[Madan Sen (JIRA)]

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

Madan Sen updated AMBARI-13731:
---
Attachment: AMBARI-13731.patch

patch as per option 1

> Ambari fails to install packages python-devel, mysql-connector-java and 
> netcat-openbsd  on SLES
> ---
>
> Key: AMBARI-13731
> URL: https://issues.apache.org/jira/browse/AMBARI-13731
> Project: Ambari
>  Issue Type: Bug
> Environment: Suse Linux
>Reporter: Madan Sen
> Attachments: AMBARI-13731.patch
>
>




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

[jira] [Created] (AMBARI-13734) HDFS destination directory is not getting updated with the recommended value

[Andrii Tkach (JIRA)]

Andrii Tkach created AMBARI-13734:
-

 Summary: HDFS destination directory is not getting updated with 
the recommended value
 Key: AMBARI-13734
 URL: https://issues.apache.org/jira/browse/AMBARI-13734
 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


# Deploy a cluster
# Navigate to Add service wizard and add Ranger service
# On landing at "configure services" page in the wizard, recommendation API 
call is made. The response of the recommendation API call recommends a value 
for ranger-hdfs-audit/xasecure.audit.destination.hdfs.dir but this is not shown 
on recommendation popup and the property is not set to that value on HDFS 
config page.



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

[jira] [Commented] (AMBARI-13266) Where to fill the security username when Ambari want to fire a SNMPv3 Trap?

[Pradeep Bhadani (JIRA)]

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

Pradeep Bhadani commented on AMBARI-13266:
--

There is an option to "Add property" when you configure SNMP notification in 
Ambari. You can set the property with key name as 
"ambari.dispatch.snmp.security.username"

> Where to fill the security username when Ambari want to fire a SNMPv3 Trap?
> ---
>
> Key: AMBARI-13266
> URL: https://issues.apache.org/jira/browse/AMBARI-13266
> Project: Ambari
>  Issue Type: Test
>  Components: alerts, ambari-server
>Affects Versions: 2.0.0
> Environment: cenOS6.5
>Reporter: huang
>
> I am using AMBARI 2.0 and want to configure SNMP alerts.It can work when i 
> tried to fire a SNMPV1 or SNMPv2c Trap.But when i tried to fire the SNMPv3 
> Trap, I have found nowhere for me to fill the security name or the security 
> level. 
>  In the logs , it mentions "ERROR [alert-dispatch-1] SNMPDispatcher:123 - 
> Unable to dispatch SNMP trap with invalid configuration. Property 
> "ambari.dispatch.snmp.security.username" should be set."
> i'm so confused,please help me.



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

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

[Canan Girgin (JIRA)]

Canan Girgin created AMBARI-13738:
-

 Summary: 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


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)

[jira] [Commented] (AMBARI-13732) Refactor config_property_helper

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13732:
-

FAILURE: Integrated in Ambari-trunk-Commit #3775 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3775/])
AMBARI-13732. Refactor config_property_helper (onechiporenko) (onechiporenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e24078b2b91a3a86bf252cb6a7d4cb8b3bbb77b3])
* ambari-web/test/utils/configs/config_property_helper_test.js
* ambari-web/app/models/configs/objects/service_config_property.js
* ambari-web/app/controllers/wizard/step7_controller.js
* ambari-web/app/utils/configs/config_property_helper.js


> Refactor config_property_helper
> ---
>
> Key: AMBARI-13732
> URL: https://issues.apache.org/jira/browse/AMBARI-13732
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-web
>Affects Versions: ambari-2.2.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: ambari-2.2.0
>
> Attachments: AMBARI-13732.patch
>
>




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

[jira] [Created] (AMBARI-13739) RESTART ZOOKEEPER_SERVER failed after Upgrade from 1.6.1 to 2.1.3

[Vitaly Brodetskyi (JIRA)]

Vitaly Brodetskyi created AMBARI-13739:
--

 Summary: RESTART ZOOKEEPER_SERVER failed after Upgrade from 1.6.1 
to 2.1.3
 Key: AMBARI-13739
 URL: https://issues.apache.org/jira/browse/AMBARI-13739
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.1.3
Reporter: Vitaly Brodetskyi
Assignee: Vitaly Brodetskyi
Priority: Blocker
 Fix For: 2.1.3


STR:
1)Deploy old version 1.6.1
2)Enable/Disable security (MIT)
3)Make Ambari only upgrade to 2.1.3

Actual results:
RESTART ZOOKEEPER_SERVER failed after Upgrade from 1.6.1 to 2.1.3
{code}
  {
  "href" : 
"http://172.22.87.177:8080/api/v1/clusters/cl1/requests/11/tasks/501;,
  "Tasks" : {
"attempt_cnt" : 1,
"cluster_name" : "cl1",
"command" : "CUSTOM_COMMAND",
"command_detail" : "RESTART ZOOKEEPER/ZOOKEEPER_SERVER",
"custom_command_name" : "RESTART",
"end_time" : 1446626534832,
"error_log" : "/var/lib/ambari-agent/data/errors-501.txt",
"exit_code" : 1,
"host_name" : "amb-upg161-rhel6mysql1446600673-3.novalocal",
"id" : 501,
"output_log" : "/var/lib/ambari-agent/data/output-501.txt",
"request_id" : 11,
"role" : "ZOOKEEPER_SERVER",
"stage_id" : 0,
"start_time" : 1446626531540,
"status" : "FAILED",
"stderr" : "Traceback (most recent call last):\n  File 
\"/var/lib/ambari-agent/cache/common-services/ZOOKEEPER/3.4.5.2.0/package/scripts/zookeeper_server.py\",
 line 179, in \nZookeeperServer().execute()\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
 line 218, in execute\nmethod(env)\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
 line 486, in restart\nself.stop(env, upgrade_type=upgrade_type)\n  File 
\"/var/lib/ambari-agent/cache/common-services/ZOOKEEPER/3.4.5.2.0/package/scripts/zookeeper_server.py\",
 line 60, in stop\nzookeeper_service(action='stop', 
upgrade_type=upgrade_type)\n  File 
\"/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py\", line 89, 
in thunk\nreturn fn(*args, **kwargs)\n  File 
\"/var/lib/ambari-agent/cache/common-services/ZOOKEEPER/3.4.5.2.0/package/scripts/zookeeper_service.py\",
 line 36, in zookeeper_service\nhdp_select.select(\"zookeeper-server\", 
params.version)\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/hdp_select.py\",
 line 116, in select\nExecute(command, sudo=True)\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line 
154, in __init__\nself.env.run()\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", 
line 156, in run\nself.run_action(resource, action)\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", 
line 119, in run_action\nprovider_action()\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
 line 238, in action_run\ntries=self.resource.tries, 
try_sleep=self.resource.try_sleep)\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
70, in inner\nresult = function(command, **kwargs)\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
92, in checked_call\ntries=tries, try_sleep=try_sleep)\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
140, in _call_wrapper\nresult = _call(command, **kwargs_copy)\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
291, in _call\nraise 
Fail(err_msg)\nresource_management.core.exceptions.Fail: Execution of 
'hdp-select set zookeeper-server 2.1.0.0-0001' returned 127. 
/var/lib/ambari-agent/ambari-sudo.sh: line 50: hdp-select: command not found",
"stdout" : "2015-11-04 08:42:14,133 - Group['hadoop'] {}\n2015-11-04 
08:42:14,135 - Group['nobody'] {}\n2015-11-04 08:42:14,135 - Group['users'] 
{}\n2015-11-04 08:42:14,135 - User['hive'] {'gid': 'hadoop', 'groups': 
['hadoop']}\n2015-11-04 08:42:14,137 - User['oozie'] {'gid': 'hadoop', 
'groups': ['users']}\n2015-11-04 08:42:14,138 - User['nobody'] {'gid': 
'hadoop', 'groups': ['nobody']}\n2015-11-04 08:42:14,139 - User['ambari-qa'] 
{'gid': 'hadoop', 'groups': ['users']}\n2015-11-04 08:42:14,140 - User['hdfs'] 
{'gid': 'hadoop', 'groups': ['hadoop']}\n2015-11-04 08:42:14,142 - 
User['storm'] {'gid': 'hadoop', 'groups': ['hadoop']}\n2015-11-04 08:42:14,143 
- User['mapred'] {'gid': 'hadoop', 'groups': ['hadoop']}\n2015-11-04 
08:42:14,144 - User['hbase'] {'gid': 'hadoop', 'groups': 
['hadoop']}\n2015-11-04 08:42:14,145 - User['tez'] {'gid': 'hadoop', 'groups': 
['users']}\n2015-11-04 08:42:14,146 - User['zookeeper'] {'gid': 'hadoop', 
'groups': ['hadoop']}\n2015-11-04 08:42:14,147 - User['falcon'] {'gid': 

Review Request 39972: RESTART ZOOKEEPER_SERVER failed after Upgrade from 1.6.1 to 2.1.3

[Vitalyi Brodetskyi]

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

Review request for Ambari, Dmitro Lisnichenko and Sumit Mohanty.


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


Repository: ambari


Description
---

STR:
1)Deploy old version 1.6.1
2)Enable/Disable security (MIT)
3)Make Ambari only upgrade to 2.1.3

Actual results:
RESTART ZOOKEEPER_SERVER failed after Upgrade from 1.6.1 to 2.1.3
{code}
  {
  "href" : 
"http://172.22.87.177:8080/api/v1/clusters/cl1/requests/11/tasks/501;,
  "Tasks" : {
"attempt_cnt" : 1,
"cluster_name" : "cl1",
"command" : "CUSTOM_COMMAND",
"command_detail" : "RESTART ZOOKEEPER/ZOOKEEPER_SERVER",
"custom_command_name" : "RESTART",
"end_time" : 1446626534832,
"error_log" : "/var/lib/ambari-agent/data/errors-501.txt",
"exit_code" : 1,
"host_name" : "amb-upg161-rhel6mysql1446600673-3.novalocal",
"id" : 501,
"output_log" : "/var/lib/ambari-agent/data/output-501.txt",
"request_id" : 11,
"role" : "ZOOKEEPER_SERVER",
"stage_id" : 0,
"start_time" : 1446626531540,
"status" : "FAILED",
"stderr" : "Traceback (most recent call last):\n  File 
\"/var/lib/ambari-agent/cache/common-services/ZOOKEEPER/3.4.5.2.0/package/scripts/zookeeper_server.py\",
 line 179, in \nZookeeperServer().execute()\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
 line 218, in execute\nmethod(env)\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
 line 486, in restart\nself.stop(env, upgrade_type=upgrade_type)\n  File 
\"/var/lib/ambari-agent/cache/common-services/ZOOKEEPER/3.4.5.2.0/package/scripts/zookeeper_server.py\",
 line 60, in stop\nzookeeper_service(action='stop', 
upgrade_type=upgrade_type)\n  File 
\"/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py\", line 89, 
in thunk\nreturn fn(*args, **kwargs)\n  File 
\"/var/lib/ambari-agent/cache/common-services/ZOOKEEPER/3.4.5.2.0/package/scripts/zookeeper_service.py\",
 line 36, in zookeeper_service\nhdp_select.sel
 ect(\"zookeeper-server\", params.version)\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/hdp_select.py\",
 line 116, in select\nExecute(command, sudo=True)\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line 
154, in __init__\nself.env.run()\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", 
line 156, in run\nself.run_action(resource, action)\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", 
line 119, in run_action\nprovider_action()\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
 line 238, in action_run\ntries=self.resource.tries, 
try_sleep=self.resource.try_sleep)\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
70, in inner\nresult = function(command, **kwargs)\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line
  92, in checked_call\ntries=tries, try_sleep=try_sleep)\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
140, in _call_wrapper\nresult = _call(command, **kwargs_copy)\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
291, in _call\nraise 
Fail(err_msg)\nresource_management.core.exceptions.Fail: Execution of 
'hdp-select set zookeeper-server 2.1.0.0-0001' returned 127. 
/var/lib/ambari-agent/ambari-sudo.sh: line 50: hdp-select: command not found",
"stdout" : "2015-11-04 08:42:14,133 - Group['hadoop'] {}\n2015-11-04 
08:42:14,135 - Group['nobody'] {}\n2015-11-04 08:42:14,135 - Group['users'] 
{}\n2015-11-04 08:42:14,135 - User['hive'] {'gid': 'hadoop', 'groups': 
['hadoop']}\n2015-11-04 08:42:14,137 - User['oozie'] {'gid': 'hadoop', 
'groups': ['users']}\n2015-11-04 08:42:14,138 - User['nobody'] {'gid': 
'hadoop', 'groups': ['nobody']}\n2015-11-04 08:42:14,139 - User['ambari-qa'] 
{'gid': 'hadoop', 'groups': ['users']}\n2015-11-04 08:42:14,140 - User['hdfs'] 
{'gid': 'hadoop', 'groups': ['hadoop']}\n2015-11-04 08:42:14,142 - 
User['storm'] {'gid': 'hadoop', 'groups': ['hadoop']}\n2015-11-04 08:42:14,143 
- User['mapred'] {'gid': 'hadoop', 'groups': ['hadoop']}\n2015-11-04 
08:42:14,144 - User['hbase'] {'gid': 'hadoop', 'groups': 
['hadoop']}\n2015-11-04 08:42:14,145 - User['tez'] {'gid': 'hadoop', 'groups': 
['users']}\n2015-11-04 08:42:14,146 - User['zookeeper'] {'gid': 'hadoop', 
'groups': ['hadoop']}\n2015-11-04 08:42:14,147 - User['
 falcon'] {'gid': 'hadoop', 'groups': ['users']}\n2015-11-04 08:42:14,148 - 
User['sqoop'] {'gid': 'hadoop', 'groups': ['hadoop']}\n2015-11-04 08:42:14,150 

[jira] [Updated] (AMBARI-13732) Refactor config_property_helper

[Oleg Nechiporenko (JIRA)]

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

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

> Refactor config_property_helper
> ---
>
> Key: AMBARI-13732
> URL: https://issues.apache.org/jira/browse/AMBARI-13732
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-web
>Affects Versions: ambari-2.2.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: ambari-2.2.0
>
> Attachments: AMBARI-13732.patch
>
>




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

[jira] [Commented] (AMBARI-13732) Refactor config_property_helper

[Oleg Nechiporenko (JIRA)]

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

Oleg Nechiporenko commented on AMBARI-13732:


  10268 tests complete (14 seconds)
  105 tests pending

> Refactor config_property_helper
> ---
>
> Key: AMBARI-13732
> URL: https://issues.apache.org/jira/browse/AMBARI-13732
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-web
>Affects Versions: ambari-2.2.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: ambari-2.2.0
>
> Attachments: AMBARI-13732.patch
>
>




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

[jira] [Commented] (AMBARI-13732) Refactor config_property_helper

[Andrii Tkach (JIRA)]

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

Andrii Tkach commented on AMBARI-13732:
---

+1 for the patch

> Refactor config_property_helper
> ---
>
> Key: AMBARI-13732
> URL: https://issues.apache.org/jira/browse/AMBARI-13732
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-web
>Affects Versions: ambari-2.2.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: ambari-2.2.0
>
> Attachments: AMBARI-13732.patch
>
>




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

[jira] [Created] (AMBARI-13733) Checking selinux status on each host when creating new cluster

[Mehmet Zahid Yuzuguldu (JIRA)]

Mehmet Zahid Yuzuguldu created AMBARI-13733:
---

 Summary: Checking selinux status on each host when creating new 
cluster
 Key: AMBARI-13733
 URL: https://issues.apache.org/jira/browse/AMBARI-13733
 Project: Ambari
  Issue Type: New Feature
  Components: ambari-server, ambari-web
Reporter: Mehmet Zahid Yuzuguldu


Adding checking selinux status mechanism on each host when creating new cluster.



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

[jira] [Commented] (AMBARI-13734) HDFS destination directory is not getting updated with the recommended value

[Andrii Tkach (JIRA)]

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

Andrii Tkach commented on AMBARI-13734:
---

committed to trunk and branch-2.1

> HDFS destination directory is not getting updated with the recommended value
> 
>
> Key: AMBARI-13734
> URL: https://issues.apache.org/jira/browse/AMBARI-13734
> 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-13734.patch
>
>
> # Deploy a cluster
> # Navigate to Add service wizard and add Ranger service
> # On landing at "configure services" page in the wizard, recommendation API 
> call is made. The response of the recommendation API call recommends a value 
> for ranger-hdfs-audit/xasecure.audit.destination.hdfs.dir but this is not 
> shown on recommendation popup and the property is not set to that value on 
> HDFS config page.



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

[jira] [Commented] (AMBARI-13737) Unchecking all configuration in recommendation pop results in incorrect message

[Oleg Nechiporenko (JIRA)]

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

Oleg Nechiporenko commented on AMBARI-13737:


+1 for patch

> Unchecking all configuration in recommendation pop results in incorrect 
> message
> ---
>
> Key: AMBARI-13737
> URL: https://issues.apache.org/jira/browse/AMBARI-13737
> 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: 0_services.png, AMBARI-13737.patch
>
>
> *STR:*
> # When a recommendation pop is shown with list of config recommended to 
> change, uncheck all configs
> # Then dismiss the popup
> # Message says that {{There are 7 configuration changes in 0 services}}. 
> [^0_services.png] 
> *Expected behavior:*
> # configuration count should be equal to the checked configuration in the 
> recommendation popup
> # service count should be equal to the sum of services of which 
> configurations are changed. This is already happening right now
> # Change the message to insert *selected* word in it. Example: {{There are 7 
> configuration changes selected in 3 services}}
> # When no config is selected then drop the service count phrase in the 
> sentence. Message should be {{There are 0 configuration changes selected}}



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

[jira] [Updated] (AMBARI-13737) Unchecking all configuration in recommendation pop results in incorrect message

[Andrii Tkach (JIRA)]

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

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

> Unchecking all configuration in recommendation pop results in incorrect 
> message
> ---
>
> Key: AMBARI-13737
> URL: https://issues.apache.org/jira/browse/AMBARI-13737
> 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: 0_services.png, AMBARI-13737.patch
>
>
> *STR:*
> # When a recommendation pop is shown with list of config recommended to 
> change, uncheck all configs
> # Then dismiss the popup
> # Message says that {{There are 7 configuration changes in 0 services}}. 
> [^0_services.png] 
> *Expected behavior:*
> # configuration count should be equal to the checked configuration in the 
> recommendation popup
> # service count should be equal to the sum of services of which 
> configurations are changed. This is already happening right now
> # Change the message to insert *selected* word in it. Example: {{There are 7 
> configuration changes selected in 3 services}}
> # When no config is selected then drop the service count phrase in the 
> sentence. Message should be {{There are 0 configuration changes selected}}



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

[jira] [Commented] (AMBARI-13737) Unchecking all configuration in recommendation pop results in incorrect message

[Andrii Tkach (JIRA)]

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

Andrii Tkach commented on AMBARI-13737:
---

  10144 tests complete (14 seconds)
  104 tests pending

> Unchecking all configuration in recommendation pop results in incorrect 
> message
> ---
>
> Key: AMBARI-13737
> URL: https://issues.apache.org/jira/browse/AMBARI-13737
> 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: 0_services.png, AMBARI-13737.patch
>
>
> *STR:*
> # When a recommendation pop is shown with list of config recommended to 
> change, uncheck all configs
> # Then dismiss the popup
> # Message says that {{There are 7 configuration changes in 0 services}}. 
> [^0_services.png] 
> *Expected behavior:*
> # configuration count should be equal to the checked configuration in the 
> recommendation popup
> # service count should be equal to the sum of services of which 
> configurations are changed. This is already happening right now
> # Change the message to insert *selected* word in it. Example: {{There are 7 
> configuration changes selected in 3 services}}
> # When no config is selected then drop the service count phrase in the 
> sentence. Message should be {{There are 0 configuration changes selected}}



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

[jira] [Created] (AMBARI-13731) Ambari fails to install packages python-devel, mysql-connector-java and netcat-openbsd on SLES

[Madan Sen (JIRA)]

Madan Sen created AMBARI-13731:
--

 Summary: Ambari fails to install packages python-devel, 
mysql-connector-java and netcat-openbsd  on SLES
 Key: AMBARI-13731
 URL: https://issues.apache.org/jira/browse/AMBARI-13731
 Project: Ambari
  Issue Type: Bug
 Environment: Suse Linux
Reporter: Madan Sen






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

[jira] [Created] (AMBARI-13732) Refactor config_property_helper

[Oleg Nechiporenko (JIRA)]

Oleg Nechiporenko created AMBARI-13732:
--

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






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

[jira] [Created] (AMBARI-13735) Ambari throws error when updating Notification

[Pradeep Bhadani (JIRA)]

Pradeep Bhadani created AMBARI-13735:


 Summary: Ambari throws error when updating Notification
 Key: AMBARI-13735
 URL: https://issues.apache.org/jira/browse/AMBARI-13735
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.1.1, 2.1.2
Reporter: Pradeep Bhadani


When i try to Edit and Save any notification Ambari UI , it do not save and 
throws following error in ambari-server.log 

05 Nov 2015 11:29:08,966  WARN [qtp-client-25] ServletHandler:563 - 
/api/v1/alert_targets/52
java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextEntry(HashMap.java:922)
at java.util.HashMap$KeyIterator.next(HashMap.java:956)
at 
org.apache.ambari.server.orm.entities.AlertTargetEntity.setAlertGroups(AlertTargetEntity.java:275)
at 
org.apache.ambari.server.controller.internal.AlertTargetResourceProvider.updateAlertTargets(AlertTargetResourceProvider.java:412)
at 
org.apache.ambari.server.controller.internal.AlertTargetResourceProvider.access$100(AlertTargetResourceProvider.java:65)
at 
org.apache.ambari.server.controller.internal.AlertTargetResourceProvider$2.invoke(AlertTargetResourceProvider.java:194)
at 
org.apache.ambari.server.controller.internal.AlertTargetResourceProvider$2.invoke(AlertTargetResourceProvider.java:181)
at 
org.apache.ambari.server.controller.internal.AbstractResourceProvider.modifyResources(AbstractResourceProvider.java:330)
at 
org.apache.ambari.server.controller.internal.AlertTargetResourceProvider.updateResources(AlertTargetResourceProvider.java:181)
at 
org.apache.ambari.server.controller.internal.ClusterControllerImpl.updateResources(ClusterControllerImpl.java:310)
at 
org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.update(PersistenceManagerImpl.java:104)
at 
org.apache.ambari.server.api.handlers.UpdateHandler.persist(UpdateHandler.java:42)
at 
org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:72)
at 
org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:135)
at 
org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:105)
at 
org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:74)
at 
org.apache.ambari.server.api.services.AlertTargetService.updateGroup(AlertTargetService.java:76)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at 
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
at 
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at 
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
at 
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
at 
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:540)
at 
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:715)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1496)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
at 

[jira] [Created] (AMBARI-13736) Ambari cannot dispatch SNMP trap on default alerts .Throws NullPointer exception for default alerts

[Pradeep Bhadani (JIRA)]

Pradeep Bhadani created AMBARI-13736:


 Summary: Ambari cannot dispatch SNMP trap on default alerts 
.Throws NullPointer exception for default alerts
 Key: AMBARI-13736
 URL: https://issues.apache.org/jira/browse/AMBARI-13736
 Project: Ambari
  Issue Type: Bug
Affects Versions: 2.1.1, 2.1.2
Reporter: Pradeep Bhadani


I am trying to use HDFS and YARN notification group (from default provided)  to 
send SNMP trap.
I am getting following error :

05 Nov 2015 11:38:31,244  INFO [AlertNoticeDispatchService] 
AlertNoticeDispatchService:279 - There are 1 pending alert notices about to be 
dispatched...
05 Nov 2015 11:38:31,248  INFO [alert-dispatch-2] SNMPDispatcher:116 - Sending 
SNMP trap:
  [OK] Secondary NameNode Process

05 Nov 2015 11:38:31,256 ERROR [alert-dispatch-2] SNMPDispatcher:126 - Error 
occurred during SNMP trap dispatching.
java.lang.NullPointerException
at org.snmp4j.security.AuthGeneric.passwordToKey(AuthGeneric.java:205)
at 
org.snmp4j.security.SecurityProtocols.passwordToKey(SecurityProtocols.java:269)
at org.snmp4j.security.USM.getUser(USM.java:261)
at org.snmp4j.security.USM.generateResponseMessage(USM.java:355)
at org.snmp4j.security.USM.generateRequestMessage(USM.java:215)
at org.snmp4j.mp.MPv3.prepareOutgoingMessage(MPv3.java:767)
at 
org.snmp4j.MessageDispatcherImpl.sendPdu(MessageDispatcherImpl.java:437)
at org.snmp4j.Snmp.sendMessage(Snmp.java:1051)
at org.snmp4j.Snmp.send(Snmp.java:875)
at org.snmp4j.Snmp.send(Snmp.java:868)
at org.snmp4j.Snmp.send(Snmp.java:833)
at 
org.apache.ambari.server.notifications.dispatchers.SNMPDispatcher.sendTraps(SNMPDispatcher.java:203)
at 
org.apache.ambari.server.notifications.dispatchers.SNMPDispatcher.dispatch(SNMPDispatcher.java:120)
at 
org.apache.ambari.server.notifications.DispatchRunnable.run(DispatchRunnable.java:58)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)




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

[jira] [Created] (AMBARI-13737) Unchecking all configuration in recommendation pop results in incorrect message

[Andrii Tkach (JIRA)]

Andrii Tkach created AMBARI-13737:
-

 Summary: Unchecking all configuration in recommendation pop 
results in incorrect message
 Key: AMBARI-13737
 URL: https://issues.apache.org/jira/browse/AMBARI-13737
 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: 0_services.png

*STR:*
# When a recommendation pop is shown with list of config recommended to change, 
uncheck all configs
# Then dismiss the popup
# Message says that {{There are 7 configuration changes in 0 services}}. 
[^0_services.png] 

*Expected behavior:*
# configuration count should be equal to the checked configuration in the 
recommendation popup
# service count should be equal to the sum of services of which configurations 
are changed. This is already happening right now
# Change the message to insert *selected* word in it. Example: {{There are 7 
configuration changes selected in 3 services}}
# When no config is selected then drop the service count phrase in the 
sentence. Message should be {{There are 0 configuration changes selected}}



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

[jira] [Updated] (AMBARI-13737) Unchecking all configuration in recommendation pop results in incorrect message

[Andrii Tkach (JIRA)]

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

Andrii Tkach updated AMBARI-13737:
--
Attachment: 0_services.png

> Unchecking all configuration in recommendation pop results in incorrect 
> message
> ---
>
> Key: AMBARI-13737
> URL: https://issues.apache.org/jira/browse/AMBARI-13737
> 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: 0_services.png
>
>
> *STR:*
> # When a recommendation pop is shown with list of config recommended to 
> change, uncheck all configs
> # Then dismiss the popup
> # Message says that {{There are 7 configuration changes in 0 services}}. 
> [^0_services.png] 
> *Expected behavior:*
> # configuration count should be equal to the checked configuration in the 
> recommendation popup
> # service count should be equal to the sum of services of which 
> configurations are changed. This is already happening right now
> # Change the message to insert *selected* word in it. Example: {{There are 7 
> configuration changes selected in 3 services}}
> # When no config is selected then drop the service count phrase in the 
> sentence. Message should be {{There are 0 configuration changes selected}}



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

[jira] [Updated] (AMBARI-13733) Checking selinux status on each host when creating new cluster

[Mehmet Zahid Yuzuguldu (JIRA)]

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

Mehmet Zahid Yuzuguldu updated AMBARI-13733:

Attachment: AMBARI-13733.patch

Adding checking selinux status mechanism on each host when creating new cluster.

> Checking selinux status on each host when creating new cluster
> --
>
> Key: AMBARI-13733
> URL: https://issues.apache.org/jira/browse/AMBARI-13733
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-server, ambari-web
>Reporter: Mehmet Zahid Yuzuguldu
> Attachments: AMBARI-13733.patch
>
>
> Adding checking selinux status mechanism on each host when creating new 
> cluster. 
> Patch added.



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

[jira] [Updated] (AMBARI-13734) HDFS destination directory is not getting updated with the recommended value

[Andrii Tkach (JIRA)]

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

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

> HDFS destination directory is not getting updated with the recommended value
> 
>
> Key: AMBARI-13734
> URL: https://issues.apache.org/jira/browse/AMBARI-13734
> 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-13734.patch
>
>
> # Deploy a cluster
> # Navigate to Add service wizard and add Ranger service
> # On landing at "configure services" page in the wizard, recommendation API 
> call is made. The response of the recommendation API call recommends a value 
> for ranger-hdfs-audit/xasecure.audit.destination.hdfs.dir but this is not 
> shown on recommendation popup and the property is not set to that value on 
> HDFS config page.



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

[jira] [Commented] (AMBARI-13734) HDFS destination directory is not getting updated with the recommended value

[Andrii Tkach (JIRA)]

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

Andrii Tkach commented on AMBARI-13734:
---

  10268 tests complete (14 seconds)
  105 tests pending

> HDFS destination directory is not getting updated with the recommended value
> 
>
> Key: AMBARI-13734
> URL: https://issues.apache.org/jira/browse/AMBARI-13734
> 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-13734.patch
>
>
> # Deploy a cluster
> # Navigate to Add service wizard and add Ranger service
> # On landing at "configure services" page in the wizard, recommendation API 
> call is made. The response of the recommendation API call recommends a value 
> for ranger-hdfs-audit/xasecure.audit.destination.hdfs.dir but this is not 
> shown on recommendation popup and the property is not set to that value on 
> HDFS config page.



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

[jira] [Commented] (AMBARI-13734) HDFS destination directory is not getting updated with the recommended value

[Oleg Nechiporenko (JIRA)]

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

Oleg Nechiporenko commented on AMBARI-13734:


+1 for patch

> HDFS destination directory is not getting updated with the recommended value
> 
>
> Key: AMBARI-13734
> URL: https://issues.apache.org/jira/browse/AMBARI-13734
> 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-13734.patch
>
>
> # Deploy a cluster
> # Navigate to Add service wizard and add Ranger service
> # On landing at "configure services" page in the wizard, recommendation API 
> call is made. The response of the recommendation API call recommends a value 
> for ranger-hdfs-audit/xasecure.audit.destination.hdfs.dir but this is not 
> shown on recommendation popup and the property is not set to that value on 
> HDFS config page.



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

[jira] [Commented] (AMBARI-13731) Ambari fails to install packages python-devel, mysql-connector-java and netcat-openbsd on SLES

[Madan Sen (JIRA)]

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

Madan Sen commented on AMBARI-13731:


The packages (python-devel, netcat-openbsd, mysql-connector-java) are present 
in the SLES repository

bdavm691:˜ # zypper wp python-devel
S | Name | Type| Version  | Arch   | Repository
--+--+-+--++--
  | python-devel | package | 2.6.9-0.35.1 | x86_64 | SDS SLE11 SDK SP3 Updates
  | python-devel | package | 2.6.9-0.33.1 | x86_64 | SDS SLE11 SDK SP3 Updates
  | python-devel | package | 2.6.9-0.31.1 | x86_64 | SDS SLE11 SDK SP3 Updates
  | python-devel | package | 2.6.9-0.27.1 | x86_64 | SDS SLE11 SDK SP3 Updates
  | python-devel | package | 2.6.9-0.25.1 | x86_64 | SDS SLE11 SDK SP3 Updates
  | python-devel | package | 2.6.8-0.23.1 | x86_64 | SDS SLE11 SDK SP3 Updates
  | python-devel | package | 2.6.8-0.19.1 | x86_64 | SDS SLE11 SDK SP3 Updates
  | python-devel | package | 2.6.8-0.15.1 | x86_64 | SDS SLE11 SDK SP3 Pool
bdavm691:˜ #
bdavm691:˜ # zypper wp netcat-openbsd
S | Name   | Type| Version | Arch   | Repository
--++-+-++-
  | netcat-openbsd | package | 1.89-78.8.1 | x86_64 | SDS SLES11 SP3 Updates
  | netcat-openbsd | package | 1.89-78.6.1 | x86_64 | SDS SLES11 SP3 Pool
  | netcat-openbsd | package | 1.89-78.6.1 | x86_64 | 
SUSE-Linux-Enterprise-Server-11-SP3 11.3.3-1.138

bdavm691:˜ #
bdavm691:˜ # zypper wp mysql-connector-java

S | Name | Type| Version| Arch   | Repository
--+--+-+++---
  | mysql-connector-java | package | 5.1.6-1.27 | noarch | SDS SLE11 SDK SP3 
Pool


The basic issue is of "Login Failure" while accessing the SLES repositories 
from ambari installation.


Further looking at this, found out that on the SLES machines the credentials 
for ftp repo are stored at /root/.zypp/credentials.cat file. Now there a couple 
of ways to fix the login failure issue

Option 1. Zypper seems to need $HOME to be set to pick up the credentials from 
"/root/.zypp/credentials.cat". Looking at ambari code that is firing the zypper 
install command and that seems to be only setting up the "PATH" variable. If we 
put HOME=/root environment variable the installation succeeds. I think we can 
do this install will need root access. A similar problem is reported by puppet 
https://projects.puppetlabs.com/issues/23378. So the solution would be to 
modify ambari to set $HOME variable to /root

Option 2. If we look at the zypper config file (/etc/zypp/zypp.conf) it expects 
a global credentials file, by default, at /etc/zypp/credentials.cat 
(credentials.global.file = /etc/zypp/credentials.cat). If we copy 
/root/.zypp/credentials.cat to /etc/zypp/credentials.cat installation succeeds. 
So the solution would be to document that the user needs to copy 
root/.zypp/credentials.cat to /etc/zypp/credentials.cat and run "zypper 
refresh" and "zypper update" before installing ambari. This is a quick 
work-around

I think Option 1 would be most suitable 

> Ambari fails to install packages python-devel, mysql-connector-java and 
> netcat-openbsd  on SLES
> ---
>
> Key: AMBARI-13731
> URL: https://issues.apache.org/jira/browse/AMBARI-13731
> Project: Ambari
>  Issue Type: Bug
> Environment: Suse Linux
>Reporter: Madan Sen
>




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

[jira] [Updated] (AMBARI-13733) Checking selinux status on each host when creating new cluster

[Mehmet Zahid Yuzuguldu (JIRA)]

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

Mehmet Zahid Yuzuguldu updated AMBARI-13733:

Description: 
Adding checking selinux status mechanism on each host when creating new 
cluster. 
Patch added.

  was:Adding checking selinux status mechanism on each host when creating new 
cluster.


> Checking selinux status on each host when creating new cluster
> --
>
> Key: AMBARI-13733
> URL: https://issues.apache.org/jira/browse/AMBARI-13733
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-server, ambari-web
>Reporter: Mehmet Zahid Yuzuguldu
>
> Adding checking selinux status mechanism on each host when creating new 
> cluster. 
> Patch added.



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

[jira] [Commented] (AMBARI-13737) Unchecking all configuration in recommendation pop results in incorrect message

[Andrii Tkach (JIRA)]

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

Andrii Tkach commented on AMBARI-13737:
---

committed to branch-2.1

> Unchecking all configuration in recommendation pop results in incorrect 
> message
> ---
>
> Key: AMBARI-13737
> URL: https://issues.apache.org/jira/browse/AMBARI-13737
> 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: 0_services.png, AMBARI-13737.patch
>
>
> *STR:*
> # When a recommendation pop is shown with list of config recommended to 
> change, uncheck all configs
> # Then dismiss the popup
> # Message says that {{There are 7 configuration changes in 0 services}}. 
> [^0_services.png] 
> *Expected behavior:*
> # configuration count should be equal to the checked configuration in the 
> recommendation popup
> # service count should be equal to the sum of services of which 
> configurations are changed. This is already happening right now
> # Change the message to insert *selected* word in it. Example: {{There are 7 
> configuration changes selected in 3 services}}
> # When no config is selected then drop the service count phrase in the 
> sentence. Message should be {{There are 0 configuration changes selected}}



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

[jira] [Updated] (AMBARI-13747) Hive View : Add Database/Table creation from File

[Nitiraj Singh Rathore (JIRA)]

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

Nitiraj Singh Rathore updated AMBARI-13747:
---
Attachment: AMBARI-13747_branch-2.1.patch

> Hive View : Add Database/Table creation from File
> -
>
> Key: AMBARI-13747
> URL: https://issues.apache.org/jira/browse/AMBARI-13747
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-views
>Affects Versions: 2.1.0
>Reporter: Nitiraj Singh Rathore
>Assignee: Nitiraj Singh Rathore
> Attachments: AMBARI-13747_branch-2.1.patch
>
>
> Hive View should have a widget to:
> Create/Choose a database and create a table inside it
> Create table using a delimited (such as CSV) file from HDFS or local file 
> system
> Discover column names if it has a header
> Discover suggested data types
> Create a table with a given name
> Optionally create an internal table that is ORC by default



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

[jira] [Updated] (AMBARI-13741) API call to delete service fails with error: integrity constraint violated - child record found

[Sebastian Toader (JIRA)]

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

Sebastian Toader updated AMBARI-13741:
--
Attachment: AMBARI-13741.v1.patch

> API call to delete service fails with error: integrity constraint violated - 
> child record found
> ---
>
> Key: AMBARI-13741
> URL: https://issues.apache.org/jira/browse/AMBARI-13741
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
> Attachments: AMBARI-13741.v1.patch
>
>
> Deleting a service from existing cluster using REST API 
> (https://cwiki.apache.org/confluence/display/AMBARI/Using+APIs+to+delete+a+service+or+all+host+components+on+a+host)
>  fails with the below error:
> Call: DELETE FROM clusterservice Where ((cluster_id = ?) AND (service_name = 
> ?))
> Caused by: ... ORA-02292 integrity constraint violated - child record found



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

[jira] [Updated] (AMBARI-13745) Unit test test_recommendAmsConfigurations fails

[Dmytro Sen (JIRA)]

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

Dmytro Sen updated AMBARI-13745:

Attachment: AMBARI-13745-trunk.patch

> Unit test test_recommendAmsConfigurations fails
> ---
>
> Key: AMBARI-13745
> URL: https://issues.apache.org/jira/browse/AMBARI-13745
> Project: Ambari
>  Issue Type: Bug
>  Components: test
>Affects Versions: 2.1.3
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
> Fix For: 2.1.3
>
> Attachments: AMBARI-13745-trunk.patch
>
>
> {code}
> FAIL: test_recommendAmsConfigurations 
> (test_stack_advisor.TestHDP22StackAdvisor)
> --
> Traceback (most recent call last):
>   File 
> "/home/dmitry/ambari/ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py",
>  line 2159, in test_recommendAmsConfigurations
> self.assertEquals(configurations, expected)
> AssertionError: {'ams-env': {'properties': {'metrics_collector_heapsize': 
> '640'}}, 'ams-hbase-en [truncated]... != {'ams-env': {'properties': 
> {'metrics_collector_heapsize': '640'}}, 'ams-hbase-en [truncated]...
>   {'ams-env': {'properties': {'metrics_collector_heapsize': '640'}},
>'ams-hbase-env': {'properties': {'hbase_master_heapsize': '4096',
> 'hbase_master_xmn_size': '448'}},
>'ams-hbase-site': {'properties': {'hbase.hregion.memstore.flush.size': 
> '134217728',
>  
> 'hbase.regionserver.global.memstore.lowerLimit': '0.3',
>  
> 'hbase.regionserver.global.memstore.upperLimit': '0.35',
>  'hbase.rootdir': 
> 'file:///var/lib/ambari-metrics-collector/hbase',
>  'hbase.tmp.dir': 
> '/var/lib/ambari-metrics-collector/hbase-tmp',
>  'hfile.block.cache.size': '0.3',
>  
> 'phoenix.coprocessor.maxMetaDataCacheSize': '2048'}},
>'ams-site': {'properties': 
> {'timeline.metrics.cluster.aggregate.splitpoints': ' ',
> -  'timeline.metrics.host.aggregate.splitpoints': 
> 'master.Server.numDeadRegionServers',
> +  'timeline.metrics.host.aggregate.splitpoints': 
> 'jvm.JvmMetrics.MemHeapCommittedM,regionserver.Server.Increment_median',
>'timeline.metrics.host.aggregator.ttl': 
> '86400'}}}
> --
> Total run:862
> Total errors:0
> Total failures:1
> ERROR
> {code}



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

Review Request 39977: API call to delete service fails with error: integrity constraint violated - child record found

[Sebastian Toader]

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

Review request for Ambari, Jonathan Hurley and Robert Levas.


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


Repository: ambari


Description
---

Deleting a service from existing cluster using REST API 
(https://cwiki.apache.org/confluence/display/AMBARI/Using+APIs+to+delete+a+service+or+all+host+components+on+a+host)
 fails with the below error:

Call: DELETE FROM clusterservice Where ((cluster_id = ?) AND (service_name = ?))
Caused by: ... ORA-02292 integrity constraint violated - child record found


Diffs
-

  
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ClusterServiceEntity.java
 d34e2d5 
  
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ServiceComponentDesiredStateEntity.java
 4195710 
  
ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
 898aa33 
  
ambari-server/src/main/java/org/apache/ambari/server/state/svccomphost/ServiceComponentHostImpl.java
 c0804ff 
  
ambari-server/src/test/java/org/apache/ambari/server/state/cluster/ClusterImplTest.java
 39431ed 

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


Testing
---

Manual testing:

1. Created a simple 3 node cluster uzing the wizzard
2. Deleted a service using REST API
3. Verified that affected records were deleted from the following tables: 
clusterservices, servicedesiredstate, servicecomponentdesiredstate, 
hostcomponentstate, hostcomponentdesiredstate
4. Refresh UI than re-add the deleted service.

 
Unit tests:
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 1:11:05.677s
[INFO] Finished at: Thu Nov 05 17:02:51 CET 2015
[INFO] Final Memory: 32M/763M
[INFO] 


Thanks,

Sebastian Toader

[jira] [Commented] (AMBARI-13745) Unit test test_recommendAmsConfigurations fails

[Dmytro Sen (JIRA)]

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

Dmytro Sen commented on AMBARI-13745:
-

{code}
--
Ran 249 tests in 8.477s

OK
--
Total run:830
Total errors:0
Total failures:0
OK
{code}

> Unit test test_recommendAmsConfigurations fails
> ---
>
> Key: AMBARI-13745
> URL: https://issues.apache.org/jira/browse/AMBARI-13745
> Project: Ambari
>  Issue Type: Bug
>  Components: test
>Affects Versions: 2.1.3
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
> Fix For: 2.1.3
>
> Attachments: AMBARI-13745-trunk.patch
>
>
> {code}
> FAIL: test_recommendAmsConfigurations 
> (test_stack_advisor.TestHDP22StackAdvisor)
> --
> Traceback (most recent call last):
>   File 
> "/home/dmitry/ambari/ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py",
>  line 2159, in test_recommendAmsConfigurations
> self.assertEquals(configurations, expected)
> AssertionError: {'ams-env': {'properties': {'metrics_collector_heapsize': 
> '640'}}, 'ams-hbase-en [truncated]... != {'ams-env': {'properties': 
> {'metrics_collector_heapsize': '640'}}, 'ams-hbase-en [truncated]...
>   {'ams-env': {'properties': {'metrics_collector_heapsize': '640'}},
>'ams-hbase-env': {'properties': {'hbase_master_heapsize': '4096',
> 'hbase_master_xmn_size': '448'}},
>'ams-hbase-site': {'properties': {'hbase.hregion.memstore.flush.size': 
> '134217728',
>  
> 'hbase.regionserver.global.memstore.lowerLimit': '0.3',
>  
> 'hbase.regionserver.global.memstore.upperLimit': '0.35',
>  'hbase.rootdir': 
> 'file:///var/lib/ambari-metrics-collector/hbase',
>  'hbase.tmp.dir': 
> '/var/lib/ambari-metrics-collector/hbase-tmp',
>  'hfile.block.cache.size': '0.3',
>  
> 'phoenix.coprocessor.maxMetaDataCacheSize': '2048'}},
>'ams-site': {'properties': 
> {'timeline.metrics.cluster.aggregate.splitpoints': ' ',
> -  'timeline.metrics.host.aggregate.splitpoints': 
> 'master.Server.numDeadRegionServers',
> +  'timeline.metrics.host.aggregate.splitpoints': 
> 'jvm.JvmMetrics.MemHeapCommittedM,regionserver.Server.Increment_median',
>'timeline.metrics.host.aggregator.ttl': 
> '86400'}}}
> --
> Total run:862
> Total errors:0
> Total failures:1
> ERROR
> {code}



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

Re: Review Request 39977: API call to delete service fails with error: integrity constraint violated - child record found

[Alejandro Fernandez]

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

Ship it!


Ship It!

- Alejandro Fernandez


On Nov. 5, 2015, 4:11 p.m., Sebastian Toader wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39977/
> ---
> 
> (Updated Nov. 5, 2015, 4:11 p.m.)
> 
> 
> Review request for Ambari, Jonathan Hurley and Robert Levas.
> 
> 
> Bugs: AMBARI-13741
> https://issues.apache.org/jira/browse/AMBARI-13741
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Deleting a service from existing cluster using REST API 
> (https://cwiki.apache.org/confluence/display/AMBARI/Using+APIs+to+delete+a+service+or+all+host+components+on+a+host)
>  fails with the below error:
> 
> Call: DELETE FROM clusterservice Where ((cluster_id = ?) AND (service_name = 
> ?))
> Caused by: ... ORA-02292 integrity constraint violated - child record found
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ClusterServiceEntity.java
>  d34e2d5 
>   
> ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ServiceComponentDesiredStateEntity.java
>  4195710 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
>  898aa33 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/svccomphost/ServiceComponentHostImpl.java
>  c0804ff 
>   
> ambari-server/src/test/java/org/apache/ambari/server/state/cluster/ClusterImplTest.java
>  39431ed 
> 
> Diff: https://reviews.apache.org/r/39977/diff/
> 
> 
> Testing
> ---
> 
> Manual testing:
> 
> 1. Created a simple 3 node cluster uzing the wizzard
> 2. Deleted a service using REST API
> 3. Verified that affected records were deleted from the following tables: 
> clusterservices, servicedesiredstate, servicecomponentdesiredstate, 
> hostcomponentstate, hostcomponentdesiredstate
> 4. Refresh UI than re-add the deleted service.
> 
>  
> Unit tests:
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 1:11:05.677s
> [INFO] Finished at: Thu Nov 05 17:02:51 CET 2015
> [INFO] Final Memory: 32M/763M
> [INFO] 
> 
> 
> 
> Thanks,
> 
> Sebastian Toader
> 
>

Review Request 39980: Hive View : Add Database/Table creation from File

[Nitiraj Rathore]

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

Review request for Ambari, Srimanth Gunturi, Sid Wagle, and Yusaku Sako.


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


Repository: ambari


Description
---

Hive View should have a widget to:
Create/Choose a database and create a table inside it
Create table using a delimited (such as CSV) file from HDFS or local file system
Discover column names if it has a header
Discover suggested data types
Create a table with a given name
Optionally create an internal table that is ORC by default

Implementation Steps :
User uploads a CSV file. 
Server reads the input stream and without saving parses it to generate preview 
rows and detect datatypes of columns
Server sends table info to the UI.
User can change column names and datatypes and submits table info.
Server creates a table using hive job, and returns job info back.
UI keeps looping for job success.
On Job success UI sends the same file again.
If required the file’s columns are extracted and rest of the input stream is 
given to the HDFS Api for uploading to the hive metastore.
Server returns success or exception.

Changes : 
ColumnDescription : added enum for hive data types.?
ConnectionFactory : Added HdfsApi for connection to HDFS.
package.json : added dependency ember-cli-uploader
bower.json : added dependency ember-uploader": "0.3.9"
view.xml : added resource upload for UploadService

Additions :
  resources/uploads: new packages for upload related classes
ColumnDescriptionImpl : another impl ColumnDescription for better 
handling of data
IParser : Interface for parsers
DataParser : Decorator Parser for hiding internal impls.
CSVParser : for parsing CSV using apache commons-csv
QueryGenerator : class for generating HQL query from given inputs.
UploadService : REST interface for front end

DataParserTest : the test case class for DataParser.

UI
 router.js : added route /upload-table

/app/adapters : 
file-upload : ember uploader customized
upload-table : adapter for REST calls

/controllers : 
 upload-table : controller for handling all activities in 
Upload Table tab

/templates : 
upload-table : template for UI on Upload Tables tab

Minor changes :
Row : added equals and hashcode toString
ParseOptions : Parsing options to be passed to parser
ParseUtils : Utility class
TableInfo : Input to QueryGenerator’s method
  UI
file-upload
navbar-widget : now includes one more tab for upload table
i18n.js : added constants
app.scss : minor change
constants.js : added constants


Diffs
-

  
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/client/ColumnDescription.java
 d7ea560 
  
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/client/ConnectionFactory.java
 82ac1f5 
  contrib/views/hive/src/main/java/org/apache/ambari/view/hive/client/Row.java 
306530a 
  
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/uploads/CSVParser.java
 PRE-CREATION 
  
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/uploads/ColumnDescriptionImpl.java
 PRE-CREATION 
  
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/uploads/DataParser.java
 PRE-CREATION 
  
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/uploads/IParser.java
 PRE-CREATION 
  
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/uploads/ParseOptions.java
 PRE-CREATION 
  
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/uploads/ParseUtils.java
 PRE-CREATION 
  
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/uploads/QueryGenerator.java
 PRE-CREATION 
  
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/uploads/TableInfo.java
 PRE-CREATION 
  
contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/uploads/UploadService.java
 PRE-CREATION 
  contrib/views/hive/src/main/resources/ui/hive-web/app/adapters/file-upload.js 
PRE-CREATION 
  
contrib/views/hive/src/main/resources/ui/hive-web/app/adapters/upload-table.js 
PRE-CREATION 
  
contrib/views/hive/src/main/resources/ui/hive-web/app/components/file-upload.js 
PRE-CREATION 
  
contrib/views/hive/src/main/resources/ui/hive-web/app/components/navbar-widget.js
 c3659cf 
  
contrib/views/hive/src/main/resources/ui/hive-web/app/controllers/upload-table.js
 PRE-CREATION 
  contrib/views/hive/src/main/resources/ui/hive-web/app/initializers/i18n.js 
5ae9b7e 
  contrib/views/hive/src/main/resources/ui/hive-web/app/router.js 5a51b11 
  

Re: Review Request 39979: Unit test test_recommendAmsConfigurations fails

[Vitalyi Brodetskyi]

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

Ship it!


Ship It!

- Vitalyi Brodetskyi


On Лис. 5, 2015, 4:01 після полудня, Dmytro Sen wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39979/
> ---
> 
> (Updated Лис. 5, 2015, 4:01 після полудня)
> 
> 
> Review request for Ambari and Vitalyi Brodetskyi.
> 
> 
> Bugs: AMBARI-13745
> https://issues.apache.org/jira/browse/AMBARI-13745
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> FAIL: test_recommendAmsConfigurations 
> (test_stack_advisor.TestHDP22StackAdvisor)
> --
> Traceback (most recent call last):
>   File 
> "/home/dmitry/ambari/ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py",
>  line 2159, in test_recommendAmsConfigurations
> self.assertEquals(configurations, expected)
> AssertionError: {'ams-env': {'properties': {'metrics_collector_heapsize': 
> '640'}}, 'ams-hbase-en [truncated]... != {'ams-env': {'properties': 
> {'metrics_collector_heapsize': '640'}}, 'ams-hbase-en [truncated]...
>   {'ams-env': {'properties': {'metrics_collector_heapsize': '640'}},
>'ams-hbase-env': {'properties': {'hbase_master_heapsize': '4096',
> 'hbase_master_xmn_size': '448'}},
>'ams-hbase-site': {'properties': {'hbase.hregion.memstore.flush.size': 
> '134217728',
>  
> 'hbase.regionserver.global.memstore.lowerLimit': '0.3',
>  
> 'hbase.regionserver.global.memstore.upperLimit': '0.35',
>  'hbase.rootdir': 
> 'file:///var/lib/ambari-metrics-collector/hbase',
>  'hbase.tmp.dir': 
> '/var/lib/ambari-metrics-collector/hbase-tmp',
>  'hfile.block.cache.size': '0.3',
>  
> 'phoenix.coprocessor.maxMetaDataCacheSize': '2048'}},
>'ams-site': {'properties': 
> {'timeline.metrics.cluster.aggregate.splitpoints': ' ',
> -  'timeline.metrics.host.aggregate.splitpoints': 
> 'master.Server.numDeadRegionServers',
> +  'timeline.metrics.host.aggregate.splitpoints': 
> 'jvm.JvmMetrics.MemHeapCommittedM,regionserver.Server.Increment_median',
>'timeline.metrics.host.aggregator.ttl': 
> '86400'}}}
> 
> --
> Total run:862
> Total errors:0
> Total failures:1
> ERROR
> 
> 
> Diffs
> -
> 
>   ambari-server/src/test/python/stacks/2.1/TEZ/test_service_check.py 5b3d9f4 
>   ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py 
> a5a588f 
> 
> Diff: https://reviews.apache.org/r/39979/diff/
> 
> 
> Testing
> ---
> 
> --
> Ran 249 tests in 8.477s
> 
> OK
> --
> Total run:830
> Total errors:0
> Total failures:0
> OK
> 
> 
> Thanks,
> 
> Dmytro Sen
> 
>

[jira] [Created] (AMBARI-13747) Hive View : Add Database/Table creation from File

[Nitiraj Singh Rathore (JIRA)]

Nitiraj Singh Rathore created AMBARI-13747:
--

 Summary: Hive View : Add Database/Table creation from File
 Key: AMBARI-13747
 URL: https://issues.apache.org/jira/browse/AMBARI-13747
 Project: Ambari
  Issue Type: Task
  Components: ambari-views
Affects Versions: 2.1.0
Reporter: Nitiraj Singh Rathore
Assignee: Nitiraj Singh Rathore


Hive View should have a widget to:
Create/Choose a database and create a table inside it
Create table using a delimited (such as CSV) file from HDFS or local file system
Discover column names if it has a header
Discover suggested data types
Create a table with a given name
Optionally create an internal table that is ORC by default



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

Re: Review Request 39977: API call to delete service fails with error: integrity constraint violated - child record found

[Robert Levas]

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

Ship it!


Ship It!


ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
 (line 1955)


Can this be JavaDoc-ed so we know why this method was added?


- Robert Levas


On Nov. 5, 2015, 11:11 a.m., Sebastian Toader wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39977/
> ---
> 
> (Updated Nov. 5, 2015, 11:11 a.m.)
> 
> 
> Review request for Ambari, Jonathan Hurley and Robert Levas.
> 
> 
> Bugs: AMBARI-13741
> https://issues.apache.org/jira/browse/AMBARI-13741
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Deleting a service from existing cluster using REST API 
> (https://cwiki.apache.org/confluence/display/AMBARI/Using+APIs+to+delete+a+service+or+all+host+components+on+a+host)
>  fails with the below error:
> 
> Call: DELETE FROM clusterservice Where ((cluster_id = ?) AND (service_name = 
> ?))
> Caused by: ... ORA-02292 integrity constraint violated - child record found
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ClusterServiceEntity.java
>  d34e2d5 
>   
> ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ServiceComponentDesiredStateEntity.java
>  4195710 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
>  898aa33 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/svccomphost/ServiceComponentHostImpl.java
>  c0804ff 
>   
> ambari-server/src/test/java/org/apache/ambari/server/state/cluster/ClusterImplTest.java
>  39431ed 
> 
> Diff: https://reviews.apache.org/r/39977/diff/
> 
> 
> Testing
> ---
> 
> Manual testing:
> 
> 1. Created a simple 3 node cluster uzing the wizzard
> 2. Deleted a service using REST API
> 3. Verified that affected records were deleted from the following tables: 
> clusterservices, servicedesiredstate, servicecomponentdesiredstate, 
> hostcomponentstate, hostcomponentdesiredstate
> 4. Refresh UI than re-add the deleted service.
> 
>  
> Unit tests:
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 1:11:05.677s
> [INFO] Finished at: Thu Nov 05 17:02:51 CET 2015
> [INFO] Final Memory: 32M/763M
> [INFO] 
> 
> 
> 
> Thanks,
> 
> Sebastian Toader
> 
>

[jira] [Commented] (AMBARI-13742) Flume Agent metrics graphs issues

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13742:
-

FAILURE: Integrated in Ambari-trunk-Commit #3777 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3777/])
AMBARI-13742. Flume Agent metrics graphs issues (hiveww: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c62f4416305277b4f8929eb5243d616773c8f315])
* ambari-web/app/assets/test/tests.js
* ambari-web/app/styles/application.less
* ambari-web/app/views.js
* 
ambari-web/app/views/main/service/info/metrics/flume/flume_agent_metrics_section.js
* 
ambari-web/app/templates/main/service/info/metrics/flume/flume_agent_metrics_section.hbs
* 
ambari-web/test/views/main/service/info/metrics/flume/flume_agent_metrics_section_test.js
* ambari-web/app/views/main/service/services/flume.js
* ambari-web/app/templates/main/service/info/summary.hbs


> Flume Agent metrics graphs issues
> -
>
> Key: AMBARI-13742
> URL: https://issues.apache.org/jira/browse/AMBARI-13742
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.3
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13742.patch
>
>
> # For graphs in the bottom row of every section, dropdown list with format 
> names is almost entirely hidden (except a little upper part of 'CSV' item).
> # No time period controls are present.



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

[jira] [Commented] (AMBARI-13711) AMS HBase prinicpals for Master and RS need to have the same value

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13711:
-

FAILURE: Integrated in Ambari-trunk-Commit #3777 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3777/])
AMBARI-13711 AMS HBase prinicpals for Master and RS need to have the (dsen: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=abd6fb589ae6cfb84782f1d275b90e3ec528ecc8])
* 
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/kerberos.json


> AMS HBase prinicpals for Master and RS need to have the same value
> --
>
> Key: AMBARI-13711
> URL: https://issues.apache.org/jira/browse/AMBARI-13711
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics, security
>Affects Versions: 2.1.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13711.patch
>
>
> Zookeeper ACLs not allow znode created using one principal to be read by the 
> other unless proper ACL are set. 
> Error trace:
> {code}
> 2015-10-19 09:13:04,145 WARN  [main-EventThread] zookeeper.ZKUtil: 
> regionserver:61320-0x1507f5f87460001, quorum=host1:61181, 
> baseZNode=/ams-hbase Unable to get data of znode /ams-hbase/running
> org.apache.zookeeper.KeeperException$NoAuthException: KeeperErrorCode = 
> NoAuth for /ams-hbase/running
> at 
> org.apache.zookeeper.KeeperException.create(KeeperException.java:113)
> {code}



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

[jira] [Commented] (AMBARI-13739) RESTART ZOOKEEPER_SERVER failed after Upgrade from 1.6.1 to 2.1.3

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13739:
-

FAILURE: Integrated in Ambari-trunk-Commit #3777 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3777/])
AMBARI-13739. RESTART ZOOKEEPER_SERVER failed after Upgrade from 1.6.1 
(vbrodetskyi: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6c39604268c67989e7a87a66e3a12f1562b6bb42])
* 
ambari-server/src/main/resources/common-services/ZOOKEEPER/3.4.5.2.0/package/scripts/zookeeper_service.py
* 
ambari-server/src/main/resources/common-services/ZOOKEEPER/3.4.5.2.0/package/scripts/zookeeper.py


> RESTART ZOOKEEPER_SERVER failed after Upgrade from 1.6.1 to 2.1.3
> -
>
> Key: AMBARI-13739
> URL: https://issues.apache.org/jira/browse/AMBARI-13739
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.3
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.1.3
>
> Attachments: AMBARI-13739.patch
>
>
> STR:
> 1)Deploy old version 1.6.1
> 2)Enable/Disable security (MIT)
> 3)Make Ambari only upgrade to 2.1.3
> Actual results:
> RESTART ZOOKEEPER_SERVER failed after Upgrade from 1.6.1 to 2.1.3
> {code}
>   {
>   "href" : 
> "http://172.22.87.177:8080/api/v1/clusters/cl1/requests/11/tasks/501;,
>   "Tasks" : {
> "attempt_cnt" : 1,
> "cluster_name" : "cl1",
> "command" : "CUSTOM_COMMAND",
> "command_detail" : "RESTART ZOOKEEPER/ZOOKEEPER_SERVER",
> "custom_command_name" : "RESTART",
> "end_time" : 1446626534832,
> "error_log" : "/var/lib/ambari-agent/data/errors-501.txt",
> "exit_code" : 1,
> "host_name" : "amb-upg161-rhel6mysql1446600673-3.novalocal",
> "id" : 501,
> "output_log" : "/var/lib/ambari-agent/data/output-501.txt",
> "request_id" : 11,
> "role" : "ZOOKEEPER_SERVER",
> "stage_id" : 0,
> "start_time" : 1446626531540,
> "status" : "FAILED",
> "stderr" : "Traceback (most recent call last):\n  File 
> \"/var/lib/ambari-agent/cache/common-services/ZOOKEEPER/3.4.5.2.0/package/scripts/zookeeper_server.py\",
>  line 179, in \nZookeeperServer().execute()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
>  line 218, in execute\nmethod(env)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
>  line 486, in restart\nself.stop(env, upgrade_type=upgrade_type)\n  File 
> \"/var/lib/ambari-agent/cache/common-services/ZOOKEEPER/3.4.5.2.0/package/scripts/zookeeper_server.py\",
>  line 60, in stop\nzookeeper_service(action='stop', 
> upgrade_type=upgrade_type)\n  File 
> \"/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py\", line 
> 89, in thunk\nreturn fn(*args, **kwargs)\n  File 
> \"/var/lib/ambari-agent/cache/common-services/ZOOKEEPER/3.4.5.2.0/package/scripts/zookeeper_service.py\",
>  line 36, in zookeeper_service\nhdp_select.select(\"zookeeper-server\", 
> params.version)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/hdp_select.py\",
>  line 116, in select\nExecute(command, sudo=True)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line 
> 154, in __init__\nself.env.run()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", 
> line 156, in run\nself.run_action(resource, action)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", 
> line 119, in run_action\nprovider_action()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
>  line 238, in action_run\ntries=self.resource.tries, 
> try_sleep=self.resource.try_sleep)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 70, in inner\nresult = function(command, **kwargs)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 92, in checked_call\ntries=tries, try_sleep=try_sleep)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 140, in _call_wrapper\nresult = _call(command, **kwargs_copy)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 291, in _call\nraise 
> Fail(err_msg)\nresource_management.core.exceptions.Fail: Execution of 
> 'hdp-select set zookeeper-server 2.1.0.0-0001' returned 127. 
> /var/lib/ambari-agent/ambari-sudo.sh: line 50: hdp-select: command not found",
> "stdout" : "2015-11-04 08:42:14,133 - Group['hadoop'] {}\n2015-11-04 
> 08:42:14,135 - Group['nobody'] {}\n2015-11-04 08:42:14,135 - 

[jira] [Resolved] (AMBARI-13717) Couldn`t start the most of services after upgrade from 2.1.2 to 2.1.3.0 (Debian7)

[Andrew Onischuk (JIRA)]

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

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

Committed to trunk and branch-2.1

> Couldn`t start the most of services after upgrade from 2.1.2 to 2.1.3.0 
> (Debian7)
> -
>
> Key: AMBARI-13717
> URL: https://issues.apache.org/jira/browse/AMBARI-13717
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.1.3
>
>
> STR:  
> 1)Deploy old version 2.1.2  
> 2)Make Ambari only upgrade to 2.1.3  
> 4)Try to start All services  
> Actual results:  
> Couldn`t start the most of services after upgrade (FALCON, FLUME,
> HISTORYSERVER, KNOX_GATEWAY, MC, NAMENODE, NM etc..)  
> **Details are in Last available request file - attached**



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

Re: Review Request 39978: Ranger Plugin Enabling not working in 2.2 because of a stack_advisor error

[Dmytro Sen]

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

Ship it!


Ship It!

- Dmytro Sen


On Ноя. 5, 2015, 3:55 п.п., Vitalyi Brodetskyi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39978/
> ---
> 
> (Updated Ноя. 5, 2015, 3:55 п.п.)
> 
> 
> Review request for Ambari and Dmytro Sen.
> 
> 
> Bugs: AMBARI-13746
> https://issues.apache.org/jira/browse/AMBARI-13746
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Getting below error in stack_advisor
> {noformat}
> Traceback (most recent call last):
>   File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 158, 
> in 
> main(sys.argv)
>   File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 115, 
> in main
> result = stackAdvisor.validateConfigurations(services, hosts)
>   File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py", 
> line 463, in validateConfigurations
> validationItems = self.getConfigurationsValidationItems(services, hosts)
>   File 
> "/var/lib/ambari-server/resources/scripts/./../stacks/HDP/2.0.6/services/stack_advisor.py",
>  line 706, in getConfigurationsValidationItems
> recommendations = self.recommendConfigurations(services, hosts)
>   File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py", 
> line 569, in recommendConfigurations
> calculation(configurations, clusterSummary, services, hosts)
>   File 
> "/var/lib/ambari-server/resources/scripts/./../stacks/HDP/2.2/services/stack_advisor.py",
>  line 782, in recommendStormConfigurations
> core_site = services["configurations"]["core-site"]["properties"]
> KeyError: 'core-site'
> {noformat}
> 
> 
> Diffs
> -
> 
>   ambari-server/src/main/resources/stacks/HDP/2.2/services/stack_advisor.py 
> 8238481 
>   ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py 
> a5a588f 
> 
> Diff: https://reviews.apache.org/r/39978/diff/
> 
> 
> Testing
> ---
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Vitalyi Brodetskyi
> 
>

[jira] [Commented] (AMBARI-13739) RESTART ZOOKEEPER_SERVER failed after Upgrade from 1.6.1 to 2.1.3

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13739:
-

FAILURE: Integrated in Ambari-branch-2.1 #805 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/805/])
AMBARI-13739. RESTART ZOOKEEPER_SERVER failed after Upgrade from 1.6.1 
(vbrodetskyi: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b4b7df682736809b7d5dedc0e70b4670eea3b748])
* 
ambari-server/src/main/resources/common-services/ZOOKEEPER/3.4.5.2.0/package/scripts/zookeeper_service.py
* 
ambari-server/src/main/resources/common-services/ZOOKEEPER/3.4.5.2.0/package/scripts/zookeeper.py


> RESTART ZOOKEEPER_SERVER failed after Upgrade from 1.6.1 to 2.1.3
> -
>
> Key: AMBARI-13739
> URL: https://issues.apache.org/jira/browse/AMBARI-13739
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.3
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.1.3
>
> Attachments: AMBARI-13739.patch
>
>
> STR:
> 1)Deploy old version 1.6.1
> 2)Enable/Disable security (MIT)
> 3)Make Ambari only upgrade to 2.1.3
> Actual results:
> RESTART ZOOKEEPER_SERVER failed after Upgrade from 1.6.1 to 2.1.3
> {code}
>   {
>   "href" : 
> "http://172.22.87.177:8080/api/v1/clusters/cl1/requests/11/tasks/501;,
>   "Tasks" : {
> "attempt_cnt" : 1,
> "cluster_name" : "cl1",
> "command" : "CUSTOM_COMMAND",
> "command_detail" : "RESTART ZOOKEEPER/ZOOKEEPER_SERVER",
> "custom_command_name" : "RESTART",
> "end_time" : 1446626534832,
> "error_log" : "/var/lib/ambari-agent/data/errors-501.txt",
> "exit_code" : 1,
> "host_name" : "amb-upg161-rhel6mysql1446600673-3.novalocal",
> "id" : 501,
> "output_log" : "/var/lib/ambari-agent/data/output-501.txt",
> "request_id" : 11,
> "role" : "ZOOKEEPER_SERVER",
> "stage_id" : 0,
> "start_time" : 1446626531540,
> "status" : "FAILED",
> "stderr" : "Traceback (most recent call last):\n  File 
> \"/var/lib/ambari-agent/cache/common-services/ZOOKEEPER/3.4.5.2.0/package/scripts/zookeeper_server.py\",
>  line 179, in \nZookeeperServer().execute()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
>  line 218, in execute\nmethod(env)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
>  line 486, in restart\nself.stop(env, upgrade_type=upgrade_type)\n  File 
> \"/var/lib/ambari-agent/cache/common-services/ZOOKEEPER/3.4.5.2.0/package/scripts/zookeeper_server.py\",
>  line 60, in stop\nzookeeper_service(action='stop', 
> upgrade_type=upgrade_type)\n  File 
> \"/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py\", line 
> 89, in thunk\nreturn fn(*args, **kwargs)\n  File 
> \"/var/lib/ambari-agent/cache/common-services/ZOOKEEPER/3.4.5.2.0/package/scripts/zookeeper_service.py\",
>  line 36, in zookeeper_service\nhdp_select.select(\"zookeeper-server\", 
> params.version)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/hdp_select.py\",
>  line 116, in select\nExecute(command, sudo=True)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line 
> 154, in __init__\nself.env.run()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", 
> line 156, in run\nself.run_action(resource, action)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", 
> line 119, in run_action\nprovider_action()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
>  line 238, in action_run\ntries=self.resource.tries, 
> try_sleep=self.resource.try_sleep)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 70, in inner\nresult = function(command, **kwargs)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 92, in checked_call\ntries=tries, try_sleep=try_sleep)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 140, in _call_wrapper\nresult = _call(command, **kwargs_copy)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
> 291, in _call\nraise 
> Fail(err_msg)\nresource_management.core.exceptions.Fail: Execution of 
> 'hdp-select set zookeeper-server 2.1.0.0-0001' returned 127. 
> /var/lib/ambari-agent/ambari-sudo.sh: line 50: hdp-select: command not found",
> "stdout" : "2015-11-04 08:42:14,133 - Group['hadoop'] {}\n2015-11-04 
> 08:42:14,135 - Group['nobody'] {}\n2015-11-04 08:42:14,135 - 

[jira] [Commented] (AMBARI-13742) Flume Agent metrics graphs issues

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13742:
-

FAILURE: Integrated in Ambari-branch-2.1 #805 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/805/])
AMBARI-13742. Flume Agent metrics graphs issues (hiveww: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ade07b3afc7fd774dee7603c02524d949af9e83f])
* ambari-web/app/assets/test/tests.js
* 
ambari-web/app/views/main/service/info/metrics/flume/flume_agent_metrics_section.js
* 
ambari-web/test/views/main/service/info/metrics/flume/flume_agent_metrics_section_test.js
* ambari-web/app/views.js
* ambari-web/app/styles/application.less
* ambari-web/app/templates/main/service/info/summary.hbs
* ambari-web/app/views/main/service/services/flume.js
* 
ambari-web/app/templates/main/service/info/metrics/flume/flume_agent_metrics_section.hbs


> Flume Agent metrics graphs issues
> -
>
> Key: AMBARI-13742
> URL: https://issues.apache.org/jira/browse/AMBARI-13742
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.3
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13742.patch
>
>
> # For graphs in the bottom row of every section, dropdown list with format 
> names is almost entirely hidden (except a little upper part of 'CSV' item).
> # No time period controls are present.



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

Review Request 39979: Unit test test_recommendAmsConfigurations fails

[Dmytro Sen]

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

Review request for Ambari and Vitalyi Brodetskyi.


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


Repository: ambari


Description
---

FAIL: test_recommendAmsConfigurations (test_stack_advisor.TestHDP22StackAdvisor)
--
Traceback (most recent call last):
  File 
"/home/dmitry/ambari/ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py",
 line 2159, in test_recommendAmsConfigurations
self.assertEquals(configurations, expected)
AssertionError: {'ams-env': {'properties': {'metrics_collector_heapsize': 
'640'}}, 'ams-hbase-en [truncated]... != {'ams-env': {'properties': 
{'metrics_collector_heapsize': '640'}}, 'ams-hbase-en [truncated]...
  {'ams-env': {'properties': {'metrics_collector_heapsize': '640'}},
   'ams-hbase-env': {'properties': {'hbase_master_heapsize': '4096',
'hbase_master_xmn_size': '448'}},
   'ams-hbase-site': {'properties': {'hbase.hregion.memstore.flush.size': 
'134217728',
 
'hbase.regionserver.global.memstore.lowerLimit': '0.3',
 
'hbase.regionserver.global.memstore.upperLimit': '0.35',
 'hbase.rootdir': 
'file:///var/lib/ambari-metrics-collector/hbase',
 'hbase.tmp.dir': 
'/var/lib/ambari-metrics-collector/hbase-tmp',
 'hfile.block.cache.size': '0.3',
 
'phoenix.coprocessor.maxMetaDataCacheSize': '2048'}},
   'ams-site': {'properties': 
{'timeline.metrics.cluster.aggregate.splitpoints': ' ',
-  'timeline.metrics.host.aggregate.splitpoints': 
'master.Server.numDeadRegionServers',
+  'timeline.metrics.host.aggregate.splitpoints': 
'jvm.JvmMetrics.MemHeapCommittedM,regionserver.Server.Increment_median',
   'timeline.metrics.host.aggregator.ttl': 
'86400'}}}

--
Total run:862
Total errors:0
Total failures:1
ERROR


Diffs
-

  ambari-server/src/test/python/stacks/2.1/TEZ/test_service_check.py 5b3d9f4 
  ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py a5a588f 

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


Testing
---

--
Ran 249 tests in 8.477s

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


Thanks,

Dmytro Sen

[jira] [Resolved] (AMBARI-13744) Implement ability to retry operations after database exception for blueprint deploy

[Myroslav Papirkovskyy (JIRA)]

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

Myroslav Papirkovskyy resolved AMBARI-13744.

Resolution: Fixed

Pushed to trunk and branch-2.1

> Implement ability to retry operations after database exception for blueprint 
> deploy
> ---
>
> Key: AMBARI-13744
> URL: https://issues.apache.org/jira/browse/AMBARI-13744
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.3
>Reporter: Myroslav Papirkovskyy
>Assignee: Myroslav Papirkovskyy
>Priority: Critical
> Fix For: 2.1.3
>
>
> Jira is related to AMBARI-13663. Same functionality for blueprint-based 
> deploy.



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

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

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-13738:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12770796/AMBARI-13738.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 5 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 ambari-web:

  org.apache.ambari.server.agent.AgentResourceTest

  The test build failed in ambari-web 

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

This message is automatically generated.

> 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)

[jira] [Created] (AMBARI-13749) Hive server 2 fails to start in kerberized environment

[Vitaly Brodetskyi (JIRA)]

Vitaly Brodetskyi created AMBARI-13749:
--

 Summary: Hive server 2 fails to start in kerberized environment
 Key: AMBARI-13749
 URL: https://issues.apache.org/jira/browse/AMBARI-13749
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.1.3
Reporter: Vitaly Brodetskyi
Assignee: Vitaly Brodetskyi
Priority: Critical
 Fix For: 2.1.3






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

[jira] [Commented] (AMBARI-13730) Express Upgrade: Add max degree of parallelism to control number of tasks run in parallel

[Jayush Luniya (JIRA)]

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

Jayush Luniya commented on AMBARI-13730:


Branch-2.1
commit 9c85b24391d337600e333eea7aa1182744e4550d
Author: Jayush Luniya 
Date:   Thu Nov 5 10:28:26 2015 -0800

AMBARI-13730: Express Upgrade: Add max degree of parallelism to control 
number of tasks run in parallel (jluniya)

Conflicts:

ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/Grouping.java

ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/StageWrapperBuilder.java

> Express Upgrade: Add max degree of parallelism to control number of tasks run 
> in parallel
> -
>
> Key: AMBARI-13730
> URL: https://issues.apache.org/jira/browse/AMBARI-13730
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.2.0, 2.1.3
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.1.3
>
>




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

Re: Review Request 39984: Hive server 2 fails to start in kerberized environment

[Robert Levas]

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

Ship it!


Ship It!

- Robert Levas


On Nov. 5, 2015, 1:28 p.m., Vitalyi Brodetskyi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39984/
> ---
> 
> (Updated Nov. 5, 2015, 1:28 p.m.)
> 
> 
> Review request for Ambari, Andrew Onischuk, Dmytro Sen, Jaimin Jetly, Robert 
> Levas, and Sumit Mohanty.
> 
> 
> Bugs: AMBARI-13749
> https://issues.apache.org/jira/browse/AMBARI-13749
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> HS2 fails to start on kerberized cluster, for stack 2.2.4.2.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_service.py
>  456c018 
>   ambari-server/src/test/python/stacks/2.0.6/HIVE/test_hive_server.py ed20c96 
>   ambari-server/src/test/python/stacks/2.0.6/configs/secured.json a2c41e4 
> 
> Diff: https://reviews.apache.org/r/39984/diff/
> 
> 
> Testing
> ---
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Vitalyi Brodetskyi
> 
>

[jira] [Commented] (AMBARI-13745) Unit test test_recommendAmsConfigurations fails

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13745:
-

SUCCESS: Integrated in Ambari-branch-2.1 #806 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/806/])
AMBARI-13745 Unit test test_recommendAmsConfigurations fails (dsen) (dsen: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4f8cb0fa0d33f51e7df93e6c1e1a70f76c14d04b])
* ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py
* ambari-server/src/test/python/stacks/2.1/TEZ/test_service_check.py


> Unit test test_recommendAmsConfigurations fails
> ---
>
> Key: AMBARI-13745
> URL: https://issues.apache.org/jira/browse/AMBARI-13745
> Project: Ambari
>  Issue Type: Bug
>  Components: test
>Affects Versions: 2.1.3
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
> Fix For: 2.1.3
>
> Attachments: AMBARI-13745-trunk.patch
>
>
> {code}
> FAIL: test_recommendAmsConfigurations 
> (test_stack_advisor.TestHDP22StackAdvisor)
> --
> Traceback (most recent call last):
>   File 
> "/home/dmitry/ambari/ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py",
>  line 2159, in test_recommendAmsConfigurations
> self.assertEquals(configurations, expected)
> AssertionError: {'ams-env': {'properties': {'metrics_collector_heapsize': 
> '640'}}, 'ams-hbase-en [truncated]... != {'ams-env': {'properties': 
> {'metrics_collector_heapsize': '640'}}, 'ams-hbase-en [truncated]...
>   {'ams-env': {'properties': {'metrics_collector_heapsize': '640'}},
>'ams-hbase-env': {'properties': {'hbase_master_heapsize': '4096',
> 'hbase_master_xmn_size': '448'}},
>'ams-hbase-site': {'properties': {'hbase.hregion.memstore.flush.size': 
> '134217728',
>  
> 'hbase.regionserver.global.memstore.lowerLimit': '0.3',
>  
> 'hbase.regionserver.global.memstore.upperLimit': '0.35',
>  'hbase.rootdir': 
> 'file:///var/lib/ambari-metrics-collector/hbase',
>  'hbase.tmp.dir': 
> '/var/lib/ambari-metrics-collector/hbase-tmp',
>  'hfile.block.cache.size': '0.3',
>  
> 'phoenix.coprocessor.maxMetaDataCacheSize': '2048'}},
>'ams-site': {'properties': 
> {'timeline.metrics.cluster.aggregate.splitpoints': ' ',
> -  'timeline.metrics.host.aggregate.splitpoints': 
> 'master.Server.numDeadRegionServers',
> +  'timeline.metrics.host.aggregate.splitpoints': 
> 'jvm.JvmMetrics.MemHeapCommittedM,regionserver.Server.Increment_median',
>'timeline.metrics.host.aggregator.ttl': 
> '86400'}}}
> --
> Total run:862
> Total errors:0
> Total failures:1
> ERROR
> {code}



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

[jira] [Commented] (AMBARI-13746) Ranger Plugin Enabling not working in 2.2 because of a stack_advisor error

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13746:
-

SUCCESS: Integrated in Ambari-branch-2.1 #806 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/806/])
AMBARI-13746. Ranger Plugin Enabling not working in 2.2 because of a 
(vbrodetskyi: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8261a8d8c0ff5cbe45a003aeca088338f5f7f080])
* ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py
* ambari-server/src/main/resources/stacks/HDP/2.2/services/stack_advisor.py


> Ranger Plugin Enabling not working in 2.2 because of a stack_advisor error
> --
>
> Key: AMBARI-13746
> URL: https://issues.apache.org/jira/browse/AMBARI-13746
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.3
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13746.patch
>
>
> Getting below error in stack_advisor
> {noformat}
> Traceback (most recent call last):
>   File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 158, 
> in 
> main(sys.argv)
>   File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 115, 
> in main
> result = stackAdvisor.validateConfigurations(services, hosts)
>   File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py", 
> line 463, in validateConfigurations
> validationItems = self.getConfigurationsValidationItems(services, hosts)
>   File 
> "/var/lib/ambari-server/resources/scripts/./../stacks/HDP/2.0.6/services/stack_advisor.py",
>  line 706, in getConfigurationsValidationItems
> recommendations = self.recommendConfigurations(services, hosts)
>   File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py", 
> line 569, in recommendConfigurations
> calculation(configurations, clusterSummary, services, hosts)
>   File 
> "/var/lib/ambari-server/resources/scripts/./../stacks/HDP/2.2/services/stack_advisor.py",
>  line 782, in recommendStormConfigurations
> core_site = services["configurations"]["core-site"]["properties"]
> KeyError: 'core-site'
> {noformat}



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

[jira] [Updated] (AMBARI-13721) Ambari functional tests infrastructure

[Nahappan Somasundaram (JIRA)]

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

Nahappan Somasundaram updated AMBARI-13721:
---
Description: 
Run a test version of the ambari-server with an in-memory DB and ambari-agent 
that run during the functional testing and cover several basic use cases  like 
heartbeat monitoring, adding and deleting services, components, hosts, etc.

** Functional test design: **
The functional tests run the same way as unit tests, using JUnit 
Enabling/disabling of the functional tests can be done using a Maven 
configuration. 
The building blocks of the functional tests are: 
A local ambari server that wraps the actual AmbariServer implementation with 
Guice to instantiate an in-memory database (use the existing 
InMemoryDefaultTestModule class) 
Methods to set up a default cluster with a few hosts, with each host running 
components like Ambari Metrics Service, HDFS, YARN and Zookeeper. These methods 
use the ambari server's RESTful APIs. 
Methods that use HttpClient to perform operations using the RESTful APIs to 
add/remove cluster, hosts, services, service components and service component 
hosts. 
A simple functional test to start the local server on a thread, get status from 
the server and then shutdown. 
Additional unit tests can be built on top of the start-status check-stop 
functional tests, default cluster setup method and helper methods to test 
specific scenarios. 
 
Future work: 
Local ambari agent simulator for each host.

  was:
Run a test version of the ambari-server with an in-memory DB and ambari-agent 
that run during the functional testing and cover several basic use cases  like 
heartbeat monitoring, adding and deleting services, components, hosts, etc.

Functional test design: 
The functional tests run the same way as unit tests, using JUnit 
Enabling/disabling of the functional tests can be done using a Maven 
configuration. 
The building blocks of the functional tests are: 
A local ambari server that wraps the actual AmbariServer implementation with 
Guice to instantiate an in-memory database (use the existing 
InMemoryDefaultTestModule class) 
Methods to set up a default cluster with a few hosts, with each host running 
components like Ambari Metrics Service, HDFS, YARN and Zookeeper. These methods 
use the ambari server's RESTful APIs. 
Methods that use HttpClient to perform operations using the RESTful APIs to 
add/remove cluster, hosts, services, service components and service component 
hosts. 
A simple functional test to start the local server on a thread, get status from 
the server and then shutdown. 
Additional unit tests can be built on top of the start-status check-stop 
functional tests, default cluster setup method and helper methods to test 
specific scenarios. 
 
Future work: 
Local ambari agent simulator for each host.


> Ambari functional tests infrastructure
> --
>
> Key: AMBARI-13721
> URL: https://issues.apache.org/jira/browse/AMBARI-13721
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.1.3
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.1.3
>
>
> Run a test version of the ambari-server with an in-memory DB and ambari-agent 
> that run during the functional testing and cover several basic use cases  
> like heartbeat monitoring, adding and deleting services, components, hosts, 
> etc.
> ** Functional test design: **
> The functional tests run the same way as unit tests, using JUnit 
> Enabling/disabling of the functional tests can be done using a Maven 
> configuration. 
> The building blocks of the functional tests are: 
> A local ambari server that wraps the actual AmbariServer implementation with 
> Guice to instantiate an in-memory database (use the existing 
> InMemoryDefaultTestModule class) 
> Methods to set up a default cluster with a few hosts, with each host running 
> components like Ambari Metrics Service, HDFS, YARN and Zookeeper. These 
> methods use the ambari server's RESTful APIs. 
> Methods that use HttpClient to perform operations using the RESTful APIs to 
> add/remove cluster, hosts, services, service components and service component 
> hosts. 
> A simple functional test to start the local server on a thread, get status 
> from the server and then shutdown. 
> Additional unit tests can be built on top of the start-status check-stop 
> functional tests, default cluster setup method and helper methods to test 
> specific scenarios. 
>  
> Future work: 
> Local ambari agent simulator for each host.



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

Review Request 39984: Hive server 2 fails to start in kerberized environment

[Vitalyi Brodetskyi]

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

Review request for Ambari, Andrew Onischuk, Dmytro Sen, Jaimin Jetly, Robert 
Levas, and Sumit Mohanty.


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


Repository: ambari


Description
---

HS2 fails to start on kerberized cluster, for stack 2.2.4.2.


Diffs
-

  
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_service.py
 456c018 
  ambari-server/src/test/python/stacks/2.0.6/HIVE/test_hive_server.py ed20c96 
  ambari-server/src/test/python/stacks/2.0.6/configs/secured.json a2c41e4 

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


Testing
---

mvn clean test


Thanks,

Vitalyi Brodetskyi

[jira] [Commented] (AMBARI-13746) Ranger Plugin Enabling not working in 2.2 because of a stack_advisor error

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13746:
-

FAILURE: Integrated in Ambari-trunk-Commit #3778 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3778/])
AMBARI-13746. Ranger Plugin Enabling not working in 2.2 because of a 
(vbrodetskyi: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4db9a1eefe7ea847f93d7c7c19ee025d8ca638c6])
* ambari-server/src/main/resources/stacks/HDP/2.2/services/stack_advisor.py
* ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py


> Ranger Plugin Enabling not working in 2.2 because of a stack_advisor error
> --
>
> Key: AMBARI-13746
> URL: https://issues.apache.org/jira/browse/AMBARI-13746
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.3
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13746.patch
>
>
> Getting below error in stack_advisor
> {noformat}
> Traceback (most recent call last):
>   File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 158, 
> in 
> main(sys.argv)
>   File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 115, 
> in main
> result = stackAdvisor.validateConfigurations(services, hosts)
>   File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py", 
> line 463, in validateConfigurations
> validationItems = self.getConfigurationsValidationItems(services, hosts)
>   File 
> "/var/lib/ambari-server/resources/scripts/./../stacks/HDP/2.0.6/services/stack_advisor.py",
>  line 706, in getConfigurationsValidationItems
> recommendations = self.recommendConfigurations(services, hosts)
>   File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py", 
> line 569, in recommendConfigurations
> calculation(configurations, clusterSummary, services, hosts)
>   File 
> "/var/lib/ambari-server/resources/scripts/./../stacks/HDP/2.2/services/stack_advisor.py",
>  line 782, in recommendStormConfigurations
> core_site = services["configurations"]["core-site"]["properties"]
> KeyError: 'core-site'
> {noformat}



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

[jira] [Commented] (AMBARI-13745) Unit test test_recommendAmsConfigurations fails

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13745:
-

FAILURE: Integrated in Ambari-trunk-Commit #3778 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3778/])
AMBARI-13745 Unit test test_recommendAmsConfigurations fails (dsen) (dsen: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ab16f41780639b1a1e38061dfd172f7bea77265e])
* ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py
* ambari-server/src/test/python/stacks/2.1/TEZ/test_service_check.py


> Unit test test_recommendAmsConfigurations fails
> ---
>
> Key: AMBARI-13745
> URL: https://issues.apache.org/jira/browse/AMBARI-13745
> Project: Ambari
>  Issue Type: Bug
>  Components: test
>Affects Versions: 2.1.3
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
> Fix For: 2.1.3
>
> Attachments: AMBARI-13745-trunk.patch
>
>
> {code}
> FAIL: test_recommendAmsConfigurations 
> (test_stack_advisor.TestHDP22StackAdvisor)
> --
> Traceback (most recent call last):
>   File 
> "/home/dmitry/ambari/ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py",
>  line 2159, in test_recommendAmsConfigurations
> self.assertEquals(configurations, expected)
> AssertionError: {'ams-env': {'properties': {'metrics_collector_heapsize': 
> '640'}}, 'ams-hbase-en [truncated]... != {'ams-env': {'properties': 
> {'metrics_collector_heapsize': '640'}}, 'ams-hbase-en [truncated]...
>   {'ams-env': {'properties': {'metrics_collector_heapsize': '640'}},
>'ams-hbase-env': {'properties': {'hbase_master_heapsize': '4096',
> 'hbase_master_xmn_size': '448'}},
>'ams-hbase-site': {'properties': {'hbase.hregion.memstore.flush.size': 
> '134217728',
>  
> 'hbase.regionserver.global.memstore.lowerLimit': '0.3',
>  
> 'hbase.regionserver.global.memstore.upperLimit': '0.35',
>  'hbase.rootdir': 
> 'file:///var/lib/ambari-metrics-collector/hbase',
>  'hbase.tmp.dir': 
> '/var/lib/ambari-metrics-collector/hbase-tmp',
>  'hfile.block.cache.size': '0.3',
>  
> 'phoenix.coprocessor.maxMetaDataCacheSize': '2048'}},
>'ams-site': {'properties': 
> {'timeline.metrics.cluster.aggregate.splitpoints': ' ',
> -  'timeline.metrics.host.aggregate.splitpoints': 
> 'master.Server.numDeadRegionServers',
> +  'timeline.metrics.host.aggregate.splitpoints': 
> 'jvm.JvmMetrics.MemHeapCommittedM,regionserver.Server.Increment_median',
>'timeline.metrics.host.aggregator.ttl': 
> '86400'}}}
> --
> Total run:862
> Total errors:0
> Total failures:1
> ERROR
> {code}



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

[jira] [Commented] (AMBARI-13721) Ambari functional tests infrastructure

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty commented on AMBARI-13721:


[~smnaha], it will be a good addition to the test suite. Can you provide some 
general idea of how these can be run - assuming these tests are different than 
the unit tests.

> Ambari functional tests infrastructure
> --
>
> Key: AMBARI-13721
> URL: https://issues.apache.org/jira/browse/AMBARI-13721
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.1.3
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.1.3
>
>
> Run a test version of the ambari-server with an in-memory DB and ambari-agent 
> that run during the functional testing and cover several basic use cases  
> like heartbeat monitoring, adding and deleting services, components, hosts, 
> etc.



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

[jira] [Commented] (AMBARI-13741) API call to delete service fails with error: integrity constraint violated - child record found

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-13741:


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

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

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

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

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

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

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

This message is automatically generated.

> API call to delete service fails with error: integrity constraint violated - 
> child record found
> ---
>
> Key: AMBARI-13741
> URL: https://issues.apache.org/jira/browse/AMBARI-13741
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
> Attachments: AMBARI-13741.v1.patch
>
>
> Deleting a service from existing cluster using REST API 
> (https://cwiki.apache.org/confluence/display/AMBARI/Using+APIs+to+delete+a+service+or+all+host+components+on+a+host)
>  fails with the below error:
> Call: DELETE FROM clusterservice Where ((cluster_id = ?) AND (service_name = 
> ?))
> Caused by: ... ORA-02292 integrity constraint violated - child record found



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

[jira] [Updated] (AMBARI-13721) Ambari functional tests infrastructure

[Nahappan Somasundaram (JIRA)]

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

Nahappan Somasundaram updated AMBARI-13721:
---
Description: 
Run a test version of the ambari-server with an in-memory DB and ambari-agent 
that run during the functional testing and cover several basic use cases  like 
heartbeat monitoring, adding and deleting services, components, hosts, etc.

 ** Functional test design: **
The functional tests run the same way as unit tests, using JUnit 
Enabling/disabling of the functional tests can be done using a Maven 
configuration. 
The building blocks of the functional tests are: 
A local ambari server that wraps the actual AmbariServer implementation with 
Guice to instantiate an in-memory database (use the existing 
InMemoryDefaultTestModule class) 
Methods to set up a default cluster with a few hosts, with each host running 
components like Ambari Metrics Service, HDFS, YARN and Zookeeper. These methods 
use the ambari server's RESTful APIs. 
Methods that use HttpClient to perform operations using the RESTful APIs to 
add/remove cluster, hosts, services, service components and service component 
hosts. 
A simple functional test to start the local server on a thread, get status from 
the server and then shutdown. 
Additional unit tests can be built on top of the start-status check-stop 
functional tests, default cluster setup method and helper methods to test 
specific scenarios. 
 
Future work: 
Local ambari agent simulator for each host.

  was:
Run a test version of the ambari-server with an in-memory DB and ambari-agent 
that run during the functional testing and cover several basic use cases  like 
heartbeat monitoring, adding and deleting services, components, hosts, etc.

** Functional test design: **
The functional tests run the same way as unit tests, using JUnit 
Enabling/disabling of the functional tests can be done using a Maven 
configuration. 
The building blocks of the functional tests are: 
A local ambari server that wraps the actual AmbariServer implementation with 
Guice to instantiate an in-memory database (use the existing 
InMemoryDefaultTestModule class) 
Methods to set up a default cluster with a few hosts, with each host running 
components like Ambari Metrics Service, HDFS, YARN and Zookeeper. These methods 
use the ambari server's RESTful APIs. 
Methods that use HttpClient to perform operations using the RESTful APIs to 
add/remove cluster, hosts, services, service components and service component 
hosts. 
A simple functional test to start the local server on a thread, get status from 
the server and then shutdown. 
Additional unit tests can be built on top of the start-status check-stop 
functional tests, default cluster setup method and helper methods to test 
specific scenarios. 
 
Future work: 
Local ambari agent simulator for each host.


> Ambari functional tests infrastructure
> --
>
> Key: AMBARI-13721
> URL: https://issues.apache.org/jira/browse/AMBARI-13721
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.1.3
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.1.3
>
>
> Run a test version of the ambari-server with an in-memory DB and ambari-agent 
> that run during the functional testing and cover several basic use cases  
> like heartbeat monitoring, adding and deleting services, components, hosts, 
> etc.
>  ** Functional test design: **
> The functional tests run the same way as unit tests, using JUnit 
> Enabling/disabling of the functional tests can be done using a Maven 
> configuration. 
> The building blocks of the functional tests are: 
> A local ambari server that wraps the actual AmbariServer implementation with 
> Guice to instantiate an in-memory database (use the existing 
> InMemoryDefaultTestModule class) 
> Methods to set up a default cluster with a few hosts, with each host running 
> components like Ambari Metrics Service, HDFS, YARN and Zookeeper. These 
> methods use the ambari server's RESTful APIs. 
> Methods that use HttpClient to perform operations using the RESTful APIs to 
> add/remove cluster, hosts, services, service components and service component 
> hosts. 
> A simple functional test to start the local server on a thread, get status 
> from the server and then shutdown. 
> Additional unit tests can be built on top of the start-status check-stop 
> functional tests, default cluster setup method and helper methods to test 
> specific scenarios. 
>  
> Future work: 
> Local ambari agent simulator for each host.



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

Re: Review Request 39937: Ambari should restore tez.lib.uris to stack defaults when upgrading Tez

[Nate Cole]

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

Ship it!



ambari-server/src/main/resources/stacks/HDP/2.1/upgrades/nonrolling-upgrade-2.3.xml
 (line 260)


Alejandro is right - we keep the changed values.  However, for RU we'll 
still process a straight set (not sure about EU).


- Nate Cole


On Nov. 4, 2015, 11:58 a.m., Dmitro Lisnichenko wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39937/
> ---
> 
> (Updated Nov. 4, 2015, 11:58 a.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jonathan Hurley, Jayush 
> Luniya, and Nate Cole.
> 
> 
> Bugs: AMBARI-13713
> https://issues.apache.org/jira/browse/AMBARI-13713
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Customers apply hotfixes for Tez by modifying tez.lib.uris to point to a new 
> tez tarball to avoid affecting currently running jobs.
> 
> When Ambari does an upgrade to a future version, this config should be 
> reverted to point to the newly uploaded tez tarball ( from the upgraded 
> version ).
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/stacks/HDP/2.1/upgrades/nonrolling-upgrade-2.3.xml
>  ad9346e 
>   ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/config-upgrade.xml 
> 14bd266 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/nonrolling-upgrade-2.2.xml
>  c9ba8d2 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/nonrolling-upgrade-2.3.xml
>  06e5859 
>   ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.2.xml 
> f210930 
>   ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.3.xml 
> 5b78cfd 
>   ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/config-upgrade.xml 
> 53329ee 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.3.xml
>  016bad6 
>   ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.3.xml 
> b0bd7d9 
> 
> Diff: https://reviews.apache.org/r/39937/diff/
> 
> 
> Testing
> ---
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Dmitro Lisnichenko
> 
>

[jira] [Updated] (AMBARI-13749) Hive server 2 fails to start in kerberized environment

[Vitaly Brodetskyi (JIRA)]

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

Vitaly Brodetskyi updated AMBARI-13749:
---
Description: HS2 fails to start on kerberized cluster, for stack 2.2.4.2.

> Hive server 2 fails to start in kerberized environment
> --
>
> Key: AMBARI-13749
> URL: https://issues.apache.org/jira/browse/AMBARI-13749
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.3
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13749.patch
>
>
> HS2 fails to start on kerberized cluster, for stack 2.2.4.2.



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

[jira] [Updated] (AMBARI-13721) Ambari functional tests infrastructure

[Nahappan Somasundaram (JIRA)]

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

Nahappan Somasundaram updated AMBARI-13721:
---
Description: 
Run a test version of the ambari-server with an in-memory DB and ambari-agent 
that run during the functional testing and cover several basic use cases  like 
heartbeat monitoring, adding and deleting services, components, hosts, etc.

Functional test design: 
The functional tests run the same way as unit tests, using JUnit 
Enabling/disabling of the functional tests can be done using a Maven 
configuration. 
The building blocks of the functional tests are: 
A local ambari server that wraps the actual AmbariServer implementation with 
Guice to instantiate an in-memory database (use the existing 
InMemoryDefaultTestModule class) 
Methods to set up a default cluster with a few hosts, with each host running 
components like Ambari Metrics Service, HDFS, YARN and Zookeeper. These methods 
use the ambari server's RESTful APIs. 
Methods that use HttpClient to perform operations using the RESTful APIs to 
add/remove cluster, hosts, services, service components and service component 
hosts. 
A simple functional test to start the local server on a thread, get status from 
the server and then shutdown. 
Additional unit tests can be built on top of the start-status check-stop 
functional tests, default cluster setup method and helper methods to test 
specific scenarios. 
 
Future work: 
Local ambari agent simulator for each host.

  was:
Run a test version of the ambari-server with an in-memory DB and ambari-agent 
that run during the functional testing and cover several basic use cases  like 
heartbeat monitoring, adding and deleting services, components, hosts, etc.

** Functional test design: **
* The functional tests run the same way as unit tests, using JUnit 
* Enabling/disabling of the functional tests can be done using a Maven 
configuration. 
* The building blocks of the functional tests are: 
** A local ambari server that wraps the actual AmbariServer 
implementation with Guice to instantiate an in-memory database (use the   
existing InMemoryDefaultTestModule class) 
** Methods to set up a default cluster with a few hosts, with each host 
running components like Ambari Metrics Service, HDFS, YARN and Zookeeper. These 
methods use the ambari server's RESTful APIs. 
** Methods that use HttpClient to perform operations using the RESTful 
APIs to add/remove cluster, hosts, services, service components and service 
component hosts. 
** A simple functional test to start the local server on a thread, get 
status from the server and then shutdown. 
* Additional unit tests can be built on top of the start-status check-stop 
functional tests, default cluster setup method and helper methods to test 
specific scenarios. 
 
** Future work: **
* Local ambari agent simulator for each host.


> Ambari functional tests infrastructure
> --
>
> Key: AMBARI-13721
> URL: https://issues.apache.org/jira/browse/AMBARI-13721
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.1.3
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.1.3
>
>
> Run a test version of the ambari-server with an in-memory DB and ambari-agent 
> that run during the functional testing and cover several basic use cases  
> like heartbeat monitoring, adding and deleting services, components, hosts, 
> etc.
> Functional test design: 
> The functional tests run the same way as unit tests, using JUnit 
> Enabling/disabling of the functional tests can be done using a Maven 
> configuration. 
> The building blocks of the functional tests are: 
> A local ambari server that wraps the actual AmbariServer implementation with 
> Guice to instantiate an in-memory database (use the existing 
> InMemoryDefaultTestModule class) 
> Methods to set up a default cluster with a few hosts, with each host running 
> components like Ambari Metrics Service, HDFS, YARN and Zookeeper. These 
> methods use the ambari server's RESTful APIs. 
> Methods that use HttpClient to perform operations using the RESTful APIs to 
> add/remove cluster, hosts, services, service components and service component 
> hosts. 
> A simple functional test to start the local server on a thread, get status 
> from the server and then shutdown. 
> Additional unit tests can be built on top of the start-status check-stop 
> functional tests, default cluster setup method and helper methods to test 
> specific scenarios. 
>  
> Future work: 
> Local ambari agent simulator for each host.



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

[jira] [Updated] (AMBARI-13721) Ambari functional tests infrastructure

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-13721:
---
Fix Version/s: (was: 2.2.0)
   2.1.3

> Ambari functional tests infrastructure
> --
>
> Key: AMBARI-13721
> URL: https://issues.apache.org/jira/browse/AMBARI-13721
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.1.3
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.1.3
>
>
> Run a test version of the ambari-server with an in-memory DB and ambari-agent 
> that run during the functional testing and cover several basic use cases  
> like heartbeat monitoring, adding and deleting services, components, hosts, 
> etc.



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

[jira] [Updated] (AMBARI-13721) Ambari functional tests infrastructure

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-13721:
---
Issue Type: Task  (was: Bug)

> Ambari functional tests infrastructure
> --
>
> Key: AMBARI-13721
> URL: https://issues.apache.org/jira/browse/AMBARI-13721
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.1.3
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.1.3
>
>
> Run a test version of the ambari-server with an in-memory DB and ambari-agent 
> that run during the functional testing and cover several basic use cases  
> like heartbeat monitoring, adding and deleting services, components, hosts, 
> etc.



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

Re: Review Request 39977: API call to delete service fails with error: integrity constraint violated - child record found

[Sid Wagle]

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



ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
 (line 1955)


Please document that this need to be called only with write lock acquired.



ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
 (line 1960)


What about serviceComponentHostsByHost, this map will still cache stale 
data with a cahced refernce to dettached entity.

The root cause of re-appearing data is the cached entity refrences !

The other evil is Cascade + manual operations mix. This defientely solves 
one of the problem areas.


- Sid Wagle


On Nov. 5, 2015, 5:27 p.m., Sebastian Toader wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39977/
> ---
> 
> (Updated Nov. 5, 2015, 5:27 p.m.)
> 
> 
> Review request for Ambari, Jonathan Hurley, Robert Levas, Sumit Mohanty, and 
> Sid Wagle.
> 
> 
> Bugs: AMBARI-13741
> https://issues.apache.org/jira/browse/AMBARI-13741
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Deleting a service from existing cluster using REST API 
> (https://cwiki.apache.org/confluence/display/AMBARI/Using+APIs+to+delete+a+service+or+all+host+components+on+a+host)
>  fails with the below error:
> 
> Call: DELETE FROM clusterservice Where ((cluster_id = ?) AND (service_name = 
> ?))
> Caused by: ... ORA-02292 integrity constraint violated - child record found
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ClusterServiceEntity.java
>  d34e2d5 
>   
> ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ServiceComponentDesiredStateEntity.java
>  4195710 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
>  898aa33 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/svccomphost/ServiceComponentHostImpl.java
>  c0804ff 
>   
> ambari-server/src/test/java/org/apache/ambari/server/state/cluster/ClusterImplTest.java
>  39431ed 
> 
> Diff: https://reviews.apache.org/r/39977/diff/
> 
> 
> Testing
> ---
> 
> Manual testing:
> 
> 1. Created a simple 3 node cluster uzing the wizzard
> 2. Deleted a service using REST API
> 3. Verified that affected records were deleted from the following tables: 
> clusterservices, servicedesiredstate, servicecomponentdesiredstate, 
> hostcomponentstate, hostcomponentdesiredstate
> 4. Refresh UI than re-add the deleted service.
> 
>  
> Unit tests:
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 1:11:05.677s
> [INFO] Finished at: Thu Nov 05 17:02:51 CET 2015
> [INFO] Final Memory: 32M/763M
> [INFO] 
> 
> 
> 
> Thanks,
> 
> Sebastian Toader
> 
>

[jira] [Created] (AMBARI-13748) Being able to clean repository cache before installing open source components

[Di Li (JIRA)]

Di Li created AMBARI-13748:
--

 Summary: Being able to clean repository cache before installing 
open source components
 Key: AMBARI-13748
 URL: https://issues.apache.org/jira/browse/AMBARI-13748
 Project: Ambari
  Issue Type: New Feature
  Components: ambari-agent, ambari-server
Affects Versions: 2.1.0
Reporter: Di Li
 Fix For: trunk


Need a way for Ambari to trigger a repository clean (yum clean expire-cache, 
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.



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

[jira] [Commented] (AMBARI-13730) Express Upgrade: Add max degree of parallelism to control number of tasks run in parallel

[Jayush Luniya (JIRA)]

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

Jayush Luniya commented on AMBARI-13730:


Trunk:
commit 625e4ff293f36b83a2b03ac9cc48d746f692e4ee
Author: Jayush Luniya 
Date:   Thu Nov 5 10:28:26 2015 -0800

AMBARI-13730: Express Upgrade: Add max degree of parallelism to control 
number of tasks run in parallel (jluniya)

> Express Upgrade: Add max degree of parallelism to control number of tasks run 
> in parallel
> -
>
> Key: AMBARI-13730
> URL: https://issues.apache.org/jira/browse/AMBARI-13730
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.2.0, 2.1.3
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.1.3
>
>




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

[jira] [Resolved] (AMBARI-13730) Express Upgrade: Add max degree of parallelism to control number of tasks run in parallel

[Jayush Luniya (JIRA)]

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

Jayush Luniya resolved AMBARI-13730.

Resolution: Fixed

> Express Upgrade: Add max degree of parallelism to control number of tasks run 
> in parallel
> -
>
> Key: AMBARI-13730
> URL: https://issues.apache.org/jira/browse/AMBARI-13730
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.2.0, 2.1.3
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.1.3
>
>




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

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

[Jayush Luniya (JIRA)]

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

Jayush Luniya commented on AMBARI-13705:


[~swagle]
Looks like issue is still not fixed :(
Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/4177//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/4177//console

Running 
org.apache.ambari.server.controller.metrics.timeline.cache.TimelineMetricCacheSizingTest
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.363 sec <<< 
FAILURE!
testTimelineMetricCacheSizing(org.apache.ambari.server.controller.metrics.timeline.cache.TimelineMetricCacheSizingTest)
  Time elapsed: 1.143 sec  <<< FAILURE!
java.lang.AssertionError: Sample size is 9, expected to begreater that 10 MB
at org.junit.Assert.fail(Assert.java:93)
at org.junit.Assert.assertTrue(Assert.java:43)
at 
org.apache.ambari.server.controller.metrics.timeline.cache.TimelineMetricCacheSizingTest.testTimelineMetricCacheSizing(TimelineMetricCacheSizingTest.java:110)

> 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: Siddharth Wagle
> Fix For: 2.1.3
>
> Attachments: AMBARI-13705.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-13749) Hive server 2 fails to start in kerberized environment

[Vitaly Brodetskyi (JIRA)]

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

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

> Hive server 2 fails to start in kerberized environment
> --
>
> Key: AMBARI-13749
> URL: https://issues.apache.org/jira/browse/AMBARI-13749
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.3
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13749.patch
>
>




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

[jira] [Updated] (AMBARI-13721) Ambari functional tests infrastructure

[Nahappan Somasundaram (JIRA)]

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

Nahappan Somasundaram updated AMBARI-13721:
---
Description: 
Run a test version of the ambari-server with an in-memory DB and ambari-agent 
that run during the functional testing and cover several basic use cases  like 
heartbeat monitoring, adding and deleting services, components, hosts, etc.

* Functional test design: 
* The functional tests run the same way as unit tests, using JUnit 
* Enabling/disabling of the functional tests can be done using a Maven 
configuration. 
* The building blocks of the functional tests are: 
** A local ambari server that wraps the actual AmbariServer 
implementation with Guice to instantiate an in-memory database (use the 
existing InMemoryDefaultTestModule class) 
** Methods to set up a default cluster with a few hosts, with each host 
running components like Ambari Metrics Service, HDFS, YARN and Zookeeper. These 
methods use the ambari server's RESTful APIs. 
** Methods that use HttpClient to perform operations using the RESTful 
APIs to add/remove cluster, hosts, services, service components and service 
component hosts. 
** A simple functional test to start the local server on a thread, get 
status from the server and then shutdown. 
* Additional unit tests can be built on top of the start-status check-stop 
functional tests, default cluster setup method and helper methods to test 
specific scenarios. 
  
*Future work:
* Local ambari agent simulator for each host.

  was:
Run a test version of the ambari-server with an in-memory DB and ambari-agent 
that run during the functional testing and cover several basic use cases  like 
heartbeat monitoring, adding and deleting services, components, hosts, etc.

* Functional test design: 
* The functional tests run the same way as unit tests, using JUnit 
* Enabling/disabling of the functional tests can be done using a Maven 
configuration. 
* The building blocks of the functional tests are: 
** A local ambari server that wraps the actual AmbariServer 
implementation with Guice to instantiate an in-memory database (use the 
existing InMemoryDefaultTestModule class) 
** Methods to set up a default cluster with a few hosts, with each host 
running components like Ambari Metrics Service, HDFS, YARN and Zookeeper. These 
methods use the ambari server's RESTful APIs. 
** Methods that use HttpClient to perform operations using the RESTful 
APIs to add/remove cluster, hosts, services, service components and service 
component hosts. 
** A simple functional test to start the local server on a thread, get 
status from the server and then shutdown. 
* Additional unit tests can be built on top of the start-status check-stop 
functional tests, default cluster setup method and helper methods to test 
specific scenarios. 
  
** Future work: ** 
* Local ambari agent simulator for each host.


> Ambari functional tests infrastructure
> --
>
> Key: AMBARI-13721
> URL: https://issues.apache.org/jira/browse/AMBARI-13721
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.1.3
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.1.3
>
>
> Run a test version of the ambari-server with an in-memory DB and ambari-agent 
> that run during the functional testing and cover several basic use cases  
> like heartbeat monitoring, adding and deleting services, components, hosts, 
> etc.
> * Functional test design: 
> * The functional tests run the same way as unit tests, using JUnit 
> * Enabling/disabling of the functional tests can be done using a Maven 
> configuration. 
> * The building blocks of the functional tests are: 
> ** A local ambari server that wraps the actual AmbariServer 
> implementation with Guice to instantiate an in-memory database (use the 
> existing InMemoryDefaultTestModule class) 
> ** Methods to set up a default cluster with a few hosts, with each 
> host running components like Ambari Metrics Service, HDFS, YARN and 
> Zookeeper. These methods use the ambari server's RESTful APIs. 
> ** Methods that use HttpClient to perform operations using the 
> RESTful APIs to add/remove cluster, hosts, services, service components and 
> service component hosts. 
> ** A simple functional test to start the local server on a thread, 
> get status from the server and then shutdown. 
> * Additional unit tests can be built on top of the start-status check-stop 
> functional tests, default cluster setup method and helper methods to test 
> specific scenarios. 
>   
> *Future work:
> * Local ambari agent simulator for each host.



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

[jira] [Commented] (AMBARI-13743) Flume and Storm Ambari metrics are not working

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-13743:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12770809/AMBARI-13743-trunk.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 2 new 
or modified test files.

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

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

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

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

This message is automatically generated.

> Flume and Storm Ambari metrics are not working
> --
>
> Key: AMBARI-13743
> URL: https://issues.apache.org/jira/browse/AMBARI-13743
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics, ambari-upgrade
>Affects Versions: 2.1.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
> Fix For: 2.1.3
>
> Attachments: AMBARI-13743-trunk.patch
>
>
> After the ambari is upgraded from ambari 1.7.0 to Ambari to Ambari 2.1.2 no 
> flume and storm graphs shown



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

[jira] [Created] (AMBARI-13752) Add a functional test to create a local ambari server and test it's status using an API call

[Nahappan Somasundaram (JIRA)]

Nahappan Somasundaram created AMBARI-13752:
--

 Summary: Add a functional test to create a local ambari server and 
test it's status using an API call
 Key: AMBARI-13752
 URL: https://issues.apache.org/jira/browse/AMBARI-13752
 Project: Ambari
  Issue Type: Sub-task
  Components: ambari-server
Affects Versions: 2.1.2
Reporter: Nahappan Somasundaram
Assignee: Nahappan Somasundaram
 Fix For: 2.2.0


Write a functional test to configure an ambari server to use an in-memory 
database and test it's status using an API call.

Specifically, this test uses InMemoryDefaultTestModule() to configure the Guice 
injector so that the AmbariServer instances does not require an external DB. 
This test also disables SSL for agent communication since we don't have an 
agent simulator yet.

The test makes a call to /api/v1/stacks to get the list of stacks. This is an 
indicator that the ambari server is running and responds to RESTful API 
requests.



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

[jira] [Created] (AMBARI-13753) Refactor code that caches stale entity references

[Siddharth Wagle (JIRA)]

Siddharth Wagle created AMBARI-13753:


 Summary: Refactor code that caches stale entity references 
 Key: AMBARI-13753
 URL: https://issues.apache.org/jira/browse/AMBARI-13753
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 1.5.0
Reporter: Siddharth Wagle
Assignee: Siddharth Wagle
 Fix For: 2.1.3


- Deleted hostcomponent rows re-appear
- Inconsistencies in hostcomponentstate and hostcomponentdesiredstate tables



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

Re: Review Request 39994: UI changes for 'Verifying Skipped Failures' stage

[Yusaku Sako]

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

Ship it!


Ship It!

- Yusaku Sako


On Nov. 5, 2015, 9:15 p.m., Xi Wang wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39994/
> ---
> 
> (Updated Nov. 5, 2015, 9:15 p.m.)
> 
> 
> Review request for Ambari and Yusaku Sako.
> 
> 
> Bugs: AMBARI-13750
> https://issues.apache.org/jira/browse/AMBARI-13750
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> AMBARI-13704 and AMBARI-13722 details the changes to the RU stage titled 
> "Verifying Skipped Failures".  
> New structured output of that specific task will detail what failures 
> occurred and where they occurred. 
> The failures info (hostNames and serviceNames) will be display on UI.
> see attached.
> 
> 
> Diffs
> -
> 
>   ambari-web/app/messages.js 377ed7d 
>   ambari-web/app/styles/stack_versions.less dab19c6 
>   ambari-web/app/templates/main/admin/stack_upgrade/stack_upgrade_wizard.hbs 
> a45bad1 
>   ambari-web/app/utils/ajax/ajax.js 9ab6f30 
>   ambari-web/app/views/main/admin/stack_upgrade/upgrade_wizard_view.js 
> aff8f94 
> 
> Diff: https://reviews.apache.org/r/39994/diff/
> 
> 
> Testing
> ---
> 
> Tested e2e.
>  10271 tests complete (12 seconds)
>   105 tests pending
> 
> 
> Thanks,
> 
> Xi Wang
> 
>

[jira] [Updated] (AMBARI-13751) Ranger User Info: Bind Anonymous value needs to be flipped

[Jaimin D Jetly (JIRA)]

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

Jaimin D Jetly updated AMBARI-13751:

Attachment: AMBARI-13751.patch

> Ranger User Info: Bind Anonymous value needs to be flipped
> --
>
> Key: AMBARI-13751
> URL: https://issues.apache.org/jira/browse/AMBARI-13751
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.1.3
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
> Fix For: 2.1.3
>
> Attachments: AMBARI-13751.patch
>
>




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

[jira] [Updated] (AMBARI-13751) Ranger User Info: Visibility of bind user and password field should happen when Bind Anonymous value is false

[Jaimin D Jetly (JIRA)]

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

Jaimin D Jetly updated AMBARI-13751:

Summary: Ranger User Info: Visibility of bind user and password field 
should happen when Bind Anonymous value is false  (was: Ranger User Info: Bind 
Anonymous value needs to be flipped)

> Ranger User Info: Visibility of bind user and password field should happen 
> when Bind Anonymous value is false
> -
>
> Key: AMBARI-13751
> URL: https://issues.apache.org/jira/browse/AMBARI-13751
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.1.3
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
> Fix For: 2.1.3
>
> Attachments: AMBARI-13751.patch
>
>




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

[jira] [Commented] (AMBARI-13727) Update Ambari 1.8 JDK build number to 1.8u60

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13727:
-

FAILURE: Integrated in Ambari-branch-2.1 #807 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/807/])
AMBARI-13727. Update Ambari 1.8 JDK build number to 1.8u60 (srimanth) 
(sgunturi: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c950aaf07fbf1038e5a3d1e052250eadf2b64536])
* ambari-server/conf/unix/ambari.properties
* ambari-server/src/test/python/stacks/2.2/configs/knox_upgrade.json
* ambari-server/src/test/python/stacks/2.3/configs/storm_default.json
* ambari-server/src/test/python/stacks/2.3/configs/hbase_secure.json
* ambari-server/src/test/python/stacks/2.3/configs/hbase_default.json
* ambari-server/src/test/python/stacks/2.3/configs/storm_default_secure.json
* ambari-server/src/main/python/ambari_server/serverSetup.py


> Update Ambari 1.8 JDK build number to 1.8u60
> 
>
> Key: AMBARI-13727
> URL: https://issues.apache.org/jira/browse/AMBARI-13727
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.2
>Reporter: Srimanth Gunturi
>Assignee: Srimanth Gunturi
> Fix For: 2.1.3
>
> Attachments: AMBARI-13727.patch
>
>
> Ambari uses JDK 1.8u40 build which has the following bug:
> [https://bugs.openjdk.java.net/browse/JDK-8078439]. This is a negotiation bug 
> that prevents properly configured web browsers on windows hosts from 
> accessing kerberized APIs if HDP 2.3 is installed with the JDK 1.8u40 which 
> we provide.  We should update this to the current JDK which is 1.8u60 on 
> Oracle's site, which I have had one customer already confirm does not have 
> this issue.



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

[jira] [Commented] (AMBARI-13730) Express Upgrade: Add max degree of parallelism to control number of tasks run in parallel

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13730:
-

FAILURE: Integrated in Ambari-branch-2.1 #807 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/807/])
AMBARI-13730: Express Upgrade: Add max degree of parallelism to control 
(jluniya: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9c85b24391d337600e333eea7aa1182744e4550d])
* ambari-server/src/test/java/org/apache/ambari/server/utils/SetUtilsTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/state/stack/upgrade/StageWrapperBuilderTest.java
* 
ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/nonrolling-upgrade-2.2.xml
* 
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/Grouping.java
* 
ambari-server/src/test/java/org/apache/ambari/server/state/stack/UpgradePackTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ColocatedGrouping.java
* ambari-server/src/main/java/org/apache/ambari/server/utils/SetUtils.java
* 
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/StageWrapperBuilder.java
* 
ambari-server/src/main/resources/stacks/HDP/2.1/upgrades/nonrolling-upgrade-2.3.xml
* 
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.3.xml
* 
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ServiceCheckGrouping.java
* 
ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/nonrolling-upgrade-2.3.xml
* 
ambari-server/src/test/resources/stacks/HDP/2.1.1/upgrades/upgrade_test_nonrolling.xml
* ambari-server/src/main/java/org/apache/ambari/server/state/UpgradeHelper.java
* 
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ClusterGrouping.java
* 
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ParallelScheduler.java


> Express Upgrade: Add max degree of parallelism to control number of tasks run 
> in parallel
> -
>
> Key: AMBARI-13730
> URL: https://issues.apache.org/jira/browse/AMBARI-13730
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.2.0, 2.1.3
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.1.3
>
>




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

[jira] [Commented] (AMBARI-13744) Implement ability to retry operations after database exception for blueprint deploy

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13744:
-

FAILURE: Integrated in Ambari-branch-2.1 #807 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/807/])
AMBARI-13744. Implement ability to retry operations after database 
(mpapyrkovskyy: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c13288fa9a290498eccd4b1eefc117e2b0e4d067])
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClusterResourceProviderTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/topology/AmbariContext.java
* 
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
* ambari-server/src/main/java/org/apache/ambari/server/utils/RetryHelper.java
* 
ambari-server/src/main/java/org/apache/ambari/server/topology/TopologyManager.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AbstractResourceProvider.java


> Implement ability to retry operations after database exception for blueprint 
> deploy
> ---
>
> Key: AMBARI-13744
> URL: https://issues.apache.org/jira/browse/AMBARI-13744
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.3
>Reporter: Myroslav Papirkovskyy
>Assignee: Myroslav Papirkovskyy
>Priority: Critical
> Fix For: 2.1.3
>
>
> Jira is related to AMBARI-13663. Same functionality for blueprint-based 
> deploy.



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

[jira] [Commented] (AMBARI-13750) UI changes for 'Verifying Skipped Failures' stage

[Yusaku Sako (JIRA)]

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

Yusaku Sako commented on AMBARI-13750:
--

[~xiwang0309], can you create a patch for branch-2.1 as well?

> UI changes for 'Verifying Skipped Failures' stage
> -
>
> Key: AMBARI-13750
> URL: https://issues.apache.org/jira/browse/AMBARI-13750
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.3
>Reporter: Xi Wang
>Assignee: Xi Wang
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13750.patch, ServiceCheckFail1.png, 
> SlaveComponentsFail.png, slaveComponentFail2.png, 
> slaveComponentsFailuresManualStep.png
>
>
> AMBARI-13704 and AMBARI-13722 details the changes to the RU stage titled 
> "Verifying Skipped Failures".  
> New structured output of that specific task will detail what failures 
> occurred and where they occurred. 
> The failures info (hostNames and serviceNames) will be display on UI.
> see attached.



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

[jira] [Commented] (AMBARI-13729) Change the Spark thrift server security configurations

[Judy Nash (JIRA)]

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

Judy Nash commented on AMBARI-13729:


+1 LGTM. 

> Change the Spark thrift server security configurations
> --
>
> Key: AMBARI-13729
> URL: https://issues.apache.org/jira/browse/AMBARI-13729
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: trunk
>Reporter: Saisai Shao
> Fix For: trunk
>
> Attachments: AMBARI-13729.patch
>
>
> "hive.security.authorization.enabled" would be better changed to 
> "hive.server2.authentication". And "hive.server2.enable.doAs" is not well 
> supported currently.



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

[jira] [Updated] (AMBARI-13751) Ranger User Info: Visibility of bind user and password field should happen when Bind Anonymous value is false

[Jaimin D Jetly (JIRA)]

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

Jaimin D Jetly updated AMBARI-13751:

Priority: Critical  (was: Major)

> Ranger User Info: Visibility of bind user and password field should happen 
> when Bind Anonymous value is false
> -
>
> Key: AMBARI-13751
> URL: https://issues.apache.org/jira/browse/AMBARI-13751
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.1.3
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13751.patch
>
>




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

[jira] [Commented] (AMBARI-13751) Ranger User Info: Visibility of bind user and password field should happen when Bind Anonymous value is false

[Jaimin D Jetly (JIRA)]

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

Jaimin D Jetly commented on AMBARI-13751:
-

Patch has been manually tested to work on a cluster

> Ranger User Info: Visibility of bind user and password field should happen 
> when Bind Anonymous value is false
> -
>
> Key: AMBARI-13751
> URL: https://issues.apache.org/jira/browse/AMBARI-13751
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.1.3
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
> Fix For: 2.1.3
>
> Attachments: AMBARI-13751.patch
>
>




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

Review Request 39996: Refactor code that caches stale entity references

[Sid Wagle]

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

Review request for Ambari, Myroslav Papirkovskyy, Sumit Mohanty, and Sebastian 
Toader.


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


Repository: ambari


Description
---

- Deleted hostcomponent rows re-appear
- Inconsistencies in hostcomponentstate and hostcomponentdesiredstate tables

Preliminary patch.


Diffs
-

  
ambari-server/src/main/java/org/apache/ambari/server/state/ServiceComponentImpl.java
 6150011 
  ambari-server/src/main/java/org/apache/ambari/server/state/ServiceImpl.java 
bbe2f62 
  
ambari-server/src/main/java/org/apache/ambari/server/state/svccomphost/ServiceComponentHostImpl.java
 c0804ff 
  
ambari-server/src/test/java/org/apache/ambari/server/testing/DBInconsistencyTests.java
 PRE-CREATION 

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


Testing
---

Unit testing in progress.


Thanks,

Sid Wagle

[jira] [Updated] (AMBARI-13721) Ambari functional tests infrastructure

[Nahappan Somasundaram (JIRA)]

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

Nahappan Somasundaram updated AMBARI-13721:
---
Description: 
Run a test version of the ambari-server with an in-memory DB and ambari-agent 
that run during the functional testing and cover several basic use cases  like 
heartbeat monitoring, adding and deleting services, components, hosts, etc.

** Functional test design: **
* The functional tests run the same way as unit tests, using JUnit 
* Enabling/disabling of the functional tests can be done using a Maven 
configuration. 
* The building blocks of the functional tests are: 
** A local ambari server that wraps the actual AmbariServer 
implementation with Guice to instantiate an in-memory database (use the   
existing InMemoryDefaultTestModule class) 
** Methods to set up a default cluster with a few hosts, with each host 
running components like Ambari Metrics Service, HDFS, YARN and Zookeeper. These 
methods use the ambari server's RESTful APIs. 
** Methods that use HttpClient to perform operations using the RESTful 
APIs to add/remove cluster, hosts, services, service components and service 
component hosts. 
** A simple functional test to start the local server on a thread, get 
status from the server and then shutdown. 
* Additional unit tests can be built on top of the start-status check-stop 
functional tests, default cluster setup method and helper methods to test 
specific scenarios. 
 
** Future work: **
* Local ambari agent simulator for each host.

  was:Run a test version of the ambari-server with an in-memory DB and 
ambari-agent that run during the functional testing and cover several basic use 
cases  like heartbeat monitoring, adding and deleting services, components, 
hosts, etc.


> Ambari functional tests infrastructure
> --
>
> Key: AMBARI-13721
> URL: https://issues.apache.org/jira/browse/AMBARI-13721
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.1.3
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.1.3
>
>
> Run a test version of the ambari-server with an in-memory DB and ambari-agent 
> that run during the functional testing and cover several basic use cases  
> like heartbeat monitoring, adding and deleting services, components, hosts, 
> etc.
> ** Functional test design: **
> * The functional tests run the same way as unit tests, using JUnit 
> * Enabling/disabling of the functional tests can be done using a Maven 
> configuration. 
> * The building blocks of the functional tests are: 
> ** A local ambari server that wraps the actual AmbariServer 
> implementation with Guice to instantiate an in-memory database (use the   
> existing InMemoryDefaultTestModule class) 
> ** Methods to set up a default cluster with a few hosts, with each 
> host running components like Ambari Metrics Service, HDFS, YARN and 
> Zookeeper. These methods use the ambari server's RESTful APIs. 
> ** Methods that use HttpClient to perform operations using the 
> RESTful APIs to add/remove cluster, hosts, services, service components and 
> service component hosts. 
> ** A simple functional test to start the local server on a thread, 
> get status from the server and then shutdown. 
> * Additional unit tests can be built on top of the start-status check-stop 
> functional tests, default cluster setup method and helper methods to test 
> specific scenarios. 
>  
> ** Future work: **
> * Local ambari agent simulator for each host.



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

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

[jun aoki (JIRA)]

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

jun aoki updated AMBARI-13665:
--
Attachment: AMBARI-13665-3.patch

> Enable HAWQ/PXF services in Ambari 2.1.3
> 
>
> Key: AMBARI-13665
> URL: https://issues.apache.org/jira/browse/AMBARI-13665
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: 2.1.3
>Reporter: Alexander Denissov
>Assignee: Mithun Mathew
> Fix For: 2.1.3
>
> Attachments: AMBARI-13665-2.patch, AMBARI-13665-3.patch, 
> AMBARI-13665.patch
>
>
> We would like to have Apache HAWQ/PXF services, currently defined in Ambari 
> trunk, be available in Ambari 2.1.3. The patch attached to this story should 
> be applied on branch-2.1 for the code to be available in Ambari 2.1.3 release.



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

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

[Aravindan Vijayan (JIRA)]

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

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

> 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: Siddharth Wagle
> Fix For: 2.1.3
>
> Attachments: AMBARI-13705.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-13721) Ambari functional tests infrastructure

[Nahappan Somasundaram (JIRA)]

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

Nahappan Somasundaram updated AMBARI-13721:
---
Description: 
Run a test version of the ambari-server with an in-memory DB and ambari-agent 
that run during the functional testing and cover several basic use cases  like 
heartbeat monitoring, adding and deleting services, components, hosts, etc.

* Functional test design: 
* The functional tests run the same way as unit tests, using JUnit 
* Enabling/disabling of the functional tests can be done using a Maven 
configuration. 
* The building blocks of the functional tests are: 
** A local ambari server that wraps the actual AmbariServer 
implementation with Guice to instantiate an in-memory database (use the 
existing InMemoryDefaultTestModule class) 
** Methods to set up a default cluster with a few hosts, with each host 
running components like Ambari Metrics Service, HDFS, YARN and Zookeeper. These 
methods use the ambari server's RESTful APIs. 
** Methods that use HttpClient to perform operations using the RESTful 
APIs to add/remove cluster, hosts, services, service components and service 
component hosts. 
** A simple functional test to start the local server on a thread, get 
status from the server and then shutdown. 
* Additional unit tests can be built on top of the start-status check-stop 
functional tests, default cluster setup method and helper methods to test 
specific scenarios. 
  
** Future work: ** 
* Local ambari agent simulator for each host.

  was:
Run a test version of the ambari-server with an in-memory DB and ambari-agent 
that run during the functional testing and cover several basic use cases  like 
heartbeat monitoring, adding and deleting services, components, hosts, etc.

** Functional test design: ** 
* The functional tests run the same way as unit tests, using JUnit 
* Enabling/disabling of the functional tests can be done using a Maven 
configuration. 
* The building blocks of the functional tests are: 
** A local ambari server that wraps the actual AmbariServer 
implementation with Guice to instantiate an in-memory database (use the 
existing InMemoryDefaultTestModule class) 
** Methods to set up a default cluster with a few hosts, with each host 
running components like Ambari Metrics Service, HDFS, YARN and Zookeeper. These 
methods use the ambari server's RESTful APIs. 
** Methods that use HttpClient to perform operations using the RESTful 
APIs to add/remove cluster, hosts, services, service components and service 
component hosts. 
** A simple functional test to start the local server on a thread, get 
status from the server and then shutdown. 
* Additional unit tests can be built on top of the start-status check-stop 
functional tests, default cluster setup method and helper methods to test 
specific scenarios. 
  
** Future work: ** 
* Local ambari agent simulator for each host.


> Ambari functional tests infrastructure
> --
>
> Key: AMBARI-13721
> URL: https://issues.apache.org/jira/browse/AMBARI-13721
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.1.3
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.1.3
>
>
> Run a test version of the ambari-server with an in-memory DB and ambari-agent 
> that run during the functional testing and cover several basic use cases  
> like heartbeat monitoring, adding and deleting services, components, hosts, 
> etc.
> * Functional test design: 
> * The functional tests run the same way as unit tests, using JUnit 
> * Enabling/disabling of the functional tests can be done using a Maven 
> configuration. 
> * The building blocks of the functional tests are: 
> ** A local ambari server that wraps the actual AmbariServer 
> implementation with Guice to instantiate an in-memory database (use the 
> existing InMemoryDefaultTestModule class) 
> ** Methods to set up a default cluster with a few hosts, with each 
> host running components like Ambari Metrics Service, HDFS, YARN and 
> Zookeeper. These methods use the ambari server's RESTful APIs. 
> ** Methods that use HttpClient to perform operations using the 
> RESTful APIs to add/remove cluster, hosts, services, service components and 
> service component hosts. 
> ** A simple functional test to start the local server on a thread, 
> get status from the server and then shutdown. 
> * Additional unit tests can be built on top of the start-status check-stop 
> functional tests, default cluster setup method and helper methods to test 
> specific scenarios. 
>   
> ** Future work: ** 
> * Local ambari agent simulator for each host.



--
This message was sent by Atlassian 

[jira] [Commented] (AMBARI-13730) Express Upgrade: Add max degree of parallelism to control number of tasks run in parallel

[Hudson (JIRA)]

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

Hudson commented on AMBARI-13730:
-

FAILURE: Integrated in Ambari-trunk-Commit #3779 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3779/])
AMBARI-13730: Express Upgrade: Add max degree of parallelism to control 
(jluniya: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=625e4ff293f36b83a2b03ac9cc48d746f692e4ee])
* 
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/StageWrapperBuilder.java
* 
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ServiceCheckGrouping.java
* 
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/Grouping.java
* 
ambari-server/src/test/resources/stacks/HDP/2.1.1/upgrades/upgrade_test_nonrolling.xml
* ambari-server/src/test/java/org/apache/ambari/server/utils/SetUtilsTest.java
* 
ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/nonrolling-upgrade-2.2.xml
* 
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ColocatedGrouping.java
* ambari-server/src/main/java/org/apache/ambari/server/state/UpgradeHelper.java
* 
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.3.xml
* 
ambari-server/src/main/resources/stacks/HDP/2.1/upgrades/nonrolling-upgrade-2.3.xml
* 
ambari-server/src/test/java/org/apache/ambari/server/state/stack/upgrade/StageWrapperBuilderTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/state/stack/UpgradePackTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ParallelScheduler.java
* 
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ClusterGrouping.java
* ambari-server/src/main/java/org/apache/ambari/server/utils/SetUtils.java


> Express Upgrade: Add max degree of parallelism to control number of tasks run 
> in parallel
> -
>
> Key: AMBARI-13730
> URL: https://issues.apache.org/jira/browse/AMBARI-13730
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.2.0, 2.1.3
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.1.3
>
>




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

[jira] [Created] (AMBARI-13751) Ranger User Info: Bind Anonymous value needs to be flipped

[Jaimin D Jetly (JIRA)]

Jaimin D Jetly created AMBARI-13751:
---

 Summary: Ranger User Info: Bind Anonymous value needs to be flipped
 Key: AMBARI-13751
 URL: https://issues.apache.org/jira/browse/AMBARI-13751
 Project: Ambari
  Issue Type: Bug
  Components: stacks
Affects Versions: 2.1.3
Reporter: Jaimin D Jetly
Assignee: Jaimin D Jetly
 Fix For: 2.1.3






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

Review Request 39994: UI changes for 'Verifying Skipped Failures' stage

[Xi Wang]

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

Review request for Ambari and Yusaku Sako.


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


Repository: ambari


Description
---

AMBARI-13704 and AMBARI-13722 details the changes to the RU stage titled 
"Verifying Skipped Failures".  
New structured output of that specific task will detail what failures occurred 
and where they occurred. 
The failures info (hostNames and serviceNames) will be display on UI.
see attached.


Diffs
-

  ambari-web/app/messages.js 377ed7d 
  ambari-web/app/styles/stack_versions.less dab19c6 
  ambari-web/app/templates/main/admin/stack_upgrade/stack_upgrade_wizard.hbs 
a45bad1 
  ambari-web/app/utils/ajax/ajax.js 9ab6f30 
  ambari-web/app/views/main/admin/stack_upgrade/upgrade_wizard_view.js aff8f94 

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


Testing
---

Tested e2e.
 10271 tests complete (12 seconds)
  105 tests pending


Thanks,

Xi Wang