[jira] [Created] (AMBARI-24653) YARN Timeline server v2 related system tests fail.
Aravindan Vijayan created AMBARI-24653: -- Summary: YARN Timeline server v2 related system tests fail. Key: AMBARI-24653 URL: https://issues.apache.org/jira/browse/AMBARI-24653 Project: Ambari Issue Type: Bug Affects Versions: 2.7.2 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Fix For: 2.7.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24648) Log Search: add simple file based authorization
[ https://issues.apache.org/jira/browse/AMBARI-24648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24648: Labels: pull-request-available (was: ) > Log Search: add simple file based authorization > > > Key: AMBARI-24648 > URL: https://issues.apache.org/jira/browse/AMBARI-24648 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > > Make a simple way to authorize users. > At fist just create a simple one where you can list to users (who can be > admin or simple user) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24648) Log Search: add simple file based authorization
[ https://issues.apache.org/jira/browse/AMBARI-24648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-24648: -- Summary: Log Search: add simple file based authorization (was: Log Search: add simple authorization ) > Log Search: add simple file based authorization > > > Key: AMBARI-24648 > URL: https://issues.apache.org/jira/browse/AMBARI-24648 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Fix For: 3.0.0 > > > Make a simple way to authorize users. > At fist just create a simple one where you can list to users (who can be > admin or simple user) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24652) Grafana failed to show data for custom metrics
[
https://issues.apache.org/jira/browse/AMBARI-24652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
amarnath reddy pappu updated AMBARI-24652:
--
Description:
*Steps to reproduce:
*
1. First generate metrics and post it to AMS.
curl --header "Content-Type: application/json" -X POST
http://apappu3.hdp.com:6188/ws/v1/timeline/metrics --data @data1.json
{noformat}
{
"metrics": [
{
"metricname": "AMBARI_METRICS.SmokeTest.FakeMetric",
"appid": "AMS-TEST-APPID",
"hostname": "ambari20-5",
"timestamp": 1537211229000,
"starttime": 1537211229000,
"metrics": {
"1537211229000": 0.963781711428,
"153721123": 1432075898000
}
}
]
}
{noformat}
2. Now make REST api call to see if the data is present.
http://apappu3.hdp.com:3000/api/datasources/proxy/1/ws/v1/timeline/metrics?metricNames=AMBARI_METRICS.SmokeTest.FakeMetric._avg=%=AMS-TEST-APPID
This does not return any data - reason for this is , while writing it takes the
appid as case sensitive but while reading always looks for lower case appid.
Workaround: change the appid from "AMS-TEST-APPID" to "ams-test-appid" (all
lower case)- then GET REST API works fine.
was:
Steps to reproduce:
1. First generate metrics and post it to AMS.
curl --header "Content-Type: application/json" -X POST
http://apappu3.hdp.com:6188/ws/v1/timeline/metrics --data @data1.json
{noformat}
{
"metrics": [
{
"metricname": "AMBARI_METRICS.SmokeTest.FakeMetric",
"appid": "AMS-TEST-APPID",
"hostname": "ambari20-5",
"timestamp": 1537211229000,
"starttime": 1537211229000,
"metrics": {
"1537211229000": 0.963781711428,
"153721123": 1432075898000
}
}
]
}
{noformat}
2. Now make REST api call to see if the data is present.
http://apappu3.hdp.com:3000/api/datasources/proxy/1/ws/v1/timeline/metrics?metricNames=AMBARI_METRICS.SmokeTest.FakeMetric._avg=%=AMS-TEST-APPID
Note that app*i*d is lowercase "i" not appId
3. Now generate a new dashboard in grafana and then generate a Graph.
select the component name as "AMS-TEST-APPID" - here Grafana sends "appId"
instead of "appid" and it does not get any data.
If we try to post REST API with appId (upper case I) call would fail.
So AMS should accept the REST calls with appId and then it may work with Grafana
> Grafana failed to show data for custom metrics
> --
>
> Key: AMBARI-24652
> URL: https://issues.apache.org/jira/browse/AMBARI-24652
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.6.2
>Reporter: amarnath reddy pappu
>Priority: Major
>
> *Steps to reproduce:
> *
> 1. First generate metrics and post it to AMS.
> curl --header "Content-Type: application/json" -X POST
> http://apappu3.hdp.com:6188/ws/v1/timeline/metrics --data @data1.json
> {noformat}
> {
> "metrics": [
> {
> "metricname": "AMBARI_METRICS.SmokeTest.FakeMetric",
> "appid": "AMS-TEST-APPID",
> "hostname": "ambari20-5",
> "timestamp": 1537211229000,
> "starttime": 1537211229000,
> "metrics": {
> "1537211229000": 0.963781711428,
> "153721123": 1432075898000
> }
> }
> ]
> }
> {noformat}
> 2. Now make REST api call to see if the data is present.
> http://apappu3.hdp.com:3000/api/datasources/proxy/1/ws/v1/timeline/metrics?metricNames=AMBARI_METRICS.SmokeTest.FakeMetric._avg=%=AMS-TEST-APPID
> This does not return any data - reason for this is , while writing it takes
> the appid as case sensitive but while reading always looks for lower case
> appid.
> Workaround: change the appid from "AMS-TEST-APPID" to "ams-test-appid" (all
> lower case)- then GET REST API works fine.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24652) Grafana failed to show data for custom metrics
amarnath reddy pappu created AMBARI-24652:
-
Summary: Grafana failed to show data for custom metrics
Key: AMBARI-24652
URL: https://issues.apache.org/jira/browse/AMBARI-24652
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: trunk, 2.6.2
Reporter: amarnath reddy pappu
Steps to reproduce:
1. First generate metrics and post it to AMS.
curl --header "Content-Type: application/json" -X POST
http://apappu3.hdp.com:6188/ws/v1/timeline/metrics --data @data1.json
{noformat}
{
"metrics": [
{
"metricname": "AMBARI_METRICS.SmokeTest.FakeMetric",
"appid": "AMS-TEST-APPID",
"hostname": "ambari20-5",
"timestamp": 1537211229000,
"starttime": 1537211229000,
"metrics": {
"1537211229000": 0.963781711428,
"153721123": 1432075898000
}
}
]
}
{noformat}
2. Now make REST api call to see if the data is present.
http://apappu3.hdp.com:3000/api/datasources/proxy/1/ws/v1/timeline/metrics?metricNames=AMBARI_METRICS.SmokeTest.FakeMetric._avg=%=AMS-TEST-APPID
Note that app*i*d is lowercase "i" not appId
3. Now generate a new dashboard in grafana and then generate a Graph.
select the component name as "AMS-TEST-APPID" - here Grafana sends "appId"
instead of "appid" and it does not get any data.
If we try to post REST API with appId (upper case I) call would fail.
So AMS should accept the REST calls with appId and then it may work with Grafana
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24644) Log Search: support trusted knox proxy
[ https://issues.apache.org/jira/browse/AMBARI-24644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618159#comment-16618159 ] Hudson commented on AMBARI-24644: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9965 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9965/]) AMBARI-24644. ADDENDUM - Log Search - Fix IP address setter (oleewere: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=7289a4faa8389b112abfd318133bf2c53ae2cba8]) * (edit) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/conf/AuthPropsConfig.java > Log Search: support trusted knox proxy > -- > > Key: AMBARI-24644 > URL: https://issues.apache.org/jira/browse/AMBARI-24644 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.1 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Blocker > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24638) Ambari-agent process memory leak
[ https://issues.apache.org/jira/browse/AMBARI-24638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618025#comment-16618025 ] Hudson commented on AMBARI-24638: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #300 (See [https://builds.apache.org/job/Ambari-branch-2.7/300/]) AMBARI-24638. Ambari-agent process consuming more memory. (aonishuk) (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=57df9febbbf6bec44efd67b198d9d0e0f8a69d8a]) * (edit) ambari-common/src/main/python/ambari_ws4py/websocket.py > Ambari-agent process memory leak > > > Key: AMBARI-24638 > URL: https://issues.apache.org/jira/browse/AMBARI-24638 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > Attachments: AMBARI-24638.patch, AMBARI-24638.patch > > Time Spent: 1h 20m > Remaining Estimate: 0h > > There was one process which started using memory rapidly at certain point and > grew up to ~27GB of RSS used until eventually we restarted it. Which happened > after a month of running of 10 ambari-agent nodes. > [root@andrew2-1n01 ~]# ps aux | grep ambari_agent > root 39955 0.0 0.0 47580 6024 ?SAug17 0:00 > /usr/bin/python /usr/lib/ambari-agent/lib/ambari_agent/AmbariAgent.py start > root 39959 20.4 10.2 31623096 27154348 ? Sl Aug17 7645:55 > /usr/bin/python /usr/lib/ambari-agent/lib/ambari_agent/main.py start > Just before the growth in memory usage is seen. This exception pops out: > ERROR 2018-09-11 10:56:59,716 websocket.py:552 - Websocket connection was > closed with an exception > Traceback (most recent call last): > File "/usr/lib/ambari-agent/lib/ambari_ws4py/websocket.py", line 549, in run > if not self.once(): > File "/usr/lib/ambari-agent/lib/ambari_ws4py/websocket.py", line 428, in > once > if not self.process(self.buf[:requested]): > File "/usr/lib/ambari-agent/lib/ambari_ws4py/websocket.py", line 483, in > process > self.reading_buffer_size = s.parser.send(bytes) or DEFAULT_READING_SIZE > ValueError: generator already executing > This exception is not seen on all other nodes or on this one at any other > period (during 1 month). So I suggest it can be the root cause. > Basically this error means that generator is being used by multiple threads. > So I will upload the fix to thread-lock this place. > This is just a guess solution which might work and might not. No way to test > really. But definitely we should try this. > > This is noticed in ambari-2.7.1.0-73 version as well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24646) 'ambari-server setup-ldap' fails with AttributeError when master_key is not persisted
[
https://issues.apache.org/jira/browse/AMBARI-24646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618027#comment-16618027
]
Hudson commented on AMBARI-24646:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #300 (See
[https://builds.apache.org/job/Ambari-branch-2.7/300/])
AMBARI-24646 'ambari-server setup-ldap' fails with AttributeError when (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=80ecad698d0bb1c43788bc09b77d539fb937e402])
* (edit) ambari-server/src/main/python/ambari_server/serverConfiguration.py
> 'ambari-server setup-ldap' fails with AttributeError when master_key is not
> persisted
> -
>
> Key: AMBARI-24646
> URL: https://issues.apache.org/jira/browse/AMBARI-24646
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> *STR*
> Installed ambari-server and configured password encryption, but chose not to
> persist master key
> {code}
> [root@ctr ~]# ambari-server setup-security
> Using python /usr/bin/python
> Security setup options...
> ===
> Choose one of the following options:
> [1] Enable HTTPS for Ambari server.
> [2] Encrypt passwords stored in ambari.properties file.
> [3] Setup Ambari kerberos JAAS configuration.
> [4] Setup truststore.
> [5] Import certificate to truststore.
> ===
> Enter choice, (1-5): 2
> Password encryption is enabled.
> Do you want to reset Master Key? [y/n] (n): y
> Master Key not persisted.
> Enter current Master Key:
> Enter new Master Key:
> Re-enter master key:
> Do you want to persist master key. If you choose not to persist, you need to
> provide the Master Key while starting the ambari server as an env variable
> named AMBARI_SECURITY_MASTER_KEY or the start will prompt for the master key.
> Persist [y/n] (y)? n
> Adjusting ambari-server permissions and ownership...
> Ambari Server 'setup-security' completed successfully.
> {code}
> Then export environment variable
> export AMBARI_SECURITY_MASTER_KEY=hadoop
> Thereafter ran the following:
> *Issue #1* - Gave AttributeError after accepting the 'Save settings' prompt,
> instead of asking for master key
> {code}
> [root@ctr ~]# ambari-server setup-ldap -v
> Using python /usr/bin/python
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: about to run command: ps -p 5596
> INFO:
> process_pid=12677
> Please select the type of LDAP you want to use (AD, IPA, Generic
> LDAP):Generic LDAP
> Primary LDAP Host (ldap.ambari.apache.org): ctr
> Primary LDAP Port (389):
> Secondary LDAP Host :
> Secondary LDAP Port :
> Use SSL [true/false] (false):
> User object class (posixUser):
> User ID attribute (uid):
> Group object class (posixGroup):
> Group name attribute (cn):
> Group member attribute (memberUid):
> Distinguished name attribute (dn):
> Search Base (dc=ambari,dc=apache,dc=org): dc=apache,dc=org
> Referral method [follow/ignore] (follow):
> Bind anonymously [true/false] (false):
> Bind DN (uid=ldapbind,cn=users,dc=ambari,dc=apache,dc=org):
> uid=hdfs,ou=people,ou=dev,dc=apache,dc=org
> Enter Bind DN Password:
> Confirm Bind DN Password:
> Handling behavior for username collisions [convert/skip] for LDAP sync (skip):
> Force lower-case user names [true/false]:
> Results from LDAP are paginated when requested [true/false]:
>
> Review Settings
>
> Primary LDAP Host (ldap.ambari.apache.org): ctr
> Primary LDAP Port (389): 389
> Use SSL [true/false] (false): false
> User object class (posixUser): posixUser
> User ID attribute (uid): uid
> Group object class (posixGroup): posixGroup
> Group name attribute (cn): cn
> Group member attribute (memberUid): memberUid
> Distinguished name attribute (dn): dn
> Search Base (dc=ambari,dc=apache,dc=org): dc=apache,dc=org
> Referral method [follow/ignore] (follow): follow
> Bind anonymously [true/false] (false): false
> Handling behavior for username collisions [convert/skip] for LDAP sync
> (skip): skip
> ambari.ldap.connectivity.bind_dn: uid=hdfs,ou=people,ou=dev,dc=apache,dc=org
> ambari.ldap.connectivity.bind_password: *
> Save settings [y/n] (y)? y
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Traceback (most recent call last):
> File "/usr/sbin/ambari-server.py", line 1060, in
> mainBody()
> File
[jira] [Commented] (AMBARI-24641) Stackadvisor error while trying to add atlas service. Error - "if mountPoints[mountPoint] < reqiuredDiskSpace: KeyError: None"
[
https://issues.apache.org/jira/browse/AMBARI-24641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618023#comment-16618023
]
Hudson commented on AMBARI-24641:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #300 (See
[https://builds.apache.org/job/Ambari-branch-2.7/300/])
AMBARI-24641. Stackadvisor error while trying to add atlas service. E… (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=b18e2954b4f58e8725c2bef93862da9a4f80b84d])
* (edit) ambari-agent/src/main/python/ambari_agent/Hardware.py
* (edit)
contrib/management-packs/odpi-ambari-mpack/src/main/resources/stacks/ODPi/2.0/services/stack_advisor.py
* (edit) ambari-server/src/main/resources/stacks/stack_advisor.py
* (edit)
contrib/management-packs/hdf-ambari-mpack/src/main/resources/stacks/HDF/2.0/services/stack_advisor.py
* (edit) ambari-agent/src/test/python/ambari_agent/TestHardware.py
> Stackadvisor error while trying to add atlas service. Error - "if
> mountPoints[mountPoint] < reqiuredDiskSpace: KeyError: None"
> --
>
> Key: AMBARI-24641
> URL: https://issues.apache.org/jira/browse/AMBARI-24641
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.7.0
>Reporter: Attila Magyar
>Assignee: Attila Magyar
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.2
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Stack advisor error:
> {code}
> Error details: None
> 2018-09-11 06:40:09,738 INFO [ambari-client-thread-24150]
> StackAdvisorRunner:167 - Advisor script stderr: Traceback (most recent
> call last):
> File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 184,
> in
> main(sys.argv)
> File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 138,
> in main
> result = stackAdvisor.validateConfigurations(services, hosts)
> File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
> line 1079, in validateConfigurations
> validationItems = self.getConfigurationsValidationItems(services, hosts)
> File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
> line 1468, in getConfigurationsValidationItems
>
> items.extend(self.getConfigurationsValidationItemsForService(configurations,
> recommendedDefaults, service, services, hosts))
> File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
> line 1521, in getConfigurationsValidationItemsForService
>
> items.extend(serviceAdvisor.getServiceConfigurationsValidationItems(configurations,
> recommendedDefaults, services, hosts))
> File
> "/var/lib/ambari-server/resources/stacks/HDP/3.0/services/AMBARI_METRICS/service_advisor.py",
> line 218, in getServiceConfigurationsValidationItems
> return validator.validateListOfConfigUsingMethod(configurations,
> recommendedDefaults, services, hosts, validator.validators)
> File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
> line 1491, in validateListOfConfigUsingMethod
> validationItems = method(siteProperties, siteRecommendations,
> configurations, services, hosts)
> File
> "/var/lib/ambari-server/resources/stacks/HDP/3.0/services/AMBARI_METRICS/service_advisor.py",
> line 556, in validateAmsHbaseSiteConfigurationsFromHDP206
> validationItems.extend([{"config-name": 'hbase.rootdir', "item":
> self.validatorEnoughDiskSpace(properties, 'hbase.rootdir', host["Hosts"],
> recommendedDiskSpace)}])
> File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
> line 2998, in validatorEnoughDiskSpace
> if mountPoints[mountPoint] < reqiuredDiskSpace:
> KeyError: None
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24635) Web Client Chooses Wrong Version When Reverting Configs
[
https://issues.apache.org/jira/browse/AMBARI-24635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618026#comment-16618026
]
Hudson commented on AMBARI-24635:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #300 (See
[https://builds.apache.org/job/Ambari-branch-2.7/300/])
AMBARI-24635. Web Client Chooses Wrong Version When Reverting Configs
(aleksandrkovalenko:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=74d801e99a58f5cb7d0bf6176fe1af19a1f4e8e8])
* (edit) ambari-web/app/views/common/configs/config_versions_control_view.js
* (edit) ambari-web/app/templates/common/configs/config_versions_control.hbs
AMBARI-24635. Web Client Chooses Wrong Version When Reverting Configs
(aleksandrkovalenko:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=9177549950acb645a73b3e0d9bccfc1e81232a69])
* (edit)
ambari-web/test/views/common/configs/config_versions_control_view_test.js
> Web Client Chooses Wrong Version When Reverting Configs
> ---
>
> Key: AMBARI-24635
> URL: https://issues.apache.org/jira/browse/AMBARI-24635
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.2
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.2
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> STR:
> - Setup a simple cluster with ZK, HDFS, YARN, Hive, Pig
> - Create at least 5 different configuration versions for Pig
> - Load the Pig configuration page and select v4
> - Now select V3 and then choose "Make Current"
> At this point, the web client will populate a dialog that says {{Created from
> service config version V4}} and indeed it restores v4, not v3.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24647) [PERF] Host checks taking longer time than previous releases
[ https://issues.apache.org/jira/browse/AMBARI-24647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618024#comment-16618024 ] Hudson commented on AMBARI-24647: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #300 (See [https://builds.apache.org/job/Ambari-branch-2.7/300/]) AMBARI-24647. [PERF] Host checks taking longer time than previous (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=eb515fa4f85a56c7f0d1f2a16a9fcd0cd5e2ed7f]) * (add) ambari-server/src/main/resources/stacks/PERF/check_host.sed * (edit) contrib/utils/perf/deploy-gce-perf-cluster.py > [PERF] Host checks taking longer time than previous releases > > > Key: AMBARI-24647 > URL: https://issues.apache.org/jira/browse/AMBARI-24647 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > Attachments: AMBARI-24647.patch > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24651) Add cluster and stack settings properties to agent STOMP updates
Myroslav Papirkovskyi created AMBARI-24651: -- Summary: Add cluster and stack settings properties to agent STOMP updates Key: AMBARI-24651 URL: https://issues.apache.org/jira/browse/AMBARI-24651 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 3.0.0 Reporter: Myroslav Papirkovskyi Assignee: Myroslav Papirkovskyi Fix For: 3.0.0 Server should post cluster settings and stack settings to agent with STOMP updates. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24650) Ambari certification on " HA/Oracle RAC connection"
[ https://issues.apache.org/jira/browse/AMBARI-24650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] amarnath reddy pappu updated AMBARI-24650: -- Description: Some of the customers wants Ambari to be certified with "HA/Oracle RAC connection". was: Some of the customers Ambari to be certified with "HA/Oracle RAC connection". > Ambari certification on " HA/Oracle RAC connection" > --- > > Key: AMBARI-24650 > URL: https://issues.apache.org/jira/browse/AMBARI-24650 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.6.2 >Reporter: amarnath reddy pappu >Priority: Major > > Some of the customers wants Ambari to be certified with "HA/Oracle RAC > connection". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24650) Ambari certification on " HA/Oracle RAC connection"
amarnath reddy pappu created AMBARI-24650: - Summary: Ambari certification on " HA/Oracle RAC connection" Key: AMBARI-24650 URL: https://issues.apache.org/jira/browse/AMBARI-24650 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: trunk, 2.6.2 Reporter: amarnath reddy pappu Some of the customers Ambari to be certified with "HA/Oracle RAC connection". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24616) Disable Kerberos from Ambari UI didn't clean up keytab directories
[
https://issues.apache.org/jira/browse/AMBARI-24616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-24616:
--
Status: Patch Available (was: In Progress)
> Disable Kerberos from Ambari UI didn't clean up keytab directories
> --
>
> Key: AMBARI-24616
> URL: https://issues.apache.org/jira/browse/AMBARI-24616
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.1
>Reporter: Kishor Ramakrishnan
>Assignee: Robert Levas
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.2
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> Disable Kerberos from Ambari UI didn't clean up keytab directories,
> stderr:
> {code:java}
> 2018-09-08 05:27:19,276 - Failed to remove identity for
> amsmon/ctr-e138-1518143905142-467151-01-02.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:19,298 - Failed to remove identity for
> amsmon/ctr-e138-1518143905142-467151-01-06.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:19,325 - Failed to remove identity for
> amsmon/ctr-e138-1518143905142-467151-01-05.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:19,348 - Failed to remove identity for
> amsmon/ctr-e138-1518143905142-467151-01-03.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:19,465 - Failed to remove identity for
> dn/ctr-e138-1518143905142-467151-01-03.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:19,491 - Failed to remove identity for
> dn/ctr-e138-1518143905142-467151-01-02.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:19,515 - Failed to remove identity for
> dn/ctr-e138-1518143905142-467151-01-05.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:19,539 - Failed to remove identity for
> dn/ctr-e138-1518143905142-467151-01-04.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:19,671 - Failed to remove identity for
> hbase/ctr-e138-1518143905142-467151-01-06.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:19,696 - Failed to remove identity for
> hbase/ctr-e138-1518143905142-467151-01-03.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:19,723 - Failed to remove identity for
> hbase/ctr-e138-1518143905142-467151-01-04.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:19,744 - Failed to remove identity for
> hbase/ctr-e138-1518143905142-467151-01-02.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:19,959 - Failed to remove identity for
> nm/ctr-e138-1518143905142-467151-01-05.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:19,987 - Failed to remove identity for
> nm/ctr-e138-1518143905142-467151-01-06.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:20,049 - Failed to remove identity for
> nn/ctr-e138-1518143905142-467151-01-03.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:20,376 - Failed to remove identity for
> HTTP/ctr-e138-1518143905142-467151-01-02.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:20,399 - Failed to remove identity for
> HTTP/ctr-e138-1518143905142-467151-01-04.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:20,420 - Failed to remove identity for
> HTTP/ctr-e138-1518143905142-467151-01-03.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:20,441 - Failed to remove identity for
> HTTP/ctr-e138-1518143905142-467151-01-05.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:20,590 - Failed to remove identity for
> yarn-ats-hbase/ctr-e138-1518143905142-467151-01-03.hwx.s...@example.com
> from the Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:20,617 - Failed to remove identity for
>
[jira] [Commented] (AMBARI-24635) Web Client Chooses Wrong Version When Reverting Configs
[
https://issues.apache.org/jira/browse/AMBARI-24635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617752#comment-16617752
]
Hudson commented on AMBARI-24635:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9964 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9964/])
AMBARI-24635. Web Client Chooses Wrong Version When Reverting Configs
(aleksandrkovalenko:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=60f0b5edb2e5d53e47b008148678c56d5ff47b0e])
* (edit) ambari-web/app/templates/common/configs/config_versions_control.hbs
* (edit) ambari-web/app/views/common/configs/config_versions_control_view.js
AMBARI-24635. Web Client Chooses Wrong Version When Reverting Configs
(aleksandrkovalenko:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=f4417ffa9b81c0072181295a6738129cf6a61bd8])
* (edit)
ambari-web/test/views/common/configs/config_versions_control_view_test.js
> Web Client Chooses Wrong Version When Reverting Configs
> ---
>
> Key: AMBARI-24635
> URL: https://issues.apache.org/jira/browse/AMBARI-24635
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.2
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.2
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> STR:
> - Setup a simple cluster with ZK, HDFS, YARN, Hive, Pig
> - Create at least 5 different configuration versions for Pig
> - Load the Pig configuration page and select v4
> - Now select V3 and then choose "Make Current"
> At this point, the web client will populate a dialog that says {{Created from
> service config version V4}} and indeed it restores v4, not v3.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24616) Disable Kerberos from Ambari UI didn't clean up keytab directories
[
https://issues.apache.org/jira/browse/AMBARI-24616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24616:
Labels: pull-request-available (was: )
> Disable Kerberos from Ambari UI didn't clean up keytab directories
> --
>
> Key: AMBARI-24616
> URL: https://issues.apache.org/jira/browse/AMBARI-24616
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.1
>Reporter: Kishor Ramakrishnan
>Assignee: Robert Levas
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.2
>
>
> Disable Kerberos from Ambari UI didn't clean up keytab directories,
> stderr:
> {code:java}
> 2018-09-08 05:27:19,276 - Failed to remove identity for
> amsmon/ctr-e138-1518143905142-467151-01-02.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:19,298 - Failed to remove identity for
> amsmon/ctr-e138-1518143905142-467151-01-06.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:19,325 - Failed to remove identity for
> amsmon/ctr-e138-1518143905142-467151-01-05.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:19,348 - Failed to remove identity for
> amsmon/ctr-e138-1518143905142-467151-01-03.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:19,465 - Failed to remove identity for
> dn/ctr-e138-1518143905142-467151-01-03.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:19,491 - Failed to remove identity for
> dn/ctr-e138-1518143905142-467151-01-02.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:19,515 - Failed to remove identity for
> dn/ctr-e138-1518143905142-467151-01-05.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:19,539 - Failed to remove identity for
> dn/ctr-e138-1518143905142-467151-01-04.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:19,671 - Failed to remove identity for
> hbase/ctr-e138-1518143905142-467151-01-06.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:19,696 - Failed to remove identity for
> hbase/ctr-e138-1518143905142-467151-01-03.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:19,723 - Failed to remove identity for
> hbase/ctr-e138-1518143905142-467151-01-04.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:19,744 - Failed to remove identity for
> hbase/ctr-e138-1518143905142-467151-01-02.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:19,959 - Failed to remove identity for
> nm/ctr-e138-1518143905142-467151-01-05.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:19,987 - Failed to remove identity for
> nm/ctr-e138-1518143905142-467151-01-06.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:20,049 - Failed to remove identity for
> nn/ctr-e138-1518143905142-467151-01-03.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:20,376 - Failed to remove identity for
> HTTP/ctr-e138-1518143905142-467151-01-02.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:20,399 - Failed to remove identity for
> HTTP/ctr-e138-1518143905142-467151-01-04.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:20,420 - Failed to remove identity for
> HTTP/ctr-e138-1518143905142-467151-01-03.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:20,441 - Failed to remove identity for
> HTTP/ctr-e138-1518143905142-467151-01-05.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:20,590 - Failed to remove identity for
> yarn-ats-hbase/ctr-e138-1518143905142-467151-01-03.hwx.s...@example.com
> from the Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:20,617 - Failed to remove identity for
>
[jira] [Updated] (AMBARI-24646) 'ambari-server setup-ldap' fails with AttributeError when master_key is not persisted
[
https://issues.apache.org/jira/browse/AMBARI-24646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24646:
Labels: pull-request-available (was: )
> 'ambari-server setup-ldap' fails with AttributeError when master_key is not
> persisted
> -
>
> Key: AMBARI-24646
> URL: https://issues.apache.org/jira/browse/AMBARI-24646
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.2
>
>
> *STR*
> Installed ambari-server and configured password encryption, but chose not to
> persist master key
> {code}
> [root@ctr ~]# ambari-server setup-security
> Using python /usr/bin/python
> Security setup options...
> ===
> Choose one of the following options:
> [1] Enable HTTPS for Ambari server.
> [2] Encrypt passwords stored in ambari.properties file.
> [3] Setup Ambari kerberos JAAS configuration.
> [4] Setup truststore.
> [5] Import certificate to truststore.
> ===
> Enter choice, (1-5): 2
> Password encryption is enabled.
> Do you want to reset Master Key? [y/n] (n): y
> Master Key not persisted.
> Enter current Master Key:
> Enter new Master Key:
> Re-enter master key:
> Do you want to persist master key. If you choose not to persist, you need to
> provide the Master Key while starting the ambari server as an env variable
> named AMBARI_SECURITY_MASTER_KEY or the start will prompt for the master key.
> Persist [y/n] (y)? n
> Adjusting ambari-server permissions and ownership...
> Ambari Server 'setup-security' completed successfully.
> {code}
> Then export environment variable
> export AMBARI_SECURITY_MASTER_KEY=hadoop
> Thereafter ran the following:
> *Issue #1* - Gave AttributeError after accepting the 'Save settings' prompt,
> instead of asking for master key
> {code}
> [root@ctr ~]# ambari-server setup-ldap -v
> Using python /usr/bin/python
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: about to run command: ps -p 5596
> INFO:
> process_pid=12677
> Please select the type of LDAP you want to use (AD, IPA, Generic
> LDAP):Generic LDAP
> Primary LDAP Host (ldap.ambari.apache.org): ctr
> Primary LDAP Port (389):
> Secondary LDAP Host :
> Secondary LDAP Port :
> Use SSL [true/false] (false):
> User object class (posixUser):
> User ID attribute (uid):
> Group object class (posixGroup):
> Group name attribute (cn):
> Group member attribute (memberUid):
> Distinguished name attribute (dn):
> Search Base (dc=ambari,dc=apache,dc=org): dc=apache,dc=org
> Referral method [follow/ignore] (follow):
> Bind anonymously [true/false] (false):
> Bind DN (uid=ldapbind,cn=users,dc=ambari,dc=apache,dc=org):
> uid=hdfs,ou=people,ou=dev,dc=apache,dc=org
> Enter Bind DN Password:
> Confirm Bind DN Password:
> Handling behavior for username collisions [convert/skip] for LDAP sync (skip):
> Force lower-case user names [true/false]:
> Results from LDAP are paginated when requested [true/false]:
>
> Review Settings
>
> Primary LDAP Host (ldap.ambari.apache.org): ctr
> Primary LDAP Port (389): 389
> Use SSL [true/false] (false): false
> User object class (posixUser): posixUser
> User ID attribute (uid): uid
> Group object class (posixGroup): posixGroup
> Group name attribute (cn): cn
> Group member attribute (memberUid): memberUid
> Distinguished name attribute (dn): dn
> Search Base (dc=ambari,dc=apache,dc=org): dc=apache,dc=org
> Referral method [follow/ignore] (follow): follow
> Bind anonymously [true/false] (false): false
> Handling behavior for username collisions [convert/skip] for LDAP sync
> (skip): skip
> ambari.ldap.connectivity.bind_dn: uid=hdfs,ou=people,ou=dev,dc=apache,dc=org
> ambari.ldap.connectivity.bind_password: *
> Save settings [y/n] (y)? y
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Traceback (most recent call last):
> File "/usr/sbin/ambari-server.py", line 1060, in
> mainBody()
> File "/usr/sbin/ambari-server.py", line 1030, in mainBody
> main(options, args, parser)
> File "/usr/sbin/ambari-server.py", line 980, in main
> action_obj.execute()
> File "/usr/sbin/ambari-server.py", line 79, in execute
> self.fn(*self.args, **self.kwargs)
> File "/usr/lib/ambari-server/lib/ambari_server/setupSecurity.py", line 860,
> in setup_ldap
> encrypted_passwd = encrypt_password(LDAP_MGR_PASSWORD_ALIAS, mgr_password,
>
[jira] [Commented] (AMBARI-24644) Log Search: support trusted knox proxy
[ https://issues.apache.org/jira/browse/AMBARI-24644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617678#comment-16617678 ] Hudson commented on AMBARI-24644: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9963 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9963/]) AMBARI-24644. Log Search: support trusted knox proxy. (#2327) (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=9d307c8758088cde7e7fb9a960525c9e6bc7f799]) * (add) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/web/filters/LogsearchTrustedProxyFilter.java * (edit) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/conf/SecurityConfig.java * (edit) ambari-logsearch/docker/test-config/logsearch/logsearch-sso.properties * (edit) ambari-logsearch/docker/Dockerfile * (edit) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/conf/AuthPropsConfig.java > Log Search: support trusted knox proxy > -- > > Key: AMBARI-24644 > URL: https://issues.apache.org/jira/browse/AMBARI-24644 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.1 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Blocker > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24648) Log Search: add simple authorization
[ https://issues.apache.org/jira/browse/AMBARI-24648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-24648: -- Component/s: ambari-logsearch > Log Search: add simple authorization > - > > Key: AMBARI-24648 > URL: https://issues.apache.org/jira/browse/AMBARI-24648 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Fix For: 3.0.0 > > > Make a simple way to authorize users. > At fist just create a simple one where you can list to users (who can be > admin or simple user) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24638) Ambari-agent process memory leak
[ https://issues.apache.org/jira/browse/AMBARI-24638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617559#comment-16617559 ] Hudson commented on AMBARI-24638: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9962 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9962/]) AMBARI-24638. Ambari-agent process consuming more memory. (aonishuk) (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=4db8904e67cd814bd775243717e049d95e2f92e1]) * (edit) ambari-common/src/main/python/ambari_ws4py/websocket.py > Ambari-agent process memory leak > > > Key: AMBARI-24638 > URL: https://issues.apache.org/jira/browse/AMBARI-24638 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > Attachments: AMBARI-24638.patch, AMBARI-24638.patch > > Time Spent: 1h 20m > Remaining Estimate: 0h > > There was one process which started using memory rapidly at certain point and > grew up to ~27GB of RSS used until eventually we restarted it. Which happened > after a month of running of 10 ambari-agent nodes. > [root@andrew2-1n01 ~]# ps aux | grep ambari_agent > root 39955 0.0 0.0 47580 6024 ?SAug17 0:00 > /usr/bin/python /usr/lib/ambari-agent/lib/ambari_agent/AmbariAgent.py start > root 39959 20.4 10.2 31623096 27154348 ? Sl Aug17 7645:55 > /usr/bin/python /usr/lib/ambari-agent/lib/ambari_agent/main.py start > Just before the growth in memory usage is seen. This exception pops out: > ERROR 2018-09-11 10:56:59,716 websocket.py:552 - Websocket connection was > closed with an exception > Traceback (most recent call last): > File "/usr/lib/ambari-agent/lib/ambari_ws4py/websocket.py", line 549, in run > if not self.once(): > File "/usr/lib/ambari-agent/lib/ambari_ws4py/websocket.py", line 428, in > once > if not self.process(self.buf[:requested]): > File "/usr/lib/ambari-agent/lib/ambari_ws4py/websocket.py", line 483, in > process > self.reading_buffer_size = s.parser.send(bytes) or DEFAULT_READING_SIZE > ValueError: generator already executing > This exception is not seen on all other nodes or on this one at any other > period (during 1 month). So I suggest it can be the root cause. > Basically this error means that generator is being used by multiple threads. > So I will upload the fix to thread-lock this place. > This is just a guess solution which might work and might not. No way to test > really. But definitely we should try this. > > This is noticed in ambari-2.7.1.0-73 version as well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24647) [PERF] Host checks taking longer time than previous releases
[ https://issues.apache.org/jira/browse/AMBARI-24647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617558#comment-16617558 ] Hudson commented on AMBARI-24647: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9962 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9962/]) AMBARI-24647. [PERF] Host checks taking longer time than previous (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=10706cb851cba628f3fd415620e82dce955a66b9]) * (add) ambari-server/src/main/resources/stacks/PERF/check_host.sed * (edit) contrib/utils/perf/deploy-gce-perf-cluster.py > [PERF] Host checks taking longer time than previous releases > > > Key: AMBARI-24647 > URL: https://issues.apache.org/jira/browse/AMBARI-24647 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > Attachments: AMBARI-24647.patch > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24644) Log Search: support trusted knox proxy
[ https://issues.apache.org/jira/browse/AMBARI-24644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-24644. --- Resolution: Fixed > Log Search: support trusted knox proxy > -- > > Key: AMBARI-24644 > URL: https://issues.apache.org/jira/browse/AMBARI-24644 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.1 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Blocker > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24644) Log Search: support trusted knox proxy
[ https://issues.apache.org/jira/browse/AMBARI-24644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-24644: -- Fix Version/s: (was: 2.7.2) 3.0.0 > Log Search: support trusted knox proxy > -- > > Key: AMBARI-24644 > URL: https://issues.apache.org/jira/browse/AMBARI-24644 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.1 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Blocker > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24649) Add Kafka ZooKeeper ensemble to Kafka service summary page with copy to clipboard, similar to Hive service has for JDBC url with zookeepers
[ https://issues.apache.org/jira/browse/AMBARI-24649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hari Sekhon updated AMBARI-24649: - Summary: Add Kafka ZooKeeper ensemble to Kafka service summary page with copy to clipboard, similar to Hive service has for JDBC url with zookeepers (was: Add Kafka ZooKeeper ensemble to Kafka service summary page with copy to clipboard, similar to Hive has) > Add Kafka ZooKeeper ensemble to Kafka service summary page with copy to > clipboard, similar to Hive service has for JDBC url with zookeepers > --- > > Key: AMBARI-24649 > URL: https://issues.apache.org/jira/browse/AMBARI-24649 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: 2.6.2 >Reporter: Hari Sekhon >Priority: Minor > > Add Kafka ZooKeeper ensemble to Kafka service summary with copy to clipboard > button for convenience to pass to kafka-topics.sh and other kafka commands > --zookeeper switches. > Hive service summary page already has this for HiveServer2 / HS2 Interactive > JDBC urls. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24649) Add Kafka ZooKeeper ensemble to Kafka service summary page with copy to clipboard, similar to Hive has
[ https://issues.apache.org/jira/browse/AMBARI-24649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hari Sekhon updated AMBARI-24649: - Priority: Minor (was: Major) > Add Kafka ZooKeeper ensemble to Kafka service summary page with copy to > clipboard, similar to Hive has > -- > > Key: AMBARI-24649 > URL: https://issues.apache.org/jira/browse/AMBARI-24649 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: 2.6.2 >Reporter: Hari Sekhon >Priority: Minor > > Add Kafka ZooKeeper ensemble to Kafka service summary with copy to clipboard > button for convenience to pass to kafka-topics.sh and other kafka commands > --zookeeper switches. > Hive service summary page already has this for HiveServer2 / HS2 Interactive > JDBC urls. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24649) Add Kafka ZooKeeper ensemble to Kafka service summary page with copy to clipboard, similar to Hive has
Hari Sekhon created AMBARI-24649: Summary: Add Kafka ZooKeeper ensemble to Kafka service summary page with copy to clipboard, similar to Hive has Key: AMBARI-24649 URL: https://issues.apache.org/jira/browse/AMBARI-24649 Project: Ambari Issue Type: Improvement Components: ambari-web Affects Versions: 2.6.2 Reporter: Hari Sekhon Add Kafka ZooKeeper ensemble to Kafka service summary with copy to clipboard button for convenience to pass to kafka-topics.sh and other kafka commands --zookeeper switches. Hive service summary page already has this for HiveServer2 / HS2 Interactive JDBC urls. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24648) Log Search: add simple authorization
[ https://issues.apache.org/jira/browse/AMBARI-24648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-24648: -- Description: Make a simple way to authorize users. At fist just create a simple one where you can list to users (who can be admin or simple user) > Log Search: add simple authorization > - > > Key: AMBARI-24648 > URL: https://issues.apache.org/jira/browse/AMBARI-24648 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Fix For: 3.0.0 > > > Make a simple way to authorize users. > At fist just create a simple one where you can list to users (who can be > admin or simple user) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24648) Log Search: add simple authorization
Olivér Szabó created AMBARI-24648: - Summary: Log Search: add simple authorization Key: AMBARI-24648 URL: https://issues.apache.org/jira/browse/AMBARI-24648 Project: Ambari Issue Type: Bug Affects Versions: 2.7.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24640) Log Search: support to remove suffixes from field names
[
https://issues.apache.org/jira/browse/AMBARI-24640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-24640:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Log Search: support to remove suffixes from field names
> ---
>
> Key: AMBARI-24640
> URL: https://issues.apache.org/jira/browse/AMBARI-24640
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.7.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.2
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> new available properties to remove suffixes:
> {{logsearch.web.labels.service_logs.field.fallback.suffixes=_l,_s,_b,_i}}
> {{logsearch.web.labels.audit_logs.field.fallback.suffixes=_l,_s,_b,_i}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24641) Stackadvisor error while trying to add atlas service. Error - "if mountPoints[mountPoint] < reqiuredDiskSpace: KeyError: None"
[
https://issues.apache.org/jira/browse/AMBARI-24641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617420#comment-16617420
]
Hudson commented on AMBARI-24641:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9957 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9957/])
AMBARI-24641. Stackadvisor error while trying to add atlas service. E… (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=cbb50ad120ac05f89b19cfe1f1bc819860dfd1bb])
* (edit) ambari-agent/src/main/python/ambari_agent/Hardware.py
* (edit) ambari-server/src/main/resources/stacks/stack_advisor.py
* (edit)
contrib/management-packs/hdf-ambari-mpack/src/main/resources/stacks/HDF/2.0/services/stack_advisor.py
* (edit) ambari-agent/src/test/python/ambari_agent/TestHardware.py
* (edit)
contrib/management-packs/odpi-ambari-mpack/src/main/resources/stacks/ODPi/2.0/services/stack_advisor.py
> Stackadvisor error while trying to add atlas service. Error - "if
> mountPoints[mountPoint] < reqiuredDiskSpace: KeyError: None"
> --
>
> Key: AMBARI-24641
> URL: https://issues.apache.org/jira/browse/AMBARI-24641
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.7.0
>Reporter: Attila Magyar
>Assignee: Attila Magyar
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.2
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Stack advisor error:
> {code}
> Error details: None
> 2018-09-11 06:40:09,738 INFO [ambari-client-thread-24150]
> StackAdvisorRunner:167 - Advisor script stderr: Traceback (most recent
> call last):
> File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 184,
> in
> main(sys.argv)
> File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 138,
> in main
> result = stackAdvisor.validateConfigurations(services, hosts)
> File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
> line 1079, in validateConfigurations
> validationItems = self.getConfigurationsValidationItems(services, hosts)
> File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
> line 1468, in getConfigurationsValidationItems
>
> items.extend(self.getConfigurationsValidationItemsForService(configurations,
> recommendedDefaults, service, services, hosts))
> File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
> line 1521, in getConfigurationsValidationItemsForService
>
> items.extend(serviceAdvisor.getServiceConfigurationsValidationItems(configurations,
> recommendedDefaults, services, hosts))
> File
> "/var/lib/ambari-server/resources/stacks/HDP/3.0/services/AMBARI_METRICS/service_advisor.py",
> line 218, in getServiceConfigurationsValidationItems
> return validator.validateListOfConfigUsingMethod(configurations,
> recommendedDefaults, services, hosts, validator.validators)
> File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
> line 1491, in validateListOfConfigUsingMethod
> validationItems = method(siteProperties, siteRecommendations,
> configurations, services, hosts)
> File
> "/var/lib/ambari-server/resources/stacks/HDP/3.0/services/AMBARI_METRICS/service_advisor.py",
> line 556, in validateAmsHbaseSiteConfigurationsFromHDP206
> validationItems.extend([{"config-name": 'hbase.rootdir', "item":
> self.validatorEnoughDiskSpace(properties, 'hbase.rootdir', host["Hosts"],
> recommendedDiskSpace)}])
> File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
> line 2998, in validatorEnoughDiskSpace
> if mountPoints[mountPoint] < reqiuredDiskSpace:
> KeyError: None
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24641) Stackadvisor error while trying to add atlas service. Error - "if mountPoints[mountPoint] < reqiuredDiskSpace: KeyError: None"
[
https://issues.apache.org/jira/browse/AMBARI-24641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Magyar resolved AMBARI-24641.
Resolution: Fixed
> Stackadvisor error while trying to add atlas service. Error - "if
> mountPoints[mountPoint] < reqiuredDiskSpace: KeyError: None"
> --
>
> Key: AMBARI-24641
> URL: https://issues.apache.org/jira/browse/AMBARI-24641
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.7.0
>Reporter: Attila Magyar
>Assignee: Attila Magyar
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.2
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Stack advisor error:
> {code}
> Error details: None
> 2018-09-11 06:40:09,738 INFO [ambari-client-thread-24150]
> StackAdvisorRunner:167 - Advisor script stderr: Traceback (most recent
> call last):
> File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 184,
> in
> main(sys.argv)
> File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 138,
> in main
> result = stackAdvisor.validateConfigurations(services, hosts)
> File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
> line 1079, in validateConfigurations
> validationItems = self.getConfigurationsValidationItems(services, hosts)
> File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
> line 1468, in getConfigurationsValidationItems
>
> items.extend(self.getConfigurationsValidationItemsForService(configurations,
> recommendedDefaults, service, services, hosts))
> File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
> line 1521, in getConfigurationsValidationItemsForService
>
> items.extend(serviceAdvisor.getServiceConfigurationsValidationItems(configurations,
> recommendedDefaults, services, hosts))
> File
> "/var/lib/ambari-server/resources/stacks/HDP/3.0/services/AMBARI_METRICS/service_advisor.py",
> line 218, in getServiceConfigurationsValidationItems
> return validator.validateListOfConfigUsingMethod(configurations,
> recommendedDefaults, services, hosts, validator.validators)
> File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
> line 1491, in validateListOfConfigUsingMethod
> validationItems = method(siteProperties, siteRecommendations,
> configurations, services, hosts)
> File
> "/var/lib/ambari-server/resources/stacks/HDP/3.0/services/AMBARI_METRICS/service_advisor.py",
> line 556, in validateAmsHbaseSiteConfigurationsFromHDP206
> validationItems.extend([{"config-name": 'hbase.rootdir', "item":
> self.validatorEnoughDiskSpace(properties, 'hbase.rootdir', host["Hosts"],
> recommendedDiskSpace)}])
> File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
> line 2998, in validatorEnoughDiskSpace
> if mountPoints[mountPoint] < reqiuredDiskSpace:
> KeyError: None
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24647) [PERF] Host checks taking longer time than previous releases
[ https://issues.apache.org/jira/browse/AMBARI-24647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24647: Labels: pull-request-available (was: ) > [PERF] Host checks taking longer time than previous releases > > > Key: AMBARI-24647 > URL: https://issues.apache.org/jira/browse/AMBARI-24647 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > Attachments: AMBARI-24647.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24647) [PERF] Host checks taking longer time than previous releases
[ https://issues.apache.org/jira/browse/AMBARI-24647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24647: - Attachment: AMBARI-24647.patch > [PERF] Host checks taking longer time than previous releases > > > Key: AMBARI-24647 > URL: https://issues.apache.org/jira/browse/AMBARI-24647 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.2 > > Attachments: AMBARI-24647.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24647) [PERF] Host checks taking longer time than previous releases
Andrew Onischuk created AMBARI-24647: Summary: [PERF] Host checks taking longer time than previous releases Key: AMBARI-24647 URL: https://issues.apache.org/jira/browse/AMBARI-24647 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.7.2 Attachments: AMBARI-24647.patch -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24647) [PERF] Host checks taking longer time than previous releases
[ https://issues.apache.org/jira/browse/AMBARI-24647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24647: - Status: Patch Available (was: Open) > [PERF] Host checks taking longer time than previous releases > > > Key: AMBARI-24647 > URL: https://issues.apache.org/jira/browse/AMBARI-24647 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.2 > > Attachments: AMBARI-24647.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
