[jira] [Updated] (AMBARI-20368) HBase-client install fails when HDFS has not been installed
[ https://issues.apache.org/jira/browse/AMBARI-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-20368: - Description: the problem is that the installing of hbase-client is before hdfs-client, and the hdfs-client installed failed because the hadoop-conf-dir didn't exist. so there are two ways to solve this problem. the first method is that create the hadoop-conf-dir in hbase.py the second method is that setting the orders in role_command_order.json. I think that we can take the first method. Maybe there is no necessary to deal with hdfs-site about hadoop_conf_dir in hbase.py. was: the problem is that the installing of hbase-client is before hdfs-client, and the hdfs-client installed failed because the hadoop-conf-dir didn't exist. so there are two ways to solve this problem. the first method is that create the hadoop-conf-dir in hbase.py the second method is that setting the orders in role_command_order.json. I think that we can take the first method. > HBase-client install fails when HDFS has not been installed > --- > > Key: AMBARI-20368 > URL: https://issues.apache.org/jira/browse/AMBARI-20368 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0, 2.4.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: 2.5.0, 2.4.2, 2.5.1 > > Attachments: AMBARI-20368-1.patch, AMBARI-20368.patch, > screenshot-1.png, screenshot-2.png > > > the problem is that the installing of hbase-client is before hdfs-client, and > the hdfs-client installed failed because the hadoop-conf-dir didn't exist. > so there are two ways to solve this problem. > the first method is that create the hadoop-conf-dir in hbase.py > the second method is that setting the orders in role_command_order.json. > I think that we can take the first method. > Maybe > there is no necessary to deal with hdfs-site about hadoop_conf_dir in > hbase.py. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20368) HBase-client install fails when HDFS has not been installed
[ https://issues.apache.org/jira/browse/AMBARI-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-20368: - Fix Version/s: 2.5.1 2.5.0 > HBase-client install fails when HDFS has not been installed > --- > > Key: AMBARI-20368 > URL: https://issues.apache.org/jira/browse/AMBARI-20368 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0, 2.4.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: 2.5.0, 2.4.2, 2.5.1 > > Attachments: AMBARI-20368-1.patch, AMBARI-20368.patch, > screenshot-1.png, screenshot-2.png > > > the problem is that the installing of hbase-client is before hdfs-client, and > the hdfs-client installed failed because the hadoop-conf-dir didn't exist. > so there are two ways to solve this problem. > the first method is that create the hadoop-conf-dir in hbase.py > the second method is that setting the orders in role_command_order.json. > I think that we can take the first method. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20368) HBase-client install fails when HDFS has not been installed
[ https://issues.apache.org/jira/browse/AMBARI-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-20368: - Attachment: AMBARI-20368-1.patch there is no necessary to deal with hdfs-site in hbase.py > HBase-client install fails when HDFS has not been installed > --- > > Key: AMBARI-20368 > URL: https://issues.apache.org/jira/browse/AMBARI-20368 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0, 2.4.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: 2.4.2 > > Attachments: AMBARI-20368-1.patch, AMBARI-20368.patch, > screenshot-1.png, screenshot-2.png > > > the problem is that the installing of hbase-client is before hdfs-client, and > the hdfs-client installed failed because the hadoop-conf-dir didn't exist. > so there are two ways to solve this problem. > the first method is that create the hadoop-conf-dir in hbase.py > the second method is that setting the orders in role_command_order.json. > I think that we can take the first method. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20368) HBase-client install fails when HDFS has not been installed
[ https://issues.apache.org/jira/browse/AMBARI-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-20368: - Fix Version/s: (was: trunk) 2.4.2 > HBase-client install fails when HDFS has not been installed > --- > > Key: AMBARI-20368 > URL: https://issues.apache.org/jira/browse/AMBARI-20368 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0, 2.4.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: 2.4.2 > > Attachments: AMBARI-20368-1.patch, AMBARI-20368.patch, > screenshot-1.png, screenshot-2.png > > > the problem is that the installing of hbase-client is before hdfs-client, and > the hdfs-client installed failed because the hadoop-conf-dir didn't exist. > so there are two ways to solve this problem. > the first method is that create the hadoop-conf-dir in hbase.py > the second method is that setting the orders in role_command_order.json. > I think that we can take the first method. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20368) HBase-client install fails when HDFS has not been installed
[ https://issues.apache.org/jira/browse/AMBARI-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-20368: - Affects Version/s: (was: 2.5.0) (was: 2.4.1) (was: trunk) > HBase-client install fails when HDFS has not been installed > --- > > Key: AMBARI-20368 > URL: https://issues.apache.org/jira/browse/AMBARI-20368 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0, 2.4.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-20368.patch, screenshot-1.png, screenshot-2.png > > > the problem is that the installing of hbase-client is before hdfs-client, and > the hdfs-client installed failed because the hadoop-conf-dir didn't exist. > so there are two ways to solve this problem. > the first method is that create the hadoop-conf-dir in hbase.py > the second method is that setting the orders in role_command_order.json. > I think that we can take the first method. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (AMBARI-20368) HBase-client install fails when HDFS has not been installed
[ https://issues.apache.org/jira/browse/AMBARI-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu reopened AMBARI-20368: -- > HBase-client install fails when HDFS has not been installed > --- > > Key: AMBARI-20368 > URL: https://issues.apache.org/jira/browse/AMBARI-20368 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.4.0, 2.4.1, 2.5.0, 2.4.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-20368.patch, screenshot-1.png, screenshot-2.png > > > the problem is that the installing of hbase-client is before hdfs-client, and > the hdfs-client installed failed because the hadoop-conf-dir didn't exist. > so there are two ways to solve this problem. > the first method is that create the hadoop-conf-dir in hbase.py > the second method is that setting the orders in role_command_order.json. > I think that we can take the first method. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20368) HBase-client install fails when HDFS has not been installed
[ https://issues.apache.org/jira/browse/AMBARI-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-20368: - Status: Patch Available (was: Reopened) > HBase-client install fails when HDFS has not been installed > --- > > Key: AMBARI-20368 > URL: https://issues.apache.org/jira/browse/AMBARI-20368 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.4.0, 2.4.1, 2.5.0, 2.4.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-20368.patch, screenshot-1.png, screenshot-2.png > > > the problem is that the installing of hbase-client is before hdfs-client, and > the hdfs-client installed failed because the hadoop-conf-dir didn't exist. > so there are two ways to solve this problem. > the first method is that create the hadoop-conf-dir in hbase.py > the second method is that setting the orders in role_command_order.json. > I think that we can take the first method. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20443) No need to show `hive_ambari_database`
[
https://issues.apache.org/jira/browse/AMBARI-20443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-20443:
-
Attachment: AMBARI-20443.3.patch
> No need to show `hive_ambari_database`
> --
>
> Key: AMBARI-20443
> URL: https://issues.apache.org/jira/browse/AMBARI-20443
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0, 2.4.2
> Environment: Ambari 2.4.2 with Hive
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Fix For: trunk
>
> Attachments: AMBARI-20443.0.patch, AMBARI-20443.1.patch,
> AMBARI-20443.2.patch, AMBARI-20443.3.patch, screenshot-1.png
>
>
> In Advanced hive-env, there is a parameter named {{hive_ambari_database}}.
> Though I change the parameter, it looks like nothing has changed. I greped
> the entire ambari source code, the parameter is not referenced.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20368) HBase-client install fails when HDFS has not been installed
[ https://issues.apache.org/jira/browse/AMBARI-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-20368: - Status: Open (was: Patch Available) > HBase-client install fails when HDFS has not been installed > --- > > Key: AMBARI-20368 > URL: https://issues.apache.org/jira/browse/AMBARI-20368 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.4.0, 2.4.1, 2.5.0, 2.4.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-20368.patch, screenshot-1.png, screenshot-2.png > > > the problem is that the installing of hbase-client is before hdfs-client, and > the hdfs-client installed failed because the hadoop-conf-dir didn't exist. > so there are two ways to solve this problem. > the first method is that create the hadoop-conf-dir in hbase.py > the second method is that setting the orders in role_command_order.json. > I think that we can take the first method. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-20368) HBase-client install fails when HDFS has not been installed
[ https://issues.apache.org/jira/browse/AMBARI-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu resolved AMBARI-20368. -- Resolution: Implemented > HBase-client install fails when HDFS has not been installed > --- > > Key: AMBARI-20368 > URL: https://issues.apache.org/jira/browse/AMBARI-20368 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.4.0, 2.4.1, 2.5.0, 2.4.2 >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-20368.patch, screenshot-1.png, screenshot-2.png > > > the problem is that the installing of hbase-client is before hdfs-client, and > the hdfs-client installed failed because the hadoop-conf-dir didn't exist. > so there are two ways to solve this problem. > the first method is that create the hadoop-conf-dir in hbase.py > the second method is that setting the orders in role_command_order.json. > I think that we can take the first method. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20767) Add the Chinese translation files
[ https://issues.apache.org/jira/browse/AMBARI-20767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] PetterWang updated AMBARI-20767: Description: Need chinese translation files , include ambari-admin\src\main\resources\ui\admin-web\app\scripts\i18n.config.js and ambari-web\app\locales\zh\messages.js (was: Need to have chinese translation files , include ambari-admin\src\main\resources\ui\admin-web\app\scripts\i18n.config.js and ambari-web\app\locales\zh\messages.js) > Add the Chinese translation files > - > > Key: AMBARI-20767 > URL: https://issues.apache.org/jira/browse/AMBARI-20767 > Project: Ambari > Issue Type: New Feature > Components: ambari-admin, ambari-web >Affects Versions: 2.4.0 >Reporter: PetterWang > Fix For: 2.4.0 > > > Need chinese translation files , include > ambari-admin\src\main\resources\ui\admin-web\app\scripts\i18n.config.js and > ambari-web\app\locales\zh\messages.js -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20767) Add the Chinese translation files
PetterWang created AMBARI-20767: --- Summary: Add the Chinese translation files Key: AMBARI-20767 URL: https://issues.apache.org/jira/browse/AMBARI-20767 Project: Ambari Issue Type: New Feature Components: ambari-admin, ambari-web Affects Versions: 2.4.0 Reporter: PetterWang Fix For: 2.4.0 Need to have chinese translation files , include ambari-admin\src\main\resources\ui\admin-web\app\scripts\i18n.config.js and ambari-web\app\locales\zh\messages.js -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20738) Cannot add repo for additional OS to an existing HDP version
[ https://issues.apache.org/jira/browse/AMBARI-20738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-20738: -- Status: Patch Available (was: Open) > Cannot add repo for additional OS to an existing HDP version > > > Key: AMBARI-20738 > URL: https://issues.apache.org/jira/browse/AMBARI-20738 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.5.1 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.5.1 > > Attachments: AMBARI-20738.patch > > > When trying to add a repo for rhel7, to an already registered HDP version > that only has a repo for rhel6, I get a JS error when trying to click Save. > STR > Install a cluster with HDP 2.6 - that only has a rhel6 repo defined (remove > all others during install). > Post install try to add a rhel7 repo. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20738) Cannot add repo for additional OS to an existing HDP version
[ https://issues.apache.org/jira/browse/AMBARI-20738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-20738: -- Attachment: AMBARI-20738.patch > Cannot add repo for additional OS to an existing HDP version > > > Key: AMBARI-20738 > URL: https://issues.apache.org/jira/browse/AMBARI-20738 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.5.1 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.5.1 > > Attachments: AMBARI-20738.patch > > > When trying to add a repo for rhel7, to an already registered HDP version > that only has a repo for rhel6, I get a JS error when trying to click Save. > STR > Install a cluster with HDP 2.6 - that only has a rhel6 repo defined (remove > all others during install). > Post install try to add a rhel7 repo. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20754) get_value_from_jmx constantly prints exception message in retry mechanism, which brings bad user experience
[
https://issues.apache.org/jira/browse/AMBARI-20754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yuanbo Liu updated AMBARI-20754:
Status: Patch Available (was: Open)
> get_value_from_jmx constantly prints exception message in retry mechanism,
> which brings bad user experience
> ---
>
> Key: AMBARI-20754
> URL: https://issues.apache.org/jira/browse/AMBARI-20754
> Project: Ambari
> Issue Type: Bug
>Reporter: Yuanbo Liu
>Assignee: Yuanbo Liu
> Attachments: AMBARI-20754.001.patch
>
>
> {{get_value_from_jmx}} of {{jmx.py}} is used in getting NameNode HA state. As
> we know, if the cluster is large, it takes a long time for Namenode to leave
> safe mode when restarting Namenode, thus we use retry mechanism to invoke
> {{get_value_from_jmx}} in case of getting wrong state. The problem is that,
> {{get_value_from_jmx}} will print several exception message into std_error
> during retrying, it confuses users because there're error messages in
> std_error, while all the services restart successfully. Here are the error
> messages:
> {quote}
> 2017-04-12 15:12:56,633 - Getting jmx metrics from NN failed. URL:
> http://:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
> line 38, in get_value_from_jmx
>_, data, _ = get_user_call_output(cmd, user=run_user, quiet=False)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/get_user_call_output.py",
> line 61, in get_user_call_output
>raise ExecutionFailed(err_msg, code, files_output[0], files_output[1])
> ExecutionFailed: Execution of 'curl --negotiate -u : -s
> 'http://:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem'
> 1>/tmp/tmpWp05DF 2>/tmp/tmphm2dny' returned 7.
> 2017-04-12 15:12:58,562 - Getting jmx metrics from NN failed. URL:
> http://:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
> line 42, in get_value_from_jmx
>return data_dict["beans"][0][property]
> IndexError: list index out of range
> {quote}
> We should improve it.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20754) get_value_from_jmx constantly prints exception message in retry mechanism, which brings bad user experience
[
https://issues.apache.org/jira/browse/AMBARI-20754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yuanbo Liu updated AMBARI-20754:
Attachment: AMBARI-20754.001.patch
> get_value_from_jmx constantly prints exception message in retry mechanism,
> which brings bad user experience
> ---
>
> Key: AMBARI-20754
> URL: https://issues.apache.org/jira/browse/AMBARI-20754
> Project: Ambari
> Issue Type: Bug
>Reporter: Yuanbo Liu
>Assignee: Yuanbo Liu
> Attachments: AMBARI-20754.001.patch
>
>
> {{get_value_from_jmx}} of {{jmx.py}} is used in getting NameNode HA state. As
> we know, if the cluster is large, it takes a long time for Namenode to leave
> safe mode when restarting Namenode, thus we use retry mechanism to invoke
> {{get_value_from_jmx}} in case of getting wrong state. The problem is that,
> {{get_value_from_jmx}} will print several exception message into std_error
> during retrying, it confuses users because there're error messages in
> std_error, while all the services restart successfully. Here are the error
> messages:
> {quote}
> 2017-04-12 15:12:56,633 - Getting jmx metrics from NN failed. URL:
> http://:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
> line 38, in get_value_from_jmx
>_, data, _ = get_user_call_output(cmd, user=run_user, quiet=False)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/get_user_call_output.py",
> line 61, in get_user_call_output
>raise ExecutionFailed(err_msg, code, files_output[0], files_output[1])
> ExecutionFailed: Execution of 'curl --negotiate -u : -s
> 'http://:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem'
> 1>/tmp/tmpWp05DF 2>/tmp/tmphm2dny' returned 7.
> 2017-04-12 15:12:58,562 - Getting jmx metrics from NN failed. URL:
> http://:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
> line 42, in get_value_from_jmx
>return data_dict["beans"][0][property]
> IndexError: list index out of range
> {quote}
> We should improve it.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20766) Log Feeder fill cluster name if it is not set
[ https://issues.apache.org/jira/browse/AMBARI-20766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-20766: Status: Patch Available (was: In Progress) > Log Feeder fill cluster name if it is not set > - > > Key: AMBARI-20766 > URL: https://issues.apache.org/jira/browse/AMBARI-20766 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.5.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.5.1 > > Attachments: AMBARI-20766.patch > > > If for some reason there is no cluster set for a log entry, set it to the > actual cluster. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20766) Log Feeder fill cluster name if it is not set
[ https://issues.apache.org/jira/browse/AMBARI-20766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-20766: Attachment: AMBARI-20766.patch > Log Feeder fill cluster name if it is not set > - > > Key: AMBARI-20766 > URL: https://issues.apache.org/jira/browse/AMBARI-20766 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.5.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.5.1 > > Attachments: AMBARI-20766.patch > > > If for some reason there is no cluster set for a log entry, set it to the > actual cluster. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20766) Log Feeder fill cluster name if it is not set
Miklos Gergely created AMBARI-20766: --- Summary: Log Feeder fill cluster name if it is not set Key: AMBARI-20766 URL: https://issues.apache.org/jira/browse/AMBARI-20766 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 2.5.0 Reporter: Miklos Gergely Assignee: Miklos Gergely Fix For: 2.5.1 If for some reason there is no cluster set for a log entry, set it to the actual cluster. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20762) Add more database options for beacon in stack advisor
[ https://issues.apache.org/jira/browse/AMBARI-20762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15968452#comment-15968452 ] Hudson commented on AMBARI-20762: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7298 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7298/]) AMBARI-20762. Add more database options for BEACON in stack (xiwang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c57300a359bfdb3225e2660a661733fc58daac2c]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/stack_advisor.py > Add more database options for beacon in stack advisor > - > > Key: AMBARI-20762 > URL: https://issues.apache.org/jira/browse/AMBARI-20762 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 2.5.1 > > Attachments: AMBARI-20762.patch, AMBARI-20762.patch > > > In the configs/Database page of beacon, on selecting each database type, the > JDBC Driver Class and URL should be updated automatically. > This part should be done in stack advisor. > (Beacon supports three db types : New derby, existed MySQL and existed Oracle > ) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20762) Add more database options for beacon in stack advisor
[ https://issues.apache.org/jira/browse/AMBARI-20762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15968436#comment-15968436 ] Hudson commented on AMBARI-20762: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1407 (See [https://builds.apache.org/job/Ambari-branch-2.5/1407/]) AMBARI-20762. Add more database options for BEACON in stack (xiwang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=777eacd2be2c9477405ae53bd5faaa8b53b88aec]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/stack_advisor.py > Add more database options for beacon in stack advisor > - > > Key: AMBARI-20762 > URL: https://issues.apache.org/jira/browse/AMBARI-20762 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 2.5.1 > > Attachments: AMBARI-20762.patch, AMBARI-20762.patch > > > In the configs/Database page of beacon, on selecting each database type, the > JDBC Driver Class and URL should be updated automatically. > This part should be done in stack advisor. > (Beacon supports three db types : New derby, existed MySQL and existed Oracle > ) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20763) Update YARN's ATS configs 'apptimelineserver_heapsize' and 'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6.
[
https://issues.apache.org/jira/browse/AMBARI-20763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15968435#comment-15968435
]
Hudson commented on AMBARI-20763:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1407 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1407/])
AMBARI-20763. Update YARN's ATS configs 'apptimelineserver_heapsize' and
(sshridhar:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b313614c55610b4d4434a099ec276520f3f7da4d])
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.6/services/YARN/configuration/yarn-env.xml
* (edit) ambari-server/src/test/python/stacks/2.5/common/test_stack_advisor.py
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.6/services/stack_advisor.py
* (edit) ambari-server/src/test/python/stacks/2.6/common/test_stack_advisor.py
> Update YARN's ATS configs 'apptimelineserver_heapsize' and
> 'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6.
> -
>
> Key: AMBARI-20763
> URL: https://issues.apache.org/jira/browse/AMBARI-20763
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: trunk, 2.5.1
>
> Attachments: AMBARI-20763-branch2.5.patch, AMBARI-20763-trunk.patch
>
>
> In 2.6, update the following YARN configs related to ATS:
> - {{'yarn.timeline-service.entity-group-fs-store.app-cache-size'}} on cluster
> initialization/creation based on host memory.
> - {{'apptimelineserver_heapsize'}} on : (1). cluster initialization/creation
> and/or (2). when a change is detected in value for
> {{'yarn.timeline-service.entity-group-fs-store.app-cache-size'}}, using
> formula:
>{code}
> ats_heapsize = long(min(math.floor(host_mem/2),
> long(yarn_timeline_app_cache_size) * 500 + 3072)) // Value in MB
>{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20763) Update YARN's ATS configs 'apptimelineserver_heapsize' and 'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6.
[
https://issues.apache.org/jira/browse/AMBARI-20763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15968403#comment-15968403
]
Hudson commented on AMBARI-20763:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7297 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7297/])
AMBARI-20763. Update YARN's ATS configs 'apptimelineserver_heapsize' and
(sshridhar:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=38f84bf12d04981017bbcfc3d44c243f062ed055])
* (edit)
ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/service_advisor.py
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.6/services/stack_advisor.py
* (edit) ambari-server/src/test/python/stacks/2.5/common/test_stack_advisor.py
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.6/services/YARN/configuration/yarn-env.xml
* (edit) ambari-server/src/test/python/stacks/2.6/common/test_stack_advisor.py
> Update YARN's ATS configs 'apptimelineserver_heapsize' and
> 'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6.
> -
>
> Key: AMBARI-20763
> URL: https://issues.apache.org/jira/browse/AMBARI-20763
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: trunk, 2.5.1
>
> Attachments: AMBARI-20763-branch2.5.patch, AMBARI-20763-trunk.patch
>
>
> In 2.6, update the following YARN configs related to ATS:
> - {{'yarn.timeline-service.entity-group-fs-store.app-cache-size'}} on cluster
> initialization/creation based on host memory.
> - {{'apptimelineserver_heapsize'}} on : (1). cluster initialization/creation
> and/or (2). when a change is detected in value for
> {{'yarn.timeline-service.entity-group-fs-store.app-cache-size'}}, using
> formula:
>{code}
> ats_heapsize = long(min(math.floor(host_mem/2),
> long(yarn_timeline_app_cache_size) * 500 + 3072)) // Value in MB
>{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20509) hbase master port or hbase rest port is not populated in advance-topology.xml
[
https://issues.apache.org/jira/browse/AMBARI-20509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15968397#comment-15968397
]
Hudson commented on AMBARI-20509:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1406 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1406/])
Revert "AMBARI-20509. Incorrect webhbase host and port for Knox Topology
(smohanty:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e4db0c2dc26a8f8ff887262fb334649db73ebefc])
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.6/services/KNOX/configuration/topology.xml
> hbase master port or hbase rest port is not populated in advance-topology.xml
> -
>
> Key: AMBARI-20509
> URL: https://issues.apache.org/jira/browse/AMBARI-20509
> Project: Ambari
> Issue Type: Bug
>Reporter: Sandeep More
>Assignee: Sandeep More
> Fix For: trunk, 2.5.1
>
> Attachments: AMBARI-20509.001.patch, AMBARI-20509.002.patch
>
>
> hbase master port or hbase rest port is not populated in
> advance-topology.xml, port is empty, that creates invalid webhbase url in
> default topology.
> {code}
>
> WEBHBASE
> http://myhost:
>
> {code}
> this is the topology from ambari:
> {code}
>
> WEBHBASE
> http://{{hbase_master_host}}:{{hbase_master_port}}
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20762) Add more database options for beacon in stack advisor
[ https://issues.apache.org/jira/browse/AMBARI-20762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-20762: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.5 > Add more database options for beacon in stack advisor > - > > Key: AMBARI-20762 > URL: https://issues.apache.org/jira/browse/AMBARI-20762 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 2.5.1 > > Attachments: AMBARI-20762.patch, AMBARI-20762.patch > > > In the configs/Database page of beacon, on selecting each database type, the > JDBC Driver Class and URL should be updated automatically. > This part should be done in stack advisor. > (Beacon supports three db types : New derby, existed MySQL and existed Oracle > ) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20763) Update YARN's ATS configs 'apptimelineserver_heapsize' and 'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6.
[
https://issues.apache.org/jira/browse/AMBARI-20763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-20763:
-
Attachment: AMBARI-20763-branch2.5.patch
> Update YARN's ATS configs 'apptimelineserver_heapsize' and
> 'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6.
> -
>
> Key: AMBARI-20763
> URL: https://issues.apache.org/jira/browse/AMBARI-20763
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: trunk, 2.5.1
>
> Attachments: AMBARI-20763-branch2.5.patch, AMBARI-20763-trunk.patch
>
>
> In 2.6, update the following YARN configs related to ATS:
> - {{'yarn.timeline-service.entity-group-fs-store.app-cache-size'}} on cluster
> initialization/creation based on host memory.
> - {{'apptimelineserver_heapsize'}} on : (1). cluster initialization/creation
> and/or (2). when a change is detected in value for
> {{'yarn.timeline-service.entity-group-fs-store.app-cache-size'}}, using
> formula:
>{code}
> ats_heapsize = long(min(math.floor(host_mem/2),
> long(yarn_timeline_app_cache_size) * 500 + 3072)) // Value in MB
>{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20763) Update YARN's ATS configs 'apptimelineserver_heapsize' and 'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6.
[
https://issues.apache.org/jira/browse/AMBARI-20763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15968365#comment-15968365
]
Swapan Shridhar commented on AMBARI-20763:
--
commits:
trunk
{code}
commit 38f84bf12d04981017bbcfc3d44c243f062ed055
Author: Swapan Shridhar
Date: Thu Apr 13 15:57:10 2017 -0700
AMBARI-20763. Update YARN's ATS configs 'apptimelineserver_heapsize' and
'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6.
{code}
branch-2.5:
{code}
commit b313614c55610b4d4434a099ec276520f3f7da4d
Author: Swapan Shridhar
Date: Thu Apr 13 16:00:38 2017 -0700
AMBARI-20763. Update YARN's ATS configs 'apptimelineserver_heapsize' and
'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6.
{code}
> Update YARN's ATS configs 'apptimelineserver_heapsize' and
> 'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6.
> -
>
> Key: AMBARI-20763
> URL: https://issues.apache.org/jira/browse/AMBARI-20763
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: trunk, 2.5.1
>
> Attachments: AMBARI-20763-branch2.5.patch, AMBARI-20763-trunk.patch
>
>
> In 2.6, update the following YARN configs related to ATS:
> - {{'yarn.timeline-service.entity-group-fs-store.app-cache-size'}} on cluster
> initialization/creation based on host memory.
> - {{'apptimelineserver_heapsize'}} on : (1). cluster initialization/creation
> and/or (2). when a change is detected in value for
> {{'yarn.timeline-service.entity-group-fs-store.app-cache-size'}}, using
> formula:
>{code}
> ats_heapsize = long(min(math.floor(host_mem/2),
> long(yarn_timeline_app_cache_size) * 500 + 3072)) // Value in MB
>{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20763) Update YARN's ATS configs 'apptimelineserver_heapsize' and 'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6.
[
https://issues.apache.org/jira/browse/AMBARI-20763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-20763:
-
Status: Patch Available (was: Open)
> Update YARN's ATS configs 'apptimelineserver_heapsize' and
> 'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6.
> -
>
> Key: AMBARI-20763
> URL: https://issues.apache.org/jira/browse/AMBARI-20763
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: trunk, 2.5.1
>
> Attachments: AMBARI-20763-branch2.5.patch, AMBARI-20763-trunk.patch
>
>
> In 2.6, update the following YARN configs related to ATS:
> - {{'yarn.timeline-service.entity-group-fs-store.app-cache-size'}} on cluster
> initialization/creation based on host memory.
> - {{'apptimelineserver_heapsize'}} on : (1). cluster initialization/creation
> and/or (2). when a change is detected in value for
> {{'yarn.timeline-service.entity-group-fs-store.app-cache-size'}}, using
> formula:
>{code}
> ats_heapsize = long(min(math.floor(host_mem/2),
> long(yarn_timeline_app_cache_size) * 500 + 3072)) // Value in MB
>{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20763) Update YARN's ATS configs 'apptimelineserver_heapsize' and 'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6.
[
https://issues.apache.org/jira/browse/AMBARI-20763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-20763:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Update YARN's ATS configs 'apptimelineserver_heapsize' and
> 'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6.
> -
>
> Key: AMBARI-20763
> URL: https://issues.apache.org/jira/browse/AMBARI-20763
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: trunk, 2.5.1
>
> Attachments: AMBARI-20763-branch2.5.patch, AMBARI-20763-trunk.patch
>
>
> In 2.6, update the following YARN configs related to ATS:
> - {{'yarn.timeline-service.entity-group-fs-store.app-cache-size'}} on cluster
> initialization/creation based on host memory.
> - {{'apptimelineserver_heapsize'}} on : (1). cluster initialization/creation
> and/or (2). when a change is detected in value for
> {{'yarn.timeline-service.entity-group-fs-store.app-cache-size'}}, using
> formula:
>{code}
> ats_heapsize = long(min(math.floor(host_mem/2),
> long(yarn_timeline_app_cache_size) * 500 + 3072)) // Value in MB
>{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20762) Add more database options for beacon in stack advisor
[ https://issues.apache.org/jira/browse/AMBARI-20762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-20762: - Attachment: (was: AMBARI-20762.patch) > Add more database options for beacon in stack advisor > - > > Key: AMBARI-20762 > URL: https://issues.apache.org/jira/browse/AMBARI-20762 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 2.5.1 > > Attachments: AMBARI-20762.patch, AMBARI-20762.patch > > > In the configs/Database page of beacon, on selecting each database type, the > JDBC Driver Class and URL should be updated automatically. > This part should be done in stack advisor. > (Beacon supports three db types : New derby, existed MySQL and existed Oracle > ) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20762) Add more database options for beacon in stack advisor
[ https://issues.apache.org/jira/browse/AMBARI-20762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-20762: - Attachment: AMBARI-20762.patch > Add more database options for beacon in stack advisor > - > > Key: AMBARI-20762 > URL: https://issues.apache.org/jira/browse/AMBARI-20762 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 2.5.1 > > Attachments: AMBARI-20762.patch, AMBARI-20762.patch, > AMBARI-20762.patch > > > In the configs/Database page of beacon, on selecting each database type, the > JDBC Driver Class and URL should be updated automatically. > This part should be done in stack advisor. > (Beacon supports three db types : New derby, existed MySQL and existed Oracle > ) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20763) Update YARN's ATS configs 'apptimelineserver_heapsize' and 'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6.
[
https://issues.apache.org/jira/browse/AMBARI-20763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-20763:
-
Attachment: AMBARI-20763-trunk.patch
> Update YARN's ATS configs 'apptimelineserver_heapsize' and
> 'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6.
> -
>
> Key: AMBARI-20763
> URL: https://issues.apache.org/jira/browse/AMBARI-20763
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: trunk, 2.5.1
>
> Attachments: AMBARI-20763-trunk.patch
>
>
> In 2.6, update the following YARN configs related to ATS:
> - {{'yarn.timeline-service.entity-group-fs-store.app-cache-size'}} on cluster
> initialization/creation based on host memory.
> - {{'apptimelineserver_heapsize'}} on : (1). cluster initialization/creation
> and/or (2). when a change is detected in value for
> {{'yarn.timeline-service.entity-group-fs-store.app-cache-size'}}, using
> formula:
>{code}
> ats_heapsize = long(min(math.floor(host_mem/2),
> long(yarn_timeline_app_cache_size) * 500 + 3072)) // Value in MB
>{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20650) Remove Server attribute from the HTTP response headers
[ https://issues.apache.org/jira/browse/AMBARI-20650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15968354#comment-15968354 ] Hudson commented on AMBARI-20650: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7296 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7296/]) AMBARI-20650: Remove Server attribute from the HTTP response headers (sangeetar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f894e486a6f8eab31aec5add517a35ec9a11b655]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java > Remove Server attribute from the HTTP response headers > -- > > Key: AMBARI-20650 > URL: https://issues.apache.org/jira/browse/AMBARI-20650 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Fix For: trunk, 2.5.1 > > Attachments: AMBARI-20650.patch > > > Currently the HTTP response header contains the Jetty version. > Server:Jetty(8.1.19.v20160209) > To follow best security practices, it would be good to avoid including this > information in the response headers. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20763) Update YARN's ATS configs 'apptimelineserver_heapsize' and 'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6.
[
https://issues.apache.org/jira/browse/AMBARI-20763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-20763:
-
Attachment: (was: AMBARI-20763-trunk.patch)
> Update YARN's ATS configs 'apptimelineserver_heapsize' and
> 'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6.
> -
>
> Key: AMBARI-20763
> URL: https://issues.apache.org/jira/browse/AMBARI-20763
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: trunk, 2.5.1
>
> Attachments: AMBARI-20763-trunk.patch
>
>
> In 2.6, update the following YARN configs related to ATS:
> - {{'yarn.timeline-service.entity-group-fs-store.app-cache-size'}} on cluster
> initialization/creation based on host memory.
> - {{'apptimelineserver_heapsize'}} on : (1). cluster initialization/creation
> and/or (2). when a change is detected in value for
> {{'yarn.timeline-service.entity-group-fs-store.app-cache-size'}}, using
> formula:
>{code}
> ats_heapsize = long(min(math.floor(host_mem/2),
> long(yarn_timeline_app_cache_size) * 500 + 3072)) // Value in MB
>{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20763) Update YARN's ATS configs 'apptimelineserver_heapsize' and 'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6.
[
https://issues.apache.org/jira/browse/AMBARI-20763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-20763:
-
Attachment: (was: AMBARI-20763-branch2.5.patch)
> Update YARN's ATS configs 'apptimelineserver_heapsize' and
> 'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6.
> -
>
> Key: AMBARI-20763
> URL: https://issues.apache.org/jira/browse/AMBARI-20763
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: trunk, 2.5.1
>
> Attachments: AMBARI-20763-trunk.patch
>
>
> In 2.6, update the following YARN configs related to ATS:
> - {{'yarn.timeline-service.entity-group-fs-store.app-cache-size'}} on cluster
> initialization/creation based on host memory.
> - {{'apptimelineserver_heapsize'}} on : (1). cluster initialization/creation
> and/or (2). when a change is detected in value for
> {{'yarn.timeline-service.entity-group-fs-store.app-cache-size'}}, using
> formula:
>{code}
> ats_heapsize = long(min(math.floor(host_mem/2),
> long(yarn_timeline_app_cache_size) * 500 + 3072)) // Value in MB
>{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20762) Add more database options for beacon in stack advisor
[ https://issues.apache.org/jira/browse/AMBARI-20762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-20762: - Attachment: AMBARI-20762.patch > Add more database options for beacon in stack advisor > - > > Key: AMBARI-20762 > URL: https://issues.apache.org/jira/browse/AMBARI-20762 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 2.5.1 > > Attachments: AMBARI-20762.patch, AMBARI-20762.patch > > > In the configs/Database page of beacon, on selecting each database type, the > JDBC Driver Class and URL should be updated automatically. > This part should be done in stack advisor. > (Beacon supports three db types : New derby, existed MySQL and existed Oracle > ) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20763) Update YARN's ATS configs 'apptimelineserver_heapsize' and 'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6.
[
https://issues.apache.org/jira/browse/AMBARI-20763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-20763:
-
Attachment: AMBARI-20763-trunk.patch
> Update YARN's ATS configs 'apptimelineserver_heapsize' and
> 'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6.
> -
>
> Key: AMBARI-20763
> URL: https://issues.apache.org/jira/browse/AMBARI-20763
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: trunk, 2.5.1
>
> Attachments: AMBARI-20763-branch2.5.patch, AMBARI-20763-trunk.patch
>
>
> In 2.6, update the following YARN configs related to ATS:
> - {{'yarn.timeline-service.entity-group-fs-store.app-cache-size'}} on cluster
> initialization/creation based on host memory.
> - {{'apptimelineserver_heapsize'}} on : (1). cluster initialization/creation
> and/or (2). when a change is detected in value for
> {{'yarn.timeline-service.entity-group-fs-store.app-cache-size'}}, using
> formula:
>{code}
> ats_heapsize = long(min(math.floor(host_mem/2),
> long(yarn_timeline_app_cache_size) * 500 + 3072)) // Value in MB
>{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20762) Add more database options for beacon in stack advisor
[ https://issues.apache.org/jira/browse/AMBARI-20762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-20762: - Attachment: (was: AMBARI-20762.patch) > Add more database options for beacon in stack advisor > - > > Key: AMBARI-20762 > URL: https://issues.apache.org/jira/browse/AMBARI-20762 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 2.5.1 > > Attachments: AMBARI-20762.patch, AMBARI-20762.patch > > > In the configs/Database page of beacon, on selecting each database type, the > JDBC Driver Class and URL should be updated automatically. > This part should be done in stack advisor. > (Beacon supports three db types : New derby, existed MySQL and existed Oracle > ) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20762) Add more database options for beacon in stack advisor
[ https://issues.apache.org/jira/browse/AMBARI-20762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-20762: - Attachment: AMBARI-20762.patch > Add more database options for beacon in stack advisor > - > > Key: AMBARI-20762 > URL: https://issues.apache.org/jira/browse/AMBARI-20762 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 2.5.1 > > Attachments: AMBARI-20762.patch, AMBARI-20762.patch > > > In the configs/Database page of beacon, on selecting each database type, the > JDBC Driver Class and URL should be updated automatically. > This part should be done in stack advisor. > (Beacon supports three db types : New derby, existed MySQL and existed Oracle > ) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20763) Update YARN's ATS configs 'apptimelineserver_heapsize' and 'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6.
[
https://issues.apache.org/jira/browse/AMBARI-20763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-20763:
-
Attachment: AMBARI-20763-branch2.5.patch
> Update YARN's ATS configs 'apptimelineserver_heapsize' and
> 'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6.
> -
>
> Key: AMBARI-20763
> URL: https://issues.apache.org/jira/browse/AMBARI-20763
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: trunk, 2.5.1
>
> Attachments: AMBARI-20763-branch2.5.patch
>
>
> In 2.6, update the following YARN configs related to ATS:
> - {{'yarn.timeline-service.entity-group-fs-store.app-cache-size'}} on cluster
> initialization/creation based on host memory.
> - {{'apptimelineserver_heapsize'}} on : (1). cluster initialization/creation
> and/or (2). when a change is detected in value for
> {{'yarn.timeline-service.entity-group-fs-store.app-cache-size'}}, using
> formula:
>{code}
> ats_heapsize = long(min(math.floor(host_mem/2),
> long(yarn_timeline_app_cache_size) * 500 + 3072)) // Value in MB
>{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (AMBARI-20764) Add memory settings to Kafka
[ https://issues.apache.org/jira/browse/AMBARI-20764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham reassigned AMBARI-20764: --- Assignee: Bharat Viswanadham > Add memory settings to Kafka > > > Key: AMBARI-20764 > URL: https://issues.apache.org/jira/browse/AMBARI-20764 > Project: Ambari > Issue Type: Bug >Reporter: Bharat Viswanadham >Assignee: Bharat Viswanadham > > Added min and max memory settings for Kafka -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20764) Add memory settings to Kafka
Bharat Viswanadham created AMBARI-20764: --- Summary: Add memory settings to Kafka Key: AMBARI-20764 URL: https://issues.apache.org/jira/browse/AMBARI-20764 Project: Ambari Issue Type: Bug Reporter: Bharat Viswanadham Added min and max memory settings for Kafka -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20763) Update YARN's ATS configs 'apptimelineserver_heapsize' and 'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6.
[
https://issues.apache.org/jira/browse/AMBARI-20763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-20763:
-
Description:
In 2.6, update the following YARN configs related to ATS:
- {{'yarn.timeline-service.entity-group-fs-store.app-cache-size'}} on cluster
initialization/creation based on host memory.
- {{'apptimelineserver_heapsize'}} on : (1). cluster initialization/creation
and/or (2). when a change is detected in value for
{{'yarn.timeline-service.entity-group-fs-store.app-cache-size'}}, using formula:
{code}
ats_heapsize = long(min(math.floor(host_mem/2),
long(yarn_timeline_app_cache_size) * 500 + 3072)) // Value in MB
{code}
was:
In 2.6, update the following YARN configs related to ATS:
- {{'yarn.timeline-service.entity-group-fs-store.app-cache-size'}} on cluster
initialization/creation based on host memory.
- {{'apptimelineserver_heapsize'}} on : (1). cluster initialization/creation
and/or (2). when a change is detected in value for
{{'yarn.timeline-service.entity-group-fs-store.app-cache-size'}}, using formula:
{code}
ats_heapsize = long(min(math.floor(host_mem/2),
long(yarn_timeline_app_cache_size) * 500 + 3072)) // Value in MB
{code}
> Update YARN's ATS configs 'apptimelineserver_heapsize' and
> 'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6.
> -
>
> Key: AMBARI-20763
> URL: https://issues.apache.org/jira/browse/AMBARI-20763
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: trunk, 2.5.1
>
>
> In 2.6, update the following YARN configs related to ATS:
> - {{'yarn.timeline-service.entity-group-fs-store.app-cache-size'}} on cluster
> initialization/creation based on host memory.
> - {{'apptimelineserver_heapsize'}} on : (1). cluster initialization/creation
> and/or (2). when a change is detected in value for
> {{'yarn.timeline-service.entity-group-fs-store.app-cache-size'}}, using
> formula:
>{code}
> ats_heapsize = long(min(math.floor(host_mem/2),
> long(yarn_timeline_app_cache_size) * 500 + 3072)) // Value in MB
>{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20763) Update YARN's ATS configs 'apptimelineserver_heapsize' and 'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6.
[
https://issues.apache.org/jira/browse/AMBARI-20763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-20763:
-
Description:
In 2.6, update the following YARN configs related to ATS:
- {{'yarn.timeline-service.entity-group-fs-store.app-cache-size'}} on cluster
initialization/creation based on host memory.
- {{'apptimelineserver_heapsize'}} on : (1). cluster initialization/creation
and/or (2). when a change is detected in value for
{{'yarn.timeline-service.entity-group-fs-store.app-cache-size'}}, using formula:
{code}
ats_heapsize = long(min(math.floor(host_mem/2),
long(yarn_timeline_app_cache_size) * 500 + 3072)) // Value in MB
{code}
> Update YARN's ATS configs 'apptimelineserver_heapsize' and
> 'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6.
> -
>
> Key: AMBARI-20763
> URL: https://issues.apache.org/jira/browse/AMBARI-20763
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: trunk, 2.5.1
>
>
> In 2.6, update the following YARN configs related to ATS:
> - {{'yarn.timeline-service.entity-group-fs-store.app-cache-size'}} on cluster
> initialization/creation based on host memory.
> - {{'apptimelineserver_heapsize'}} on : (1). cluster initialization/creation
> and/or (2). when a change is detected in value for
> {{'yarn.timeline-service.entity-group-fs-store.app-cache-size'}}, using
> formula:
>{code}
> ats_heapsize = long(min(math.floor(host_mem/2),
> long(yarn_timeline_app_cache_size) * 500 + 3072)) // Value in MB
>{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20763) Update YARN's ATS configs 'apptimelineserver_heapsize' and 'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6.
[ https://issues.apache.org/jira/browse/AMBARI-20763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-20763: - Summary: Update YARN's ATS configs 'apptimelineserver_heapsize' and 'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6. (was: Update YARN configs 'apptimelineserver_heapsize' and 'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6.) > Update YARN's ATS configs 'apptimelineserver_heapsize' and > 'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6. > - > > Key: AMBARI-20763 > URL: https://issues.apache.org/jira/browse/AMBARI-20763 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Critical > Fix For: trunk, 2.5.1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20650) Remove Server attribute from the HTTP response headers
[ https://issues.apache.org/jira/browse/AMBARI-20650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-20650: Resolution: Fixed Status: Resolved (was: Patch Available) > Remove Server attribute from the HTTP response headers > -- > > Key: AMBARI-20650 > URL: https://issues.apache.org/jira/browse/AMBARI-20650 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Fix For: trunk, 2.5.1 > > Attachments: AMBARI-20650.patch > > > Currently the HTTP response header contains the Jetty version. > Server:Jetty(8.1.19.v20160209) > To follow best security practices, it would be good to avoid including this > information in the response headers. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20650) Remove Server attribute from the HTTP response headers
[ https://issues.apache.org/jira/browse/AMBARI-20650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15968316#comment-15968316 ] Sangeeta Ravindran commented on AMBARI-20650: - Yes, thanks Robert. Committed to trunk as commit f894e486a6f8eab31aec5add517a35ec9a11b655 Committed to 2.5.1 as commit 6cf930b111ffdf14428f4d2480a2ec2387e3e347 > Remove Server attribute from the HTTP response headers > -- > > Key: AMBARI-20650 > URL: https://issues.apache.org/jira/browse/AMBARI-20650 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Fix For: trunk, 2.5.1 > > Attachments: AMBARI-20650.patch > > > Currently the HTTP response header contains the Jetty version. > Server:Jetty(8.1.19.v20160209) > To follow best security practices, it would be good to avoid including this > information in the response headers. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20650) Remove Server attribute from the HTTP response headers
[ https://issues.apache.org/jira/browse/AMBARI-20650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-20650: Fix Version/s: 2.5.1 > Remove Server attribute from the HTTP response headers > -- > > Key: AMBARI-20650 > URL: https://issues.apache.org/jira/browse/AMBARI-20650 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Fix For: trunk, 2.5.1 > > Attachments: AMBARI-20650.patch > > > Currently the HTTP response header contains the Jetty version. > Server:Jetty(8.1.19.v20160209) > To follow best security practices, it would be good to avoid including this > information in the response headers. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20762) Add more database options for beacon in stack advisor
[
https://issues.apache.org/jira/browse/AMBARI-20762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15968312#comment-15968312
]
Hadoop QA commented on AMBARI-20762:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12863362/AMBARI-20762.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/11396//console
This message is automatically generated.
> Add more database options for beacon in stack advisor
> -
>
> Key: AMBARI-20762
> URL: https://issues.apache.org/jira/browse/AMBARI-20762
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.5.1
>Reporter: Xi Wang
>Assignee: Xi Wang
> Fix For: 2.5.1
>
> Attachments: AMBARI-20762.patch, AMBARI-20762.patch
>
>
> In the configs/Database page of beacon, on selecting each database type, the
> JDBC Driver Class and URL should be updated automatically.
> This part should be done in stack advisor.
> (Beacon supports three db types : New derby, existed MySQL and existed Oracle
> )
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19996) Perform kinit on Kafka Start
[ https://issues.apache.org/jira/browse/AMBARI-19996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15968299#comment-15968299 ] Hudson commented on AMBARI-19996: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7295 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7295/]) AMBARI-19996 Perform Kinit on Kafka Start (Bharat Viswanadham via dili) (dili: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=14c1ffd3288742354f17cbf49b6cebfee913a16f]) * (edit) ambari-server/src/main/resources/common-services/KAFKA/0.8.1/package/scripts/kafka_broker.py > Perform kinit on Kafka Start > > > Key: AMBARI-19996 > URL: https://issues.apache.org/jira/browse/AMBARI-19996 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Bharat Viswanadham >Assignee: Bharat Viswanadham > Fix For: trunk > > Attachments: AMBARI-19996.PATCH > > > Perform Kinit with kafka keytab on Kafka broker start. > As Kafka Client uses the cached kerberos ticket, so when kafka console > commands like producer, consumer are run with kafka user and cluster is > kerberoized, kinit should happen automatically -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20697) Stack advisor code in 2.3 refactor logic for ranger Kafka Plugin
[
https://issues.apache.org/jira/browse/AMBARI-20697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15968300#comment-15968300
]
Hudson commented on AMBARI-20697:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7295 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7295/])
AMBARI-20697 Stack advisor code in 2.3 refactor logic for ranger Kafka (dili:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=cfde36c077de31dda0802f983602f680afcbce29])
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.3/services/stack_advisor.py
> Stack advisor code in 2.3 refactor logic for ranger Kafka Plugin
>
>
> Key: AMBARI-20697
> URL: https://issues.apache.org/jira/browse/AMBARI-20697
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Bharat Viswanadham
>Assignee: Bharat Viswanadham
> Labels: stack, stackadvisor
> Fix For: trunk
>
> Attachments: AMBARI-20697.PATCH
>
>
> if ranger_plugin_enabled:
> # If ranger-kafka-plugin-properties/ranger-kafka-plugin-enabled,
> # determine if the Ranger/Kafka plug-in enabled enabled or not
> if 'ranger-kafka-plugin-properties' in configurations and \
> 'ranger-kafka-plugin-enabled' in
> configurations['ranger-kafka-plugin-properties']['properties']:
> ranger_plugin_enabled =
> configurations['ranger-kafka-plugin-properties']['properties']['ranger-kafka-plugin-enabled'].lower()
> == 'yes'
> # If ranger-kafka-plugin-properties/ranger-kafka-plugin-enabled was not
> changed,
> # determine if the Ranger/Kafka plug-in enabled enabled or not
> elif 'ranger-kafka-plugin-properties' in services['configurations'] and
> \
> 'ranger-kafka-plugin-enabled' in
> services['configurations']['ranger-kafka-plugin-properties']['properties']:
> ranger_plugin_enabled =
> services['configurations']['ranger-kafka-plugin-properties']['properties']['ranger-kafka-plugin-enabled'].lower()
> == 'yes'
> # Determine the value for kafka-broker/authorizer.class.name
> if ranger_plugin_enabled:
> # If the Ranger plugin for Kafka is enabled, set authorizer.class.name
> to
> #
> "org.apache.ranger.authorization.kafka.authorizer.RangerKafkaAuthorizer"
> whether Kerberos is
> # enabled or not.
> putKafkaBrokerProperty("authorizer.class.name",
> 'org.apache.ranger.authorization.kafka.authorizer.RangerKafkaAuthorizer')
> elif security_enabled:
> putKafkaBrokerProperty("authorizer.class.name",
> 'kafka.security.auth.SimpleAclAuthorizer')
> else:
> putKafkaBrokerAttributes('authorizer.class.name', 'delete', 'true')
> In the above code after ranger_plugin_enabled is true and inside conditions
> don't match then also we set authorizer.class.name to RangerKafakAuthorizer.
> So, to avoid this after checking ranger_plugin_enabled set to false and then
> continue with code checking
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20763) Update YARN configs 'apptimelineserver_heapsize' and 'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6.
[ https://issues.apache.org/jira/browse/AMBARI-20763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-20763: - Fix Version/s: 2.5.1 trunk > Update YARN configs 'apptimelineserver_heapsize' and > 'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6. > --- > > Key: AMBARI-20763 > URL: https://issues.apache.org/jira/browse/AMBARI-20763 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Critical > Fix For: trunk, 2.5.1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20763) Update YARN configs 'apptimelineserver_heapsize' and 'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6.
[ https://issues.apache.org/jira/browse/AMBARI-20763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-20763: - Component/s: ambari-server > Update YARN configs 'apptimelineserver_heapsize' and > 'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6. > --- > > Key: AMBARI-20763 > URL: https://issues.apache.org/jira/browse/AMBARI-20763 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Critical > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20763) Update YARN configs 'apptimelineserver_heapsize' and 'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6.
[ https://issues.apache.org/jira/browse/AMBARI-20763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-20763: - Affects Version/s: trunk > Update YARN configs 'apptimelineserver_heapsize' and > 'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6. > --- > > Key: AMBARI-20763 > URL: https://issues.apache.org/jira/browse/AMBARI-20763 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Critical > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20763) Update YARN configs 'apptimelineserver_heapsize' and 'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6.
[ https://issues.apache.org/jira/browse/AMBARI-20763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-20763: - Affects Version/s: 2.5.0 > Update YARN configs 'apptimelineserver_heapsize' and > 'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6. > --- > > Key: AMBARI-20763 > URL: https://issues.apache.org/jira/browse/AMBARI-20763 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Critical > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20763) Update YARN configs 'apptimelineserver_heapsize' and 'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6.
Swapan Shridhar created AMBARI-20763: Summary: Update YARN configs 'apptimelineserver_heapsize' and 'yarn.timeline-service.entity-group-fs-store.app-cache-size' logic in 2.6. Key: AMBARI-20763 URL: https://issues.apache.org/jira/browse/AMBARI-20763 Project: Ambari Issue Type: Bug Reporter: Swapan Shridhar Assignee: Swapan Shridhar Priority: Critical -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20752) Update the Accordion styles in horton style
[ https://issues.apache.org/jira/browse/AMBARI-20752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15968224#comment-15968224 ] Hudson commented on AMBARI-20752: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7294 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7294/]) AMBARI-20752. Update the Accordion styles in horton style.(xiwang) (xiwang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0c778e77ac05caf24e1a0a1028533ec42ff35da2]) * (edit) ambari-web/app/styles/theme/bootstrap-ambari.css > Update the Accordion styles in horton style > --- > > Key: AMBARI-20752 > URL: https://issues.apache.org/jira/browse/AMBARI-20752 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-20752.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20762) Add more database options for beacon in stack advisor
[ https://issues.apache.org/jira/browse/AMBARI-20762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-20762: - Attachment: AMBARI-20762.patch AMBARI-20762.patch > Add more database options for beacon in stack advisor > - > > Key: AMBARI-20762 > URL: https://issues.apache.org/jira/browse/AMBARI-20762 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 2.5.1 > > Attachments: AMBARI-20762.patch, AMBARI-20762.patch > > > In the configs/Database page of beacon, on selecting each database type, the > JDBC Driver Class and URL should be updated automatically. > This part should be done in stack advisor. > (Beacon supports three db types : New derby, existed MySQL and existed Oracle > ) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20762) Add more database options for beacon in stack advisor
[ https://issues.apache.org/jira/browse/AMBARI-20762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-20762: - Status: Patch Available (was: Open) > Add more database options for beacon in stack advisor > - > > Key: AMBARI-20762 > URL: https://issues.apache.org/jira/browse/AMBARI-20762 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 2.5.1 > > Attachments: AMBARI-20762.patch, AMBARI-20762.patch > > > In the configs/Database page of beacon, on selecting each database type, the > JDBC Driver Class and URL should be updated automatically. > This part should be done in stack advisor. > (Beacon supports three db types : New derby, existed MySQL and existed Oracle > ) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20761) Update propery description for zookeeper.connect in Kafka Config
[
https://issues.apache.org/jira/browse/AMBARI-20761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15968216#comment-15968216
]
Hadoop QA commented on AMBARI-20761:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12863345/AMBARI-20761.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 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler 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/11395//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11395//console
This message is automatically generated.
> Update propery description for zookeeper.connect in Kafka Config
>
>
> Key: AMBARI-20761
> URL: https://issues.apache.org/jira/browse/AMBARI-20761
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Bharat Viswanadham
>Assignee: Bharat Viswanadham
>Priority: Minor
> Attachments: AMBARI-20761.PATCH
>
>
>
> zookeeper.connect
> localhost:2181
>
> Zookeeper also allows you to add a "chroot" path which will make all
> kafka data for this cluster appear under a particular path.
> This is a way to setup multiple Kafka clusters or other applications on
> the same zookeeper cluster. To do this give a connection
> string in the form
> hostname1:port1,hostname2:port2,hostname3:port3/chroot/path which would put
> all this cluster's data under the
> path /chroot/path. Note that you must create this path yourself prior
> to starting the broker and consumers must use the
> same connection string.
>
> In the description it is said to create path before starting broker and
> consumer. Actually this is taken care in Kafka. So need to cleanup this.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20697) Stack advisor code in 2.3 refactor logic for ranger Kafka Plugin
[
https://issues.apache.org/jira/browse/AMBARI-20697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Viswanadham updated AMBARI-20697:
Fix Version/s: trunk
> Stack advisor code in 2.3 refactor logic for ranger Kafka Plugin
>
>
> Key: AMBARI-20697
> URL: https://issues.apache.org/jira/browse/AMBARI-20697
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Bharat Viswanadham
>Assignee: Bharat Viswanadham
> Labels: stack, stackadvisor
> Fix For: trunk
>
> Attachments: AMBARI-20697.PATCH
>
>
> if ranger_plugin_enabled:
> # If ranger-kafka-plugin-properties/ranger-kafka-plugin-enabled,
> # determine if the Ranger/Kafka plug-in enabled enabled or not
> if 'ranger-kafka-plugin-properties' in configurations and \
> 'ranger-kafka-plugin-enabled' in
> configurations['ranger-kafka-plugin-properties']['properties']:
> ranger_plugin_enabled =
> configurations['ranger-kafka-plugin-properties']['properties']['ranger-kafka-plugin-enabled'].lower()
> == 'yes'
> # If ranger-kafka-plugin-properties/ranger-kafka-plugin-enabled was not
> changed,
> # determine if the Ranger/Kafka plug-in enabled enabled or not
> elif 'ranger-kafka-plugin-properties' in services['configurations'] and
> \
> 'ranger-kafka-plugin-enabled' in
> services['configurations']['ranger-kafka-plugin-properties']['properties']:
> ranger_plugin_enabled =
> services['configurations']['ranger-kafka-plugin-properties']['properties']['ranger-kafka-plugin-enabled'].lower()
> == 'yes'
> # Determine the value for kafka-broker/authorizer.class.name
> if ranger_plugin_enabled:
> # If the Ranger plugin for Kafka is enabled, set authorizer.class.name
> to
> #
> "org.apache.ranger.authorization.kafka.authorizer.RangerKafkaAuthorizer"
> whether Kerberos is
> # enabled or not.
> putKafkaBrokerProperty("authorizer.class.name",
> 'org.apache.ranger.authorization.kafka.authorizer.RangerKafkaAuthorizer')
> elif security_enabled:
> putKafkaBrokerProperty("authorizer.class.name",
> 'kafka.security.auth.SimpleAclAuthorizer')
> else:
> putKafkaBrokerAttributes('authorizer.class.name', 'delete', 'true')
> In the above code after ranger_plugin_enabled is true and inside conditions
> don't match then also we set authorizer.class.name to RangerKafakAuthorizer.
> So, to avoid this after checking ranger_plugin_enabled set to false and then
> continue with code checking
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20697) Stack advisor code in 2.3 refactor logic for ranger Kafka Plugin
[
https://issues.apache.org/jira/browse/AMBARI-20697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Di Li updated AMBARI-20697:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Stack advisor code in 2.3 refactor logic for ranger Kafka Plugin
>
>
> Key: AMBARI-20697
> URL: https://issues.apache.org/jira/browse/AMBARI-20697
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Bharat Viswanadham
>Assignee: Bharat Viswanadham
> Labels: stack, stackadvisor
> Attachments: AMBARI-20697.PATCH
>
>
> if ranger_plugin_enabled:
> # If ranger-kafka-plugin-properties/ranger-kafka-plugin-enabled,
> # determine if the Ranger/Kafka plug-in enabled enabled or not
> if 'ranger-kafka-plugin-properties' in configurations and \
> 'ranger-kafka-plugin-enabled' in
> configurations['ranger-kafka-plugin-properties']['properties']:
> ranger_plugin_enabled =
> configurations['ranger-kafka-plugin-properties']['properties']['ranger-kafka-plugin-enabled'].lower()
> == 'yes'
> # If ranger-kafka-plugin-properties/ranger-kafka-plugin-enabled was not
> changed,
> # determine if the Ranger/Kafka plug-in enabled enabled or not
> elif 'ranger-kafka-plugin-properties' in services['configurations'] and
> \
> 'ranger-kafka-plugin-enabled' in
> services['configurations']['ranger-kafka-plugin-properties']['properties']:
> ranger_plugin_enabled =
> services['configurations']['ranger-kafka-plugin-properties']['properties']['ranger-kafka-plugin-enabled'].lower()
> == 'yes'
> # Determine the value for kafka-broker/authorizer.class.name
> if ranger_plugin_enabled:
> # If the Ranger plugin for Kafka is enabled, set authorizer.class.name
> to
> #
> "org.apache.ranger.authorization.kafka.authorizer.RangerKafkaAuthorizer"
> whether Kerberos is
> # enabled or not.
> putKafkaBrokerProperty("authorizer.class.name",
> 'org.apache.ranger.authorization.kafka.authorizer.RangerKafkaAuthorizer')
> elif security_enabled:
> putKafkaBrokerProperty("authorizer.class.name",
> 'kafka.security.auth.SimpleAclAuthorizer')
> else:
> putKafkaBrokerAttributes('authorizer.class.name', 'delete', 'true')
> In the above code after ranger_plugin_enabled is true and inside conditions
> don't match then also we set authorizer.class.name to RangerKafakAuthorizer.
> So, to avoid this after checking ranger_plugin_enabled set to false and then
> continue with code checking
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20697) Stack advisor code in 2.3 refactor logic for ranger Kafka Plugin
[
https://issues.apache.org/jira/browse/AMBARI-20697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15968200#comment-15968200
]
Di Li commented on AMBARI-20697:
pushed to trunk as
https://git-wip-us.apache.org/repos/asf?p=ambari.git;a=commit;h=cfde36c077de31dda0802f983602f680afcbce29
> Stack advisor code in 2.3 refactor logic for ranger Kafka Plugin
>
>
> Key: AMBARI-20697
> URL: https://issues.apache.org/jira/browse/AMBARI-20697
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Bharat Viswanadham
>Assignee: Bharat Viswanadham
> Labels: stack, stackadvisor
> Attachments: AMBARI-20697.PATCH
>
>
> if ranger_plugin_enabled:
> # If ranger-kafka-plugin-properties/ranger-kafka-plugin-enabled,
> # determine if the Ranger/Kafka plug-in enabled enabled or not
> if 'ranger-kafka-plugin-properties' in configurations and \
> 'ranger-kafka-plugin-enabled' in
> configurations['ranger-kafka-plugin-properties']['properties']:
> ranger_plugin_enabled =
> configurations['ranger-kafka-plugin-properties']['properties']['ranger-kafka-plugin-enabled'].lower()
> == 'yes'
> # If ranger-kafka-plugin-properties/ranger-kafka-plugin-enabled was not
> changed,
> # determine if the Ranger/Kafka plug-in enabled enabled or not
> elif 'ranger-kafka-plugin-properties' in services['configurations'] and
> \
> 'ranger-kafka-plugin-enabled' in
> services['configurations']['ranger-kafka-plugin-properties']['properties']:
> ranger_plugin_enabled =
> services['configurations']['ranger-kafka-plugin-properties']['properties']['ranger-kafka-plugin-enabled'].lower()
> == 'yes'
> # Determine the value for kafka-broker/authorizer.class.name
> if ranger_plugin_enabled:
> # If the Ranger plugin for Kafka is enabled, set authorizer.class.name
> to
> #
> "org.apache.ranger.authorization.kafka.authorizer.RangerKafkaAuthorizer"
> whether Kerberos is
> # enabled or not.
> putKafkaBrokerProperty("authorizer.class.name",
> 'org.apache.ranger.authorization.kafka.authorizer.RangerKafkaAuthorizer')
> elif security_enabled:
> putKafkaBrokerProperty("authorizer.class.name",
> 'kafka.security.auth.SimpleAclAuthorizer')
> else:
> putKafkaBrokerAttributes('authorizer.class.name', 'delete', 'true')
> In the above code after ranger_plugin_enabled is true and inside conditions
> don't match then also we set authorizer.class.name to RangerKafakAuthorizer.
> So, to avoid this after checking ranger_plugin_enabled set to false and then
> continue with code checking
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19996) Perform kinit on Kafka Start
[ https://issues.apache.org/jira/browse/AMBARI-19996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated AMBARI-19996: Fix Version/s: trunk > Perform kinit on Kafka Start > > > Key: AMBARI-19996 > URL: https://issues.apache.org/jira/browse/AMBARI-19996 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Bharat Viswanadham >Assignee: Bharat Viswanadham > Fix For: trunk > > Attachments: AMBARI-19996.PATCH > > > Perform Kinit with kafka keytab on Kafka broker start. > As Kafka Client uses the cached kerberos ticket, so when kafka console > commands like producer, consumer are run with kafka user and cluster is > kerberoized, kinit should happen automatically -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20762) Add more database options for beacon in stack advisor
Xi Wang created AMBARI-20762: Summary: Add more database options for beacon in stack advisor Key: AMBARI-20762 URL: https://issues.apache.org/jira/browse/AMBARI-20762 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.5.1 Reporter: Xi Wang Assignee: Xi Wang In the configs/Database page of beacon, on selecting each database type, the JDBC Driver Class and URL should be updated automatically. This part should be done in stack advisor. (Beacon supports three db types : New derby, existed MySQL and existed Oracle ) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20762) Add more database options for beacon in stack advisor
[ https://issues.apache.org/jira/browse/AMBARI-20762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-20762: - Fix Version/s: 2.5.1 > Add more database options for beacon in stack advisor > - > > Key: AMBARI-20762 > URL: https://issues.apache.org/jira/browse/AMBARI-20762 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 2.5.1 > > > In the configs/Database page of beacon, on selecting each database type, the > JDBC Driver Class and URL should be updated automatically. > This part should be done in stack advisor. > (Beacon supports three db types : New derby, existed MySQL and existed Oracle > ) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19996) Perform kinit on Kafka Start
[ https://issues.apache.org/jira/browse/AMBARI-19996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15968192#comment-15968192 ] Di Li commented on AMBARI-19996: pushed to trunk as https://git-wip-us.apache.org/repos/asf?p=ambari.git;a=commit;h=14c1ffd3288742354f17cbf49b6cebfee913a16f > Perform kinit on Kafka Start > > > Key: AMBARI-19996 > URL: https://issues.apache.org/jira/browse/AMBARI-19996 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Bharat Viswanadham >Assignee: Bharat Viswanadham > Attachments: AMBARI-19996.PATCH > > > Perform Kinit with kafka keytab on Kafka broker start. > As Kafka Client uses the cached kerberos ticket, so when kafka console > commands like producer, consumer are run with kafka user and cluster is > kerberoized, kinit should happen automatically -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19996) Perform kinit on Kafka Start
[ https://issues.apache.org/jira/browse/AMBARI-19996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-19996: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Perform kinit on Kafka Start > > > Key: AMBARI-19996 > URL: https://issues.apache.org/jira/browse/AMBARI-19996 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Bharat Viswanadham >Assignee: Bharat Viswanadham > Attachments: AMBARI-19996.PATCH > > > Perform Kinit with kafka keytab on Kafka broker start. > As Kafka Client uses the cached kerberos ticket, so when kafka console > commands like producer, consumer are run with kafka user and cluster is > kerberoized, kinit should happen automatically -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20752) Update the Accordion styles in horton style
[ https://issues.apache.org/jira/browse/AMBARI-20752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-20752: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and horton-style > Update the Accordion styles in horton style > --- > > Key: AMBARI-20752 > URL: https://issues.apache.org/jira/browse/AMBARI-20752 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-20752.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20650) Remove Server attribute from the HTTP response headers
[ https://issues.apache.org/jira/browse/AMBARI-20650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15968140#comment-15968140 ] Hudson commented on AMBARI-20650: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1405 (See [https://builds.apache.org/job/Ambari-branch-2.5/1405/]) AMBARI-20650: Remove Server attribute from the HTTP response headers (sangeetar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6cf930b111ffdf14428f4d2480a2ec2387e3e347]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java > Remove Server attribute from the HTTP response headers > -- > > Key: AMBARI-20650 > URL: https://issues.apache.org/jira/browse/AMBARI-20650 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-20650.patch > > > Currently the HTTP response header contains the Jetty version. > Server:Jetty(8.1.19.v20160209) > To follow best security practices, it would be good to avoid including this > information in the response headers. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20757) Selecting ignore service checks results in blank dialog box when hitting an error
[ https://issues.apache.org/jira/browse/AMBARI-20757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15968134#comment-15968134 ] Tim Thorpe commented on AMBARI-20757: - The failure seen is in ambari-server code and can't be related to my UI change. java.lang.AssertionError: expected:<6> but was:<7> at org.apache.ambari.server.state.UpgradeHelperTest.testServiceCheckUpgradeStages(UpgradeHelperTest.java:1091) > Selecting ignore service checks results in blank dialog box when hitting an > error > - > > Key: AMBARI-20757 > URL: https://issues.apache.org/jira/browse/AMBARI-20757 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk, 2.5.0 >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Fix For: trunk > > Attachments: AMBARI-20757.patch > > > In order to see what has gone wrong, you need to drill down into the last > step until you find the service check that failed. Ideally there would be a > message above where they normally appear. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20761) Update propery description for zookeeper.connect in Kafka Config
[ https://issues.apache.org/jira/browse/AMBARI-20761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated AMBARI-20761: Attachment: AMBARI-20761.PATCH > Update propery description for zookeeper.connect in Kafka Config > > > Key: AMBARI-20761 > URL: https://issues.apache.org/jira/browse/AMBARI-20761 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Bharat Viswanadham >Assignee: Bharat Viswanadham >Priority: Minor > Attachments: AMBARI-20761.PATCH > > > > zookeeper.connect > localhost:2181 > > Zookeeper also allows you to add a "chroot" path which will make all > kafka data for this cluster appear under a particular path. > This is a way to setup multiple Kafka clusters or other applications on > the same zookeeper cluster. To do this give a connection > string in the form > hostname1:port1,hostname2:port2,hostname3:port3/chroot/path which would put > all this cluster's data under the > path /chroot/path. Note that you must create this path yourself prior > to starting the broker and consumers must use the > same connection string. > > In the description it is said to create path before starting broker and > consumer. Actually this is taken care in Kafka. So need to cleanup this. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20761) Update propery description for zookeeper.connect in Kafka Config
[ https://issues.apache.org/jira/browse/AMBARI-20761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated AMBARI-20761: Assignee: Bharat Viswanadham Status: Patch Available (was: Open) > Update propery description for zookeeper.connect in Kafka Config > > > Key: AMBARI-20761 > URL: https://issues.apache.org/jira/browse/AMBARI-20761 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Bharat Viswanadham >Assignee: Bharat Viswanadham >Priority: Minor > > > zookeeper.connect > localhost:2181 > > Zookeeper also allows you to add a "chroot" path which will make all > kafka data for this cluster appear under a particular path. > This is a way to setup multiple Kafka clusters or other applications on > the same zookeeper cluster. To do this give a connection > string in the form > hostname1:port1,hostname2:port2,hostname3:port3/chroot/path which would put > all this cluster's data under the > path /chroot/path. Note that you must create this path yourself prior > to starting the broker and consumers must use the > same connection string. > > In the description it is said to create path before starting broker and > consumer. Actually this is taken care in Kafka. So need to cleanup this. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20761) Update propery description for zookeeper.connect in Kafka Config
Bharat Viswanadham created AMBARI-20761: --- Summary: Update propery description for zookeeper.connect in Kafka Config Key: AMBARI-20761 URL: https://issues.apache.org/jira/browse/AMBARI-20761 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: trunk Reporter: Bharat Viswanadham Priority: Minor zookeeper.connect localhost:2181 Zookeeper also allows you to add a "chroot" path which will make all kafka data for this cluster appear under a particular path. This is a way to setup multiple Kafka clusters or other applications on the same zookeeper cluster. To do this give a connection string in the form hostname1:port1,hostname2:port2,hostname3:port3/chroot/path which would put all this cluster's data under the path /chroot/path. Note that you must create this path yourself prior to starting the broker and consumers must use the same connection string. In the description it is said to create path before starting broker and consumer. Actually this is taken care in Kafka. So need to cleanup this. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20760) After pam setup- Hive View user home test fails
[
https://issues.apache.org/jira/browse/AMBARI-20760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15968104#comment-15968104
]
Hadoop QA commented on AMBARI-20760:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12863327/AMBARI-20760.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 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler 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/11394//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11394//console
This message is automatically generated.
> After pam setup- Hive View user home test fails
> ---
>
> Key: AMBARI-20760
> URL: https://issues.apache.org/jira/browse/AMBARI-20760
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Anita Gnanamalar Jebaraj
>Assignee: Anita Gnanamalar Jebaraj
> Attachments: AMBARI-20760.patch, error.PNG
>
>
> After setting up PAM, tried to login as PAM user and access hive view, user
> home test fails with the error as in screen shot.
> This issue was pointed out by [~hkropp] in the jira AMBARI-12263, but was not
> incorporated in the code. Pasting the comment from Henning below.
> Something we noticed is that in a secured cluster we have issues with the
> views, getting the following exception for the Hive view as an example:
> Struct:TOpenSessionResp(status:TStatus(statusCode:ERROR_STATUS,
> infoMessages:[*org.apache.hive.service.cli.HiveSQLException:Failed to
> validate proxy privilege of ambari for
> org.apache.ambari.server.security.authorization.AmbariPamAuthenticationProvider$1@3459:33:32,
>
> .
> sqlState:08S01, errorCode:0, errorMessage:Failed to validate proxy privilege
> of ambari for
> org.apache.ambari.server.security.authorization.AmbariPamAuthenticationProvider$1@3459),
> serverProtocolVersion:null)
> As you can see it tries to impersonte
> "org.apache.ambari.server.security.authorization.AmbariPamAuthenticationProvider$1@3459:33:32".
> Changing the UsernamePasswordAuthenticationToken from Principal to username
> fixes this.
> So instead of :
> UsernamePasswordAuthenticationToken token = new
> UsernamePasswordAuthenticationToken(principal, null, userAuthorities);
> We use:
> UsernamePasswordAuthenticationToken token = new
> UsernamePasswordAuthenticationToken(user.getUserName(), null,
> userAuthorities);
> What could potential also work is, overriding toString of the principal like:
> Principal principal = new Principal() {
> @Override
> public String getName() {
> return user.getUserName();
> }
> @Override
> public String toString(){
> return user.getUserName().toString();
> }
> };
> We did not test this!
> As a little side note, I notices you are using String concatenation in your
> error logging like this: LOG.error("Message"+ ex.getMessage()) I think the
> public void error(String msg, Throwable t); interface would be preferable in
> such scenarios, so: LOG.error("Message", ex)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20757) Selecting ignore service checks results in blank dialog box when hitting an error
[ https://issues.apache.org/jira/browse/AMBARI-20757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15968096#comment-15968096 ] Hudson commented on AMBARI-20757: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7293 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7293/]) AMBARI-20757 - Selecting ignore service checks results in blank dialog (tthorpe: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7e46412dc694fc78713be079e56d7347a6f2f60c]) * (edit) ambari-web/app/messages.js * (edit) ambari-web/app/templates/main/admin/stack_upgrade/stack_upgrade_wizard.hbs > Selecting ignore service checks results in blank dialog box when hitting an > error > - > > Key: AMBARI-20757 > URL: https://issues.apache.org/jira/browse/AMBARI-20757 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk, 2.5.0 >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Fix For: trunk > > Attachments: AMBARI-20757.patch > > > In order to see what has gone wrong, you need to drill down into the last > step until you find the service check that failed. Ideally there would be a > message above where they normally appear. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20760) After pam setup- Hive View user home test fails
[
https://issues.apache.org/jira/browse/AMBARI-20760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15968081#comment-15968081
]
Robert Levas commented on AMBARI-20760:
---
FYI, [~ghugare]. Can you take a look at this patch? Reviewboard -
https://reviews.apache.org/r/58429/
> After pam setup- Hive View user home test fails
> ---
>
> Key: AMBARI-20760
> URL: https://issues.apache.org/jira/browse/AMBARI-20760
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Anita Gnanamalar Jebaraj
>Assignee: Anita Gnanamalar Jebaraj
> Attachments: AMBARI-20760.patch, error.PNG
>
>
> After setting up PAM, tried to login as PAM user and access hive view, user
> home test fails with the error as in screen shot.
> This issue was pointed out by [~hkropp] in the jira AMBARI-12263, but was not
> incorporated in the code. Pasting the comment from Henning below.
> Something we noticed is that in a secured cluster we have issues with the
> views, getting the following exception for the Hive view as an example:
> Struct:TOpenSessionResp(status:TStatus(statusCode:ERROR_STATUS,
> infoMessages:[*org.apache.hive.service.cli.HiveSQLException:Failed to
> validate proxy privilege of ambari for
> org.apache.ambari.server.security.authorization.AmbariPamAuthenticationProvider$1@3459:33:32,
>
> .
> sqlState:08S01, errorCode:0, errorMessage:Failed to validate proxy privilege
> of ambari for
> org.apache.ambari.server.security.authorization.AmbariPamAuthenticationProvider$1@3459),
> serverProtocolVersion:null)
> As you can see it tries to impersonte
> "org.apache.ambari.server.security.authorization.AmbariPamAuthenticationProvider$1@3459:33:32".
> Changing the UsernamePasswordAuthenticationToken from Principal to username
> fixes this.
> So instead of :
> UsernamePasswordAuthenticationToken token = new
> UsernamePasswordAuthenticationToken(principal, null, userAuthorities);
> We use:
> UsernamePasswordAuthenticationToken token = new
> UsernamePasswordAuthenticationToken(user.getUserName(), null,
> userAuthorities);
> What could potential also work is, overriding toString of the principal like:
> Principal principal = new Principal() {
> @Override
> public String getName() {
> return user.getUserName();
> }
> @Override
> public String toString(){
> return user.getUserName().toString();
> }
> };
> We did not test this!
> As a little side note, I notices you are using String concatenation in your
> error logging like this: LOG.error("Message"+ ex.getMessage()) I think the
> public void error(String msg, Throwable t); interface would be preferable in
> such scenarios, so: LOG.error("Message", ex)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20650) Remove Server attribute from the HTTP response headers
[
https://issues.apache.org/jira/browse/AMBARI-20650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15968067#comment-15968067
]
Robert Levas commented on AMBARI-20650:
---
[~sangeetar]
+1 for this change..
Can you add {{2.5.1}} to the fix version?
> Remove Server attribute from the HTTP response headers
> --
>
> Key: AMBARI-20650
> URL: https://issues.apache.org/jira/browse/AMBARI-20650
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-20650.patch
>
>
> Currently the HTTP response header contains the Jetty version.
> Server:Jetty(8.1.19.v20160209)
> To follow best security practices, it would be good to avoid including this
> information in the response headers.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20666) beginning or ending commas in dfs.cluster.administrators cause trouble for starting services
[ https://issues.apache.org/jira/browse/AMBARI-20666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15968034#comment-15968034 ] Hudson commented on AMBARI-20666: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7292 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7292/]) AMBARI-20666 - beginning or ending commas in dfs.cluster.administrators (tthorpe: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=269ac0a1f28d26180a1f684869a884d18f96d086]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-ANY/scripts/shared_initialization.py * (edit) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-ANY/scripts/shared_initialization.py > beginning or ending commas in dfs.cluster.administrators cause trouble for > starting services > > > Key: AMBARI-20666 > URL: https://issues.apache.org/jira/browse/AMBARI-20666 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Tim Thorpe >Assignee: Tim Thorpe >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-20666.patch > > > In order to avoid issues with starting and stopping services, it would be > useful to trim any commas from the beginning or ending of the user and group > lists -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20757) Selecting ignore service checks results in blank dialog box when hitting an error
[ https://issues.apache.org/jira/browse/AMBARI-20757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-20757: Resolution: Fixed Status: Resolved (was: Patch Available) > Selecting ignore service checks results in blank dialog box when hitting an > error > - > > Key: AMBARI-20757 > URL: https://issues.apache.org/jira/browse/AMBARI-20757 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk, 2.5.0 >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Fix For: trunk > > Attachments: AMBARI-20757.patch > > > In order to see what has gone wrong, you need to drill down into the last > step until you find the service check that failed. Ideally there would be a > message above where they normally appear. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20757) Selecting ignore service checks results in blank dialog box when hitting an error
[ https://issues.apache.org/jira/browse/AMBARI-20757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-20757: Attachment: AMBARI-20757.patch > Selecting ignore service checks results in blank dialog box when hitting an > error > - > > Key: AMBARI-20757 > URL: https://issues.apache.org/jira/browse/AMBARI-20757 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk, 2.5.0 >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Fix For: trunk > > Attachments: AMBARI-20757.patch > > > In order to see what has gone wrong, you need to drill down into the last > step until you find the service check that failed. Ideally there would be a > message above where they normally appear. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20757) Selecting ignore service checks results in blank dialog box when hitting an error
[ https://issues.apache.org/jira/browse/AMBARI-20757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-20757: Status: Patch Available (was: Open) > Selecting ignore service checks results in blank dialog box when hitting an > error > - > > Key: AMBARI-20757 > URL: https://issues.apache.org/jira/browse/AMBARI-20757 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk, 2.5.0 >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Fix For: trunk > > Attachments: AMBARI-20757.patch > > > In order to see what has gone wrong, you need to drill down into the last > step until you find the service check that failed. Ideally there would be a > message above where they normally appear. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20757) Selecting ignore service checks results in blank dialog box when hitting an error
[ https://issues.apache.org/jira/browse/AMBARI-20757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-20757: Attachment: (was: AMBARI-20757.patch) > Selecting ignore service checks results in blank dialog box when hitting an > error > - > > Key: AMBARI-20757 > URL: https://issues.apache.org/jira/browse/AMBARI-20757 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk, 2.5.0 >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Fix For: trunk > > > In order to see what has gone wrong, you need to drill down into the last > step until you find the service check that failed. Ideally there would be a > message above where they normally appear. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20757) Selecting ignore service checks results in blank dialog box when hitting an error
[ https://issues.apache.org/jira/browse/AMBARI-20757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-20757: Status: Open (was: Patch Available) > Selecting ignore service checks results in blank dialog box when hitting an > error > - > > Key: AMBARI-20757 > URL: https://issues.apache.org/jira/browse/AMBARI-20757 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk, 2.5.0 >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Fix For: trunk > > > In order to see what has gone wrong, you need to drill down into the last > step until you find the service check that failed. Ideally there would be a > message above where they normally appear. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20760) After pam setup- Hive View user home test fails
[
https://issues.apache.org/jira/browse/AMBARI-20760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anita Gnanamalar Jebaraj updated AMBARI-20760:
--
Status: Patch Available (was: Open)
> After pam setup- Hive View user home test fails
> ---
>
> Key: AMBARI-20760
> URL: https://issues.apache.org/jira/browse/AMBARI-20760
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Anita Gnanamalar Jebaraj
>Assignee: Anita Gnanamalar Jebaraj
> Attachments: AMBARI-20760.patch, error.PNG
>
>
> After setting up PAM, tried to login as PAM user and access hive view, user
> home test fails with the error as in screen shot.
> This issue was pointed out by [~hkropp] in the jira AMBARI-12263, but was not
> incorporated in the code. Pasting the comment from Henning below.
> Something we noticed is that in a secured cluster we have issues with the
> views, getting the following exception for the Hive view as an example:
> Struct:TOpenSessionResp(status:TStatus(statusCode:ERROR_STATUS,
> infoMessages:[*org.apache.hive.service.cli.HiveSQLException:Failed to
> validate proxy privilege of ambari for
> org.apache.ambari.server.security.authorization.AmbariPamAuthenticationProvider$1@3459:33:32,
>
> .
> sqlState:08S01, errorCode:0, errorMessage:Failed to validate proxy privilege
> of ambari for
> org.apache.ambari.server.security.authorization.AmbariPamAuthenticationProvider$1@3459),
> serverProtocolVersion:null)
> As you can see it tries to impersonte
> "org.apache.ambari.server.security.authorization.AmbariPamAuthenticationProvider$1@3459:33:32".
> Changing the UsernamePasswordAuthenticationToken from Principal to username
> fixes this.
> So instead of :
> UsernamePasswordAuthenticationToken token = new
> UsernamePasswordAuthenticationToken(principal, null, userAuthorities);
> We use:
> UsernamePasswordAuthenticationToken token = new
> UsernamePasswordAuthenticationToken(user.getUserName(), null,
> userAuthorities);
> What could potential also work is, overriding toString of the principal like:
> Principal principal = new Principal() {
> @Override
> public String getName() {
> return user.getUserName();
> }
> @Override
> public String toString(){
> return user.getUserName().toString();
> }
> };
> We did not test this!
> As a little side note, I notices you are using String concatenation in your
> error logging like this: LOG.error("Message"+ ex.getMessage()) I think the
> public void error(String msg, Throwable t); interface would be preferable in
> such scenarios, so: LOG.error("Message", ex)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20760) After pam setup- Hive View user home test fails
[
https://issues.apache.org/jira/browse/AMBARI-20760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anita Gnanamalar Jebaraj updated AMBARI-20760:
--
Attachment: AMBARI-20760.patch
> After pam setup- Hive View user home test fails
> ---
>
> Key: AMBARI-20760
> URL: https://issues.apache.org/jira/browse/AMBARI-20760
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Anita Gnanamalar Jebaraj
>Assignee: Anita Gnanamalar Jebaraj
> Attachments: AMBARI-20760.patch, error.PNG
>
>
> After setting up PAM, tried to login as PAM user and access hive view, user
> home test fails with the error as in screen shot.
> This issue was pointed out by [~hkropp] in the jira AMBARI-12263, but was not
> incorporated in the code. Pasting the comment from Henning below.
> Something we noticed is that in a secured cluster we have issues with the
> views, getting the following exception for the Hive view as an example:
> Struct:TOpenSessionResp(status:TStatus(statusCode:ERROR_STATUS,
> infoMessages:[*org.apache.hive.service.cli.HiveSQLException:Failed to
> validate proxy privilege of ambari for
> org.apache.ambari.server.security.authorization.AmbariPamAuthenticationProvider$1@3459:33:32,
>
> .
> sqlState:08S01, errorCode:0, errorMessage:Failed to validate proxy privilege
> of ambari for
> org.apache.ambari.server.security.authorization.AmbariPamAuthenticationProvider$1@3459),
> serverProtocolVersion:null)
> As you can see it tries to impersonte
> "org.apache.ambari.server.security.authorization.AmbariPamAuthenticationProvider$1@3459:33:32".
> Changing the UsernamePasswordAuthenticationToken from Principal to username
> fixes this.
> So instead of :
> UsernamePasswordAuthenticationToken token = new
> UsernamePasswordAuthenticationToken(principal, null, userAuthorities);
> We use:
> UsernamePasswordAuthenticationToken token = new
> UsernamePasswordAuthenticationToken(user.getUserName(), null,
> userAuthorities);
> What could potential also work is, overriding toString of the principal like:
> Principal principal = new Principal() {
> @Override
> public String getName() {
> return user.getUserName();
> }
> @Override
> public String toString(){
> return user.getUserName().toString();
> }
> };
> We did not test this!
> As a little side note, I notices you are using String concatenation in your
> error logging like this: LOG.error("Message"+ ex.getMessage()) I think the
> public void error(String msg, Throwable t); interface would be preferable in
> such scenarios, so: LOG.error("Message", ex)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20757) Selecting ignore service checks results in blank dialog box when hitting an error
[ https://issues.apache.org/jira/browse/AMBARI-20757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-20757: Status: Patch Available (was: Open) > Selecting ignore service checks results in blank dialog box when hitting an > error > - > > Key: AMBARI-20757 > URL: https://issues.apache.org/jira/browse/AMBARI-20757 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk, 2.5.0 >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Fix For: trunk > > Attachments: AMBARI-20757.patch > > > In order to see what has gone wrong, you need to drill down into the last > step until you find the service check that failed. Ideally there would be a > message above where they normally appear. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20757) Selecting ignore service checks results in blank dialog box when hitting an error
[ https://issues.apache.org/jira/browse/AMBARI-20757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-20757: Attachment: AMBARI-20757.patch > Selecting ignore service checks results in blank dialog box when hitting an > error > - > > Key: AMBARI-20757 > URL: https://issues.apache.org/jira/browse/AMBARI-20757 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk, 2.5.0 >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Fix For: trunk > > Attachments: AMBARI-20757.patch > > > In order to see what has gone wrong, you need to drill down into the last > step until you find the service check that failed. Ideally there would be a > message above where they normally appear. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20759) The Web Client Upgrade Wizard Does Not Wait Long Enough When Creating a Large Upgrade
[
https://issues.apache.org/jira/browse/AMBARI-20759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15967974#comment-15967974
]
Hadoop QA commented on AMBARI-20759:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12863316/AMBARI-20759.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/11392//console
This message is automatically generated.
> The Web Client Upgrade Wizard Does Not Wait Long Enough When Creating a Large
> Upgrade
> -
>
> Key: AMBARI-20759
> URL: https://issues.apache.org/jira/browse/AMBARI-20759
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.2
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.5.1
>
> Attachments: AMBARI-20759.patch
>
>
> When creating an upgrade on a large cluster, the backend currently takes a
> very long time to create the data and persist it. Although steps are being
> taken to greatly reduce this time, it could still take up to several minutes
> for this request to go through.
> The web client currently doesn't wait long enough for the upgrade to being.
> It will produce an error message saying that the upgrade could not be created
> and then gets confused when the upgrade eventually shows up. It also allows a
> user to try to create another upgrade while the first is still being
> generated.
> STR:
> - Create a rolling upgrade on a cluster with 1000 hosts where every host has
> 15 components installed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20666) beginning or ending commas in dfs.cluster.administrators cause trouble for starting services
[
https://issues.apache.org/jira/browse/AMBARI-20666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15967971#comment-15967971
]
Hadoop QA commented on AMBARI-20666:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12863299/AMBARI-20666.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 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler 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/11391//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11391//console
This message is automatically generated.
> beginning or ending commas in dfs.cluster.administrators cause trouble for
> starting services
>
>
> Key: AMBARI-20666
> URL: https://issues.apache.org/jira/browse/AMBARI-20666
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Tim Thorpe
>Assignee: Tim Thorpe
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-20666.patch
>
>
> In order to avoid issues with starting and stopping services, it would be
> useful to trim any commas from the beginning or ending of the user and group
> lists
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20760) After pam setup- Hive View user home test fails
[
https://issues.apache.org/jira/browse/AMBARI-20760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anita Gnanamalar Jebaraj updated AMBARI-20760:
--
Description:
After setting up PAM, tried to login as PAM user and access hive view, user
home test fails with the error as in screen shot.
This issue was pointed out by [~hkropp] in the jira AMBARI-12263, but was not
incorporated in the code. Pasting the comment from Henning below.
Something we noticed is that in a secured cluster we have issues with the
views, getting the following exception for the Hive view as an example:
Struct:TOpenSessionResp(status:TStatus(statusCode:ERROR_STATUS,
infoMessages:[*org.apache.hive.service.cli.HiveSQLException:Failed to validate
proxy privilege of ambari for
org.apache.ambari.server.security.authorization.AmbariPamAuthenticationProvider$1@3459:33:32,
.
sqlState:08S01, errorCode:0, errorMessage:Failed to validate proxy privilege of
ambari for
org.apache.ambari.server.security.authorization.AmbariPamAuthenticationProvider$1@3459),
serverProtocolVersion:null)
As you can see it tries to impersonte
"org.apache.ambari.server.security.authorization.AmbariPamAuthenticationProvider$1@3459:33:32".
Changing the UsernamePasswordAuthenticationToken from Principal to username
fixes this.
So instead of :
UsernamePasswordAuthenticationToken token = new
UsernamePasswordAuthenticationToken(principal, null, userAuthorities);
We use:
UsernamePasswordAuthenticationToken token = new
UsernamePasswordAuthenticationToken(user.getUserName(), null, userAuthorities);
What could potential also work is, overriding toString of the principal like:
Principal principal = new Principal() {
@Override
public String getName() {
return user.getUserName();
}
@Override
public String toString(){
return user.getUserName().toString();
}
};
We did not test this!
As a little side note, I notices you are using String concatenation in your
error logging like this: LOG.error("Message"+ ex.getMessage()) I think the
public void error(String msg, Throwable t); interface would be preferable in
such scenarios, so: LOG.error("Message", ex)
> After pam setup- Hive View user home test fails
> ---
>
> Key: AMBARI-20760
> URL: https://issues.apache.org/jira/browse/AMBARI-20760
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Anita Gnanamalar Jebaraj
>Assignee: Anita Gnanamalar Jebaraj
> Attachments: error.PNG
>
>
> After setting up PAM, tried to login as PAM user and access hive view, user
> home test fails with the error as in screen shot.
> This issue was pointed out by [~hkropp] in the jira AMBARI-12263, but was not
> incorporated in the code. Pasting the comment from Henning below.
> Something we noticed is that in a secured cluster we have issues with the
> views, getting the following exception for the Hive view as an example:
> Struct:TOpenSessionResp(status:TStatus(statusCode:ERROR_STATUS,
> infoMessages:[*org.apache.hive.service.cli.HiveSQLException:Failed to
> validate proxy privilege of ambari for
> org.apache.ambari.server.security.authorization.AmbariPamAuthenticationProvider$1@3459:33:32,
>
> .
> sqlState:08S01, errorCode:0, errorMessage:Failed to validate proxy privilege
> of ambari for
> org.apache.ambari.server.security.authorization.AmbariPamAuthenticationProvider$1@3459),
> serverProtocolVersion:null)
> As you can see it tries to impersonte
> "org.apache.ambari.server.security.authorization.AmbariPamAuthenticationProvider$1@3459:33:32".
> Changing the UsernamePasswordAuthenticationToken from Principal to username
> fixes this.
> So instead of :
> UsernamePasswordAuthenticationToken token = new
> UsernamePasswordAuthenticationToken(principal, null, userAuthorities);
> We use:
> UsernamePasswordAuthenticationToken token = new
> UsernamePasswordAuthenticationToken(user.getUserName(), null,
> userAuthorities);
> What could potential also work is, overriding toString of the principal like:
> Principal principal = new Principal() {
> @Override
> public String getName() {
> return user.getUserName();
> }
> @Override
> public String toString(){
> return user.getUserName().toString();
> }
> };
> We did not test this!
> As a little side note, I notices you are using String concatenation in your
> error logging like this: LOG.error("Message"+ ex.getMessage()) I think the
> public void
[jira] [Commented] (AMBARI-20746) Change to warning log if Ambari doesn't have baseurls for Install Packages step before EU/RU
[ https://issues.apache.org/jira/browse/AMBARI-20746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15967965#comment-15967965 ] Hudson commented on AMBARI-20746: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7291 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7291/]) AMBARI-20746 Change to warning log if Ambari doesn't have baseurls for (dili: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b9c82add7fbe5ef652da1a47a0276b63a279470c]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/HostStackVersionResourceProvider.java * (edit) ambari-server/src/main/resources/custom_actions/scripts/install_packages.py > Change to warning log if Ambari doesn't have baseurls for Install Packages > step before EU/RU > - > > Key: AMBARI-20746 > URL: https://issues.apache.org/jira/browse/AMBARI-20746 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-20746.patch > > > Change to warning log if Ambari doesn't have baseurls for Install Packages > step before EU/RU. It currently prints out as an INFO that can be easily > ignored. Since we don't fail the Install Packages step when the baseurls are > empty, we should at least change the logging level to warning. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20760) After pam setup- Hive View user home test fails
[ https://issues.apache.org/jira/browse/AMBARI-20760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-20760: -- Attachment: error.PNG > After pam setup- Hive View user home test fails > --- > > Key: AMBARI-20760 > URL: https://issues.apache.org/jira/browse/AMBARI-20760 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj > Attachments: error.PNG > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20666) beginning or ending commas in dfs.cluster.administrators cause trouble for starting services
[ https://issues.apache.org/jira/browse/AMBARI-20666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-20666: Resolution: Fixed Fix Version/s: trunk Status: Resolved (was: Patch Available) > beginning or ending commas in dfs.cluster.administrators cause trouble for > starting services > > > Key: AMBARI-20666 > URL: https://issues.apache.org/jira/browse/AMBARI-20666 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Tim Thorpe >Assignee: Tim Thorpe >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-20666.patch > > > In order to avoid issues with starting and stopping services, it would be > useful to trim any commas from the beginning or ending of the user and group > lists -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20760) After pam setup- Hive View user home test fails
Anita Gnanamalar Jebaraj created AMBARI-20760: - Summary: After pam setup- Hive View user home test fails Key: AMBARI-20760 URL: https://issues.apache.org/jira/browse/AMBARI-20760 Project: Ambari Issue Type: Bug Affects Versions: trunk Reporter: Anita Gnanamalar Jebaraj Assignee: Anita Gnanamalar Jebaraj -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20759) The Web Client Upgrade Wizard Does Not Wait Long Enough When Creating a Large Upgrade
[ https://issues.apache.org/jira/browse/AMBARI-20759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15967957#comment-15967957 ] Andrii Tkach commented on AMBARI-20759: --- +1 for the patch > The Web Client Upgrade Wizard Does Not Wait Long Enough When Creating a Large > Upgrade > - > > Key: AMBARI-20759 > URL: https://issues.apache.org/jira/browse/AMBARI-20759 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.5.1 > > Attachments: AMBARI-20759.patch > > > When creating an upgrade on a large cluster, the backend currently takes a > very long time to create the data and persist it. Although steps are being > taken to greatly reduce this time, it could still take up to several minutes > for this request to go through. > The web client currently doesn't wait long enough for the upgrade to being. > It will produce an error message saying that the upgrade could not be created > and then gets confused when the upgrade eventually shows up. It also allows a > user to try to create another upgrade while the first is still being > generated. > STR: > - Create a rolling upgrade on a cluster with 1000 hosts where every host has > 15 components installed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20759) The Web Client Upgrade Wizard Does Not Wait Long Enough When Creating a Large Upgrade
[ https://issues.apache.org/jira/browse/AMBARI-20759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-20759: - Attachment: AMBARI-20759.patch > The Web Client Upgrade Wizard Does Not Wait Long Enough When Creating a Large > Upgrade > - > > Key: AMBARI-20759 > URL: https://issues.apache.org/jira/browse/AMBARI-20759 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.5.1 > > Attachments: AMBARI-20759.patch > > > When creating an upgrade on a large cluster, the backend currently takes a > very long time to create the data and persist it. Although steps are being > taken to greatly reduce this time, it could still take up to several minutes > for this request to go through. > The web client currently doesn't wait long enough for the upgrade to being. > It will produce an error message saying that the upgrade could not be created > and then gets confused when the upgrade eventually shows up. It also allows a > user to try to create another upgrade while the first is still being > generated. > STR: > - Create a rolling upgrade on a cluster with 1000 hosts where every host has > 15 components installed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20759) The Web Client Upgrade Wizard Does Not Wait Long Enough When Creating a Large Upgrade
[ https://issues.apache.org/jira/browse/AMBARI-20759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-20759: - Status: Patch Available (was: Open) > The Web Client Upgrade Wizard Does Not Wait Long Enough When Creating a Large > Upgrade > - > > Key: AMBARI-20759 > URL: https://issues.apache.org/jira/browse/AMBARI-20759 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.5.1 > > Attachments: AMBARI-20759.patch > > > When creating an upgrade on a large cluster, the backend currently takes a > very long time to create the data and persist it. Although steps are being > taken to greatly reduce this time, it could still take up to several minutes > for this request to go through. > The web client currently doesn't wait long enough for the upgrade to being. > It will produce an error message saying that the upgrade could not be created > and then gets confused when the upgrade eventually shows up. It also allows a > user to try to create another upgrade while the first is still being > generated. > STR: > - Create a rolling upgrade on a cluster with 1000 hosts where every host has > 15 components installed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20759) The Web Client Upgrade Wizard Does Not Wait Long Enough When Creating a Large Upgrade
Antonenko Alexander created AMBARI-20759: Summary: The Web Client Upgrade Wizard Does Not Wait Long Enough When Creating a Large Upgrade Key: AMBARI-20759 URL: https://issues.apache.org/jira/browse/AMBARI-20759 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.2 Reporter: Antonenko Alexander Assignee: Antonenko Alexander Fix For: 2.5.1 When creating an upgrade on a large cluster, the backend currently takes a very long time to create the data and persist it. Although steps are being taken to greatly reduce this time, it could still take up to several minutes for this request to go through. The web client currently doesn't wait long enough for the upgrade to being. It will produce an error message saying that the upgrade could not be created and then gets confused when the upgrade eventually shows up. It also allows a user to try to create another upgrade while the first is still being generated. STR: - Create a rolling upgrade on a cluster with 1000 hosts where every host has 15 components installed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20757) Selecting ignore service checks results in blank dialog box when hitting an error
[ https://issues.apache.org/jira/browse/AMBARI-20757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-20757: Status: Open (was: Patch Available) > Selecting ignore service checks results in blank dialog box when hitting an > error > - > > Key: AMBARI-20757 > URL: https://issues.apache.org/jira/browse/AMBARI-20757 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk, 2.5.0 >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Fix For: trunk > > > In order to see what has gone wrong, you need to drill down into the last > step until you find the service check that failed. Ideally there would be a > message above where they normally appear. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
