[jira] [Commented] (AMBARI-20418) Hive View link in service page points to v1.5 auto instance
[ https://issues.apache.org/jira/browse/AMBARI-20418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923695#comment-15923695 ] Hudson commented on AMBARI-20418: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7030 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7030/]) AMBARI-20418 : fixed : Hive View link in service page points to v1.5 (nitiraj.rathore: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=efd3b5847fbfec1ba38cdfa52ffb70e80d385a21]) * (edit) ambari-web/app/views/main/service/services/hive.js > Hive View link in service page points to v1.5 auto instance > --- > > Key: AMBARI-20418 > URL: https://issues.apache.org/jira/browse/AMBARI-20418 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > Attachments: AMBARI-20418.branch-2.5.patch, Screen Shot 2017-03-10 at > 12.06.09 AM.png > > > The hyperlink (see attachment) takes to 1.5 Hive View auto instance > It would be nice to point to the new and improved Hive View 2.0 instance upon > clicking the View link -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20418) Hive View link in service page points to v1.5 auto instance
[ https://issues.apache.org/jira/browse/AMBARI-20418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923692#comment-15923692 ] Hudson commented on AMBARI-20418: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1254 (See [https://builds.apache.org/job/Ambari-branch-2.5/1254/]) AMBARI-20418 : fixed : Hive View link in service page points to v1.5 (nitiraj.rathore: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b6b8e1c7a8129989a7202964118f8012960d1904]) * (edit) ambari-web/app/views/main/service/services/hive.js > Hive View link in service page points to v1.5 auto instance > --- > > Key: AMBARI-20418 > URL: https://issues.apache.org/jira/browse/AMBARI-20418 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > Attachments: AMBARI-20418.branch-2.5.patch, Screen Shot 2017-03-10 at > 12.06.09 AM.png > > > The hyperlink (see attachment) takes to 1.5 Hive View auto instance > It would be nice to point to the new and improved Hive View 2.0 instance upon > clicking the View link -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20437) HDFS Bytes Written and HDFS Bytes Read maybe not correct
[
https://issues.apache.org/jira/browse/AMBARI-20437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923667#comment-15923667
]
Hadoop QA commented on AMBARI-20437:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12858608/AMBARI-20437.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/11016//console
This message is automatically generated.
> HDFS Bytes Written and HDFS Bytes Read maybe not correct
>
>
> Key: AMBARI-20437
> URL: https://issues.apache.org/jira/browse/AMBARI-20437
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0, 2.5.0, 2.4.2
>Reporter: zhangxiaolu
>Assignee: zhangxiaolu
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-20437.patch
>
>
> As the description of "HDFS Bytes Written" : dfs.datanode.BytesRead and
> properties's display_unit is MB
> So in heatmap's page,values should be ${dfs.datanode.BytesRead._rate/1024} MB
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (AMBARI-20418) Hive View link in service page points to v1.5 auto instance
[ https://issues.apache.org/jira/browse/AMBARI-20418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore resolved AMBARI-20418. Resolution: Fixed committed to branch-2.5 and trunk > Hive View link in service page points to v1.5 auto instance > --- > > Key: AMBARI-20418 > URL: https://issues.apache.org/jira/browse/AMBARI-20418 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > Attachments: AMBARI-20418.branch-2.5.patch, Screen Shot 2017-03-10 at > 12.06.09 AM.png > > > The hyperlink (see attachment) takes to 1.5 Hive View auto instance > It would be nice to point to the new and improved Hive View 2.0 instance upon > clicking the View link -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20370) Fix up tez view version
[ https://issues.apache.org/jira/browse/AMBARI-20370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923473#comment-15923473 ] Hudson commented on AMBARI-20370: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1253 (See [https://builds.apache.org/job/Ambari-branch-2.5/1253/]) AMBARI-20370 : tez view version and build removed and short url of auto (nitiraj.rathore: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=706f990d07a16a9701e21d6a688be96c22161d94]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/services/stack_advisor.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.2/services/stack_advisor.py * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/AbstractUpgradeCatalog.java * (edit) ambari-server/src/test/python/stacks/2.3/common/test_stack_advisor.py * (edit) ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/AbstractUpgradeCatalogTest.java > Fix up tez view version > --- > > Key: AMBARI-20370 > URL: https://issues.apache.org/jira/browse/AMBARI-20370 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.0 > > Attachments: AMBARI-20370_branch-2.5_2.patch, AMBARI-20370_trunk.patch > > > Currently tez view version uses version and build in url. Because of this > everytime tez view is changed the value of tez.tez-ui.history-url.base needs > to be changed in tez-site. > This url should no be fixed to auto tez view instance's short url. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20070) Agent heartbeat lost due to subprocess.Popen race condition
[
https://issues.apache.org/jira/browse/AMBARI-20070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-20070:
---
Fix Version/s: (was: 3.0.0)
> Agent heartbeat lost due to subprocess.Popen race condition
> ---
>
> Key: AMBARI-20070
> URL: https://issues.apache.org/jira/browse/AMBARI-20070
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.5.0
> Environment: Python 2.7
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20070_multiprocessing.patch, AMBARI-20070.patch
>
>
> Workaround for http://bugs.python.org/issue19809 that probably causes
> {{subprocess.Popen}} call to get stuck in:
> {noformat}
> File: "/usr/lib/python2.7/subprocess.py", line 679, in __init__
> errread, errwrite)
> File: "/usr/lib/python2.7/subprocess.py", line 1244, in _execute_child
> data = _eintr_retry_call(os.read, errpipe_read, 1048576)
> File: "/usr/lib/python2.7/subprocess.py", line 478, in _eintr_retry_call
> return func(*args)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20437) HDFS Bytes Written and HDFS Bytes Read maybe not correct
[
https://issues.apache.org/jira/browse/AMBARI-20437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangxiaolu updated AMBARI-20437:
-
Attachment: AMBARI-20437.patch
> HDFS Bytes Written and HDFS Bytes Read maybe not correct
>
>
> Key: AMBARI-20437
> URL: https://issues.apache.org/jira/browse/AMBARI-20437
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0, 2.5.0, 2.4.2
>Reporter: zhangxiaolu
>Assignee: zhangxiaolu
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-20437.patch
>
>
> As the description of "HDFS Bytes Written" : dfs.datanode.BytesRead and
> properties's display_unit is MB
> So in heatmap's page,values should be ${dfs.datanode.BytesRead._rate/1024} MB
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20437) HDFS Bytes Written and HDFS Bytes Read maybe not correct
[
https://issues.apache.org/jira/browse/AMBARI-20437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangxiaolu updated AMBARI-20437:
-
Attachment: (was: AMBARI-20437.patch)
> HDFS Bytes Written and HDFS Bytes Read maybe not correct
>
>
> Key: AMBARI-20437
> URL: https://issues.apache.org/jira/browse/AMBARI-20437
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0, 2.5.0, 2.4.2
>Reporter: zhangxiaolu
>Assignee: zhangxiaolu
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-20437.patch
>
>
> As the description of "HDFS Bytes Written" : dfs.datanode.BytesRead and
> properties's display_unit is MB
> So in heatmap's page,values should be ${dfs.datanode.BytesRead._rate/1024} MB
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20370) Fix up tez view version
[ https://issues.apache.org/jira/browse/AMBARI-20370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923449#comment-15923449 ] Hudson commented on AMBARI-20370: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7029 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7029/]) AMBARI-20370 : tez view version and build removed and short url of auto (nitiraj.rathore: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=9c7b290dd89aa6ea95ce47496f56f21a9fb40231]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/services/stack_advisor.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.2/services/stack_advisor.py * (edit) ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/AbstractUpgradeCatalog.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/AbstractUpgradeCatalogTest.java * (edit) ambari-server/src/test/python/stacks/2.3/common/test_stack_advisor.py > Fix up tez view version > --- > > Key: AMBARI-20370 > URL: https://issues.apache.org/jira/browse/AMBARI-20370 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.0 > > Attachments: AMBARI-20370_branch-2.5_2.patch, AMBARI-20370_trunk.patch > > > Currently tez view version uses version and build in url. Because of this > everytime tez view is changed the value of tez.tez-ui.history-url.base needs > to be changed in tez-site. > This url should no be fixed to auto tez view instance's short url. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20437) HDFS Bytes Written and HDFS Bytes Read maybe not correct
[
https://issues.apache.org/jira/browse/AMBARI-20437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangxiaolu updated AMBARI-20437:
-
Assignee: zhangxiaolu
Status: Patch Available (was: Open)
> HDFS Bytes Written and HDFS Bytes Read maybe not correct
>
>
> Key: AMBARI-20437
> URL: https://issues.apache.org/jira/browse/AMBARI-20437
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0, 2.5.0, 2.4.2
>Reporter: zhangxiaolu
>Assignee: zhangxiaolu
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-20437.patch
>
>
> As the description of "HDFS Bytes Written" : dfs.datanode.BytesRead and
> properties's display_unit is MB
> So in heatmap's page,values should be ${dfs.datanode.BytesRead._rate/1024} MB
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20436) Create a prototype of ambari-server swagger integration
[
https://issues.apache.org/jira/browse/AMBARI-20436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923445#comment-15923445
]
Hadoop QA commented on AMBARI-20436:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12858607/AMBARI-20436.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/11015//console
This message is automatically generated.
> Create a prototype of ambari-server swagger integration
> ---
>
> Key: AMBARI-20436
> URL: https://issues.apache.org/jira/browse/AMBARI-20436
> Project: Ambari
> Issue Type: Task
> Components: ambari-server, ambari-web
>Affects Versions: 3.0.0
>Reporter: Jaimin Jetly
>Assignee: Jaimin Jetly
> Fix For: 3.0.0
>
> Attachments: AMBARI-20436.patch
>
>
> As part of this task, following changes are done:
> # A separate branch is created for this work: ambari-rest-api-explorer
> # Users, Groups and Views API are integrated with swagger and exposed from
> ambari rest api explorer ui (swagger ui) on a deployed cluster at path:
> http://c6404.ambari.apache.org:8080/api-docs
> # swagger-maven-plugin is used to generate swagger.json file on compile time.
> This file is published in web resources directory. Note that this file is
> generated build time and will be available on deployed ambari-server host at
> web resources location but it is not yet decided to be committed and
> maintained in Ambari source code
> # swagger2markup-maven-plugin is used to generate asciidoc from swagger.json
> file (that can be shown as markdown in github). More information about this
> format an be found at http://asciidoc.org/ and http://asciidoctor.org/. This
> generates files in docs/api/asciidoc/** location at build time. This
> directory is currently intended to be committed and maintained in ambari
> source code
> # swagger-ui (version: v2.1.1-M2) compiled code with the different css skin
> (adopted from [link|https://github.com/jensoleg/swagger-ui]) is committed to
> ambari-web/api-docs directory with certain modification to make it work with
> ambari api. Further ui polishing will be done in subsequent tasks. Also there
> is a strong possibility to maintain the fork code of swagger-ui and compile
> (minify and concanate) it during ambari compile time rather than directly
> using swagger-ui dist files. Doing so will help when customization done over
> swagger-ui will increase
> # swagger-annotation expects application to define schema of request body and
> response for each endpoint to be encapsulated in a class. While Ambari
> follows this pattern for some of the endpoint, there are many others which
> does not do so. For The ones which do not does so, new request and response
> classes were defined. Going forward at the completion of this epic, either
> each resource type or each resource provider should be coupled with a
> resource response class and a resource request class. As part of this patch,
> each resourceprovider worked upon introduces a new method "getResponse". At
> completion of this epic ResourceProvider interface should also declare
> methods like "getResponse" and "getRequest" that returns response schema and
> request schema instances for the resource API endpoints
> # Currently it seems that swagger has a limitation in supporting
> "subresource locator methods". This issue is been reported to swagger
> community and is being tracked at
> [link|https://github.com/swagger-api/swagger-core/issues/2136] . As a result
> of which currently as a temporary workaround, all subresources are converted
> to root resources. Also all root resources on similar path are moved under
> same subpackages.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20436) Create a prototype of ambari-server swagger integration
[ https://issues.apache.org/jira/browse/AMBARI-20436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-20436: -- Status: Patch Available (was: Open) > Create a prototype of ambari-server swagger integration > --- > > Key: AMBARI-20436 > URL: https://issues.apache.org/jira/browse/AMBARI-20436 > Project: Ambari > Issue Type: Task > Components: ambari-server, ambari-web >Affects Versions: 3.0.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly > Fix For: 3.0.0 > > Attachments: AMBARI-20436.patch > > > As part of this task, following changes are done: > # A separate branch is created for this work: ambari-rest-api-explorer > # Users, Groups and Views API are integrated with swagger and exposed from > ambari rest api explorer ui (swagger ui) on a deployed cluster at path: > http://c6404.ambari.apache.org:8080/api-docs > # swagger-maven-plugin is used to generate swagger.json file on compile time. > This file is published in web resources directory. Note that this file is > generated build time and will be available on deployed ambari-server host at > web resources location but it is not yet decided to be committed and > maintained in Ambari source code > # swagger2markup-maven-plugin is used to generate asciidoc from swagger.json > file (that can be shown as markdown in github). More information about this > format an be found at http://asciidoc.org/ and http://asciidoctor.org/. This > generates files in docs/api/asciidoc/** location at build time. This > directory is currently intended to be committed and maintained in ambari > source code > # swagger-ui (version: v2.1.1-M2) compiled code with the different css skin > (adopted from [link|https://github.com/jensoleg/swagger-ui]) is committed to > ambari-web/api-docs directory with certain modification to make it work with > ambari api. Further ui polishing will be done in subsequent tasks. Also there > is a strong possibility to maintain the fork code of swagger-ui and compile > (minify and concanate) it during ambari compile time rather than directly > using swagger-ui dist files. Doing so will help when customization done over > swagger-ui will increase > # swagger-annotation expects application to define schema of request body and > response for each endpoint to be encapsulated in a class. While Ambari > follows this pattern for some of the endpoint, there are many others which > does not do so. For The ones which do not does so, new request and response > classes were defined. Going forward at the completion of this epic, either > each resource type or each resource provider should be coupled with a > resource response class and a resource request class. As part of this patch, > each resourceprovider worked upon introduces a new method "getResponse". At > completion of this epic ResourceProvider interface should also declare > methods like "getResponse" and "getRequest" that returns response schema and > request schema instances for the resource API endpoints > # Currently it seems that swagger has a limitation in supporting > "subresource locator methods". This issue is been reported to swagger > community and is being tracked at > [link|https://github.com/swagger-api/swagger-core/issues/2136] . As a result > of which currently as a temporary workaround, all subresources are converted > to root resources. Also all root resources on similar path are moved under > same subpackages. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20436) Create a prototype of ambari-server swagger integration
[ https://issues.apache.org/jira/browse/AMBARI-20436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-20436: -- Attachment: AMBARI-20436.patch > Create a prototype of ambari-server swagger integration > --- > > Key: AMBARI-20436 > URL: https://issues.apache.org/jira/browse/AMBARI-20436 > Project: Ambari > Issue Type: Task > Components: ambari-server, ambari-web >Affects Versions: 3.0.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly > Fix For: 3.0.0 > > Attachments: AMBARI-20436.patch > > > As part of this task, following changes are done: > # A separate branch is created for this work: ambari-rest-api-explorer > # Users, Groups and Views API are integrated with swagger and exposed from > ambari rest api explorer ui (swagger ui) on a deployed cluster at path: > http://c6404.ambari.apache.org:8080/api-docs > # swagger-maven-plugin is used to generate swagger.json file on compile time. > This file is published in web resources directory. Note that this file is > generated build time and will be available on deployed ambari-server host at > web resources location but it is not yet decided to be committed and > maintained in Ambari source code > # swagger2markup-maven-plugin is used to generate asciidoc from swagger.json > file (that can be shown as markdown in github). More information about this > format an be found at http://asciidoc.org/ and http://asciidoctor.org/. This > generates files in docs/api/asciidoc/** location at build time. This > directory is currently intended to be committed and maintained in ambari > source code > # swagger-ui (version: v2.1.1-M2) compiled code with the different css skin > (adopted from [link|https://github.com/jensoleg/swagger-ui]) is committed to > ambari-web/api-docs directory with certain modification to make it work with > ambari api. Further ui polishing will be done in subsequent tasks. Also there > is a strong possibility to maintain the fork code of swagger-ui and compile > (minify and concanate) it during ambari compile time rather than directly > using swagger-ui dist files. Doing so will help when customization done over > swagger-ui will increase > # swagger-annotation expects application to define schema of request body and > response for each endpoint to be encapsulated in a class. While Ambari > follows this pattern for some of the endpoint, there are many others which > does not do so. For The ones which do not does so, new request and response > classes were defined. Going forward at the completion of this epic, either > each resource type or each resource provider should be coupled with a > resource response class and a resource request class. As part of this patch, > each resourceprovider worked upon introduces a new method "getResponse". At > completion of this epic ResourceProvider interface should also declare > methods like "getResponse" and "getRequest" that returns response schema and > request schema instances for the resource API endpoints > # Currently it seems that swagger has a limitation in supporting > "subresource locator methods". This issue is been reported to swagger > community and is being tracked at > [link|https://github.com/swagger-api/swagger-core/issues/2136] . As a result > of which currently as a temporary workaround, all subresources are converted > to root resources. Also all root resources on similar path are moved under > same subpackages. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20436) Create a prototype of ambari-server swagger integration
[ https://issues.apache.org/jira/browse/AMBARI-20436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-20436: -- Description: As part of this task, following changes are done: # A separate branch is created for this work: ambari-rest-api-explorer # Users, Groups and Views API are integrated with swagger and exposed from ambari rest api explorer ui (swagger ui) on a deployed cluster at path: http://c6404.ambari.apache.org:8080/api-docs # swagger-maven-plugin is used to generate swagger.json file on compile time. This file is published in web resources directory. Note that this file is generated build time and will be available on deployed ambari-server host at web resources location but it is not yet decided to be committed and maintained in Ambari source code # swagger2markup-maven-plugin is used to generate asciidoc from swagger.json file (that can be shown as markdown in github). More information about this format an be found at http://asciidoc.org/ and http://asciidoctor.org/. This generates files in docs/api/asciidoc/** location at build time. This directory is currently intended to be committed and maintained in ambari source code # swagger-ui (version: v2.1.1-M2) compiled code with the different css skin (adopted from [link|https://github.com/jensoleg/swagger-ui]) is committed to ambari-web/api-docs directory with certain modification to make it work with ambari api. Further ui polishing will be done in subsequent tasks. Also there is a strong possibility to maintain the fork code of swagger-ui and compile (minify and concanate) it during ambari compile time rather than directly using swagger-ui dist files. Doing so will help when customization done over swagger-ui will increase # swagger-annotation expects application to define schema of request body and response for each endpoint to be encapsulated in a class. While Ambari follows this pattern for some of the endpoint, there are many others which does not do so. For The ones which do not does so, new request and response classes were defined. Going forward at the completion of this epic, either each resource type or each resource provider should be coupled with a resource response class and a resource request class. As part of this patch, each resourceprovider worked upon introduces a new method "getResponse". At completion of this epic ResourceProvider interface should also declare methods like "getResponse" and "getRequest" that returns response schema and request schema instances for the resource API endpoints # Currently it seems that swagger has a limitation in supporting "subresource locator methods". This issue is been reported to swagger community and is being tracked at [link|https://github.com/swagger-api/swagger-core/issues/2136] . As a result of which currently as a temporary workaround, all subresources are converted to root resources. Also all root resources on similar path are moved under same subpackages. was: As part of this task, following changes are done: # Users, Groups and Views API are integrated with swagger and exposed from ambari rest api explorer ui (swagger ui) on a deployed cluster at path: http://c6404.ambari.apache.org:8080/api-docs # swagger-maven-plugin is used to generate swagger.json file on compile time. This file is published in web resources directory. Note that this file is generated build time and will be available on deployed ambari-server host at web resources location but it is not yet decided to be committed and maintained in Ambari source code # swagger2markup-maven-plugin is used to generate asciidoc from swagger.json file (that can be shown as markdown in github). More information about this format an be found at http://asciidoc.org/ and http://asciidoctor.org/. This generates files in docs/api/asciidoc/** location at build time. This directory is currently intended to be committed and maintained in ambari source code # swagger-ui (version: v2.1.1-M2) compiled code with the different css skin (adopted from [link|https://github.com/jensoleg/swagger-ui]) is committed to ambari-web/api-docs directory with certain modification to make it work with ambari api. Further ui polishing will be done in subsequent tasks. Also there is a strong possibility to maintain the fork code of swagger-ui and compile (minify and concanate) it during ambari compile time rather than directly using swagger-ui dist files. Doing so will help when customization done over swagger-ui will increase # swagger-annotation expects application to define schema of request body and response for each endpoint to be encapsulated in a class. While Ambari follows this pattern for some of the endpoint, there are many others which does not do so. For The ones which do not does so, new request and response classes were defined. Going forward at the completion of this epic, either each resource type
[jira] [Updated] (AMBARI-20436) Create a prototype of ambari-server swagger integration
[ https://issues.apache.org/jira/browse/AMBARI-20436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-20436: -- Description: As part of this task, following changes are done: # Users, Groups and Views API are integrated with swagger and exposed from ambari rest api explorer ui (swagger ui) on a deployed cluster at path: http://c6404.ambari.apache.org:8080/api-docs # swagger-maven-plugin is used to generate swagger.json file on compile time. This file is published in web resources directory. Note that this file is generated build time and will be available on deployed ambari-server host at web resources location but it is not yet decided to be committed and maintained in Ambari source code # swagger2markup-maven-plugin is used to generate asciidoc from swagger.json file (that can be shown as markdown in github). More information about this format an be found at http://asciidoc.org/ and http://asciidoctor.org/. This generates files in docs/api/asciidoc/** location at build time. This directory is currently intended to be committed and maintained in ambari source code # swagger-ui (version: v2.1.1-M2) compiled code with the different css skin (adopted from [link|https://github.com/jensoleg/swagger-ui]) is committed to ambari-web/api-docs directory with certain modification to make it work with ambari api. Further ui polishing will be done in subsequent tasks. Also there is a strong possibility to maintain the fork code of swagger-ui and compile (minify and concanate) it during ambari compile time rather than directly using swagger-ui dist files. Doing so will help when customization done over swagger-ui will increase # swagger-annotation expects application to define schema of request body and response for each endpoint to be encapsulated in a class. While Ambari follows this pattern for some of the endpoint, there are many others which does not do so. For The ones which do not does so, new request and response classes were defined. Going forward at the completion of this epic, either each resource type or each resource provider should be coupled with a resource response class and a resource request class. As part of this patch, each resourceprovider worked upon introduces a new method "getResponse". At completion of this epic ResourceProvider interface should also declare methods like "getResponse" and "getRequest" that returns response schema and request schema instances for the resource API endpoints # Currently it seems that swagger has a limitation in supporting "subresource locator methods". This issue is been reported to swagger community and is being tracked at [link|https://github.com/swagger-api/swagger-core/issues/2136] . As a result of which currently as a temporary workaround, all subresources are converted to root resources. Also all root resources on similar path are moved under same subpackages. was: As part of this task, following changes are done: # swagger-maven-plugin is used to generate swagger.json file on compile time. This file is published in web resources directory. Note that this file is generated build time and will be available on deployed ambari-server host at web resources location but it is not yet decided to be committed and maintained in Ambari source code # swagger2markup-maven-plugin is used to generate asciidoc from swagger.json file (that can be shown as markdown in github). More information about this format an be found at http://asciidoc.org/ and http://asciidoctor.org/. This generates files in docs/api/asciidoc/** location at build time. This directory is currently intended to be committed and maintained in ambari source code # swagger-ui (version: v2.1.1-M2) compiled code with the different css skin (adopted from [link|https://github.com/jensoleg/swagger-ui]) is committed to ambari-web/api-docs directory with certain modification to make it work with ambari api. Further ui polishing will be done in subsequent tasks. Also there is a strong possibility to maintain the fork code of swagger-ui and compile (minify and concanate) it during ambari compile time rather than directly using swagger-ui dist files. Doing so will help when customization done over swagger-ui will increase # swagger-annotation expects application to define schema of request body and response for each endpoint to be encapsulated in a class. While Ambari follows this pattern for some of the endpoint, there are many others which does not do so. For The ones which do not does so, new request and response classes were defined. Going forward at the completion of this epic, either each resource type or each resource provider should be coupled with a resource response class and a resource request class. As part of this patch, each resourceprovider worked upon introduces a new method "getResponse". At completion of this epic ResourceProvider interface should
[jira] [Updated] (AMBARI-20437) HDFS Bytes Written and HDFS Bytes Read maybe not correct
[
https://issues.apache.org/jira/browse/AMBARI-20437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangxiaolu updated AMBARI-20437:
-
Attachment: AMBARI-20437.patch
> HDFS Bytes Written and HDFS Bytes Read maybe not correct
>
>
> Key: AMBARI-20437
> URL: https://issues.apache.org/jira/browse/AMBARI-20437
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0, 2.5.0, 2.4.2
>Reporter: zhangxiaolu
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-20437.patch
>
>
> As the description of "HDFS Bytes Written" : dfs.datanode.BytesRead and
> properties's display_unit is MB
> So in heatmap's page,values should be ${dfs.datanode.BytesRead._rate/1024} MB
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20436) Create a prototype of ambari-server swagger integration
[ https://issues.apache.org/jira/browse/AMBARI-20436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-20436: -- Description: As part of this task, following changes are done: # swagger-maven-plugin is used to generate swagger.json file on compile time. This file is published in web resources directory. Note that this file is generated build time and will be available on deployed ambari-server host at web resources location but it is not yet decided to be committed and maintained in Ambari source code # swagger2markup-maven-plugin is used to generate asciidoc from swagger.json file (that can be shown as markdown in github). More information about this format an be found at http://asciidoc.org/ and http://asciidoctor.org/. This generates files in docs/api/asciidoc/** location at build time. This directory is currently intended to be committed and maintained in ambari source code # swagger-ui (version: v2.1.1-M2) compiled code with the different css skin (adopted from [link|https://github.com/jensoleg/swagger-ui]) is committed to ambari-web/api-docs directory with certain modification to make it work with ambari api. Further ui polishing will be done in subsequent tasks. Also there is a strong possibility to maintain the fork code of swagger-ui and compile (minify and concanate) it during ambari compile time rather than directly using swagger-ui dist files. Doing so will help when customization done over swagger-ui will increase # swagger-annotation expects application to define schema of request body and response for each endpoint to be encapsulated in a class. While Ambari follows this pattern for some of the endpoint, there are many others which does not do so. For The ones which do not does so, new request and response classes were defined. Going forward at the completion of this epic, either each resource type or each resource provider should be coupled with a resource response class and a resource request class. As part of this patch, each resourceprovider worked upon introduces a new method "getResponse". At completion of this epic ResourceProvider interface should also declare methods like "getResponse" and "getRequest" that returns response schema and request schema instances for the resource API endpoints # Currently it seems that swagger has a limitation in supporting "subresource locator methods". This issue is been reported to swagger community and is being tracked at [link|https://github.com/swagger-api/swagger-core/issues/2136] . As a result of which currently as a temporary workaround, all subresources are converted to root resources. Also all root resources on similar path are moved under same subpackages. > Create a prototype of ambari-server swagger integration > --- > > Key: AMBARI-20436 > URL: https://issues.apache.org/jira/browse/AMBARI-20436 > Project: Ambari > Issue Type: Task > Components: ambari-server, ambari-web >Affects Versions: 3.0.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly > Fix For: 3.0.0 > > > As part of this task, following changes are done: > # swagger-maven-plugin is used to generate swagger.json file on compile time. > This file is published in web resources directory. Note that this file is > generated build time and will be available on deployed ambari-server host at > web resources location but it is not yet decided to be committed and > maintained in Ambari source code > # swagger2markup-maven-plugin is used to generate asciidoc from swagger.json > file (that can be shown as markdown in github). More information about this > format an be found at http://asciidoc.org/ and http://asciidoctor.org/. This > generates files in docs/api/asciidoc/** location at build time. This > directory is currently intended to be committed and maintained in ambari > source code > # swagger-ui (version: v2.1.1-M2) compiled code with the different css skin > (adopted from [link|https://github.com/jensoleg/swagger-ui]) is committed to > ambari-web/api-docs directory with certain modification to make it work with > ambari api. Further ui polishing will be done in subsequent tasks. Also there > is a strong possibility to maintain the fork code of swagger-ui and compile > (minify and concanate) it during ambari compile time rather than directly > using swagger-ui dist files. Doing so will help when customization done over > swagger-ui will increase > # swagger-annotation expects application to define schema of request body and > response for each endpoint to be encapsulated in a class. While Ambari > follows this pattern for some of the endpoint, there are many others which > does not do so. For The ones which do not does so, new request and response > classes were defined. Going forward at th
[jira] [Updated] (AMBARI-20437) HDFS Bytes Written and HDFS Bytes Read maybe not correct
[
https://issues.apache.org/jira/browse/AMBARI-20437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangxiaolu updated AMBARI-20437:
-
Description:
As the description of "HDFS Bytes Written" : dfs.datanode.BytesRead and
properties's display_unit is MB
So in heatmap's page,values should be ${dfs.datanode.BytesRead._rate/1024} MB
was:
As the description of "HDFS Bytes Written" : dfs.datanode.BytesRead.
So in heatmap's page,values should be ${dfs.datanode.BytesRead._rate/1024} MB
> HDFS Bytes Written and HDFS Bytes Read maybe not correct
>
>
> Key: AMBARI-20437
> URL: https://issues.apache.org/jira/browse/AMBARI-20437
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0, 2.5.0, 2.4.2
>Reporter: zhangxiaolu
> Fix For: trunk, 2.5.0
>
>
> As the description of "HDFS Bytes Written" : dfs.datanode.BytesRead and
> properties's display_unit is MB
> So in heatmap's page,values should be ${dfs.datanode.BytesRead._rate/1024} MB
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20437) HDFS Bytes Written and HDFS Bytes Read maybe not correct
zhangxiaolu created AMBARI-20437:
Summary: HDFS Bytes Written and HDFS Bytes Read maybe not correct
Key: AMBARI-20437
URL: https://issues.apache.org/jira/browse/AMBARI-20437
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.4.0, 2.5.0, 2.4.2
Reporter: zhangxiaolu
Fix For: trunk, 2.5.0
As the description of "HDFS Bytes Written" : dfs.datanode.BytesRead.
So in heatmap's page,values should be ${dfs.datanode.BytesRead._rate/1024} MB
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20432) ambari-web shows redundant configuration for "Number of nodes used by Hive's LLAP"
[ https://issues.apache.org/jira/browse/AMBARI-20432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923411#comment-15923411 ] Hudson commented on AMBARI-20432: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1252 (See [https://builds.apache.org/job/Ambari-branch-2.5/1252/]) AMBARI-20432. ambari-web shows redundant configuration for "Number of (jaimin: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=3a1afd8c8ee462316888b3171c58fb0a902de98b]) * (edit) ambari-web/app/mixins/common/configs/widgets/unique/num_llap_nodes.js > ambari-web shows redundant configuration for "Number of nodes used by Hive's > LLAP" > -- > > Key: AMBARI-20432 > URL: https://issues.apache.org/jira/browse/AMBARI-20432 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Kishor Ramakrishnan >Assignee: Jaimin Jetly >Priority: Blocker > Fix For: 2.5.0 > > Attachments: AMBARI-20432.patch > > > [Upgrades] Start HSI server failed with > "org.apache.commons.cli.ParseException: Invalid configuration: 0" error > Error Logs: > SLF4J: Class path contains multiple SLF4J bindings. > SLF4J: Found binding in > [jar:file:/grid/0/hdp/2.6.0.2-4/hive2/lib/log4j-slf4j-impl-2.6.2.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: Found binding in > [jar:file:/grid/0/hdp/2.6.0.2-4/hadoop/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an > explanation. > SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory] > INFO cli.LlapServiceDriver: LLAP service driver invoked with > arguments=--hiveconf > INFO conf.HiveConf: Found configuration file > file:/etc/hive2/2.6.0.2-4/0/conf.server/hive-site.xml > WARN conf.HiveConf: HiveConf of name hive.llap.daemon.allow.permanent.fns > does not exist > WARN conf.HiveConf: HiveConf hive.llap.daemon.vcpus.per.instance expects INT > type value > WARN conf.HiveConf: HiveConf of name hive.server2.enable.impersonation does > not exist > Failed: Invalid configuration: 0 (should be greater than 0) > org.apache.commons.cli.ParseException: Invalid configuration: 0 (should be > greater than 0) > at > org.apache.hadoop.hive.llap.cli.LlapOptionsProcessor$LlapOptions.(LlapOptionsProcessor.java:94) > at > org.apache.hadoop.hive.llap.cli.LlapOptionsProcessor.processOptions(LlapOptionsProcessor.java:325) > at > org.apache.hadoop.hive.llap.cli.LlapServiceDriver.run(LlapServiceDriver.java:177) > at > org.apache.hadoop.hive.llap.cli.LlapServiceDriver.main(LlapServiceDriver.java:113) > INFO cli.LlapServiceDriver: LLAP service driver finished > Command failed after 1 tries -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20392) Get aggregate metric records from HBase encounters performance issues
[
https://issues.apache.org/jira/browse/AMBARI-20392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923405#comment-15923405
]
Hadoop QA commented on AMBARI-20392:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12858595/AMBARI-20392.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-metrics/ambari-metrics-timelineservice.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/11013//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11013//console
This message is automatically generated.
> Get aggregate metric records from HBase encounters performance issues
> -
>
> Key: AMBARI-20392
> URL: https://issues.apache.org/jira/browse/AMBARI-20392
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-metrics
>Affects Versions: 2.4.2
>Reporter: Chuan Jin
> Attachments: AMBARI-20392.patch
>
>
> I have a mini cluster ( ~6 nodes) managed by Ambari, and use a distributed
> HBase (~3 nodes) to hold metrics collected from these nodes. After I deploy
> YARN serivce, then I notice that some widgets (Cluster Memory,Cluster
> Disk,...) cannot display properly in the YARN service dashboard page. And
> Ambari Server has continuous timeout exceptions, which complains that it
> doesn't get timeline metrics for connection refused.
> The request timeout parameter is 5s, which means the query of getting metrics
> from HBase takes more time than that. Then I use Phoenix shell to login and
> perform the same query in the HBase , and it takes nearly 30s to finish. But
> If I split the big query into small pieces , i mean, use less values in the
> "metric_name" field in the where ... in clause , then the result return in 1s
> after several small queries.
> The query performance in HBase is highly based on the design of rowkey and
> the proper usage for it. In the method of getting aggregate metrics, AMS
> collector query the METRIC_AGGREGATE table in a way that may cause the
> co-processor to scan several regions across different RS. If we add more
> metrics in the service dashboard, this situation will be worse.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20432) ambari-web shows redundant configuration for "Number of nodes used by Hive's LLAP"
[ https://issues.apache.org/jira/browse/AMBARI-20432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923403#comment-15923403 ] Hudson commented on AMBARI-20432: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7028 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7028/]) AMBARI-20432. ambari-web shows redundant configuration for "Number of (jaimin: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=785d7dac9f4cf685eeba0ee4447da9f50ebbc0d1]) * (edit) ambari-web/app/mixins/common/configs/widgets/unique/num_llap_nodes.js > ambari-web shows redundant configuration for "Number of nodes used by Hive's > LLAP" > -- > > Key: AMBARI-20432 > URL: https://issues.apache.org/jira/browse/AMBARI-20432 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Kishor Ramakrishnan >Assignee: Jaimin Jetly >Priority: Blocker > Fix For: 2.5.0 > > Attachments: AMBARI-20432.patch > > > [Upgrades] Start HSI server failed with > "org.apache.commons.cli.ParseException: Invalid configuration: 0" error > Error Logs: > SLF4J: Class path contains multiple SLF4J bindings. > SLF4J: Found binding in > [jar:file:/grid/0/hdp/2.6.0.2-4/hive2/lib/log4j-slf4j-impl-2.6.2.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: Found binding in > [jar:file:/grid/0/hdp/2.6.0.2-4/hadoop/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an > explanation. > SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory] > INFO cli.LlapServiceDriver: LLAP service driver invoked with > arguments=--hiveconf > INFO conf.HiveConf: Found configuration file > file:/etc/hive2/2.6.0.2-4/0/conf.server/hive-site.xml > WARN conf.HiveConf: HiveConf of name hive.llap.daemon.allow.permanent.fns > does not exist > WARN conf.HiveConf: HiveConf hive.llap.daemon.vcpus.per.instance expects INT > type value > WARN conf.HiveConf: HiveConf of name hive.server2.enable.impersonation does > not exist > Failed: Invalid configuration: 0 (should be greater than 0) > org.apache.commons.cli.ParseException: Invalid configuration: 0 (should be > greater than 0) > at > org.apache.hadoop.hive.llap.cli.LlapOptionsProcessor$LlapOptions.(LlapOptionsProcessor.java:94) > at > org.apache.hadoop.hive.llap.cli.LlapOptionsProcessor.processOptions(LlapOptionsProcessor.java:325) > at > org.apache.hadoop.hive.llap.cli.LlapServiceDriver.run(LlapServiceDriver.java:177) > at > org.apache.hadoop.hive.llap.cli.LlapServiceDriver.main(LlapServiceDriver.java:113) > INFO cli.LlapServiceDriver: LLAP service driver finished > Command failed after 1 tries -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20370) Fix up tez view version
[ https://issues.apache.org/jira/browse/AMBARI-20370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-20370: --- Resolution: Fixed Status: Resolved (was: Patch Available) committed to branch-2.5 and trunk > Fix up tez view version > --- > > Key: AMBARI-20370 > URL: https://issues.apache.org/jira/browse/AMBARI-20370 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.0 > > Attachments: AMBARI-20370_branch-2.5_2.patch, AMBARI-20370_trunk.patch > > > Currently tez view version uses version and build in url. Because of this > everytime tez view is changed the value of tez.tez-ui.history-url.base needs > to be changed in tez-site. > This url should no be fixed to auto tez view instance's short url. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20370) Fix up tez view version
[ https://issues.apache.org/jira/browse/AMBARI-20370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-20370: --- Attachment: (was: AMBARI-20370_branch-2.5.patch) > Fix up tez view version > --- > > Key: AMBARI-20370 > URL: https://issues.apache.org/jira/browse/AMBARI-20370 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.0 > > Attachments: AMBARI-20370_branch-2.5_2.patch, AMBARI-20370_trunk.patch > > > Currently tez view version uses version and build in url. Because of this > everytime tez view is changed the value of tez.tez-ui.history-url.base needs > to be changed in tez-site. > This url should no be fixed to auto tez view instance's short url. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20370) Fix up tez view version
[ https://issues.apache.org/jira/browse/AMBARI-20370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-20370: --- Attachment: AMBARI-20370_trunk.patch AMBARI-20370_branch-2.5_2.patch removed conflicts and uploaded updated patch > Fix up tez view version > --- > > Key: AMBARI-20370 > URL: https://issues.apache.org/jira/browse/AMBARI-20370 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.0 > > Attachments: AMBARI-20370_branch-2.5_2.patch, > AMBARI-20370_branch-2.5.patch, AMBARI-20370_trunk.patch > > > Currently tez view version uses version and build in url. Because of this > everytime tez view is changed the value of tez.tez-ui.history-url.base needs > to be changed in tez-site. > This url should no be fixed to auto tez view instance's short url. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20436) Create a prototype of ambari-server swagger integration
Jaimin Jetly created AMBARI-20436: - Summary: Create a prototype of ambari-server swagger integration Key: AMBARI-20436 URL: https://issues.apache.org/jira/browse/AMBARI-20436 Project: Ambari Issue Type: Task Components: ambari-server, ambari-web Affects Versions: 3.0.0 Reporter: Jaimin Jetly Assignee: Jaimin Jetly Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20435) Integrate Ambari REST APIs with Swagger
Jaimin Jetly created AMBARI-20435: - Summary: Integrate Ambari REST APIs with Swagger Key: AMBARI-20435 URL: https://issues.apache.org/jira/browse/AMBARI-20435 Project: Ambari Issue Type: Epic Components: ambari-sever, ambari-web Affects Versions: 3.0.0 Reporter: Jaimin Jetly Assignee: Jaimin Jetly Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20392) Get aggregate metric records from HBase encounters performance issues
[ https://issues.apache.org/jira/browse/AMBARI-20392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chuan Jin updated AMBARI-20392: --- Attachment: (was: AMBARI-20392.patch) > Get aggregate metric records from HBase encounters performance issues > - > > Key: AMBARI-20392 > URL: https://issues.apache.org/jira/browse/AMBARI-20392 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics >Affects Versions: 2.4.2 >Reporter: Chuan Jin > Attachments: AMBARI-20392.patch > > > I have a mini cluster ( ~6 nodes) managed by Ambari, and use a distributed > HBase (~3 nodes) to hold metrics collected from these nodes. After I deploy > YARN serivce, then I notice that some widgets (Cluster Memory,Cluster > Disk,...) cannot display properly in the YARN service dashboard page. And > Ambari Server has continuous timeout exceptions, which complains that it > doesn't get timeline metrics for connection refused. > The request timeout parameter is 5s, which means the query of getting metrics > from HBase takes more time than that. Then I use Phoenix shell to login and > perform the same query in the HBase , and it takes nearly 30s to finish. But > If I split the big query into small pieces , i mean, use less values in the > "metric_name" field in the where ... in clause , then the result return in 1s > after several small queries. > The query performance in HBase is highly based on the design of rowkey and > the proper usage for it. In the method of getting aggregate metrics, AMS > collector query the METRIC_AGGREGATE table in a way that may cause the > co-processor to scan several regions across different RS. If we add more > metrics in the service dashboard, this situation will be worse. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20392) Get aggregate metric records from HBase encounters performance issues
[ https://issues.apache.org/jira/browse/AMBARI-20392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chuan Jin updated AMBARI-20392: --- Attachment: AMBARI-20392.patch > Get aggregate metric records from HBase encounters performance issues > - > > Key: AMBARI-20392 > URL: https://issues.apache.org/jira/browse/AMBARI-20392 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics >Affects Versions: 2.4.2 >Reporter: Chuan Jin > Attachments: AMBARI-20392.patch, AMBARI-20392.patch > > > I have a mini cluster ( ~6 nodes) managed by Ambari, and use a distributed > HBase (~3 nodes) to hold metrics collected from these nodes. After I deploy > YARN serivce, then I notice that some widgets (Cluster Memory,Cluster > Disk,...) cannot display properly in the YARN service dashboard page. And > Ambari Server has continuous timeout exceptions, which complains that it > doesn't get timeline metrics for connection refused. > The request timeout parameter is 5s, which means the query of getting metrics > from HBase takes more time than that. Then I use Phoenix shell to login and > perform the same query in the HBase , and it takes nearly 30s to finish. But > If I split the big query into small pieces , i mean, use less values in the > "metric_name" field in the where ... in clause , then the result return in 1s > after several small queries. > The query performance in HBase is highly based on the design of rowkey and > the proper usage for it. In the method of getting aggregate metrics, AMS > collector query the METRIC_AGGREGATE table in a way that may cause the > co-processor to scan several regions across different RS. If we add more > metrics in the service dashboard, this situation will be worse. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20431) Increase the calculated AM size for llap
[ https://issues.apache.org/jira/browse/AMBARI-20431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923372#comment-15923372 ] Hudson commented on AMBARI-20431: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7027 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7027/]) AMBARI-20431. ADDENDUM. Increase the calculated AM size for llap. (sshridhar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=72b3084834e03e883079c4253b6d27653603156e]) * (edit) ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/service_advisor.py > Increase the calculated AM size for llap > > > Key: AMBARI-20431 > URL: https://issues.apache.org/jira/browse/AMBARI-20431 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Sumit Mohanty >Assignee: Siddharth Seth >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20431.ADDENDUM.trunk.patch, AMBARI-20431.patch > > > Instead of shipping with a AM size of 2GB, the plan is to ship with an AM > size of 4GB. The new calculation allows for higher AM size on nodes with > higher memory. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20434) Enhance Kafka Service Check
[ https://issues.apache.org/jira/browse/AMBARI-20434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] WangJie updated AMBARI-20434: - Status: Patch Available (was: Open) > Enhance Kafka Service Check > --- > > Key: AMBARI-20434 > URL: https://issues.apache.org/jira/browse/AMBARI-20434 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: WangJie > Fix For: trunk > > Attachments: AMBARI-20434.patch > > > Problem: > Kafka Service Check will create the kafka topic only if the topic doesn't > exist. > if it exists, Kafka Service Check will return success directly. > After topic is being created, we sense that each time running service check > will not reflect the kafka actual state correctly > Suggestion: > Every running kafka service check, delete the existed topic and recreate it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20434) Enhance Kafka Service Check
[ https://issues.apache.org/jira/browse/AMBARI-20434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] WangJie updated AMBARI-20434: - Attachment: AMBARI-20434.patch > Enhance Kafka Service Check > --- > > Key: AMBARI-20434 > URL: https://issues.apache.org/jira/browse/AMBARI-20434 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: WangJie > Fix For: trunk > > Attachments: AMBARI-20434.patch > > > Problem: > Kafka Service Check will create the kafka topic only if the topic doesn't > exist. > if it exists, Kafka Service Check will return success directly. > After topic is being created, we sense that each time running service check > will not reflect the kafka actual state correctly > Suggestion: > Every running kafka service check, delete the existed topic and recreate it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20434) Enhance Kafka Service Check
WangJie created AMBARI-20434: Summary: Enhance Kafka Service Check Key: AMBARI-20434 URL: https://issues.apache.org/jira/browse/AMBARI-20434 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: trunk Reporter: WangJie Fix For: trunk Problem: Kafka Service Check will create the kafka topic only if the topic doesn't exist. if it exists, Kafka Service Check will return success directly. After topic is being created, we sense that each time running service check will not reflect the kafka actual state correctly Suggestion: Every running kafka service check, delete the existed topic and recreate it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20433) Need the ability to have dynamic dependency between component/services
Tuong Truong created AMBARI-20433: - Summary: Need the ability to have dynamic dependency between component/services Key: AMBARI-20433 URL: https://issues.apache.org/jira/browse/AMBARI-20433 Project: Ambari Issue Type: Improvement Components: ambari-server Environment: all Reporter: Tuong Truong Currently, service interdependency are statically defined in the stack regardless its needed or not. For instance, Spark has a static dependency on Hive and will force Hive to be installed whenevern Spark is install, but Hive is only needed if Spark Thrift Server component is installed. It would be nice if the stack has to ability to declare the dependency conditionally and at component level and the dependency will only be in effect when the component is chosen. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20432) ambari-web shows redundant configuration for "Number of nodes used by Hive's LLAP"
[ https://issues.apache.org/jira/browse/AMBARI-20432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-20432: -- Resolution: Fixed Status: Resolved (was: Patch Available) Patch committed to trunk and branch-2.5 > ambari-web shows redundant configuration for "Number of nodes used by Hive's > LLAP" > -- > > Key: AMBARI-20432 > URL: https://issues.apache.org/jira/browse/AMBARI-20432 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Kishor Ramakrishnan >Assignee: Jaimin Jetly >Priority: Blocker > Fix For: 2.5.0 > > Attachments: AMBARI-20432.patch > > > [Upgrades] Start HSI server failed with > "org.apache.commons.cli.ParseException: Invalid configuration: 0" error > Error Logs: > SLF4J: Class path contains multiple SLF4J bindings. > SLF4J: Found binding in > [jar:file:/grid/0/hdp/2.6.0.2-4/hive2/lib/log4j-slf4j-impl-2.6.2.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: Found binding in > [jar:file:/grid/0/hdp/2.6.0.2-4/hadoop/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an > explanation. > SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory] > INFO cli.LlapServiceDriver: LLAP service driver invoked with > arguments=--hiveconf > INFO conf.HiveConf: Found configuration file > file:/etc/hive2/2.6.0.2-4/0/conf.server/hive-site.xml > WARN conf.HiveConf: HiveConf of name hive.llap.daemon.allow.permanent.fns > does not exist > WARN conf.HiveConf: HiveConf hive.llap.daemon.vcpus.per.instance expects INT > type value > WARN conf.HiveConf: HiveConf of name hive.server2.enable.impersonation does > not exist > Failed: Invalid configuration: 0 (should be greater than 0) > org.apache.commons.cli.ParseException: Invalid configuration: 0 (should be > greater than 0) > at > org.apache.hadoop.hive.llap.cli.LlapOptionsProcessor$LlapOptions.(LlapOptionsProcessor.java:94) > at > org.apache.hadoop.hive.llap.cli.LlapOptionsProcessor.processOptions(LlapOptionsProcessor.java:325) > at > org.apache.hadoop.hive.llap.cli.LlapServiceDriver.run(LlapServiceDriver.java:177) > at > org.apache.hadoop.hive.llap.cli.LlapServiceDriver.main(LlapServiceDriver.java:113) > INFO cli.LlapServiceDriver: LLAP service driver finished > Command failed after 1 tries -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20402) Assign Slaves and Clients page displays incorrect configuration unless a change is made in Assign Masters page
[ https://issues.apache.org/jira/browse/AMBARI-20402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923337#comment-15923337 ] Sumit Mohanty commented on AMBARI-20402: [~sangeetar] is there a review board request for this patch? > Assign Slaves and Clients page displays incorrect configuration unless a > change is made in Assign Masters page > -- > > Key: AMBARI-20402 > URL: https://issues.apache.org/jira/browse/AMBARI-20402 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Fix For: 2.5.0 > > Attachments: AMBARI-20402.patch, > AssignSlavesAndClients_AfterChanges.jpg, > AssignSlavesAndClients_BeforeChanges.jpg > > > 1. On a multi-node cluster (for e.g. 5-node cluster), run the ambari install > wizard. > 2. Do not change defaults and navigate to Step 6 (Assign Slaves and Clients). > 3. The recommended configuration does not seem to be place the components > well. For e.g., DataNodes are recommended on all 5 nodes. (see > AssignSlavesAndClients_BeforeChanges.jpg). > 4. Navigate back to Step 5 (Assign Masters). Make a change. For e.g. move the > Atlas Metadata Server to a different host. Next, change it back to the > original host so that in effect nothing has changed. > 5. Now move to Step 6 again and see that the configuration has changed and > seems more in line with best practices although effectively nothing has > changed in the Assign Masters page. (see > AssignSlavesAndClients_AfterChanges.jpg) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20290) null in heapmap page
[
https://issues.apache.org/jira/browse/AMBARI-20290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923318#comment-15923318
]
zhangxiaolu commented on AMBARI-20290:
--
[~nc...@hortonworks.com]Thank you so much for reviewing my patch on
reviewboard, and could you commit the patch ? Thanks a lot.
> null in heapmap page
>
>
> Key: AMBARI-20290
> URL: https://issues.apache.org/jira/browse/AMBARI-20290
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk, 2.4.0, 2.5.0
>Reporter: zhangxiaolu
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-20290.patch, screenshot-1.png, screenshot-2.png,
> screenshot-3.png
>
>
> drawWidget: function () {
> if (this.get('isLoaded')) {
> var hostToValueMap = this.calculateValues();
> var hostNames = [];
> if (this.get('racks').everyProperty('isLoaded', true)) {
> this.get('racks').forEach(function (rack) {
> hostNames = hostNames.concat(rack.hosts.mapProperty('hostName'));
> });
> }
> var metricObject = App.MainChartHeatmapMetric.create({
> name: this.get('content.displayName'),
> units: this.get('content.properties.display_unit'),
> maximumValue: this.get('controller.inputMaximum'),
> hostNames: hostNames,
> hostToValueMap: hostToValueMap
> });
> this.set('controller.selectedMetric', metricObject);
> App.loadTimer.finish('Heatmaps Page');
> App.loadTimer.finish('Service Heatmaps Page');
> }
> }.observes('racks.@each.isLoaded'),
> as loaded like top:
> this.get('content.displayName') is always null
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20431) Increase the calculated AM size for llap
[
https://issues.apache.org/jira/browse/AMBARI-20431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923313#comment-15923313
]
Swapan Shridhar commented on AMBARI-20431:
--
commit for [^AMBARI-20431.ADDENDUM.trunk.patch] in trunk:
{code}
commit 72b3084834e03e883079c4253b6d27653603156e
Author: Swapan Shridhar
Date: Mon Mar 13 16:39:47 2017 -0700
AMBARI-20431. ADDENDUM. Increase the calculated AM size for llap.
{code}
> Increase the calculated AM size for llap
>
>
> Key: AMBARI-20431
> URL: https://issues.apache.org/jira/browse/AMBARI-20431
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.0
>Reporter: Sumit Mohanty
>Assignee: Siddharth Seth
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20431.ADDENDUM.trunk.patch, AMBARI-20431.patch
>
>
> Instead of shipping with a AM size of 2GB, the plan is to ship with an AM
> size of 4GB. The new calculation allows for higher AM size on nodes with
> higher memory.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20432) ambari-web shows redundant configuration for "Number of nodes used by Hive's LLAP"
[ https://issues.apache.org/jira/browse/AMBARI-20432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-20432: -- Priority: Blocker (was: Critical) > ambari-web shows redundant configuration for "Number of nodes used by Hive's > LLAP" > -- > > Key: AMBARI-20432 > URL: https://issues.apache.org/jira/browse/AMBARI-20432 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Kishor Ramakrishnan >Assignee: Jaimin Jetly >Priority: Blocker > Fix For: 2.5.0 > > Attachments: AMBARI-20432.patch > > > [Upgrades] Start HSI server failed with > "org.apache.commons.cli.ParseException: Invalid configuration: 0" error > Error Logs: > SLF4J: Class path contains multiple SLF4J bindings. > SLF4J: Found binding in > [jar:file:/grid/0/hdp/2.6.0.2-4/hive2/lib/log4j-slf4j-impl-2.6.2.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: Found binding in > [jar:file:/grid/0/hdp/2.6.0.2-4/hadoop/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an > explanation. > SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory] > INFO cli.LlapServiceDriver: LLAP service driver invoked with > arguments=--hiveconf > INFO conf.HiveConf: Found configuration file > file:/etc/hive2/2.6.0.2-4/0/conf.server/hive-site.xml > WARN conf.HiveConf: HiveConf of name hive.llap.daemon.allow.permanent.fns > does not exist > WARN conf.HiveConf: HiveConf hive.llap.daemon.vcpus.per.instance expects INT > type value > WARN conf.HiveConf: HiveConf of name hive.server2.enable.impersonation does > not exist > Failed: Invalid configuration: 0 (should be greater than 0) > org.apache.commons.cli.ParseException: Invalid configuration: 0 (should be > greater than 0) > at > org.apache.hadoop.hive.llap.cli.LlapOptionsProcessor$LlapOptions.(LlapOptionsProcessor.java:94) > at > org.apache.hadoop.hive.llap.cli.LlapOptionsProcessor.processOptions(LlapOptionsProcessor.java:325) > at > org.apache.hadoop.hive.llap.cli.LlapServiceDriver.run(LlapServiceDriver.java:177) > at > org.apache.hadoop.hive.llap.cli.LlapServiceDriver.main(LlapServiceDriver.java:113) > INFO cli.LlapServiceDriver: LLAP service driver finished > Command failed after 1 tries -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20432) ambari-web shows redundant configuration for "Number of nodes used by Hive's LLAP"
[ https://issues.apache.org/jira/browse/AMBARI-20432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-20432: -- Status: Patch Available (was: Open) > ambari-web shows redundant configuration for "Number of nodes used by Hive's > LLAP" > -- > > Key: AMBARI-20432 > URL: https://issues.apache.org/jira/browse/AMBARI-20432 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Kishor Ramakrishnan >Assignee: Jaimin Jetly >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20432.patch > > > [Upgrades] Start HSI server failed with > "org.apache.commons.cli.ParseException: Invalid configuration: 0" error > Error Logs: > SLF4J: Class path contains multiple SLF4J bindings. > SLF4J: Found binding in > [jar:file:/grid/0/hdp/2.6.0.2-4/hive2/lib/log4j-slf4j-impl-2.6.2.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: Found binding in > [jar:file:/grid/0/hdp/2.6.0.2-4/hadoop/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an > explanation. > SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory] > INFO cli.LlapServiceDriver: LLAP service driver invoked with > arguments=--hiveconf > INFO conf.HiveConf: Found configuration file > file:/etc/hive2/2.6.0.2-4/0/conf.server/hive-site.xml > WARN conf.HiveConf: HiveConf of name hive.llap.daemon.allow.permanent.fns > does not exist > WARN conf.HiveConf: HiveConf hive.llap.daemon.vcpus.per.instance expects INT > type value > WARN conf.HiveConf: HiveConf of name hive.server2.enable.impersonation does > not exist > Failed: Invalid configuration: 0 (should be greater than 0) > org.apache.commons.cli.ParseException: Invalid configuration: 0 (should be > greater than 0) > at > org.apache.hadoop.hive.llap.cli.LlapOptionsProcessor$LlapOptions.(LlapOptionsProcessor.java:94) > at > org.apache.hadoop.hive.llap.cli.LlapOptionsProcessor.processOptions(LlapOptionsProcessor.java:325) > at > org.apache.hadoop.hive.llap.cli.LlapServiceDriver.run(LlapServiceDriver.java:177) > at > org.apache.hadoop.hive.llap.cli.LlapServiceDriver.main(LlapServiceDriver.java:113) > INFO cli.LlapServiceDriver: LLAP service driver finished > Command failed after 1 tries -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20431) Increase the calculated AM size for llap
[ https://issues.apache.org/jira/browse/AMBARI-20431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923297#comment-15923297 ] Sumit Mohanty commented on AMBARI-20431: +1 to https://issues.apache.org/jira/secure/attachment/12858580/AMBARI-20431.ADDENDUM.trunk.patch > Increase the calculated AM size for llap > > > Key: AMBARI-20431 > URL: https://issues.apache.org/jira/browse/AMBARI-20431 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Sumit Mohanty >Assignee: Siddharth Seth >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20431.ADDENDUM.trunk.patch, AMBARI-20431.patch > > > Instead of shipping with a AM size of 2GB, the plan is to ship with an AM > size of 4GB. The new calculation allows for higher AM size on nodes with > higher memory. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20432) ambari-web shows redundant configuration for "Number of nodes used by Hive's LLAP"
[ https://issues.apache.org/jira/browse/AMBARI-20432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-20432: -- Summary: ambari-web shows redundant configuration for "Number of nodes used by Hive's LLAP" (was: [Upgrades] Start HSI server failed with "org.apache.commons.cli.ParseException: Invalid configuration: 0" error) > ambari-web shows redundant configuration for "Number of nodes used by Hive's > LLAP" > -- > > Key: AMBARI-20432 > URL: https://issues.apache.org/jira/browse/AMBARI-20432 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Kishor Ramakrishnan >Assignee: Jaimin Jetly >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20432.patch > > > [Upgrades] Start HSI server failed with > "org.apache.commons.cli.ParseException: Invalid configuration: 0" error > Error Logs: > SLF4J: Class path contains multiple SLF4J bindings. > SLF4J: Found binding in > [jar:file:/grid/0/hdp/2.6.0.2-4/hive2/lib/log4j-slf4j-impl-2.6.2.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: Found binding in > [jar:file:/grid/0/hdp/2.6.0.2-4/hadoop/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an > explanation. > SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory] > INFO cli.LlapServiceDriver: LLAP service driver invoked with > arguments=--hiveconf > INFO conf.HiveConf: Found configuration file > file:/etc/hive2/2.6.0.2-4/0/conf.server/hive-site.xml > WARN conf.HiveConf: HiveConf of name hive.llap.daemon.allow.permanent.fns > does not exist > WARN conf.HiveConf: HiveConf hive.llap.daemon.vcpus.per.instance expects INT > type value > WARN conf.HiveConf: HiveConf of name hive.server2.enable.impersonation does > not exist > Failed: Invalid configuration: 0 (should be greater than 0) > org.apache.commons.cli.ParseException: Invalid configuration: 0 (should be > greater than 0) > at > org.apache.hadoop.hive.llap.cli.LlapOptionsProcessor$LlapOptions.(LlapOptionsProcessor.java:94) > at > org.apache.hadoop.hive.llap.cli.LlapOptionsProcessor.processOptions(LlapOptionsProcessor.java:325) > at > org.apache.hadoop.hive.llap.cli.LlapServiceDriver.run(LlapServiceDriver.java:177) > at > org.apache.hadoop.hive.llap.cli.LlapServiceDriver.main(LlapServiceDriver.java:113) > INFO cli.LlapServiceDriver: LLAP service driver finished > Command failed after 1 tries -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20432) [Upgrades] Start HSI server failed with "org.apache.commons.cli.ParseException: Invalid configuration: 0" error
[ https://issues.apache.org/jira/browse/AMBARI-20432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-20432: -- Attachment: AMBARI-20432.patch > [Upgrades] Start HSI server failed with > "org.apache.commons.cli.ParseException: Invalid configuration: 0" error > --- > > Key: AMBARI-20432 > URL: https://issues.apache.org/jira/browse/AMBARI-20432 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Kishor Ramakrishnan >Assignee: Jaimin Jetly >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20432.patch > > > [Upgrades] Start HSI server failed with > "org.apache.commons.cli.ParseException: Invalid configuration: 0" error > Error Logs: > SLF4J: Class path contains multiple SLF4J bindings. > SLF4J: Found binding in > [jar:file:/grid/0/hdp/2.6.0.2-4/hive2/lib/log4j-slf4j-impl-2.6.2.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: Found binding in > [jar:file:/grid/0/hdp/2.6.0.2-4/hadoop/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an > explanation. > SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory] > INFO cli.LlapServiceDriver: LLAP service driver invoked with > arguments=--hiveconf > INFO conf.HiveConf: Found configuration file > file:/etc/hive2/2.6.0.2-4/0/conf.server/hive-site.xml > WARN conf.HiveConf: HiveConf of name hive.llap.daemon.allow.permanent.fns > does not exist > WARN conf.HiveConf: HiveConf hive.llap.daemon.vcpus.per.instance expects INT > type value > WARN conf.HiveConf: HiveConf of name hive.server2.enable.impersonation does > not exist > Failed: Invalid configuration: 0 (should be greater than 0) > org.apache.commons.cli.ParseException: Invalid configuration: 0 (should be > greater than 0) > at > org.apache.hadoop.hive.llap.cli.LlapOptionsProcessor$LlapOptions.(LlapOptionsProcessor.java:94) > at > org.apache.hadoop.hive.llap.cli.LlapOptionsProcessor.processOptions(LlapOptionsProcessor.java:325) > at > org.apache.hadoop.hive.llap.cli.LlapServiceDriver.run(LlapServiceDriver.java:177) > at > org.apache.hadoop.hive.llap.cli.LlapServiceDriver.main(LlapServiceDriver.java:113) > INFO cli.LlapServiceDriver: LLAP service driver finished > Command failed after 1 tries -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-20432) [Upgrades] Start HSI server failed with "org.apache.commons.cli.ParseException: Invalid configuration: 0" error
[ https://issues.apache.org/jira/browse/AMBARI-20432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly reassigned AMBARI-20432: - Assignee: Jaimin Jetly > [Upgrades] Start HSI server failed with > "org.apache.commons.cli.ParseException: Invalid configuration: 0" error > --- > > Key: AMBARI-20432 > URL: https://issues.apache.org/jira/browse/AMBARI-20432 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Kishor Ramakrishnan >Assignee: Jaimin Jetly >Priority: Critical > Fix For: 2.5.0 > > > [Upgrades] Start HSI server failed with > "org.apache.commons.cli.ParseException: Invalid configuration: 0" error > Error Logs: > SLF4J: Class path contains multiple SLF4J bindings. > SLF4J: Found binding in > [jar:file:/grid/0/hdp/2.6.0.2-4/hive2/lib/log4j-slf4j-impl-2.6.2.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: Found binding in > [jar:file:/grid/0/hdp/2.6.0.2-4/hadoop/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an > explanation. > SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory] > INFO cli.LlapServiceDriver: LLAP service driver invoked with > arguments=--hiveconf > INFO conf.HiveConf: Found configuration file > file:/etc/hive2/2.6.0.2-4/0/conf.server/hive-site.xml > WARN conf.HiveConf: HiveConf of name hive.llap.daemon.allow.permanent.fns > does not exist > WARN conf.HiveConf: HiveConf hive.llap.daemon.vcpus.per.instance expects INT > type value > WARN conf.HiveConf: HiveConf of name hive.server2.enable.impersonation does > not exist > Failed: Invalid configuration: 0 (should be greater than 0) > org.apache.commons.cli.ParseException: Invalid configuration: 0 (should be > greater than 0) > at > org.apache.hadoop.hive.llap.cli.LlapOptionsProcessor$LlapOptions.(LlapOptionsProcessor.java:94) > at > org.apache.hadoop.hive.llap.cli.LlapOptionsProcessor.processOptions(LlapOptionsProcessor.java:325) > at > org.apache.hadoop.hive.llap.cli.LlapServiceDriver.run(LlapServiceDriver.java:177) > at > org.apache.hadoop.hive.llap.cli.LlapServiceDriver.main(LlapServiceDriver.java:113) > INFO cli.LlapServiceDriver: LLAP service driver finished > Command failed after 1 tries -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20431) Increase the calculated AM size for llap
[ https://issues.apache.org/jira/browse/AMBARI-20431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923259#comment-15923259 ] Hudson commented on AMBARI-20431: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1251 (See [https://builds.apache.org/job/Ambari-branch-2.5/1251/]) AMBARI-20431. Increase the calculated AM size for llap (sseth via (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e6e56e8bad617c65997c31773338bb176169b4a2]) * (edit) ambari-server/src/test/python/stacks/2.5/common/test_stack_advisor.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py > Increase the calculated AM size for llap > > > Key: AMBARI-20431 > URL: https://issues.apache.org/jira/browse/AMBARI-20431 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Sumit Mohanty >Assignee: Siddharth Seth >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20431.ADDENDUM.trunk.patch, AMBARI-20431.patch > > > Instead of shipping with a AM size of 2GB, the plan is to ship with an AM > size of 4GB. The new calculation allows for higher AM size on nodes with > higher memory. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20432) [Upgrades] Start HSI server failed with "org.apache.commons.cli.ParseException: Invalid configuration: 0" error
Kishor Ramakrishnan created AMBARI-20432: Summary: [Upgrades] Start HSI server failed with "org.apache.commons.cli.ParseException: Invalid configuration: 0" error Key: AMBARI-20432 URL: https://issues.apache.org/jira/browse/AMBARI-20432 Project: Ambari Issue Type: Bug Reporter: Kishor Ramakrishnan Priority: Critical [Upgrades] Start HSI server failed with "org.apache.commons.cli.ParseException: Invalid configuration: 0" error Error Logs: SLF4J: Class path contains multiple SLF4J bindings. SLF4J: Found binding in [jar:file:/grid/0/hdp/2.6.0.2-4/hive2/lib/log4j-slf4j-impl-2.6.2.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [jar:file:/grid/0/hdp/2.6.0.2-4/hadoop/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory] INFO cli.LlapServiceDriver: LLAP service driver invoked with arguments=--hiveconf INFO conf.HiveConf: Found configuration file file:/etc/hive2/2.6.0.2-4/0/conf.server/hive-site.xml WARN conf.HiveConf: HiveConf of name hive.llap.daemon.allow.permanent.fns does not exist WARN conf.HiveConf: HiveConf hive.llap.daemon.vcpus.per.instance expects INT type value WARN conf.HiveConf: HiveConf of name hive.server2.enable.impersonation does not exist Failed: Invalid configuration: 0 (should be greater than 0) org.apache.commons.cli.ParseException: Invalid configuration: 0 (should be greater than 0) at org.apache.hadoop.hive.llap.cli.LlapOptionsProcessor$LlapOptions.(LlapOptionsProcessor.java:94) at org.apache.hadoop.hive.llap.cli.LlapOptionsProcessor.processOptions(LlapOptionsProcessor.java:325) at org.apache.hadoop.hive.llap.cli.LlapServiceDriver.run(LlapServiceDriver.java:177) at org.apache.hadoop.hive.llap.cli.LlapServiceDriver.main(LlapServiceDriver.java:113) INFO cli.LlapServiceDriver: LLAP service driver finished Command failed after 1 tries -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20432) [Upgrades] Start HSI server failed with "org.apache.commons.cli.ParseException: Invalid configuration: 0" error
[ https://issues.apache.org/jira/browse/AMBARI-20432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishor Ramakrishnan updated AMBARI-20432: - Affects Version/s: 2.5.0 Fix Version/s: 2.5.0 Component/s: ambari-server > [Upgrades] Start HSI server failed with > "org.apache.commons.cli.ParseException: Invalid configuration: 0" error > --- > > Key: AMBARI-20432 > URL: https://issues.apache.org/jira/browse/AMBARI-20432 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Kishor Ramakrishnan >Priority: Critical > Fix For: 2.5.0 > > > [Upgrades] Start HSI server failed with > "org.apache.commons.cli.ParseException: Invalid configuration: 0" error > Error Logs: > SLF4J: Class path contains multiple SLF4J bindings. > SLF4J: Found binding in > [jar:file:/grid/0/hdp/2.6.0.2-4/hive2/lib/log4j-slf4j-impl-2.6.2.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: Found binding in > [jar:file:/grid/0/hdp/2.6.0.2-4/hadoop/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an > explanation. > SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory] > INFO cli.LlapServiceDriver: LLAP service driver invoked with > arguments=--hiveconf > INFO conf.HiveConf: Found configuration file > file:/etc/hive2/2.6.0.2-4/0/conf.server/hive-site.xml > WARN conf.HiveConf: HiveConf of name hive.llap.daemon.allow.permanent.fns > does not exist > WARN conf.HiveConf: HiveConf hive.llap.daemon.vcpus.per.instance expects INT > type value > WARN conf.HiveConf: HiveConf of name hive.server2.enable.impersonation does > not exist > Failed: Invalid configuration: 0 (should be greater than 0) > org.apache.commons.cli.ParseException: Invalid configuration: 0 (should be > greater than 0) > at > org.apache.hadoop.hive.llap.cli.LlapOptionsProcessor$LlapOptions.(LlapOptionsProcessor.java:94) > at > org.apache.hadoop.hive.llap.cli.LlapOptionsProcessor.processOptions(LlapOptionsProcessor.java:325) > at > org.apache.hadoop.hive.llap.cli.LlapServiceDriver.run(LlapServiceDriver.java:177) > at > org.apache.hadoop.hive.llap.cli.LlapServiceDriver.main(LlapServiceDriver.java:113) > INFO cli.LlapServiceDriver: LLAP service driver finished > Command failed after 1 tries -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20431) Increase the calculated AM size for llap
[ https://issues.apache.org/jira/browse/AMBARI-20431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923198#comment-15923198 ] Swapan Shridhar commented on AMBARI-20431: -- [~sumitmohanty] I have added the addendum patch for trunk [^AMBARI-20431.ADDENDUM.trunk.patch]. Can you review ? > Increase the calculated AM size for llap > > > Key: AMBARI-20431 > URL: https://issues.apache.org/jira/browse/AMBARI-20431 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Sumit Mohanty >Assignee: Siddharth Seth >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20431.ADDENDUM.trunk.patch, AMBARI-20431.patch > > > Instead of shipping with a AM size of 2GB, the plan is to ship with an AM > size of 4GB. The new calculation allows for higher AM size on nodes with > higher memory. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20409) Hue Migration View Giving error while migrating Pig Jobs in Postgres DB
[
https://issues.apache.org/jira/browse/AMBARI-20409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923197#comment-15923197
]
Hadoop QA commented on AMBARI-20409:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12858521/AMBARI-20409.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
contrib/views/hueambarimigration.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/11012//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11012//console
This message is automatically generated.
> Hue Migration View Giving error while migrating Pig Jobs in Postgres DB
> ---
>
> Key: AMBARI-20409
> URL: https://issues.apache.org/jira/browse/AMBARI-20409
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Reporter: Ishan Bhatt
>Assignee: Ishan Bhatt
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-20409.patch
>
>
> While Migrating pig Job
> Error displayed:-
> {code}
> SQL Exception: ERROR: column "ds_inprogress" is of type boolean but
> expression is of type integer Hint: You will need to rewrite or cast the
> expression. Position: 46
> {code}
> Log:-
> {code}
> 0 Mar 2017 12:00:38,477 INFO [Thread-64] PigJobMigrationUtility:139 - Loop
> No.1
> 10 Mar 2017 12:00:38,477 INFO [Thread-64] PigJobMigrationUtility:140 -
>
> 10 Mar 2017 12:00:38,477 INFO [Thread-64] PigJobMigrationUtility:141 - the
> title of script describeSchema
> 10 Mar 2017 12:00:38,501 ERROR [Thread-64] PigJobMigrationUtility:191 - sql
> exception in ambari database:
> org.postgresql.util.PSQLException: ERROR: column "ds_inprogress" is of type
> boolean but expression is of type integer
> Hint: You will need to rewrite or cast the expression.
> Position: 46
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2062)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1795)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:257)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:479)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:367)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.executeUpdate(AbstractJdbc2Statement.java:321)
> at
> com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeUpdate(NewProxyPreparedStatement.java:105)
> at
> org.apache.ambari.view.huetoambarimigration.migration.pig.pigjob.PigJobMigrationImplementation.insertRowPigJob(PigJobMigrationImplementation.java:204)
> at
> org.apache.ambari.view.huetoambarimigration.migration.pig.pigjob.PigJobMigrationUtility.pigJobMigration(PigJobMigrationUtility.java:155)
> at
> org.apache.ambari.view.huetoambarimigration.migration.pig.pigjob.PigJobStartJob.run(PigJobStartJob.java:59)
> 10 Mar 2017 12:00:38,503 INFO [Thread-64] PigJobMigrationUtility:195 - roll
> back done
> 10 Mar 2017 12:00:38,510 INFO [Thread-64] PigJobMigrationUtility:225 -
> --
> 10 Mar 2017 12:00:38,510 INFO [Thread-64] PigJobMigrationUtility:226 - pig
> Job Migration End
> 10 Mar 2017 12:00:38,510 INFO [Thread-64] PigJobMigrationUtility:227 -
> --
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20431) Increase the calculated AM size for llap
[ https://issues.apache.org/jira/browse/AMBARI-20431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-20431: - Attachment: AMBARI-20431.ADDENDUM.trunk.patch > Increase the calculated AM size for llap > > > Key: AMBARI-20431 > URL: https://issues.apache.org/jira/browse/AMBARI-20431 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Sumit Mohanty >Assignee: Siddharth Seth >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20431.ADDENDUM.trunk.patch, AMBARI-20431.patch > > > Instead of shipping with a AM size of 2GB, the plan is to ship with an AM > size of 4GB. The new calculation allows for higher AM size on nodes with > higher memory. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20431) Increase the calculated AM size for llap
[ https://issues.apache.org/jira/browse/AMBARI-20431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923189#comment-15923189 ] Hudson commented on AMBARI-20431: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7026 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7026/]) AMBARI-20431. Increase the calculated AM size for llap (sseth via (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f92e8c916fe1850487a5969f7c1b97ea7eaf9c64]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py * (edit) ambari-server/src/test/python/stacks/2.5/common/test_stack_advisor.py > Increase the calculated AM size for llap > > > Key: AMBARI-20431 > URL: https://issues.apache.org/jira/browse/AMBARI-20431 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Sumit Mohanty >Assignee: Siddharth Seth >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20431.patch > > > Instead of shipping with a AM size of 2GB, the plan is to ship with an AM > size of 4GB. The new calculation allows for higher AM size on nodes with > higher memory. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (AMBARI-20431) Increase the calculated AM size for llap
[
https://issues.apache.org/jira/browse/AMBARI-20431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923168#comment-15923168
]
Swapan Shridhar edited comment on AMBARI-20431 at 3/13/17 11:31 PM:
+1 for this patch for Ambari-2.5 branch
{{For trunk:}}
A separate patch required, where we need to add the same code logic for
3.0/service_advisor.py as well at:
https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/service_advisor.py#L1453
CC [~sseth] | [~sumitmohanty]
was (Author: swapanshridhar):
+1 for the patch.
> Increase the calculated AM size for llap
>
>
> Key: AMBARI-20431
> URL: https://issues.apache.org/jira/browse/AMBARI-20431
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.0
>Reporter: Sumit Mohanty
>Assignee: Siddharth Seth
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20431.patch
>
>
> Instead of shipping with a AM size of 2GB, the plan is to ship with an AM
> size of 4GB. The new calculation allows for higher AM size on nodes with
> higher memory.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20431) Increase the calculated AM size for llap
[ https://issues.apache.org/jira/browse/AMBARI-20431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-20431: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.5 > Increase the calculated AM size for llap > > > Key: AMBARI-20431 > URL: https://issues.apache.org/jira/browse/AMBARI-20431 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Sumit Mohanty >Assignee: Siddharth Seth >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20431.patch > > > Instead of shipping with a AM size of 2GB, the plan is to ship with an AM > size of 4GB. The new calculation allows for higher AM size on nodes with > higher memory. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20431) Increase the calculated AM size for llap
[ https://issues.apache.org/jira/browse/AMBARI-20431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923168#comment-15923168 ] Swapan Shridhar commented on AMBARI-20431: -- +1 for the patch. > Increase the calculated AM size for llap > > > Key: AMBARI-20431 > URL: https://issues.apache.org/jira/browse/AMBARI-20431 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Sumit Mohanty >Assignee: Siddharth Seth >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20431.patch > > > Instead of shipping with a AM size of 2GB, the plan is to ship with an AM > size of 4GB. The new calculation allows for higher AM size on nodes with > higher memory. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-20430) Knox Proxy - Ambari HIVE2.0 view doesn't showup due to Servicecheck issues
[ https://issues.apache.org/jira/browse/AMBARI-20430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SuryaKranthi Koneru resolved AMBARI-20430. -- Resolution: Invalid should be a knox bug, so closing this ambari issue > Knox Proxy - Ambari HIVE2.0 view doesn't showup due to Servicecheck issues > -- > > Key: AMBARI-20430 > URL: https://issues.apache.org/jira/browse/AMBARI-20430 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: SuryaKranthi Koneru >Assignee: Vivek Ratnavel Subramanian >Priority: Critical > Fix For: 2.5.0 > > > Hive Server interactive not removed from Hive summary page even after HSI is > disabled. > Strange Fact : HSI is started without any error when did a restart all stale > components even though HSI is disabled -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-20431) Increase the calculated AM size for llap
[ https://issues.apache.org/jira/browse/AMBARI-20431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty reassigned AMBARI-20431: -- Assignee: Siddharth Seth (was: Sumit Mohanty) > Increase the calculated AM size for llap > > > Key: AMBARI-20431 > URL: https://issues.apache.org/jira/browse/AMBARI-20431 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Sumit Mohanty >Assignee: Siddharth Seth >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20431.patch > > > Instead of shipping with a AM size of 2GB, the plan is to ship with an AM > size of 4GB. The new calculation allows for higher AM size on nodes with > higher memory. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20430) Knox Proxy - Ambari HIVE2.0 view doesn't showup due to Servicecheck issues
[ https://issues.apache.org/jira/browse/AMBARI-20430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SuryaKranthi Koneru updated AMBARI-20430: - Component/s: (was: ambari-sever) (was: ambari-web) ambari-views > Knox Proxy - Ambari HIVE2.0 view doesn't showup due to Servicecheck issues > -- > > Key: AMBARI-20430 > URL: https://issues.apache.org/jira/browse/AMBARI-20430 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: SuryaKranthi Koneru >Assignee: Vivek Ratnavel Subramanian >Priority: Critical > Fix For: 2.5.0 > > > Hive Server interactive not removed from Hive summary page even after HSI is > disabled. > Strange Fact : HSI is started without any error when did a restart all stale > components even though HSI is disabled -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20431) Increase the calculated AM size for llap
[ https://issues.apache.org/jira/browse/AMBARI-20431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-20431: --- Attachment: AMBARI-20431.patch > Increase the calculated AM size for llap > > > Key: AMBARI-20431 > URL: https://issues.apache.org/jira/browse/AMBARI-20431 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Sumit Mohanty >Assignee: Sumit Mohanty >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20431.patch > > > Instead of shipping with a AM size of 2GB, the plan is to ship with an AM > size of 4GB. The new calculation allows for higher AM size on nodes with > higher memory. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20431) Increase the calculated AM size for llap
[ https://issues.apache.org/jira/browse/AMBARI-20431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-20431: --- Status: Patch Available (was: Open) > Increase the calculated AM size for llap > > > Key: AMBARI-20431 > URL: https://issues.apache.org/jira/browse/AMBARI-20431 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Sumit Mohanty >Assignee: Sumit Mohanty >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20431.patch > > > Instead of shipping with a AM size of 2GB, the plan is to ship with an AM > size of 4GB. The new calculation allows for higher AM size on nodes with > higher memory. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20431) Increase the calculated AM size for llap
Sumit Mohanty created AMBARI-20431: -- Summary: Increase the calculated AM size for llap Key: AMBARI-20431 URL: https://issues.apache.org/jira/browse/AMBARI-20431 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.5.0 Reporter: Sumit Mohanty Assignee: Sumit Mohanty Priority: Critical Fix For: 2.5.0 Instead of shipping with a AM size of 2GB, the plan is to ship with an AM size of 4GB. The new calculation allows for higher AM size on nodes with higher memory. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20428) UI - bugs with styles
[
https://issues.apache.org/jira/browse/AMBARI-20428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923130#comment-15923130
]
Hadoop QA commented on AMBARI-20428:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12858525/AMBARI-20428.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in
contrib/views/hive-next
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/11011//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11011//console
This message is automatically generated.
> UI - bugs with styles
> -
>
> Key: AMBARI-20428
> URL: https://issues.apache.org/jira/browse/AMBARI-20428
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-20428.patch
>
>
> STR
> Ambari 2.5.0.0 with a very long cluster name, add Hive, register bits for new
> HDP version
> 1. Look at the stacks and versions page with limited screen size
> The cluster name will be cut-off
> 2. The Hive view can display errors (such as when the Hive server is down),
> but the icons for "x" or right arrow have a hand-icon on-hover, which makes
> it seem like it's clickable but clicking does nothing.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20430) Knox Proxy - Ambari HIVE2.0 view doesn't showup due to Servicecheck issues
SuryaKranthi Koneru created AMBARI-20430: Summary: Knox Proxy - Ambari HIVE2.0 view doesn't showup due to Servicecheck issues Key: AMBARI-20430 URL: https://issues.apache.org/jira/browse/AMBARI-20430 Project: Ambari Issue Type: Bug Components: ambari-sever, ambari-web Affects Versions: 2.5.0 Reporter: SuryaKranthi Koneru Assignee: Vivek Ratnavel Subramanian Priority: Critical Fix For: 2.5.0 Hive Server interactive not removed from Hive summary page even after HSI is disabled. Strange Fact : HSI is started without any error when did a restart all stale components even though HSI is disabled -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20070) Agent heartbeat lost due to subprocess.Popen race condition
[
https://issues.apache.org/jira/browse/AMBARI-20070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923100#comment-15923100
]
Hudson commented on AMBARI-20070:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7025 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7025/])
AMBARI-20070. Agent heartbeat lost due to subprocess.Popen race (adoroszlai:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=19c9e25587316bceb46c1585fce712fdf5056e39])
* (edit) ambari-agent/src/main/python/ambari_agent/main.py
> Agent heartbeat lost due to subprocess.Popen race condition
> ---
>
> Key: AMBARI-20070
> URL: https://issues.apache.org/jira/browse/AMBARI-20070
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.5.0
> Environment: Python 2.7
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Critical
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-20070_multiprocessing.patch, AMBARI-20070.patch
>
>
> Workaround for http://bugs.python.org/issue19809 that probably causes
> {{subprocess.Popen}} call to get stuck in:
> {noformat}
> File: "/usr/lib/python2.7/subprocess.py", line 679, in __init__
> errread, errwrite)
> File: "/usr/lib/python2.7/subprocess.py", line 1244, in _execute_child
> data = _eintr_retry_call(os.read, errpipe_read, 1048576)
> File: "/usr/lib/python2.7/subprocess.py", line 478, in _eintr_retry_call
> return func(*args)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20070) Agent heartbeat lost due to subprocess.Popen race condition
[
https://issues.apache.org/jira/browse/AMBARI-20070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923094#comment-15923094
]
Hudson commented on AMBARI-20070:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1250 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1250/])
AMBARI-20070. Agent heartbeat lost due to subprocess.Popen race (adoroszlai:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=7794d1326f075bd1c7e8a3ce5a8eb62c48154d8a])
* (edit) ambari-agent/src/main/python/ambari_agent/main.py
> Agent heartbeat lost due to subprocess.Popen race condition
> ---
>
> Key: AMBARI-20070
> URL: https://issues.apache.org/jira/browse/AMBARI-20070
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.5.0
> Environment: Python 2.7
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Critical
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-20070_multiprocessing.patch, AMBARI-20070.patch
>
>
> Workaround for http://bugs.python.org/issue19809 that probably causes
> {{subprocess.Popen}} call to get stuck in:
> {noformat}
> File: "/usr/lib/python2.7/subprocess.py", line 679, in __init__
> errread, errwrite)
> File: "/usr/lib/python2.7/subprocess.py", line 1244, in _execute_child
> data = _eintr_retry_call(os.read, errpipe_read, 1048576)
> File: "/usr/lib/python2.7/subprocess.py", line 478, in _eintr_retry_call
> return func(*args)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20426) Hive Server interactive not removed from Hive summary page after HSI is disabled
[ https://issues.apache.org/jira/browse/AMBARI-20426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-20426: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.5. > Hive Server interactive not removed from Hive summary page after HSI is > disabled > > > Key: AMBARI-20426 > URL: https://issues.apache.org/jira/browse/AMBARI-20426 > Project: Ambari > Issue Type: Bug > Components: ambari-sever, ambari-web >Affects Versions: 2.5.0 >Reporter: Kishor Ramakrishnan >Assignee: Vivek Ratnavel Subramanian >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20426.v0.patch > > > Hive Server interactive not removed from Hive summary page even after HSI is > disabled. > Strange Fact : HSI is started without any error when did a restart all stale > components even though HSI is disabled -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20400) Yarn should not copy Tez and Slider tar ball if Tez and Sliders are not installed on the cluster
[
https://issues.apache.org/jira/browse/AMBARI-20400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923058#comment-15923058
]
Hadoop QA commented on AMBARI-20400:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12858534/AMBARI-20400.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/11010//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11010//console
This message is automatically generated.
> Yarn should not copy Tez and Slider tar ball if Tez and Sliders are not
> installed on the cluster
>
>
> Key: AMBARI-20400
> URL: https://issues.apache.org/jira/browse/AMBARI-20400
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-20400.patch
>
>
> It's possible to install a cluster without Tez and Slider via blueprint. In
> this case, Yarn historyserver start logic prints two warnings about unable to
> copy tez and slider tar ball to HDFS.
> Yarn history server should skip the copy hdfs tar ball logic for tez and
> slider if they are not installed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20426) Hive Server interactive not removed from Hive summary page after HSI is disabled
[ https://issues.apache.org/jira/browse/AMBARI-20426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923037#comment-15923037 ] Hudson commented on AMBARI-20426: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7024 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7024/]) AMBARI-20426. Hive Server interactive not removed from Hive summary page (yusaku: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=9446252fa2324e74d594febd913a7e4e056f7644]) * (edit) ambari-web/app/mixins/main/service/configs/component_actions_by_configs.js > Hive Server interactive not removed from Hive summary page after HSI is > disabled > > > Key: AMBARI-20426 > URL: https://issues.apache.org/jira/browse/AMBARI-20426 > Project: Ambari > Issue Type: Bug > Components: ambari-sever, ambari-web >Affects Versions: 2.5.0 >Reporter: Kishor Ramakrishnan >Assignee: Vivek Ratnavel Subramanian >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20426.v0.patch > > > Hive Server interactive not removed from Hive summary page even after HSI is > disabled. > Strange Fact : HSI is started without any error when did a restart all stale > components even though HSI is disabled -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20426) Hive Server interactive not removed from Hive summary page after HSI is disabled
[ https://issues.apache.org/jira/browse/AMBARI-20426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923032#comment-15923032 ] Hudson commented on AMBARI-20426: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1249 (See [https://builds.apache.org/job/Ambari-branch-2.5/1249/]) AMBARI-20426. Hive Server interactive not removed from Hive summary page (yusaku: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=09fcf9b07ffc90facbabe991d04dc377159297b8]) * (edit) ambari-web/app/mixins/main/service/configs/component_actions_by_configs.js > Hive Server interactive not removed from Hive summary page after HSI is > disabled > > > Key: AMBARI-20426 > URL: https://issues.apache.org/jira/browse/AMBARI-20426 > Project: Ambari > Issue Type: Bug > Components: ambari-sever, ambari-web >Affects Versions: 2.5.0 >Reporter: Kishor Ramakrishnan >Assignee: Vivek Ratnavel Subramanian >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20426.v0.patch > > > Hive Server interactive not removed from Hive summary page even after HSI is > disabled. > Strange Fact : HSI is started without any error when did a restart all stale > components even though HSI is disabled -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20402) Assign Slaves and Clients page displays incorrect configuration unless a change is made in Assign Masters page
[ https://issues.apache.org/jira/browse/AMBARI-20402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-20402: Resolution: Fixed Status: Resolved (was: Patch Available) > Assign Slaves and Clients page displays incorrect configuration unless a > change is made in Assign Masters page > -- > > Key: AMBARI-20402 > URL: https://issues.apache.org/jira/browse/AMBARI-20402 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Fix For: 2.5.0 > > Attachments: AMBARI-20402.patch, > AssignSlavesAndClients_AfterChanges.jpg, > AssignSlavesAndClients_BeforeChanges.jpg > > > 1. On a multi-node cluster (for e.g. 5-node cluster), run the ambari install > wizard. > 2. Do not change defaults and navigate to Step 6 (Assign Slaves and Clients). > 3. The recommended configuration does not seem to be place the components > well. For e.g., DataNodes are recommended on all 5 nodes. (see > AssignSlavesAndClients_BeforeChanges.jpg). > 4. Navigate back to Step 5 (Assign Masters). Make a change. For e.g. move the > Atlas Metadata Server to a different host. Next, change it back to the > original host so that in effect nothing has changed. > 5. Now move to Step 6 again and see that the configuration has changed and > seems more in line with best practices although effectively nothing has > changed in the Assign Masters page. (see > AssignSlavesAndClients_AfterChanges.jpg) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20402) Assign Slaves and Clients page displays incorrect configuration unless a change is made in Assign Masters page
[ https://issues.apache.org/jira/browse/AMBARI-20402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15922988#comment-15922988 ] Sangeeta Ravindran commented on AMBARI-20402: - Committed to 2.5 as commit 819d4f25339476622ffe73dd64acb85e24b52969 Author: Sangeeta Ravindran Date: Mon Mar 13 11:56:04 2017 -0700 AMBARI-20402: Assign Slaves and Clients page displays incorrect configuration unless a change is made in Assign Masters page (sangeetar) > Assign Slaves and Clients page displays incorrect configuration unless a > change is made in Assign Masters page > -- > > Key: AMBARI-20402 > URL: https://issues.apache.org/jira/browse/AMBARI-20402 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Fix For: 2.5.0 > > Attachments: AMBARI-20402.patch, > AssignSlavesAndClients_AfterChanges.jpg, > AssignSlavesAndClients_BeforeChanges.jpg > > > 1. On a multi-node cluster (for e.g. 5-node cluster), run the ambari install > wizard. > 2. Do not change defaults and navigate to Step 6 (Assign Slaves and Clients). > 3. The recommended configuration does not seem to be place the components > well. For e.g., DataNodes are recommended on all 5 nodes. (see > AssignSlavesAndClients_BeforeChanges.jpg). > 4. Navigate back to Step 5 (Assign Masters). Make a change. For e.g. move the > Atlas Metadata Server to a different host. Next, change it back to the > original host so that in effect nothing has changed. > 5. Now move to Step 6 again and see that the configuration has changed and > seems more in line with best practices although effectively nothing has > changed in the Assign Masters page. (see > AssignSlavesAndClients_AfterChanges.jpg) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (AMBARI-20402) Assign Slaves and Clients page displays incorrect configuration unless a change is made in Assign Masters page
[ https://issues.apache.org/jira/browse/AMBARI-20402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15922982#comment-15922982 ] Sangeeta Ravindran edited comment on AMBARI-20402 at 3/13/17 9:34 PM: -- Failure in Jenkins build is unrelated to the fix. Failure occurs in ambari-admin project: Additional error details: fatal: unable to access 'https://github.com/lodash/lodash.git/': gnutls_handshake() failed: A TLS packet with unexpected length was received. [ERROR] Command execution failed. org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1) at org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:404) was (Author: sangeetar): Committed to 2.5 as commit 819d4f25339476622ffe73dd64acb85e24b52969 Author: Sangeeta Ravindran Date: Mon Mar 13 11:56:04 2017 -0700 AMBARI-20402: Assign Slaves and Clients page displays incorrect configuration unless a change is made in Assign Masters page (sangeetar) > Assign Slaves and Clients page displays incorrect configuration unless a > change is made in Assign Masters page > -- > > Key: AMBARI-20402 > URL: https://issues.apache.org/jira/browse/AMBARI-20402 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Fix For: 2.5.0 > > Attachments: AMBARI-20402.patch, > AssignSlavesAndClients_AfterChanges.jpg, > AssignSlavesAndClients_BeforeChanges.jpg > > > 1. On a multi-node cluster (for e.g. 5-node cluster), run the ambari install > wizard. > 2. Do not change defaults and navigate to Step 6 (Assign Slaves and Clients). > 3. The recommended configuration does not seem to be place the components > well. For e.g., DataNodes are recommended on all 5 nodes. (see > AssignSlavesAndClients_BeforeChanges.jpg). > 4. Navigate back to Step 5 (Assign Masters). Make a change. For e.g. move the > Atlas Metadata Server to a different host. Next, change it back to the > original host so that in effect nothing has changed. > 5. Now move to Step 6 again and see that the configuration has changed and > seems more in line with best practices although effectively nothing has > changed in the Assign Masters page. (see > AssignSlavesAndClients_AfterChanges.jpg) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20426) Hive Server interactive not removed from Hive summary page after HSI is disabled
[
https://issues.apache.org/jira/browse/AMBARI-20426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15922987#comment-15922987
]
Hadoop QA commented on AMBARI-20426:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12858532/AMBARI-20426.v0.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/11009//console
This message is automatically generated.
> Hive Server interactive not removed from Hive summary page after HSI is
> disabled
>
>
> Key: AMBARI-20426
> URL: https://issues.apache.org/jira/browse/AMBARI-20426
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever, ambari-web
>Affects Versions: 2.5.0
>Reporter: Kishor Ramakrishnan
>Assignee: Vivek Ratnavel Subramanian
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20426.v0.patch
>
>
> Hive Server interactive not removed from Hive summary page even after HSI is
> disabled.
> Strange Fact : HSI is started without any error when did a restart all stale
> components even though HSI is disabled
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20402) Assign Slaves and Clients page displays incorrect configuration unless a change is made in Assign Masters page
[ https://issues.apache.org/jira/browse/AMBARI-20402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15922982#comment-15922982 ] Sangeeta Ravindran commented on AMBARI-20402: - Committed to 2.5 as commit 819d4f25339476622ffe73dd64acb85e24b52969 Author: Sangeeta Ravindran Date: Mon Mar 13 11:56:04 2017 -0700 AMBARI-20402: Assign Slaves and Clients page displays incorrect configuration unless a change is made in Assign Masters page (sangeetar) > Assign Slaves and Clients page displays incorrect configuration unless a > change is made in Assign Masters page > -- > > Key: AMBARI-20402 > URL: https://issues.apache.org/jira/browse/AMBARI-20402 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Fix For: 2.5.0 > > Attachments: AMBARI-20402.patch, > AssignSlavesAndClients_AfterChanges.jpg, > AssignSlavesAndClients_BeforeChanges.jpg > > > 1. On a multi-node cluster (for e.g. 5-node cluster), run the ambari install > wizard. > 2. Do not change defaults and navigate to Step 6 (Assign Slaves and Clients). > 3. The recommended configuration does not seem to be place the components > well. For e.g., DataNodes are recommended on all 5 nodes. (see > AssignSlavesAndClients_BeforeChanges.jpg). > 4. Navigate back to Step 5 (Assign Masters). Make a change. For e.g. move the > Atlas Metadata Server to a different host. Next, change it back to the > original host so that in effect nothing has changed. > 5. Now move to Step 6 again and see that the configuration has changed and > seems more in line with best practices although effectively nothing has > changed in the Assign Masters page. (see > AssignSlavesAndClients_AfterChanges.jpg) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20070) Agent heartbeat lost due to subprocess.Popen race condition
[
https://issues.apache.org/jira/browse/AMBARI-20070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-20070:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to
[trunk|http://git-wip-us.apache.org/repos/asf/ambari/commit/19c9e255] and
[branch-2.5|http://git-wip-us.apache.org/repos/asf/ambari/commit/7794d132].
> Agent heartbeat lost due to subprocess.Popen race condition
> ---
>
> Key: AMBARI-20070
> URL: https://issues.apache.org/jira/browse/AMBARI-20070
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.5.0
> Environment: Python 2.7
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Critical
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-20070_multiprocessing.patch, AMBARI-20070.patch
>
>
> Workaround for http://bugs.python.org/issue19809 that probably causes
> {{subprocess.Popen}} call to get stuck in:
> {noformat}
> File: "/usr/lib/python2.7/subprocess.py", line 679, in __init__
> errread, errwrite)
> File: "/usr/lib/python2.7/subprocess.py", line 1244, in _execute_child
> data = _eintr_retry_call(os.read, errpipe_read, 1048576)
> File: "/usr/lib/python2.7/subprocess.py", line 478, in _eintr_retry_call
> return func(*args)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20429) Warn users about pending requests while trying to enable Interactive Query immediately after disabling it
[ https://issues.apache.org/jira/browse/AMBARI-20429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-20429: Attachment: AMBARI-20429.v0.branch-2.5.patch > Warn users about pending requests while trying to enable Interactive Query > immediately after disabling it > - > > Key: AMBARI-20429 > URL: https://issues.apache.org/jira/browse/AMBARI-20429 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Attachments: AMBARI-20429.v0.branch-2.5.patch > > > There is no warning or protection for the user to avoid enabling of > Interactive Query immediately after disabling it. Showing a popup to warn the > user about a pending batch request would be helpful here. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20426) Hive Server interactive not removed from Hive summary page after HSI is disabled
[ https://issues.apache.org/jira/browse/AMBARI-20426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-20426: Status: Patch Available (was: In Progress) > Hive Server interactive not removed from Hive summary page after HSI is > disabled > > > Key: AMBARI-20426 > URL: https://issues.apache.org/jira/browse/AMBARI-20426 > Project: Ambari > Issue Type: Bug > Components: ambari-sever, ambari-web >Affects Versions: 2.5.0 >Reporter: Kishor Ramakrishnan >Assignee: Vivek Ratnavel Subramanian >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20426.v0.patch > > > Hive Server interactive not removed from Hive summary page even after HSI is > disabled. > Strange Fact : HSI is started without any error when did a restart all stale > components even though HSI is disabled -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20429) Warn users about pending requests while trying to enable Interactive Query immediately after disabling it
Vivek Ratnavel Subramanian created AMBARI-20429: --- Summary: Warn users about pending requests while trying to enable Interactive Query immediately after disabling it Key: AMBARI-20429 URL: https://issues.apache.org/jira/browse/AMBARI-20429 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian There is no warning or protection for the user to avoid enabling of Interactive Query immediately after disabling it. Showing a popup to warn the user about a pending batch request would be helpful here. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20402) Assign Slaves and Clients page displays incorrect configuration unless a change is made in Assign Masters page
[ https://issues.apache.org/jira/browse/AMBARI-20402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15922849#comment-15922849 ] Hudson commented on AMBARI-20402: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1248 (See [https://builds.apache.org/job/Ambari-branch-2.5/1248/]) AMBARI-20402: Assign Slaves and Clients page displays incorrect (sangeetar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=819d4f25339476622ffe73dd64acb85e24b52969]) * (edit) ambari-web/app/mixins/wizard/assign_master_components.js > Assign Slaves and Clients page displays incorrect configuration unless a > change is made in Assign Masters page > -- > > Key: AMBARI-20402 > URL: https://issues.apache.org/jira/browse/AMBARI-20402 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Fix For: 2.5.0 > > Attachments: AMBARI-20402.patch, > AssignSlavesAndClients_AfterChanges.jpg, > AssignSlavesAndClients_BeforeChanges.jpg > > > 1. On a multi-node cluster (for e.g. 5-node cluster), run the ambari install > wizard. > 2. Do not change defaults and navigate to Step 6 (Assign Slaves and Clients). > 3. The recommended configuration does not seem to be place the components > well. For e.g., DataNodes are recommended on all 5 nodes. (see > AssignSlavesAndClients_BeforeChanges.jpg). > 4. Navigate back to Step 5 (Assign Masters). Make a change. For e.g. move the > Atlas Metadata Server to a different host. Next, change it back to the > original host so that in effect nothing has changed. > 5. Now move to Step 6 again and see that the configuration has changed and > seems more in line with best practices although effectively nothing has > changed in the Assign Masters page. (see > AssignSlavesAndClients_AfterChanges.jpg) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20400) Yarn should not copy Tez and Slider tar ball if Tez and Sliders are not installed on the cluster
[ https://issues.apache.org/jira/browse/AMBARI-20400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-20400: --- Status: Patch Available (was: In Progress) > Yarn should not copy Tez and Slider tar ball if Tez and Sliders are not > installed on the cluster > > > Key: AMBARI-20400 > URL: https://issues.apache.org/jira/browse/AMBARI-20400 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-20400.patch > > > It's possible to install a cluster without Tez and Slider via blueprint. In > this case, Yarn historyserver start logic prints two warnings about unable to > copy tez and slider tar ball to HDFS. > Yarn history server should skip the copy hdfs tar ball logic for tez and > slider if they are not installed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20400) Yarn should not copy Tez and Slider tar ball if Tez and Sliders are not installed on the cluster
[ https://issues.apache.org/jira/browse/AMBARI-20400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-20400: --- Attachment: AMBARI-20400.patch > Yarn should not copy Tez and Slider tar ball if Tez and Sliders are not > installed on the cluster > > > Key: AMBARI-20400 > URL: https://issues.apache.org/jira/browse/AMBARI-20400 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-20400.patch > > > It's possible to install a cluster without Tez and Slider via blueprint. In > this case, Yarn historyserver start logic prints two warnings about unable to > copy tez and slider tar ball to HDFS. > Yarn history server should skip the copy hdfs tar ball logic for tez and > slider if they are not installed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20400) Yarn should not copy Tez and Slider tar ball if Tez and Sliders are not installed on the cluster
[ https://issues.apache.org/jira/browse/AMBARI-20400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-20400: --- Attachment: (was: AMBARI-20400.patch) > Yarn should not copy Tez and Slider tar ball if Tez and Sliders are not > installed on the cluster > > > Key: AMBARI-20400 > URL: https://issues.apache.org/jira/browse/AMBARI-20400 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > > It's possible to install a cluster without Tez and Slider via blueprint. In > this case, Yarn historyserver start logic prints two warnings about unable to > copy tez and slider tar ball to HDFS. > Yarn history server should skip the copy hdfs tar ball logic for tez and > slider if they are not installed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20400) Yarn should not copy Tez and Slider tar ball if Tez and Sliders are not installed on the cluster
[ https://issues.apache.org/jira/browse/AMBARI-20400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-20400: --- Status: In Progress (was: Patch Available) > Yarn should not copy Tez and Slider tar ball if Tez and Sliders are not > installed on the cluster > > > Key: AMBARI-20400 > URL: https://issues.apache.org/jira/browse/AMBARI-20400 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-20400.patch > > > It's possible to install a cluster without Tez and Slider via blueprint. In > this case, Yarn historyserver start logic prints two warnings about unable to > copy tez and slider tar ball to HDFS. > Yarn history server should skip the copy hdfs tar ball logic for tez and > slider if they are not installed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20407) When agent retries commands it needs to handle credential store processing correctly
[ https://issues.apache.org/jira/browse/AMBARI-20407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15922797#comment-15922797 ] Hudson commented on AMBARI-20407: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7023 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7023/]) AMBARI-20407. When agent retries commands it needs to handle credential (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=991c35b6e9c65b1f9953472bfb78a54cd556983a]) * (edit) ambari-agent/src/test/python/ambari_agent/TestActionQueue.py * (edit) ambari-agent/src/main/python/ambari_agent/CustomServiceOrchestrator.py * (edit) ambari-agent/src/main/python/ambari_agent/ActionQueue.py > When agent retries commands it needs to handle credential store processing > correctly > > > Key: AMBARI-20407 > URL: https://issues.apache.org/jira/browse/AMBARI-20407 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.5.0 >Reporter: Sumit Mohanty >Assignee: Sumit Mohanty >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20407.patch > > > Credential store handling has a one-way logic to move passwords to jceks > files and then removing the passwords from the configs. When agent does an > auto-retry of command execution then the initial assumption of relying on the > existence of the "password" properties no longer holds true. This incorrectly > disables credential store but as passwords are no longer available it results > in broken configurations. > The solution here is to avoid processing the password properties when command > is an implicit retry. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20407) When agent retries commands it needs to handle credential store processing correctly
[ https://issues.apache.org/jira/browse/AMBARI-20407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15922787#comment-15922787 ] Hudson commented on AMBARI-20407: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1247 (See [https://builds.apache.org/job/Ambari-branch-2.5/1247/]) AMBARI-20407. When agent retries commands it needs to handle credential (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f6d1816a57acff8a694552adb5aeedaf06d5b84c]) * (edit) ambari-agent/src/test/python/ambari_agent/TestActionQueue.py * (edit) ambari-agent/src/main/python/ambari_agent/CustomServiceOrchestrator.py * (edit) ambari-agent/src/main/python/ambari_agent/ActionQueue.py > When agent retries commands it needs to handle credential store processing > correctly > > > Key: AMBARI-20407 > URL: https://issues.apache.org/jira/browse/AMBARI-20407 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.5.0 >Reporter: Sumit Mohanty >Assignee: Sumit Mohanty >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20407.patch > > > Credential store handling has a one-way logic to move passwords to jceks > files and then removing the passwords from the configs. When agent does an > auto-retry of command execution then the initial assumption of relying on the > existence of the "password" properties no longer holds true. This incorrectly > disables credential store but as passwords are no longer available it results > in broken configurations. > The solution here is to avoid processing the password properties when command > is an implicit retry. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20426) Hive Server interactive not removed from Hive summary page after HSI is disabled
[ https://issues.apache.org/jira/browse/AMBARI-20426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-20426: Attachment: AMBARI-20426.v0.patch > Hive Server interactive not removed from Hive summary page after HSI is > disabled > > > Key: AMBARI-20426 > URL: https://issues.apache.org/jira/browse/AMBARI-20426 > Project: Ambari > Issue Type: Bug > Components: ambari-sever, ambari-web >Affects Versions: 2.5.0 >Reporter: Kishor Ramakrishnan >Assignee: Vivek Ratnavel Subramanian >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20426.v0.patch > > > Hive Server interactive not removed from Hive summary page even after HSI is > disabled. > Strange Fact : HSI is started without any error when did a restart all stale > components even though HSI is disabled -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-20426) Hive Server interactive not removed from Hive summary page after HSI is disabled
[ https://issues.apache.org/jira/browse/AMBARI-20426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian reassigned AMBARI-20426: --- Assignee: Vivek Ratnavel Subramanian > Hive Server interactive not removed from Hive summary page after HSI is > disabled > > > Key: AMBARI-20426 > URL: https://issues.apache.org/jira/browse/AMBARI-20426 > Project: Ambari > Issue Type: Bug > Components: ambari-sever, ambari-web >Affects Versions: 2.5.0 >Reporter: Kishor Ramakrishnan >Assignee: Vivek Ratnavel Subramanian >Priority: Critical > Fix For: 2.5.0 > > > Hive Server interactive not removed from Hive summary page even after HSI is > disabled. > Strange Fact : HSI is started without any error when did a restart all stale > components even though HSI is disabled -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20400) Yarn should not copy Tez and Slider tar ball if Tez and Sliders are not installed on the cluster
[
https://issues.apache.org/jira/browse/AMBARI-20400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15922741#comment-15922741
]
Hadoop QA commented on AMBARI-20400:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12857722/AMBARI-20400.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/11007//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11007//console
This message is automatically generated.
> Yarn should not copy Tez and Slider tar ball if Tez and Sliders are not
> installed on the cluster
>
>
> Key: AMBARI-20400
> URL: https://issues.apache.org/jira/browse/AMBARI-20400
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-20400.patch
>
>
> It's possible to install a cluster without Tez and Slider via blueprint. In
> this case, Yarn historyserver start logic prints two warnings about unable to
> copy tez and slider tar ball to HDFS.
> Yarn history server should skip the copy hdfs tar ball logic for tez and
> slider if they are not installed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20428) UI - bugs with styles
[ https://issues.apache.org/jira/browse/AMBARI-20428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-20428: -- Status: Patch Available (was: Open) > UI - bugs with styles > - > > Key: AMBARI-20428 > URL: https://issues.apache.org/jira/browse/AMBARI-20428 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-20428.patch > > > STR > Ambari 2.5.0.0 with a very long cluster name, add Hive, register bits for new > HDP version > 1. Look at the stacks and versions page with limited screen size > The cluster name will be cut-off > 2. The Hive view can display errors (such as when the Hive server is down), > but the icons for "x" or right arrow have a hand-icon on-hover, which makes > it seem like it's clickable but clicking does nothing. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20428) UI - bugs with styles
[ https://issues.apache.org/jira/browse/AMBARI-20428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15922724#comment-15922724 ] Aleksandr Kovalenko commented on AMBARI-20428: -- +1 for the patch > UI - bugs with styles > - > > Key: AMBARI-20428 > URL: https://issues.apache.org/jira/browse/AMBARI-20428 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-20428.patch > > > STR > Ambari 2.5.0.0 with a very long cluster name, add Hive, register bits for new > HDP version > 1. Look at the stacks and versions page with limited screen size > The cluster name will be cut-off > 2. The Hive view can display errors (such as when the Hive server is down), > but the icons for "x" or right arrow have a hand-icon on-hover, which makes > it seem like it's clickable but clicking does nothing. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20428) UI - bugs with styles
[ https://issues.apache.org/jira/browse/AMBARI-20428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-20428: -- Attachment: AMBARI-20428.patch > UI - bugs with styles > - > > Key: AMBARI-20428 > URL: https://issues.apache.org/jira/browse/AMBARI-20428 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-20428.patch > > > STR > Ambari 2.5.0.0 with a very long cluster name, add Hive, register bits for new > HDP version > 1. Look at the stacks and versions page with limited screen size > The cluster name will be cut-off > 2. The Hive view can display errors (such as when the Hive server is down), > but the icons for "x" or right arrow have a hand-icon on-hover, which makes > it seem like it's clickable but clicking does nothing. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20428) UI - bugs with styles
Andrii Tkach created AMBARI-20428: - Summary: UI - bugs with styles Key: AMBARI-20428 URL: https://issues.apache.org/jira/browse/AMBARI-20428 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 3.0.0 STR Ambari 2.5.0.0 with a very long cluster name, add Hive, register bits for new HDP version 1. Look at the stacks and versions page with limited screen size The cluster name will be cut-off 2. The Hive view can display errors (such as when the Hive server is down), but the icons for "x" or right arrow have a hand-icon on-hover, which makes it seem like it's clickable but clicking does nothing. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20412) Flume should support batch restart in hosts' page likeing datanode or region
[ https://issues.apache.org/jira/browse/AMBARI-20412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15922708#comment-15922708 ] Hudson commented on AMBARI-20412: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7022 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7022/]) AMBARI-20412. Flume should support batch restart in hosts' page likeing (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=eadbd1d4eaca52948748f559dd7f3d8a29430fef]) * (edit) ambari-server/src/main/resources/common-services/FLUME/1.4.0.2.0/metainfo.xml > Flume should support batch restart in hosts' page likeing datanode or region > > > Key: AMBARI-20412 > URL: https://issues.apache.org/jira/browse/AMBARI-20412 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk, 2.5.0, 2.4.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-20412.patch, screenshot-1.png, screenshot-2.png > > > In the host's page, Actions-Fileteed Hosts or All Hosts doesn't show flume. > flume is a slave component, so should can batch restart or stop or start. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-20263) Knox default topology config is wrong for Hbase service
[
https://issues.apache.org/jira/browse/AMBARI-20263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty reassigned AMBARI-20263:
--
Assignee: Sumit Gupta
> Knox default topology config is wrong for Hbase service
> ---
>
> Key: AMBARI-20263
> URL: https://issues.apache.org/jira/browse/AMBARI-20263
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Sumit Gupta
>Assignee: Sumit Gupta
> Fix For: 2.5.0
>
>
> Under the "Configs" tab for Knox, the Advanced Topology section has an error
> for the xml section for HBase. It looks like this:
> {code}
>
> WEBHBASE
> http://{{hbase_master_host}}:{{hbase_master_port}}
>
> {code}
> Knox talks to the REST server so the host and port should match that. The
> hbase_master_host variable may work okay but certainly the port will be wrong.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20263) Knox default topology config is wrong for Hbase service
[
https://issues.apache.org/jira/browse/AMBARI-20263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-20263:
---
Fix Version/s: 2.5.0
> Knox default topology config is wrong for Hbase service
> ---
>
> Key: AMBARI-20263
> URL: https://issues.apache.org/jira/browse/AMBARI-20263
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Sumit Gupta
> Fix For: 2.5.0
>
>
> Under the "Configs" tab for Knox, the Advanced Topology section has an error
> for the xml section for HBase. It looks like this:
> {code}
>
> WEBHBASE
> http://{{hbase_master_host}}:{{hbase_master_port}}
>
> {code}
> Knox talks to the REST server so the host and port should match that. The
> hbase_master_host variable may work okay but certainly the port will be wrong.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20425) Empty current and recommended values in "Recommended configs" panel during Add Service
[ https://issues.apache.org/jira/browse/AMBARI-20425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15922707#comment-15922707 ] Hudson commented on AMBARI-20425: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7022 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7022/]) AMBARI-20425 Empty current and recommended values in "Recommended (ababiichuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=592c1a90c66b621cada4c6f335196dce2121814a]) * (edit) ambari-web/app/messages.js * (edit) ambari-web/app/styles/application.less * (edit) ambari-web/app/views/common/configs/config_diff_view.js > Empty current and recommended values in "Recommended configs" panel during > Add Service > -- > > Key: AMBARI-20425 > URL: https://issues.apache.org/jira/browse/AMBARI-20425 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20425_branch-2.5.patch, AMBARI-20425_trunk.patch > > > In some cases current and recommended value cells in dependent configs table > are both empty and have got less than minimal cell height. > The behaviour should be as follows: > - When a new property is being added, show "Property undefined" in italics on > the left column with gray background (and the value in the right column). > - When an existing property is being removed, show "Property removed" in > italics on the right column with gray background (and the existing value in > the left column). > - When an existing property value changes, we just show the changes without > color coding except where the value itself is multi-line. Sometimes the > source/target value is empty. In this scenario we just show an empty box (as > opposed to gray background when a property is being added or removed as > described above). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20425) Empty current and recommended values in "Recommended configs" panel during Add Service
[ https://issues.apache.org/jira/browse/AMBARI-20425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15922701#comment-15922701 ] Hudson commented on AMBARI-20425: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1246 (See [https://builds.apache.org/job/Ambari-branch-2.5/1246/]) AMBARI-20425 Empty current and recommended values in "Recommended (ababiichuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=2fcef83f964cebacbc55133f54791228f177a67e]) * (edit) ambari-web/app/styles/application.less * (edit) ambari-web/app/views/common/configs/config_diff_view.js * (edit) ambari-web/app/messages.js > Empty current and recommended values in "Recommended configs" panel during > Add Service > -- > > Key: AMBARI-20425 > URL: https://issues.apache.org/jira/browse/AMBARI-20425 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20425_branch-2.5.patch, AMBARI-20425_trunk.patch > > > In some cases current and recommended value cells in dependent configs table > are both empty and have got less than minimal cell height. > The behaviour should be as follows: > - When a new property is being added, show "Property undefined" in italics on > the left column with gray background (and the value in the right column). > - When an existing property is being removed, show "Property removed" in > italics on the right column with gray background (and the existing value in > the left column). > - When an existing property value changes, we just show the changes without > color coding except where the value itself is multi-line. Sometimes the > source/target value is empty. In this scenario we just show an empty box (as > opposed to gray background when a property is being added or removed as > described above). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20409) Hue Migration View Giving error while migrating Pig Jobs in Postgres DB
[
https://issues.apache.org/jira/browse/AMBARI-20409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt updated AMBARI-20409:
-
Attachment: (was: AMBARI-20409.patch)
> Hue Migration View Giving error while migrating Pig Jobs in Postgres DB
> ---
>
> Key: AMBARI-20409
> URL: https://issues.apache.org/jira/browse/AMBARI-20409
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Reporter: Ishan Bhatt
>Assignee: Ishan Bhatt
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-20409.patch
>
>
> While Migrating pig Job
> Error displayed:-
> {code}
> SQL Exception: ERROR: column "ds_inprogress" is of type boolean but
> expression is of type integer Hint: You will need to rewrite or cast the
> expression. Position: 46
> {code}
> Log:-
> {code}
> 0 Mar 2017 12:00:38,477 INFO [Thread-64] PigJobMigrationUtility:139 - Loop
> No.1
> 10 Mar 2017 12:00:38,477 INFO [Thread-64] PigJobMigrationUtility:140 -
>
> 10 Mar 2017 12:00:38,477 INFO [Thread-64] PigJobMigrationUtility:141 - the
> title of script describeSchema
> 10 Mar 2017 12:00:38,501 ERROR [Thread-64] PigJobMigrationUtility:191 - sql
> exception in ambari database:
> org.postgresql.util.PSQLException: ERROR: column "ds_inprogress" is of type
> boolean but expression is of type integer
> Hint: You will need to rewrite or cast the expression.
> Position: 46
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2062)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1795)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:257)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:479)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:367)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.executeUpdate(AbstractJdbc2Statement.java:321)
> at
> com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeUpdate(NewProxyPreparedStatement.java:105)
> at
> org.apache.ambari.view.huetoambarimigration.migration.pig.pigjob.PigJobMigrationImplementation.insertRowPigJob(PigJobMigrationImplementation.java:204)
> at
> org.apache.ambari.view.huetoambarimigration.migration.pig.pigjob.PigJobMigrationUtility.pigJobMigration(PigJobMigrationUtility.java:155)
> at
> org.apache.ambari.view.huetoambarimigration.migration.pig.pigjob.PigJobStartJob.run(PigJobStartJob.java:59)
> 10 Mar 2017 12:00:38,503 INFO [Thread-64] PigJobMigrationUtility:195 - roll
> back done
> 10 Mar 2017 12:00:38,510 INFO [Thread-64] PigJobMigrationUtility:225 -
> --
> 10 Mar 2017 12:00:38,510 INFO [Thread-64] PigJobMigrationUtility:226 - pig
> Job Migration End
> 10 Mar 2017 12:00:38,510 INFO [Thread-64] PigJobMigrationUtility:227 -
> --
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20409) Hue Migration View Giving error while migrating Pig Jobs in Postgres DB
[
https://issues.apache.org/jira/browse/AMBARI-20409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt updated AMBARI-20409:
-
Status: Open (was: Patch Available)
> Hue Migration View Giving error while migrating Pig Jobs in Postgres DB
> ---
>
> Key: AMBARI-20409
> URL: https://issues.apache.org/jira/browse/AMBARI-20409
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Reporter: Ishan Bhatt
>Assignee: Ishan Bhatt
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-20409.patch
>
>
> While Migrating pig Job
> Error displayed:-
> {code}
> SQL Exception: ERROR: column "ds_inprogress" is of type boolean but
> expression is of type integer Hint: You will need to rewrite or cast the
> expression. Position: 46
> {code}
> Log:-
> {code}
> 0 Mar 2017 12:00:38,477 INFO [Thread-64] PigJobMigrationUtility:139 - Loop
> No.1
> 10 Mar 2017 12:00:38,477 INFO [Thread-64] PigJobMigrationUtility:140 -
>
> 10 Mar 2017 12:00:38,477 INFO [Thread-64] PigJobMigrationUtility:141 - the
> title of script describeSchema
> 10 Mar 2017 12:00:38,501 ERROR [Thread-64] PigJobMigrationUtility:191 - sql
> exception in ambari database:
> org.postgresql.util.PSQLException: ERROR: column "ds_inprogress" is of type
> boolean but expression is of type integer
> Hint: You will need to rewrite or cast the expression.
> Position: 46
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2062)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1795)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:257)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:479)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:367)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.executeUpdate(AbstractJdbc2Statement.java:321)
> at
> com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeUpdate(NewProxyPreparedStatement.java:105)
> at
> org.apache.ambari.view.huetoambarimigration.migration.pig.pigjob.PigJobMigrationImplementation.insertRowPigJob(PigJobMigrationImplementation.java:204)
> at
> org.apache.ambari.view.huetoambarimigration.migration.pig.pigjob.PigJobMigrationUtility.pigJobMigration(PigJobMigrationUtility.java:155)
> at
> org.apache.ambari.view.huetoambarimigration.migration.pig.pigjob.PigJobStartJob.run(PigJobStartJob.java:59)
> 10 Mar 2017 12:00:38,503 INFO [Thread-64] PigJobMigrationUtility:195 - roll
> back done
> 10 Mar 2017 12:00:38,510 INFO [Thread-64] PigJobMigrationUtility:225 -
> --
> 10 Mar 2017 12:00:38,510 INFO [Thread-64] PigJobMigrationUtility:226 - pig
> Job Migration End
> 10 Mar 2017 12:00:38,510 INFO [Thread-64] PigJobMigrationUtility:227 -
> --
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20409) Hue Migration View Giving error while migrating Pig Jobs in Postgres DB
[
https://issues.apache.org/jira/browse/AMBARI-20409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt updated AMBARI-20409:
-
Status: Patch Available (was: Open)
> Hue Migration View Giving error while migrating Pig Jobs in Postgres DB
> ---
>
> Key: AMBARI-20409
> URL: https://issues.apache.org/jira/browse/AMBARI-20409
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Reporter: Ishan Bhatt
>Assignee: Ishan Bhatt
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-20409.patch
>
>
> While Migrating pig Job
> Error displayed:-
> {code}
> SQL Exception: ERROR: column "ds_inprogress" is of type boolean but
> expression is of type integer Hint: You will need to rewrite or cast the
> expression. Position: 46
> {code}
> Log:-
> {code}
> 0 Mar 2017 12:00:38,477 INFO [Thread-64] PigJobMigrationUtility:139 - Loop
> No.1
> 10 Mar 2017 12:00:38,477 INFO [Thread-64] PigJobMigrationUtility:140 -
>
> 10 Mar 2017 12:00:38,477 INFO [Thread-64] PigJobMigrationUtility:141 - the
> title of script describeSchema
> 10 Mar 2017 12:00:38,501 ERROR [Thread-64] PigJobMigrationUtility:191 - sql
> exception in ambari database:
> org.postgresql.util.PSQLException: ERROR: column "ds_inprogress" is of type
> boolean but expression is of type integer
> Hint: You will need to rewrite or cast the expression.
> Position: 46
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2062)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1795)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:257)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:479)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:367)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.executeUpdate(AbstractJdbc2Statement.java:321)
> at
> com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeUpdate(NewProxyPreparedStatement.java:105)
> at
> org.apache.ambari.view.huetoambarimigration.migration.pig.pigjob.PigJobMigrationImplementation.insertRowPigJob(PigJobMigrationImplementation.java:204)
> at
> org.apache.ambari.view.huetoambarimigration.migration.pig.pigjob.PigJobMigrationUtility.pigJobMigration(PigJobMigrationUtility.java:155)
> at
> org.apache.ambari.view.huetoambarimigration.migration.pig.pigjob.PigJobStartJob.run(PigJobStartJob.java:59)
> 10 Mar 2017 12:00:38,503 INFO [Thread-64] PigJobMigrationUtility:195 - roll
> back done
> 10 Mar 2017 12:00:38,510 INFO [Thread-64] PigJobMigrationUtility:225 -
> --
> 10 Mar 2017 12:00:38,510 INFO [Thread-64] PigJobMigrationUtility:226 - pig
> Job Migration End
> 10 Mar 2017 12:00:38,510 INFO [Thread-64] PigJobMigrationUtility:227 -
> --
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20409) Hue Migration View Giving error while migrating Pig Jobs in Postgres DB
[
https://issues.apache.org/jira/browse/AMBARI-20409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt updated AMBARI-20409:
-
Attachment: AMBARI-20409.patch
> Hue Migration View Giving error while migrating Pig Jobs in Postgres DB
> ---
>
> Key: AMBARI-20409
> URL: https://issues.apache.org/jira/browse/AMBARI-20409
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Reporter: Ishan Bhatt
>Assignee: Ishan Bhatt
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-20409.patch
>
>
> While Migrating pig Job
> Error displayed:-
> {code}
> SQL Exception: ERROR: column "ds_inprogress" is of type boolean but
> expression is of type integer Hint: You will need to rewrite or cast the
> expression. Position: 46
> {code}
> Log:-
> {code}
> 0 Mar 2017 12:00:38,477 INFO [Thread-64] PigJobMigrationUtility:139 - Loop
> No.1
> 10 Mar 2017 12:00:38,477 INFO [Thread-64] PigJobMigrationUtility:140 -
>
> 10 Mar 2017 12:00:38,477 INFO [Thread-64] PigJobMigrationUtility:141 - the
> title of script describeSchema
> 10 Mar 2017 12:00:38,501 ERROR [Thread-64] PigJobMigrationUtility:191 - sql
> exception in ambari database:
> org.postgresql.util.PSQLException: ERROR: column "ds_inprogress" is of type
> boolean but expression is of type integer
> Hint: You will need to rewrite or cast the expression.
> Position: 46
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2062)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1795)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:257)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:479)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:367)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.executeUpdate(AbstractJdbc2Statement.java:321)
> at
> com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeUpdate(NewProxyPreparedStatement.java:105)
> at
> org.apache.ambari.view.huetoambarimigration.migration.pig.pigjob.PigJobMigrationImplementation.insertRowPigJob(PigJobMigrationImplementation.java:204)
> at
> org.apache.ambari.view.huetoambarimigration.migration.pig.pigjob.PigJobMigrationUtility.pigJobMigration(PigJobMigrationUtility.java:155)
> at
> org.apache.ambari.view.huetoambarimigration.migration.pig.pigjob.PigJobStartJob.run(PigJobStartJob.java:59)
> 10 Mar 2017 12:00:38,503 INFO [Thread-64] PigJobMigrationUtility:195 - roll
> back done
> 10 Mar 2017 12:00:38,510 INFO [Thread-64] PigJobMigrationUtility:225 -
> --
> 10 Mar 2017 12:00:38,510 INFO [Thread-64] PigJobMigrationUtility:226 - pig
> Job Migration End
> 10 Mar 2017 12:00:38,510 INFO [Thread-64] PigJobMigrationUtility:227 -
> --
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
