[jira] [Commented] (AMBARI-18208) Bug Fixing in HueMigration View
[ https://issues.apache.org/jira/browse/AMBARI-18208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429612#comment-15429612 ] Gaurav Nagar commented on AMBARI-18208: --- The patch includes 1. bug fixes for migrating data kerberos enabled environment 2. Added support for migrating data to next hive version(Hive 1.5.0) Without this patch, the HueMigration view wont able to work correctly in kerberized environment. Changed the priority to Blocker and fixed version to 2.4.0. > Bug Fixing in HueMigration View > --- > > Key: AMBARI-18208 > URL: https://issues.apache.org/jira/browse/AMBARI-18208 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 > Environment: JDK 1.8 > Centos 6.4 > Ambari DB:-Mysql,Postgress > Hue DB:-Sqlite,Mysql >Reporter: Pradarttana >Assignee: Gaurav Nagar >Priority: Blocker > Labels: None > Fix For: 2.4.0 > > Attachments: AMBARI-18208.1_trunk.patch, AMBARI-18208_trunk.patch > > > 1. Hive History Query Insertion in hive 1.5 and hive 1.0 (Due to DB schema > changed) > 2. Not able to migrate with kerberos enabled > 3. UI Validation bugs > 4. Mysql and Postgres Hue error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-18208) Bug Fixing in HueMigration View
[ https://issues.apache.org/jira/browse/AMBARI-18208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar reassigned AMBARI-18208: - Assignee: Gaurav Nagar > Bug Fixing in HueMigration View > --- > > Key: AMBARI-18208 > URL: https://issues.apache.org/jira/browse/AMBARI-18208 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 > Environment: JDK 1.8 > Centos 6.4 > Ambari DB:-Mysql,Postgress > Hue DB:-Sqlite,Mysql >Reporter: Pradarttana >Assignee: Gaurav Nagar >Priority: Blocker > Labels: None > Fix For: 2.4.0 > > Attachments: AMBARI-18208.1_trunk.patch, AMBARI-18208_trunk.patch > > > 1. Hive History Query Insertion in hive 1.5 and hive 1.0 (Due to DB schema > changed) > 2. Not able to migrate with kerberos enabled > 3. UI Validation bugs > 4. Mysql and Postgres Hue error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18208) Bug Fixing in HueMigration View
[ https://issues.apache.org/jira/browse/AMBARI-18208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-18208: -- Fix Version/s: (was: trunk) 2.4.0 > Bug Fixing in HueMigration View > --- > > Key: AMBARI-18208 > URL: https://issues.apache.org/jira/browse/AMBARI-18208 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 > Environment: JDK 1.8 > Centos 6.4 > Ambari DB:-Mysql,Postgress > Hue DB:-Sqlite,Mysql >Reporter: Pradarttana >Assignee: Gaurav Nagar >Priority: Blocker > Labels: None > Fix For: 2.4.0 > > Attachments: AMBARI-18208.1_trunk.patch, AMBARI-18208_trunk.patch > > > 1. Hive History Query Insertion in hive 1.5 and hive 1.0 (Due to DB schema > changed) > 2. Not able to migrate with kerberos enabled > 3. UI Validation bugs > 4. Mysql and Postgres Hue error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18208) Bug Fixing in HueMigration View
[ https://issues.apache.org/jira/browse/AMBARI-18208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-18208: -- Priority: Blocker (was: Major) > Bug Fixing in HueMigration View > --- > > Key: AMBARI-18208 > URL: https://issues.apache.org/jira/browse/AMBARI-18208 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 > Environment: JDK 1.8 > Centos 6.4 > Ambari DB:-Mysql,Postgress > Hue DB:-Sqlite,Mysql >Reporter: Pradarttana >Priority: Blocker > Labels: None > Fix For: trunk > > Attachments: AMBARI-18208.1_trunk.patch, AMBARI-18208_trunk.patch > > > 1. Hive History Query Insertion in hive 1.5 and hive 1.0 (Due to DB schema > changed) > 2. Not able to migrate with kerberos enabled > 3. UI Validation bugs > 4. Mysql and Postgres Hue error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18219) Ambari should use oozied.sh for stopping oozie so that optional catalina args can be provided
[ https://issues.apache.org/jira/browse/AMBARI-18219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429603#comment-15429603 ] Hudson commented on AMBARI-18219: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5563 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5563/]) AMBARI-18219. Ambari should use oozied.sh for stopping oozie so that (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=967ce4be73bd3f1fe553e6930a70ddaf5e6acd2a]) * (edit) ambari-server/src/test/python/stacks/2.0.6/OOZIE/test_oozie_server.py * (edit) ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py > Ambari should use oozied.sh for stopping oozie so that optional catalina args > can be provided > - > > Key: AMBARI-18219 > URL: https://issues.apache.org/jira/browse/AMBARI-18219 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Venkat Ranganathan >Assignee: Venkat Ranganathan >Priority: Blocker > Labels: 240RMApproved > Fix For: 2.4.0 > > Attachments: AMBARI-18219-2.patch, AMBARI-18219.patch > > > In some scenarios, the oozie stop can take longer and if a oozie start is > attempted it can fail with address already in use -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18224) Some images get missing in Chrome when SSL is enabled
[ https://issues.apache.org/jira/browse/AMBARI-18224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yesha Vora updated AMBARI-18224: Attachment: Screen Shot 2016-08-20 at 2.45.28 PM.png > Some images get missing in Chrome when SSL is enabled > - > > Key: AMBARI-18224 > URL: https://issues.apache.org/jira/browse/AMBARI-18224 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Yesha Vora > Attachments: Screen Shot 2016-08-20 at 2.45.28 PM.png > > > Some of the images get missing from Ambari ui when SSL is enabled. > This issue only happens in Chrome. ( Tested with Version 52.0.2743.116 > (64-bit)) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18224) Some images get missing in Chrome when SSL is enabled
Yesha Vora created AMBARI-18224: --- Summary: Some images get missing in Chrome when SSL is enabled Key: AMBARI-18224 URL: https://issues.apache.org/jira/browse/AMBARI-18224 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Yesha Vora Some of the images get missing from Ambari ui when SSL is enabled. This issue only happens in Chrome. ( Tested with Version 52.0.2743.116 (64-bit)) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18223) Atlas hook impl jars should be copied instead of the top level atlas hive hook jars for oozie hive action
[
https://issues.apache.org/jira/browse/AMBARI-18223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venkat Ranganathan updated AMBARI-18223:
Fix Version/s: trunk
Status: Patch Available (was: Open)
Currently leaving fix version to trunk
> Atlas hook impl jars should be copied instead of the top level atlas hive
> hook jars for oozie hive action
> -
>
> Key: AMBARI-18223
> URL: https://issues.apache.org/jira/browse/AMBARI-18223
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Venkat Ranganathan
>Assignee: Venkat Ranganathan
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18223.patch
>
>
> If we have the complete hive hook copied to Hive sharelib, then after
> localization all the classpaths are there and this leads to stack overflow
> errors like below
> {noformat}
> oading data to table default.hcatprocesstest_output_table partition
> (dt=2010-01-01-20)
> Partition default.hcatprocesstest_output_table{dt=2010-01-01-20} stats:
> [numFiles=1, numRows=3, totalSize=30, rawDataSize=27]
> Failing Oozie Launcher, Main class [org.apache.oozie.action.hadoop.HiveMain],
> main() threw exception, null
> java.lang.StackOverflowError
> at java.lang.Exception.(Exception.java:102)
> at
> java.lang.ReflectiveOperationException.(ReflectiveOperationException.java:89)
> at
> java.lang.reflect.InvocationTargetException.(InvocationTargetException.java:72)
> at sun.reflect.GeneratedConstructorAccessor21.newInstance(Unknown
> Source)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at java.lang.Class.newInstance(Class.java:442)
> at org.apache.atlas.hive.hook.HiveHook.initialize(HiveHook.java:76)
> at org.apache.atlas.hive.hook.HiveHook.(HiveHook.java:41)
> at sun.reflect.GeneratedConstructorAccessor21.newInstance(Unknown
> Source)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at java.lang.Class.newInstance(Class.java:442)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18223) Atlas hook impl jars should be copied instead of the top level atlas hive hook jars for oozie hive action
[
https://issues.apache.org/jira/browse/AMBARI-18223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venkat Ranganathan updated AMBARI-18223:
Attachment: AMBARI-18223.patch
> Atlas hook impl jars should be copied instead of the top level atlas hive
> hook jars for oozie hive action
> -
>
> Key: AMBARI-18223
> URL: https://issues.apache.org/jira/browse/AMBARI-18223
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Venkat Ranganathan
>Assignee: Venkat Ranganathan
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18223.patch
>
>
> If we have the complete hive hook copied to Hive sharelib, then after
> localization all the classpaths are there and this leads to stack overflow
> errors like below
> {noformat}
> oading data to table default.hcatprocesstest_output_table partition
> (dt=2010-01-01-20)
> Partition default.hcatprocesstest_output_table{dt=2010-01-01-20} stats:
> [numFiles=1, numRows=3, totalSize=30, rawDataSize=27]
> Failing Oozie Launcher, Main class [org.apache.oozie.action.hadoop.HiveMain],
> main() threw exception, null
> java.lang.StackOverflowError
> at java.lang.Exception.(Exception.java:102)
> at
> java.lang.ReflectiveOperationException.(ReflectiveOperationException.java:89)
> at
> java.lang.reflect.InvocationTargetException.(InvocationTargetException.java:72)
> at sun.reflect.GeneratedConstructorAccessor21.newInstance(Unknown
> Source)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at java.lang.Class.newInstance(Class.java:442)
> at org.apache.atlas.hive.hook.HiveHook.initialize(HiveHook.java:76)
> at org.apache.atlas.hive.hook.HiveHook.(HiveHook.java:41)
> at sun.reflect.GeneratedConstructorAccessor21.newInstance(Unknown
> Source)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at java.lang.Class.newInstance(Class.java:442)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18223) Atlas hook impl jars should be copied instead of the top level atlas hive hook jars for oozie hive action
[
https://issues.apache.org/jira/browse/AMBARI-18223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venkat Ranganathan updated AMBARI-18223:
Description:
If we have the complete hive hook copied to Hive sharelib, then after
localization all the classpaths are there and this leads to stack overflow
errors like below
{noformat}
oading data to table default.hcatprocesstest_output_table partition
(dt=2010-01-01-20)
Partition default.hcatprocesstest_output_table{dt=2010-01-01-20} stats:
[numFiles=1, numRows=3, totalSize=30, rawDataSize=27]
Failing Oozie Launcher, Main class [org.apache.oozie.action.hadoop.HiveMain],
main() threw exception, null
java.lang.StackOverflowError
at java.lang.Exception.(Exception.java:102)
at
java.lang.ReflectiveOperationException.(ReflectiveOperationException.java:89)
at
java.lang.reflect.InvocationTargetException.(InvocationTargetException.java:72)
at sun.reflect.GeneratedConstructorAccessor21.newInstance(Unknown
Source)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at java.lang.Class.newInstance(Class.java:442)
at org.apache.atlas.hive.hook.HiveHook.initialize(HiveHook.java:76)
at org.apache.atlas.hive.hook.HiveHook.(HiveHook.java:41)
at sun.reflect.GeneratedConstructorAccessor21.newInstance(Unknown
Source)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at java.lang.Class.newInstance(Class.java:442)
{noformat}
> Atlas hook impl jars should be copied instead of the top level atlas hive
> hook jars for oozie hive action
> -
>
> Key: AMBARI-18223
> URL: https://issues.apache.org/jira/browse/AMBARI-18223
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Venkat Ranganathan
>Assignee: Venkat Ranganathan
>Priority: Critical
>
> If we have the complete hive hook copied to Hive sharelib, then after
> localization all the classpaths are there and this leads to stack overflow
> errors like below
> {noformat}
> oading data to table default.hcatprocesstest_output_table partition
> (dt=2010-01-01-20)
> Partition default.hcatprocesstest_output_table{dt=2010-01-01-20} stats:
> [numFiles=1, numRows=3, totalSize=30, rawDataSize=27]
> Failing Oozie Launcher, Main class [org.apache.oozie.action.hadoop.HiveMain],
> main() threw exception, null
> java.lang.StackOverflowError
> at java.lang.Exception.(Exception.java:102)
> at
> java.lang.ReflectiveOperationException.(ReflectiveOperationException.java:89)
> at
> java.lang.reflect.InvocationTargetException.(InvocationTargetException.java:72)
> at sun.reflect.GeneratedConstructorAccessor21.newInstance(Unknown
> Source)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at java.lang.Class.newInstance(Class.java:442)
> at org.apache.atlas.hive.hook.HiveHook.initialize(HiveHook.java:76)
> at org.apache.atlas.hive.hook.HiveHook.(HiveHook.java:41)
> at sun.reflect.GeneratedConstructorAccessor21.newInstance(Unknown
> Source)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at java.lang.Class.newInstance(Class.java:442)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18220) Namenode start failed on moving namenode on a HA cluster
[ https://issues.apache.org/jira/browse/AMBARI-18220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429583#comment-15429583 ] Hudson commented on AMBARI-18220: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5562 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5562/]) AMBARI-18220. Namenode start failed on moving namenode on a HA cluster. (jaimin: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=5eb69463ed475072ab4a0a038e6f35d5b9b70fe2]) * (edit) ambari-web/app/controllers/main/service/reassign/step4_controller.js * (edit) ambari-web/test/controllers/main/service/reassign/step4_controller_test.js * (edit) ambari-web/app/views/main/service/reassign/step5_view.js > Namenode start failed on moving namenode on a HA cluster > - > > Key: AMBARI-18220 > URL: https://issues.apache.org/jira/browse/AMBARI-18220 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly >Priority: Critical > Labels: 240RMApproved > Fix For: 2.4.0 > > Attachments: AMBARI-18220.patch > > > *STR:* > 1. Enable NameNode HA > 2. Launch "move namendode" wizard > *Actual Result:* On the page "Configure Component" at the step to start > namenode, both namenodes are started. This leads to failure of the request > intermittently > *Expected Result:* Only one namenode "the one which is not being moved" > should be started -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18223) Atlas hook impl jars should be copied instead of the top level atlas hive hook jars for oozie hive action
Venkat Ranganathan created AMBARI-18223: --- Summary: Atlas hook impl jars should be copied instead of the top level atlas hive hook jars for oozie hive action Key: AMBARI-18223 URL: https://issues.apache.org/jira/browse/AMBARI-18223 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.4.0 Reporter: Venkat Ranganathan Assignee: Venkat Ranganathan Priority: Critical -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-18219) Ambari should use oozied.sh for stopping oozie so that optional catalina args can be provided
[ https://issues.apache.org/jira/browse/AMBARI-18219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty resolved AMBARI-18219. Resolution: Fixed Committed the addendum patch > Ambari should use oozied.sh for stopping oozie so that optional catalina args > can be provided > - > > Key: AMBARI-18219 > URL: https://issues.apache.org/jira/browse/AMBARI-18219 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Venkat Ranganathan >Assignee: Venkat Ranganathan >Priority: Blocker > Labels: 240RMApproved > Fix For: 2.4.0 > > Attachments: AMBARI-18219-2.patch, AMBARI-18219.patch > > > In some scenarios, the oozie stop can take longer and if a oozie start is > attempted it can fail with address already in use -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18219) Ambari should use oozied.sh for stopping oozie so that optional catalina args can be provided
[ https://issues.apache.org/jira/browse/AMBARI-18219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429574#comment-15429574 ] Sumit Mohanty commented on AMBARI-18219: +1 for the addendum patch. Good to have the force option in case stop hangs. > Ambari should use oozied.sh for stopping oozie so that optional catalina args > can be provided > - > > Key: AMBARI-18219 > URL: https://issues.apache.org/jira/browse/AMBARI-18219 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Venkat Ranganathan >Assignee: Venkat Ranganathan >Priority: Blocker > Labels: 240RMApproved > Fix For: 2.4.0 > > Attachments: AMBARI-18219-2.patch, AMBARI-18219.patch > > > In some scenarios, the oozie stop can take longer and if a oozie start is > attempted it can fail with address already in use -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18219) Ambari should use oozied.sh for stopping oozie so that optional catalina args can be provided
[ https://issues.apache.org/jira/browse/AMBARI-18219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkat Ranganathan updated AMBARI-18219: Attachment: AMBARI-18219-2.patch Fixed patch > Ambari should use oozied.sh for stopping oozie so that optional catalina args > can be provided > - > > Key: AMBARI-18219 > URL: https://issues.apache.org/jira/browse/AMBARI-18219 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Venkat Ranganathan >Assignee: Venkat Ranganathan >Priority: Blocker > Labels: 240RMApproved > Fix For: 2.4.0 > > Attachments: AMBARI-18219-2.patch, AMBARI-18219.patch > > > In some scenarios, the oozie stop can take longer and if a oozie start is > attempted it can fail with address already in use -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (AMBARI-18219) Ambari should use oozied.sh for stopping oozie so that optional catalina args can be provided
[ https://issues.apache.org/jira/browse/AMBARI-18219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkat Ranganathan reopened AMBARI-18219: - The third argument is missing "-" It should be -force. Somehow while creating the patch from the Oozie test, i edited to miss it. Fixing it > Ambari should use oozied.sh for stopping oozie so that optional catalina args > can be provided > - > > Key: AMBARI-18219 > URL: https://issues.apache.org/jira/browse/AMBARI-18219 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Venkat Ranganathan >Assignee: Venkat Ranganathan >Priority: Blocker > Labels: 240RMApproved > Fix For: 2.4.0 > > Attachments: AMBARI-18219.patch > > > In some scenarios, the oozie stop can take longer and if a oozie start is > attempted it can fail with address already in use -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18222) AMS service check fails after disabling kerberos
[
https://issues.apache.org/jira/browse/AMBARI-18222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shreya Bhat updated AMBARI-18222:
-
Fix Version/s: (was: 2.4.0)
trunk
> AMS service check fails after disabling kerberos
>
>
> Key: AMBARI-18222
> URL: https://issues.apache.org/jira/browse/AMBARI-18222
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Shreya Bhat
>Priority: Blocker
> Labels: system_test
> Fix For: trunk
>
>
> Stderr :
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/service_check.py",
> line 184, in
> AMSServiceCheck().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/service_check.py",
> line 177, in service_check
> raise Fail("Values %s and %s were not found in the response." %
> (random_value1, current_time))
> resource_management.core.exceptions.Fail: Values 0.454636953896 and
> 1471703701000 were not found in the response
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18221) Oozie server start fails while enabling wire encryption with Atlas
[
https://issues.apache.org/jira/browse/AMBARI-18221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429566#comment-15429566
]
Hudson commented on AMBARI-18221:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5561 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5561/])
AMBARI-18221. Oozie server start fails while enabling wire encryption
(smohanty:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=fe768ad8767fcd82ce13b8d762f987efa8557df2])
* (edit)
ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie.py
> Oozie server start fails while enabling wire encryption with Atlas
> --
>
> Key: AMBARI-18221
> URL: https://issues.apache.org/jira/browse/AMBARI-18221
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Blocker
> Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: AMBARI-18221.patch
>
>
> Oozie start fails with the following after wire encryption is enabled.
> {code}
> 2016-08-20 17:16:11,341 - Execute['cd /var/tmp/oozie &&
> /usr/hdp/current/oozie-server/bin/oozie-start.sh'] {'environment':
> {'OOZIE_CONFIG': '/usr/hdp/current/oozie-server/conf'}, 'not_if':
> "ambari-sudo.sh su oozie -l -s /bin/bash -c 'ls /var/run/oozie/oozie.pid
> >/dev/null 2>&1 && ps -p `cat /var/run/oozie/oozie.pid` >/dev/null 2>&1'",
> 'user': 'oozie'}
> 2016-08-20 17:16:15,494 - Found 3 files/directories inside Atlas Hive hook
> directory /usr/hdp/2.5.0.0-1234/atlas/hook/hive/
> 2016-08-20 17:16:15,701 - call['source
> /usr/hdp/current/oozie-server/conf/oozie-env.sh ; oozie admin -shareliblist
> hive | grep "\[Available ShareLib\]" -A 5'] {'logoutput': True, 'tries': 10,
> 'user': 'oozie', 'try_sleep': 5}
> Error: IO_ERROR : java.io.IOException: Error while connecting Oozie server.
> No of retries = 1. Exception = Could not authenticate, Authentication failed,
> URL:
> http://nat-s11-4-bjps-stackdeploy-4.openstacklocal:11000/oozie/versions?user.name=oozie,
> status: 302, message: Found
> 2016-08-20 17:16:34,257 - Retrying after 5 seconds. Reason: Execution of
> 'source /usr/hdp/current/oozie-server/conf/oozie-env.sh ; oozie admin
> -shareliblist hive | grep "\[Available ShareLib\]" -A 5' returned 1. Error:
> IO_ERROR : java.io.IOException: Error while connecting Oozie server. No of
> retries = 1. Exception = Could not authenticate, Authentication failed, URL:
> http://nat-s11-4-bjps-stackdeploy-4.openstacklocal:11000/oozie/versions?user.name=oozie,
> status: 302, message: Found
> {code}
> Looks like the oozie URL used is still pointing to the http instead of https.
> This is result of call {{oozie admin -shareliblist hive}} where it defaults
> to http url. So the calls need to be modified to include {{-oozie oozie_url}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18220) Namenode start failed on moving namenode on a HA cluster
[ https://issues.apache.org/jira/browse/AMBARI-18220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-18220: Resolution: Fixed Status: Resolved (was: Patch Available) +1 received on reviewboard. Patch committed to trunk and branch-2.4 > Namenode start failed on moving namenode on a HA cluster > - > > Key: AMBARI-18220 > URL: https://issues.apache.org/jira/browse/AMBARI-18220 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly >Priority: Critical > Labels: 240RMApproved > Fix For: 2.4.0 > > Attachments: AMBARI-18220.patch > > > *STR:* > 1. Enable NameNode HA > 2. Launch "move namendode" wizard > *Actual Result:* On the page "Configure Component" at the step to start > namenode, both namenodes are started. This leads to failure of the request > intermittently > *Expected Result:* Only one namenode "the one which is not being moved" > should be started -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18222) AMS service check fails after disabling kerberos
Shreya Bhat created AMBARI-18222:
Summary: AMS service check fails after disabling kerberos
Key: AMBARI-18222
URL: https://issues.apache.org/jira/browse/AMBARI-18222
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.4.0
Reporter: Shreya Bhat
Priority: Blocker
Fix For: 2.4.0
Stderr :
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/service_check.py",
line 184, in
AMSServiceCheck().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 280, in execute
method(env)
File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
line 89, in thunk
return fn(*args, **kwargs)
File
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/service_check.py",
line 177, in service_check
raise Fail("Values %s and %s were not found in the response." %
(random_value1, current_time))
resource_management.core.exceptions.Fail: Values 0.454636953896 and
1471703701000 were not found in the response
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18221) Oozie server start fails while enabling wire encryption with Atlas
[
https://issues.apache.org/jira/browse/AMBARI-18221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-18221:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk and branch-2.4
> Oozie server start fails while enabling wire encryption with Atlas
> --
>
> Key: AMBARI-18221
> URL: https://issues.apache.org/jira/browse/AMBARI-18221
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Blocker
> Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: AMBARI-18221.patch
>
>
> Oozie start fails with the following after wire encryption is enabled.
> {code}
> 2016-08-20 17:16:11,341 - Execute['cd /var/tmp/oozie &&
> /usr/hdp/current/oozie-server/bin/oozie-start.sh'] {'environment':
> {'OOZIE_CONFIG': '/usr/hdp/current/oozie-server/conf'}, 'not_if':
> "ambari-sudo.sh su oozie -l -s /bin/bash -c 'ls /var/run/oozie/oozie.pid
> >/dev/null 2>&1 && ps -p `cat /var/run/oozie/oozie.pid` >/dev/null 2>&1'",
> 'user': 'oozie'}
> 2016-08-20 17:16:15,494 - Found 3 files/directories inside Atlas Hive hook
> directory /usr/hdp/2.5.0.0-1234/atlas/hook/hive/
> 2016-08-20 17:16:15,701 - call['source
> /usr/hdp/current/oozie-server/conf/oozie-env.sh ; oozie admin -shareliblist
> hive | grep "\[Available ShareLib\]" -A 5'] {'logoutput': True, 'tries': 10,
> 'user': 'oozie', 'try_sleep': 5}
> Error: IO_ERROR : java.io.IOException: Error while connecting Oozie server.
> No of retries = 1. Exception = Could not authenticate, Authentication failed,
> URL:
> http://nat-s11-4-bjps-stackdeploy-4.openstacklocal:11000/oozie/versions?user.name=oozie,
> status: 302, message: Found
> 2016-08-20 17:16:34,257 - Retrying after 5 seconds. Reason: Execution of
> 'source /usr/hdp/current/oozie-server/conf/oozie-env.sh ; oozie admin
> -shareliblist hive | grep "\[Available ShareLib\]" -A 5' returned 1. Error:
> IO_ERROR : java.io.IOException: Error while connecting Oozie server. No of
> retries = 1. Exception = Could not authenticate, Authentication failed, URL:
> http://nat-s11-4-bjps-stackdeploy-4.openstacklocal:11000/oozie/versions?user.name=oozie,
> status: 302, message: Found
> {code}
> Looks like the oozie URL used is still pointing to the http instead of https.
> This is result of call {{oozie admin -shareliblist hive}} where it defaults
> to http url. So the calls need to be modified to include {{-oozie oozie_url}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18221) Oozie server start fails while enabling wire encryption with Atlas
[
https://issues.apache.org/jira/browse/AMBARI-18221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-18221:
---
Summary: Oozie server start fails while enabling wire encryption with Atlas
(was: Oozie server start fails while enabling wire encryption)
> Oozie server start fails while enabling wire encryption with Atlas
> --
>
> Key: AMBARI-18221
> URL: https://issues.apache.org/jira/browse/AMBARI-18221
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Blocker
> Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: AMBARI-18221.patch
>
>
> Oozie start fails with the following after wire encryption is enabled.
> {code}
> 2016-08-20 17:16:11,341 - Execute['cd /var/tmp/oozie &&
> /usr/hdp/current/oozie-server/bin/oozie-start.sh'] {'environment':
> {'OOZIE_CONFIG': '/usr/hdp/current/oozie-server/conf'}, 'not_if':
> "ambari-sudo.sh su oozie -l -s /bin/bash -c 'ls /var/run/oozie/oozie.pid
> >/dev/null 2>&1 && ps -p `cat /var/run/oozie/oozie.pid` >/dev/null 2>&1'",
> 'user': 'oozie'}
> 2016-08-20 17:16:15,494 - Found 3 files/directories inside Atlas Hive hook
> directory /usr/hdp/2.5.0.0-1234/atlas/hook/hive/
> 2016-08-20 17:16:15,701 - call['source
> /usr/hdp/current/oozie-server/conf/oozie-env.sh ; oozie admin -shareliblist
> hive | grep "\[Available ShareLib\]" -A 5'] {'logoutput': True, 'tries': 10,
> 'user': 'oozie', 'try_sleep': 5}
> Error: IO_ERROR : java.io.IOException: Error while connecting Oozie server.
> No of retries = 1. Exception = Could not authenticate, Authentication failed,
> URL:
> http://nat-s11-4-bjps-stackdeploy-4.openstacklocal:11000/oozie/versions?user.name=oozie,
> status: 302, message: Found
> 2016-08-20 17:16:34,257 - Retrying after 5 seconds. Reason: Execution of
> 'source /usr/hdp/current/oozie-server/conf/oozie-env.sh ; oozie admin
> -shareliblist hive | grep "\[Available ShareLib\]" -A 5' returned 1. Error:
> IO_ERROR : java.io.IOException: Error while connecting Oozie server. No of
> retries = 1. Exception = Could not authenticate, Authentication failed, URL:
> http://nat-s11-4-bjps-stackdeploy-4.openstacklocal:11000/oozie/versions?user.name=oozie,
> status: 302, message: Found
> {code}
> Looks like the oozie URL used is still pointing to the http instead of https.
> This is result of call {{oozie admin -shareliblist hive}} where it defaults
> to http url. So the calls need to be modified to include {{-oozie oozie_url}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18219) Ambari should use oozied.sh for stopping oozie so that optional catalina args can be provided
[ https://issues.apache.org/jira/browse/AMBARI-18219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18219: --- Labels: 240RMApproved (was: ) > Ambari should use oozied.sh for stopping oozie so that optional catalina args > can be provided > - > > Key: AMBARI-18219 > URL: https://issues.apache.org/jira/browse/AMBARI-18219 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Venkat Ranganathan >Assignee: Venkat Ranganathan >Priority: Blocker > Labels: 240RMApproved > Fix For: 2.4.0 > > Attachments: AMBARI-18219.patch > > > In some scenarios, the oozie stop can take longer and if a oozie start is > attempted it can fail with address already in use -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18221) Oozie server start fails while enabling wire encryption
[
https://issues.apache.org/jira/browse/AMBARI-18221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-18221:
---
Labels: 240RMApproved (was: )
> Oozie server start fails while enabling wire encryption
> ---
>
> Key: AMBARI-18221
> URL: https://issues.apache.org/jira/browse/AMBARI-18221
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Blocker
> Labels: 240RMApproved
> Fix For: 2.4.0
>
> Attachments: AMBARI-18221.patch
>
>
> Oozie start fails with the following after wire encryption is enabled.
> {code}
> 2016-08-20 17:16:11,341 - Execute['cd /var/tmp/oozie &&
> /usr/hdp/current/oozie-server/bin/oozie-start.sh'] {'environment':
> {'OOZIE_CONFIG': '/usr/hdp/current/oozie-server/conf'}, 'not_if':
> "ambari-sudo.sh su oozie -l -s /bin/bash -c 'ls /var/run/oozie/oozie.pid
> >/dev/null 2>&1 && ps -p `cat /var/run/oozie/oozie.pid` >/dev/null 2>&1'",
> 'user': 'oozie'}
> 2016-08-20 17:16:15,494 - Found 3 files/directories inside Atlas Hive hook
> directory /usr/hdp/2.5.0.0-1234/atlas/hook/hive/
> 2016-08-20 17:16:15,701 - call['source
> /usr/hdp/current/oozie-server/conf/oozie-env.sh ; oozie admin -shareliblist
> hive | grep "\[Available ShareLib\]" -A 5'] {'logoutput': True, 'tries': 10,
> 'user': 'oozie', 'try_sleep': 5}
> Error: IO_ERROR : java.io.IOException: Error while connecting Oozie server.
> No of retries = 1. Exception = Could not authenticate, Authentication failed,
> URL:
> http://nat-s11-4-bjps-stackdeploy-4.openstacklocal:11000/oozie/versions?user.name=oozie,
> status: 302, message: Found
> 2016-08-20 17:16:34,257 - Retrying after 5 seconds. Reason: Execution of
> 'source /usr/hdp/current/oozie-server/conf/oozie-env.sh ; oozie admin
> -shareliblist hive | grep "\[Available ShareLib\]" -A 5' returned 1. Error:
> IO_ERROR : java.io.IOException: Error while connecting Oozie server. No of
> retries = 1. Exception = Could not authenticate, Authentication failed, URL:
> http://nat-s11-4-bjps-stackdeploy-4.openstacklocal:11000/oozie/versions?user.name=oozie,
> status: 302, message: Found
> {code}
> Looks like the oozie URL used is still pointing to the http instead of https.
> This is result of call {{oozie admin -shareliblist hive}} where it defaults
> to http url. So the calls need to be modified to include {{-oozie oozie_url}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18221) Oozie server start fails while enabling wire encryption
[
https://issues.apache.org/jira/browse/AMBARI-18221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-18221:
---
Priority: Blocker (was: Critical)
> Oozie server start fails while enabling wire encryption
> ---
>
> Key: AMBARI-18221
> URL: https://issues.apache.org/jira/browse/AMBARI-18221
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18221.patch
>
>
> Oozie start fails with the following after wire encryption is enabled.
> {code}
> 2016-08-20 17:16:11,341 - Execute['cd /var/tmp/oozie &&
> /usr/hdp/current/oozie-server/bin/oozie-start.sh'] {'environment':
> {'OOZIE_CONFIG': '/usr/hdp/current/oozie-server/conf'}, 'not_if':
> "ambari-sudo.sh su oozie -l -s /bin/bash -c 'ls /var/run/oozie/oozie.pid
> >/dev/null 2>&1 && ps -p `cat /var/run/oozie/oozie.pid` >/dev/null 2>&1'",
> 'user': 'oozie'}
> 2016-08-20 17:16:15,494 - Found 3 files/directories inside Atlas Hive hook
> directory /usr/hdp/2.5.0.0-1234/atlas/hook/hive/
> 2016-08-20 17:16:15,701 - call['source
> /usr/hdp/current/oozie-server/conf/oozie-env.sh ; oozie admin -shareliblist
> hive | grep "\[Available ShareLib\]" -A 5'] {'logoutput': True, 'tries': 10,
> 'user': 'oozie', 'try_sleep': 5}
> Error: IO_ERROR : java.io.IOException: Error while connecting Oozie server.
> No of retries = 1. Exception = Could not authenticate, Authentication failed,
> URL:
> http://nat-s11-4-bjps-stackdeploy-4.openstacklocal:11000/oozie/versions?user.name=oozie,
> status: 302, message: Found
> 2016-08-20 17:16:34,257 - Retrying after 5 seconds. Reason: Execution of
> 'source /usr/hdp/current/oozie-server/conf/oozie-env.sh ; oozie admin
> -shareliblist hive | grep "\[Available ShareLib\]" -A 5' returned 1. Error:
> IO_ERROR : java.io.IOException: Error while connecting Oozie server. No of
> retries = 1. Exception = Could not authenticate, Authentication failed, URL:
> http://nat-s11-4-bjps-stackdeploy-4.openstacklocal:11000/oozie/versions?user.name=oozie,
> status: 302, message: Found
> {code}
> Looks like the oozie URL used is still pointing to the http instead of https.
> This is result of call {{oozie admin -shareliblist hive}} where it defaults
> to http url. So the calls need to be modified to include {{-oozie oozie_url}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18221) Oozie server start fails while enabling wire encryption
[
https://issues.apache.org/jira/browse/AMBARI-18221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429538#comment-15429538
]
Venkat Ranganathan commented on AMBARI-18221:
-
+1
> Oozie server start fails while enabling wire encryption
> ---
>
> Key: AMBARI-18221
> URL: https://issues.apache.org/jira/browse/AMBARI-18221
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-18221.patch
>
>
> Oozie start fails with the following after wire encryption is enabled.
> {code}
> 2016-08-20 17:16:11,341 - Execute['cd /var/tmp/oozie &&
> /usr/hdp/current/oozie-server/bin/oozie-start.sh'] {'environment':
> {'OOZIE_CONFIG': '/usr/hdp/current/oozie-server/conf'}, 'not_if':
> "ambari-sudo.sh su oozie -l -s /bin/bash -c 'ls /var/run/oozie/oozie.pid
> >/dev/null 2>&1 && ps -p `cat /var/run/oozie/oozie.pid` >/dev/null 2>&1'",
> 'user': 'oozie'}
> 2016-08-20 17:16:15,494 - Found 3 files/directories inside Atlas Hive hook
> directory /usr/hdp/2.5.0.0-1234/atlas/hook/hive/
> 2016-08-20 17:16:15,701 - call['source
> /usr/hdp/current/oozie-server/conf/oozie-env.sh ; oozie admin -shareliblist
> hive | grep "\[Available ShareLib\]" -A 5'] {'logoutput': True, 'tries': 10,
> 'user': 'oozie', 'try_sleep': 5}
> Error: IO_ERROR : java.io.IOException: Error while connecting Oozie server.
> No of retries = 1. Exception = Could not authenticate, Authentication failed,
> URL:
> http://nat-s11-4-bjps-stackdeploy-4.openstacklocal:11000/oozie/versions?user.name=oozie,
> status: 302, message: Found
> 2016-08-20 17:16:34,257 - Retrying after 5 seconds. Reason: Execution of
> 'source /usr/hdp/current/oozie-server/conf/oozie-env.sh ; oozie admin
> -shareliblist hive | grep "\[Available ShareLib\]" -A 5' returned 1. Error:
> IO_ERROR : java.io.IOException: Error while connecting Oozie server. No of
> retries = 1. Exception = Could not authenticate, Authentication failed, URL:
> http://nat-s11-4-bjps-stackdeploy-4.openstacklocal:11000/oozie/versions?user.name=oozie,
> status: 302, message: Found
> {code}
> Looks like the oozie URL used is still pointing to the http instead of https.
> This is result of call {{oozie admin -shareliblist hive}} where it defaults
> to http url. So the calls need to be modified to include {{-oozie oozie_url}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18221) Oozie server start fails while enabling wire encryption
[
https://issues.apache.org/jira/browse/AMBARI-18221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429537#comment-15429537
]
Sumit Mohanty commented on AMBARI-18221:
Ran all unit tests locally for stacks:
{code}
--
Ran 267 tests in 6.961s
OK
--
Total run:1118
Total errors:0
Total failures:0
OK
{code}
> Oozie server start fails while enabling wire encryption
> ---
>
> Key: AMBARI-18221
> URL: https://issues.apache.org/jira/browse/AMBARI-18221
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-18221.patch
>
>
> Oozie start fails with the following after wire encryption is enabled.
> {code}
> 2016-08-20 17:16:11,341 - Execute['cd /var/tmp/oozie &&
> /usr/hdp/current/oozie-server/bin/oozie-start.sh'] {'environment':
> {'OOZIE_CONFIG': '/usr/hdp/current/oozie-server/conf'}, 'not_if':
> "ambari-sudo.sh su oozie -l -s /bin/bash -c 'ls /var/run/oozie/oozie.pid
> >/dev/null 2>&1 && ps -p `cat /var/run/oozie/oozie.pid` >/dev/null 2>&1'",
> 'user': 'oozie'}
> 2016-08-20 17:16:15,494 - Found 3 files/directories inside Atlas Hive hook
> directory /usr/hdp/2.5.0.0-1234/atlas/hook/hive/
> 2016-08-20 17:16:15,701 - call['source
> /usr/hdp/current/oozie-server/conf/oozie-env.sh ; oozie admin -shareliblist
> hive | grep "\[Available ShareLib\]" -A 5'] {'logoutput': True, 'tries': 10,
> 'user': 'oozie', 'try_sleep': 5}
> Error: IO_ERROR : java.io.IOException: Error while connecting Oozie server.
> No of retries = 1. Exception = Could not authenticate, Authentication failed,
> URL:
> http://nat-s11-4-bjps-stackdeploy-4.openstacklocal:11000/oozie/versions?user.name=oozie,
> status: 302, message: Found
> 2016-08-20 17:16:34,257 - Retrying after 5 seconds. Reason: Execution of
> 'source /usr/hdp/current/oozie-server/conf/oozie-env.sh ; oozie admin
> -shareliblist hive | grep "\[Available ShareLib\]" -A 5' returned 1. Error:
> IO_ERROR : java.io.IOException: Error while connecting Oozie server. No of
> retries = 1. Exception = Could not authenticate, Authentication failed, URL:
> http://nat-s11-4-bjps-stackdeploy-4.openstacklocal:11000/oozie/versions?user.name=oozie,
> status: 302, message: Found
> {code}
> Looks like the oozie URL used is still pointing to the http instead of https.
> This is result of call {{oozie admin -shareliblist hive}} where it defaults
> to http url. So the calls need to be modified to include {{-oozie oozie_url}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18221) Oozie server start fails while enabling wire encryption
[
https://issues.apache.org/jira/browse/AMBARI-18221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-18221:
---
Status: Patch Available (was: Open)
> Oozie server start fails while enabling wire encryption
> ---
>
> Key: AMBARI-18221
> URL: https://issues.apache.org/jira/browse/AMBARI-18221
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-18221.patch
>
>
> Oozie start fails with the following after wire encryption is enabled.
> {code}
> 2016-08-20 17:16:11,341 - Execute['cd /var/tmp/oozie &&
> /usr/hdp/current/oozie-server/bin/oozie-start.sh'] {'environment':
> {'OOZIE_CONFIG': '/usr/hdp/current/oozie-server/conf'}, 'not_if':
> "ambari-sudo.sh su oozie -l -s /bin/bash -c 'ls /var/run/oozie/oozie.pid
> >/dev/null 2>&1 && ps -p `cat /var/run/oozie/oozie.pid` >/dev/null 2>&1'",
> 'user': 'oozie'}
> 2016-08-20 17:16:15,494 - Found 3 files/directories inside Atlas Hive hook
> directory /usr/hdp/2.5.0.0-1234/atlas/hook/hive/
> 2016-08-20 17:16:15,701 - call['source
> /usr/hdp/current/oozie-server/conf/oozie-env.sh ; oozie admin -shareliblist
> hive | grep "\[Available ShareLib\]" -A 5'] {'logoutput': True, 'tries': 10,
> 'user': 'oozie', 'try_sleep': 5}
> Error: IO_ERROR : java.io.IOException: Error while connecting Oozie server.
> No of retries = 1. Exception = Could not authenticate, Authentication failed,
> URL:
> http://nat-s11-4-bjps-stackdeploy-4.openstacklocal:11000/oozie/versions?user.name=oozie,
> status: 302, message: Found
> 2016-08-20 17:16:34,257 - Retrying after 5 seconds. Reason: Execution of
> 'source /usr/hdp/current/oozie-server/conf/oozie-env.sh ; oozie admin
> -shareliblist hive | grep "\[Available ShareLib\]" -A 5' returned 1. Error:
> IO_ERROR : java.io.IOException: Error while connecting Oozie server. No of
> retries = 1. Exception = Could not authenticate, Authentication failed, URL:
> http://nat-s11-4-bjps-stackdeploy-4.openstacklocal:11000/oozie/versions?user.name=oozie,
> status: 302, message: Found
> {code}
> Looks like the oozie URL used is still pointing to the http instead of https.
> This is result of call {{oozie admin -shareliblist hive}} where it defaults
> to http url. So the calls need to be modified to include {{-oozie oozie_url}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18221) Oozie server start fails while enabling wire encryption
[
https://issues.apache.org/jira/browse/AMBARI-18221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-18221:
---
Attachment: AMBARI-18221.patch
> Oozie server start fails while enabling wire encryption
> ---
>
> Key: AMBARI-18221
> URL: https://issues.apache.org/jira/browse/AMBARI-18221
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-18221.patch
>
>
> Oozie start fails with the following after wire encryption is enabled.
> {code}
> 2016-08-20 17:16:11,341 - Execute['cd /var/tmp/oozie &&
> /usr/hdp/current/oozie-server/bin/oozie-start.sh'] {'environment':
> {'OOZIE_CONFIG': '/usr/hdp/current/oozie-server/conf'}, 'not_if':
> "ambari-sudo.sh su oozie -l -s /bin/bash -c 'ls /var/run/oozie/oozie.pid
> >/dev/null 2>&1 && ps -p `cat /var/run/oozie/oozie.pid` >/dev/null 2>&1'",
> 'user': 'oozie'}
> 2016-08-20 17:16:15,494 - Found 3 files/directories inside Atlas Hive hook
> directory /usr/hdp/2.5.0.0-1234/atlas/hook/hive/
> 2016-08-20 17:16:15,701 - call['source
> /usr/hdp/current/oozie-server/conf/oozie-env.sh ; oozie admin -shareliblist
> hive | grep "\[Available ShareLib\]" -A 5'] {'logoutput': True, 'tries': 10,
> 'user': 'oozie', 'try_sleep': 5}
> Error: IO_ERROR : java.io.IOException: Error while connecting Oozie server.
> No of retries = 1. Exception = Could not authenticate, Authentication failed,
> URL:
> http://nat-s11-4-bjps-stackdeploy-4.openstacklocal:11000/oozie/versions?user.name=oozie,
> status: 302, message: Found
> 2016-08-20 17:16:34,257 - Retrying after 5 seconds. Reason: Execution of
> 'source /usr/hdp/current/oozie-server/conf/oozie-env.sh ; oozie admin
> -shareliblist hive | grep "\[Available ShareLib\]" -A 5' returned 1. Error:
> IO_ERROR : java.io.IOException: Error while connecting Oozie server. No of
> retries = 1. Exception = Could not authenticate, Authentication failed, URL:
> http://nat-s11-4-bjps-stackdeploy-4.openstacklocal:11000/oozie/versions?user.name=oozie,
> status: 302, message: Found
> {code}
> Looks like the oozie URL used is still pointing to the http instead of https.
> This is result of call {{oozie admin -shareliblist hive}} where it defaults
> to http url. So the calls need to be modified to include {{-oozie oozie_url}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18221) Oozie server start fails while enabling wire encryption
Sumit Mohanty created AMBARI-18221:
--
Summary: Oozie server start fails while enabling wire encryption
Key: AMBARI-18221
URL: https://issues.apache.org/jira/browse/AMBARI-18221
Project: Ambari
Issue Type: Bug
Components: stacks
Affects Versions: 2.4.0
Reporter: Sumit Mohanty
Assignee: Sumit Mohanty
Priority: Critical
Fix For: 2.4.0
Oozie start fails with the following after wire encryption is enabled.
{code}
2016-08-20 17:16:11,341 - Execute['cd /var/tmp/oozie &&
/usr/hdp/current/oozie-server/bin/oozie-start.sh'] {'environment':
{'OOZIE_CONFIG': '/usr/hdp/current/oozie-server/conf'}, 'not_if':
"ambari-sudo.sh su oozie -l -s /bin/bash -c 'ls /var/run/oozie/oozie.pid
>/dev/null 2>&1 && ps -p `cat /var/run/oozie/oozie.pid` >/dev/null 2>&1'",
'user': 'oozie'}
2016-08-20 17:16:15,494 - Found 3 files/directories inside Atlas Hive hook
directory /usr/hdp/2.5.0.0-1234/atlas/hook/hive/
2016-08-20 17:16:15,701 - call['source
/usr/hdp/current/oozie-server/conf/oozie-env.sh ; oozie admin -shareliblist
hive | grep "\[Available ShareLib\]" -A 5'] {'logoutput': True, 'tries': 10,
'user': 'oozie', 'try_sleep': 5}
Error: IO_ERROR : java.io.IOException: Error while connecting Oozie server. No
of retries = 1. Exception = Could not authenticate, Authentication failed, URL:
http://nat-s11-4-bjps-stackdeploy-4.openstacklocal:11000/oozie/versions?user.name=oozie,
status: 302, message: Found
2016-08-20 17:16:34,257 - Retrying after 5 seconds. Reason: Execution of
'source /usr/hdp/current/oozie-server/conf/oozie-env.sh ; oozie admin
-shareliblist hive | grep "\[Available ShareLib\]" -A 5' returned 1. Error:
IO_ERROR : java.io.IOException: Error while connecting Oozie server. No of
retries = 1. Exception = Could not authenticate, Authentication failed, URL:
http://nat-s11-4-bjps-stackdeploy-4.openstacklocal:11000/oozie/versions?user.name=oozie,
status: 302, message: Found
{code}
Looks like the oozie URL used is still pointing to the http instead of https.
This is result of call {{oozie admin -shareliblist hive}} where it defaults to
http url. So the calls need to be modified to include {{-oozie oozie_url}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18219) Ambari should use oozied.sh for stopping oozie so that optional catalina args can be provided
[ https://issues.apache.org/jira/browse/AMBARI-18219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429521#comment-15429521 ] Hudson commented on AMBARI-18219: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5560 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5560/]) AMBARI-18219. Ambari should use oozied.sh for stopping oozie so that (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=cfef220d92ed102cde2ed77fe6d12bd973a189a2]) * (edit) ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py * (edit) ambari-server/src/test/python/stacks/2.0.6/OOZIE/test_oozie_server.py > Ambari should use oozied.sh for stopping oozie so that optional catalina args > can be provided > - > > Key: AMBARI-18219 > URL: https://issues.apache.org/jira/browse/AMBARI-18219 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Venkat Ranganathan >Assignee: Venkat Ranganathan >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-18219.patch > > > In some scenarios, the oozie stop can take longer and if a oozie start is > attempted it can fail with address already in use -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18219) Ambari should use oozied.sh for stopping oozie so that optional catalina args can be provided
[ https://issues.apache.org/jira/browse/AMBARI-18219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-18219: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.4 > Ambari should use oozied.sh for stopping oozie so that optional catalina args > can be provided > - > > Key: AMBARI-18219 > URL: https://issues.apache.org/jira/browse/AMBARI-18219 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Venkat Ranganathan >Assignee: Venkat Ranganathan >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-18219.patch > > > In some scenarios, the oozie stop can take longer and if a oozie start is > attempted it can fail with address already in use -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18218) File View throws IllegalArguementException post Ambari 2.4.0.0 upgrade
[
https://issues.apache.org/jira/browse/AMBARI-18218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429504#comment-15429504
]
Hadoop QA commented on AMBARI-18218:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12824689/AMBARI-18218_branch-2.4.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8474//console
This message is automatically generated.
> File View throws IllegalArguementException post Ambari 2.4.0.0 upgrade
> --
>
> Key: AMBARI-18218
> URL: https://issues.apache.org/jira/browse/AMBARI-18218
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18218_branch-2.4.patch
>
>
> The fileView throws below exception after upgrade
> {code}
> Service 'hdfs' check failed:
> java.lang.IllegalArgumentException: The value of property
> dfs.namenode.https-address.stanleyhotel.nn1 must not be null
> at
> com.google.common.base.Preconditions.checkArgument(Preconditions.java:125)
> at org.apache.hadoop.conf.Configuration.set(Configuration.java:1134)
> at org.apache.hadoop.conf.Configuration.set(Configuration.java:1115)
> at
> org.apache.ambari.view.utils.hdfs.ConfigurationBuilder.copyClusterProperty(ConfigurationBuilder.java:227)
> at
> org.apache.ambari.view.utils.hdfs.ConfigurationBuilder.copyHAProperties(ConfigurationBuilder.java:210)
> at
> org.apache.ambari.view.utils.hdfs.ConfigurationBuilder.parseProperties(ConfigurationBuilder.java:102)
> at
> org.apache.ambari.view.utils.hdfs.ConfigurationBuilder.buildConfig(ConfigurationBuilder.java:278)
> at org.apache.ambari.view.utils.hdfs.HdfsApi.(HdfsApi.java:65)
> at
> org.apache.ambari.view.utils.hdfs.HdfsUtil.connectToHDFSApi(HdfsUtil.java:127)
> at
> org.apache.ambari.view.commons.hdfs.HdfsService.hdfsSmokeTest(HdfsService.java:136)
> at
> org.apache.ambari.view.filebrowser.HelpService.hdfsStatus(HelpService.java:86)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> 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.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> 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._handleRe
[jira] [Commented] (AMBARI-18220) Namenode start failed on moving namenode on a HA cluster
[ https://issues.apache.org/jira/browse/AMBARI-18220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429506#comment-15429506 ] Sumit Mohanty commented on AMBARI-18220: +1 on fixing this for 2.4.0. > Namenode start failed on moving namenode on a HA cluster > - > > Key: AMBARI-18220 > URL: https://issues.apache.org/jira/browse/AMBARI-18220 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-18220.patch > > > *STR:* > 1. Enable NameNode HA > 2. Launch "move namendode" wizard > *Actual Result:* On the page "Configure Component" at the step to start > namenode, both namenodes are started. This leads to failure of the request > intermittently > *Expected Result:* Only one namenode "the one which is not being moved" > should be started -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18220) Namenode start failed on moving namenode on a HA cluster
[
https://issues.apache.org/jira/browse/AMBARI-18220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429502#comment-15429502
]
Hadoop QA commented on AMBARI-18220:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12824709/AMBARI-18220.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8472//console
This message is automatically generated.
> Namenode start failed on moving namenode on a HA cluster
> -
>
> Key: AMBARI-18220
> URL: https://issues.apache.org/jira/browse/AMBARI-18220
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-18220.patch
>
>
> *STR:*
> 1. Enable NameNode HA
> 2. Launch "move namendode" wizard
> *Actual Result:* On the page "Configure Component" at the step to start
> namenode, both namenodes are started. This leads to failure of the request
> intermittently
> *Expected Result:* Only one namenode "the one which is not being moved"
> should be started
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18219) Ambari should use oozied.sh for stopping oozie so that optional catalina args can be provided
[
https://issues.apache.org/jira/browse/AMBARI-18219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429503#comment-15429503
]
Hadoop QA commented on AMBARI-18219:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12824708/AMBARI-18219.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8473//console
This message is automatically generated.
> Ambari should use oozied.sh for stopping oozie so that optional catalina args
> can be provided
> -
>
> Key: AMBARI-18219
> URL: https://issues.apache.org/jira/browse/AMBARI-18219
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Venkat Ranganathan
>Assignee: Venkat Ranganathan
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18219.patch
>
>
> In some scenarios, the oozie stop can take longer and if a oozie start is
> attempted it can fail with address already in use
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18220) Namenode start failed on moving namenode on a HA cluster
[ https://issues.apache.org/jira/browse/AMBARI-18220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429498#comment-15429498 ] Jaimin D Jetly commented on AMBARI-18220: - Thanks to [~vrathod] for bringing this issue to notice. > Namenode start failed on moving namenode on a HA cluster > - > > Key: AMBARI-18220 > URL: https://issues.apache.org/jira/browse/AMBARI-18220 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-18220.patch > > > *STR:* > 1. Enable NameNode HA > 2. Launch "move namendode" wizard > *Actual Result:* On the page "Configure Component" at the step to start > namenode, both namenodes are started. This leads to failure of the request > intermittently > *Expected Result:* Only one namenode "the one which is not being moved" > should be started -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18220) Namenode start failed on moving namenode on a HA cluster
[ https://issues.apache.org/jira/browse/AMBARI-18220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-18220: Description: *STR:* 1. Enable NameNode HA 2. Launch "move namendode" wizard *Actual Result:* On the page "Configure Component" at the step to start namenode, both namenodes are started. This leads to failure of the request intermittently *Expected Result:* Only one namenode "the one which is not being moved" should be started was: STR: 1. Enable NameNode HA 2. Launch "move namendode" wizard Actual Result: On the page "Configure Component" at the step to start namenode, both namenodes are started. This leads to failure of the request intermittently Expected Result: Only one namenode "the one which is not being moved" should be started > Namenode start failed on moving namenode on a HA cluster > - > > Key: AMBARI-18220 > URL: https://issues.apache.org/jira/browse/AMBARI-18220 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-18220.patch > > > *STR:* > 1. Enable NameNode HA > 2. Launch "move namendode" wizard > *Actual Result:* On the page "Configure Component" at the step to start > namenode, both namenodes are started. This leads to failure of the request > intermittently > *Expected Result:* Only one namenode "the one which is not being moved" > should be started -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18220) Namenode start failed on moving namenode on a HA cluster
[ https://issues.apache.org/jira/browse/AMBARI-18220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-18220: Description: STR: 1. Enable NameNode HA 2. Launch "move namendode" wizard Actual Result: On the page "Configure Component" at the step to start namenode, both namenodes are started. This leads to failure of the request intermittently Expected Result: Only one namenode "the one which is not being moved" should be started > Namenode start failed on moving namenode on a HA cluster > - > > Key: AMBARI-18220 > URL: https://issues.apache.org/jira/browse/AMBARI-18220 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-18220.patch > > > STR: > 1. Enable NameNode HA > 2. Launch "move namendode" wizard > Actual Result: On the page "Configure Component" at the step to start > namenode, both namenodes are started. This leads to failure of the request > intermittently > Expected Result: Only one namenode "the one which is not being moved" should > be started -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18219) Ambari should use oozied.sh for stopping oozie so that optional catalina args can be provided
[ https://issues.apache.org/jira/browse/AMBARI-18219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429490#comment-15429490 ] Mahadev konar commented on AMBARI-18219: +1 for the patch. > Ambari should use oozied.sh for stopping oozie so that optional catalina args > can be provided > - > > Key: AMBARI-18219 > URL: https://issues.apache.org/jira/browse/AMBARI-18219 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Venkat Ranganathan >Assignee: Venkat Ranganathan >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-18219.patch > > > In some scenarios, the oozie stop can take longer and if a oozie start is > attempted it can fail with address already in use -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18220) Namenode start failed on moving namenode on a HA cluster
[ https://issues.apache.org/jira/browse/AMBARI-18220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-18220: Status: Patch Available (was: Open) > Namenode start failed on moving namenode on a HA cluster > - > > Key: AMBARI-18220 > URL: https://issues.apache.org/jira/browse/AMBARI-18220 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-18220.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18220) Namenode start failed on moving namenode on a HA cluster
[ https://issues.apache.org/jira/browse/AMBARI-18220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-18220: Attachment: AMBARI-18220.patch > Namenode start failed on moving namenode on a HA cluster > - > > Key: AMBARI-18220 > URL: https://issues.apache.org/jira/browse/AMBARI-18220 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-18220.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18219) Ambari should use oozied.sh for stopping oozie so that optional catalina args can be provided
[ https://issues.apache.org/jira/browse/AMBARI-18219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkat Ranganathan updated AMBARI-18219: Attachment: AMBARI-18219.patch Uploaded with current bug id > Ambari should use oozied.sh for stopping oozie so that optional catalina args > can be provided > - > > Key: AMBARI-18219 > URL: https://issues.apache.org/jira/browse/AMBARI-18219 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Venkat Ranganathan >Assignee: Venkat Ranganathan >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-18219.patch > > > In some scenarios, the oozie stop can take longer and if a oozie start is > attempted it can fail with address already in use -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18219) Ambari should use oozied.sh for stopping oozie so that optional catalina args can be provided
[ https://issues.apache.org/jira/browse/AMBARI-18219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429485#comment-15429485 ] Sumit Mohanty commented on AMBARI-18219: Changes look good - +1 > Ambari should use oozied.sh for stopping oozie so that optional catalina args > can be provided > - > > Key: AMBARI-18219 > URL: https://issues.apache.org/jira/browse/AMBARI-18219 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Venkat Ranganathan >Assignee: Venkat Ranganathan >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-18219.patch > > > In some scenarios, the oozie stop can take longer and if a oozie start is > attempted it can fail with address already in use -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18219) Ambari should use oozied.sh for stopping oozie so that optional catalina args can be provided
[ https://issues.apache.org/jira/browse/AMBARI-18219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkat Ranganathan updated AMBARI-18219: Attachment: (was: AMBARI-18129.patch) > Ambari should use oozied.sh for stopping oozie so that optional catalina args > can be provided > - > > Key: AMBARI-18219 > URL: https://issues.apache.org/jira/browse/AMBARI-18219 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Venkat Ranganathan >Assignee: Venkat Ranganathan >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-18219.patch > > > In some scenarios, the oozie stop can take longer and if a oozie start is > attempted it can fail with address already in use -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18219) Ambari should use oozied.sh for stopping oozie so that optional catalina args can be provided
[ https://issues.apache.org/jira/browse/AMBARI-18219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkat Ranganathan updated AMBARI-18219: Status: Patch Available (was: Open) > Ambari should use oozied.sh for stopping oozie so that optional catalina args > can be provided > - > > Key: AMBARI-18219 > URL: https://issues.apache.org/jira/browse/AMBARI-18219 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Venkat Ranganathan >Assignee: Venkat Ranganathan >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-18129.patch > > > In some scenarios, the oozie stop can take longer and if a oozie start is > attempted it can fail with address already in use -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18220) Namenode start failed on moving namenode on a HA cluster
Jaimin D Jetly created AMBARI-18220: --- Summary: Namenode start failed on moving namenode on a HA cluster Key: AMBARI-18220 URL: https://issues.apache.org/jira/browse/AMBARI-18220 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Jaimin D Jetly Assignee: Jaimin D Jetly Priority: Critical Fix For: 2.4.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18219) Ambari should use oozied.sh for stopping oozie so that optional catalina args can be provided
[ https://issues.apache.org/jira/browse/AMBARI-18219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkat Ranganathan updated AMBARI-18219: Priority: Blocker (was: Major) > Ambari should use oozied.sh for stopping oozie so that optional catalina args > can be provided > - > > Key: AMBARI-18219 > URL: https://issues.apache.org/jira/browse/AMBARI-18219 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Venkat Ranganathan >Assignee: Venkat Ranganathan >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-18129.patch > > > In some scenarios, the oozie stop can take longer and if a oozie start is > attempted it can fail with address already in use -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18219) Ambari should use oozied.sh for stopping oozie so that optional catalina args can be provided
[ https://issues.apache.org/jira/browse/AMBARI-18219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkat Ranganathan updated AMBARI-18219: Fix Version/s: 2.4.0 > Ambari should use oozied.sh for stopping oozie so that optional catalina args > can be provided > - > > Key: AMBARI-18219 > URL: https://issues.apache.org/jira/browse/AMBARI-18219 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Venkat Ranganathan >Assignee: Venkat Ranganathan >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-18129.patch > > > In some scenarios, the oozie stop can take longer and if a oozie start is > attempted it can fail with address already in use -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18219) Ambari should use oozied.sh for stopping oozie so that optional catalina args can be provided
[ https://issues.apache.org/jira/browse/AMBARI-18219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkat Ranganathan updated AMBARI-18219: Attachment: AMBARI-18129.patch Fixed use of oozie-stop.sh with 60 seconds delay and forced kill Fixed UT > Ambari should use oozied.sh for stopping oozie so that optional catalina args > can be provided > - > > Key: AMBARI-18219 > URL: https://issues.apache.org/jira/browse/AMBARI-18219 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Venkat Ranganathan >Assignee: Venkat Ranganathan > Attachments: AMBARI-18129.patch > > > In some scenarios, the oozie stop can take longer and if a oozie start is > attempted it can fail with address already in use -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18219) Ambari should use oozied.sh for stopping oozie so that optional catalina args can be provided
[ https://issues.apache.org/jira/browse/AMBARI-18219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429475#comment-15429475 ] Venkat Ranganathan commented on AMBARI-18219: - Skipping RB as it is a simple fix > Ambari should use oozied.sh for stopping oozie so that optional catalina args > can be provided > - > > Key: AMBARI-18219 > URL: https://issues.apache.org/jira/browse/AMBARI-18219 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Venkat Ranganathan >Assignee: Venkat Ranganathan > Attachments: AMBARI-18129.patch > > > In some scenarios, the oozie stop can take longer and if a oozie start is > attempted it can fail with address already in use -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18219) Ambari should use oozied.sh for stopping oozie so that optional catalina args can be provided
Venkat Ranganathan created AMBARI-18219: --- Summary: Ambari should use oozied.sh for stopping oozie so that optional catalina args can be provided Key: AMBARI-18219 URL: https://issues.apache.org/jira/browse/AMBARI-18219 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.4.0 Reporter: Venkat Ranganathan Assignee: Venkat Ranganathan In some scenarios, the oozie stop can take longer and if a oozie start is attempted it can fail with address already in use -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15422) Server Error on Hive View
[ https://issues.apache.org/jira/browse/AMBARI-15422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429343#comment-15429343 ] Zhang Ruiqiang commented on AMBARI-15422: - I hit this error recently too, do you solved it ? > Server Error on Hive View > - > > Key: AMBARI-15422 > URL: https://issues.apache.org/jira/browse/AMBARI-15422 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.1.2 > Environment: hdp 2.3.2 > ambari 2.1.2 >Reporter: Jonas Friedrich > Attachments: error.txt, screenshot1.PNG > > > Hi, i´ve got a Problem with a hive view on ambari 2.1.2. > I´m running a hdp 2.3.2 cluster and want to create a hive view. I´ve done the > steps described here: > http://big-analytics.blogspot.de/2015/11/creating-ambari-hive-views-in-ibm-open.html > I got a Server error when i open the hive view (see screenshot1) > My ambari-server.log looks like here: -- This message was sent by Atlassian JIRA (v6.3.4#6332)
