[jira] [Commented] (AMBARI-22817) Update backend code to handle new versioning schema
[
https://issues.apache.org/jira/browse/AMBARI-22817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16615485#comment-16615485
]
Hudson commented on AMBARI-22817:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9954 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9954/])
[AMBARI-22817] Update backend code to handle new versioning schema.
(mradhakrishnan:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=611337c928c99222133effb3ad8dc708cdfb8da3])
* (add)
ambari-common/src/main/python/resource_management/libraries/functions/module_version.py
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/utils/TestVersionUtils.java
* (add)
ambari-server/src/main/java/org/apache/ambari/server/utils/MpackVersion.java
* (add)
ambari-common/src/main/python/resource_management/libraries/functions/mpack_version.py
* (add)
ambari-server/src/main/java/org/apache/ambari/server/utils/ModuleVersion.java
* (edit) ambari-server/src/test/python/TestVersion.py
> Update backend code to handle new versioning schema
> ---
>
> Key: AMBARI-22817
> URL: https://issues.apache.org/jira/browse/AMBARI-22817
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Attachments: AMBARI-22817.patch, AMBARI-22817_part2.patch
>
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> The new module and mpack meta rpms will have be versioned as follows
> *Mpack Versioning*
> {code}
> ..-b
> ..-h-b
> {code}
> *Examples*
> {code}
> hdpcore 3.0.0-b123
> hdpcore 3.0.0-h7-b111
> edw 1.0.0-b234
> edw 1.0.0-h15-b7
> {code}
> *Module Versioning*
> {code}
> ...-b
> ...-h-b
> {code}
> *Examples*
> {code}
> hdfs 3.0.0.1-b123
> hdfs 3.0.1.0-h77-b11
> zookeeper 3.5.1.0-b111
> zookeeper 3.5.1.1-h21-b10
> {code}
> We need the BE code (java, python) to handle this versioning schema while
> comparing versions, formatting versions etc.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24645) Issues with tooltip containing custom time range for charts
[ https://issues.apache.org/jira/browse/AMBARI-24645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16615338#comment-16615338 ] Hudson commented on AMBARI-24645: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #269 (See [https://builds.apache.org/job/Ambari-branch-2.7/269/]) AMBARI-24645 Issues with tooltip containing custom time range for (ababiichuk: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=580153bb959ec70760c4b241edefe5bcaf8823ba]) * (edit) ambari-web/app/mixins/common/widgets/time_range_mixin.js * (edit) ambari-web/app/views/main/service/info/metrics_view.js * (edit) ambari-web/app/templates/main/service/info/metrics/flume/flume_agent_metrics_section.hbs > Issues with tooltip containing custom time range for charts > --- > > Key: AMBARI-24645 > URL: https://issues.apache.org/jira/browse/AMBARI-24645 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.2 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > Time Spent: 1h > Remaining Estimate: 0h > > - The tooltip content is not formatted > - Tooltip isn't displayed on some pages -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24645) Issues with tooltip containing custom time range for charts
[ https://issues.apache.org/jira/browse/AMBARI-24645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16615246#comment-16615246 ] Hudson commented on AMBARI-24645: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9953 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9953/]) AMBARI-24645 Issues with tooltip containing custom time range for (ababiichuk: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=9a81c820816df788493cc43e37de4d33e01ddc3a]) * (edit) ambari-web/app/mixins/common/widgets/time_range_mixin.js * (edit) ambari-web/app/views/main/service/info/metrics_view.js * (edit) ambari-web/app/templates/main/service/info/metrics/flume/flume_agent_metrics_section.hbs > Issues with tooltip containing custom time range for charts > --- > > Key: AMBARI-24645 > URL: https://issues.apache.org/jira/browse/AMBARI-24645 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.2 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > Time Spent: 1h > Remaining Estimate: 0h > > - The tooltip content is not formatted > - Tooltip isn't displayed on some pages -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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
]
Dmitry Lysnichenko updated AMBARI-24646:
Description:
*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,
options)
File "/usr/lib/ambari-server/lib/ambari_server/serverConfiguration.py", line
858, in encrypt_password
return get_encrypted_password(alias, password, properties, options)
File "/usr/lib/ambari-server/lib/ambari_server/serverConfiguration.py", line
867, in get_encrypted_password
masterKey = get_original_master_key(properties, options)
File "/usr/lib/ambari-server/lib/ambari_server/serverConfiguration.py", line
1022, in get_original_master_key
if options is not None and options.master_key is not None and
options.master_key:
AttributeError: Values instance has no attribute 'master_key'
[root@ctr ~]#
{code}
*Issue #2* - Kept asking for Master key on the prompt, despite giving correct
values
{code}
[root@ctr ~]# ambari-server setup
Using python /usr/bin/python
Setup ambari-server
Checking SELinux...
[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
]
Dmitry Lysnichenko updated AMBARI-24646:
Component/s: ambari-server
> '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
> 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,
> options)
> File
[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
]
Dmitry Lysnichenko updated AMBARI-24646:
Fix Version/s: 2.7.2
> '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
> 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,
> options)
> File
[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
]
Dmitry Lysnichenko updated AMBARI-24646:
Affects Version/s: 2.7.0
> '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
> 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,
> options)
> File
[jira] [Created] (AMBARI-24646) 'ambari-server setup-ldap' fails with AttributeError when master_key is not persisted
Dmitry Lysnichenko created AMBARI-24646:
---
Summary: '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
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko
*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,
options)
File "/usr/lib/ambari-server/lib/ambari_server/serverConfiguration.py", line
858, in encrypt_password
return get_encrypted_password(alias, password, properties, options)
File "/usr/lib/ambari-server/lib/ambari_server/serverConfiguration.py", line
867, in get_encrypted_password
masterKey = get_original_master_key(properties, options)
File "/usr/lib/ambari-server/lib/ambari_server/serverConfiguration.py", line
1022, in get_original_master_key
if options is not None and options.master_key is not None and
options.master_key:
AttributeError: Values instance has no attribute 'master_key'
[jira] [Updated] (AMBARI-24645) Issues with tooltip containing custom time range for charts
[ https://issues.apache.org/jira/browse/AMBARI-24645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-24645: -- Resolution: Fixed Status: Resolved (was: Patch Available) Merged to trunk and branch-2.7 > Issues with tooltip containing custom time range for charts > --- > > Key: AMBARI-24645 > URL: https://issues.apache.org/jira/browse/AMBARI-24645 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.2 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > Time Spent: 1h > Remaining Estimate: 0h > > - The tooltip content is not formatted > - Tooltip isn't displayed on some pages -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24645) Issues with tooltip containing custom time range for charts
[ https://issues.apache.org/jira/browse/AMBARI-24645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-24645: -- Status: Patch Available (was: Open) > Issues with tooltip containing custom time range for charts > --- > > Key: AMBARI-24645 > URL: https://issues.apache.org/jira/browse/AMBARI-24645 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.2 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > Time Spent: 20m > Remaining Estimate: 0h > > - The tooltip content is not formatted > - Tooltip isn't displayed on some pages -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24645) Issues with tooltip containing custom time range for charts
[ https://issues.apache.org/jira/browse/AMBARI-24645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24645: Labels: pull-request-available (was: ) > Issues with tooltip containing custom time range for charts > --- > > Key: AMBARI-24645 > URL: https://issues.apache.org/jira/browse/AMBARI-24645 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.2 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > > - The tooltip content is not formatted > - Tooltip isn't displayed on some pages -- 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 ] ASF GitHub Bot updated AMBARI-24644: Labels: pull-request-available (was: ) > 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: 2.7.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (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:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24635:
Labels: pull-request-available (was: )
> 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
>
>
> 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-24639) Not able to turn off maintenance mode for a host.
[
https://issues.apache.org/jira/browse/AMBARI-24639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16614956#comment-16614956
]
Hudson commented on AMBARI-24639:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9952 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9952/])
AMBARI-24639 Not able to turn off maintenance mode for a host. (1963907+atkach:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=6d7ef715d06fb5a8b7e2ba78d20e881de4227d1b])
* (edit) ambari-web/app/controllers/main/host/details.js
> Not able to turn off maintenance mode for a host.
> -
>
> Key: AMBARI-24639
> URL: https://issues.apache.org/jira/browse/AMBARI-24639
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.2
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.2
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> In the cluster , while trying to turn off maintenance mode on host , nothing
> happens and below error is seen in the console.
> Initial analysis indicate that this could be because some host components are
> out of sync. But this may or may not be RC. Kindly check.
> {code:java}
> Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.onOffPassiveModeForHost (app.js:26825)
> at Class.doAction (app.js:26800)
> at handler (vendor.js:31554)
> at HTMLAnchorElement. (vendor.js:23346)
> at HTMLDivElement.dispatch (vendor.js:3178)
> at HTMLDivElement.elemData.handle (vendor.js:2854)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24642) hive service check failing related to LLAP in Ambari
[
https://issues.apache.org/jira/browse/AMBARI-24642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akhil S Naik updated AMBARI-24642:
--
Description:
I have following configuration in ambari for my Hive
Default group: hive.server2.transport.mode=binary
LLAP group: hive.server2.transport.mode=http (by adding this property in
Custom hive-interactive-site )
The issue here is that when I'm doing a service check of Hive, this is what
ambari is trying to do is trying to connect to the interactive server with
transport mode 'binary' and port 10500 through it's in http mode.
{code:java}
2018-09-14 11:50:21,639 - Running Hive Server2 checks
2018-09-14 11:50:21,639 - --
2018-09-14 11:50:21,641 - Server Address List :
['hiveinteractive.openstacklocal'], Port : 10500, SSL KeyStore : None
2018-09-14 11:50:21,641 - Waiting for the Hive Server2 to start...
2018-09-14 11:50:21,641 - Execute['/usr/bin/kinit -kt
/etc/security/keytabs/smokeuser.headless.keytab ambari-qa-kar...@godofwar.com;
'] {'user': 'ambari-qa'}
2018-09-14 11:50:21,816 - Execute['! beeline -u
'jdbc:hive2://hiveinteractive.openstacklocal:10500/;transportMode=binary;principal=hive/_h...@godofwar.com'
-e '' 2>&1| awk '{print}'|grep -i -e 'Connection refused' -e 'Invalid URL'']
{'path': ['/bin/', '/usr/bin/', '/usr/lib/hive/bin/', '/usr/sbin/'],
'timeout_kill_strategy': 2, 'timeout': 30, 'user': 'ambari-qa'}
{code}
ambari should connect through to LLAP through http and port 10501 as my LLAP
server is in http mode
was:
I have following configuration in ambari for my Hive
Default group: hive.server2.transport.mode=binary
LLAP group: hive.server2.transport.mode=http
The issue here is that when I'm doing a service check of Hive, this is what
ambari is trying to do is trying to connect to the interactive server with
transport mode 'binary' and port 10500 through it's in http mode.
{code:java}
2018-09-14 11:50:21,639 - Running Hive Server2 checks
2018-09-14 11:50:21,639 - --
2018-09-14 11:50:21,641 - Server Address List :
['hiveinteractive.openstacklocal'], Port : 10500, SSL KeyStore : None
2018-09-14 11:50:21,641 - Waiting for the Hive Server2 to start...
2018-09-14 11:50:21,641 - Execute['/usr/bin/kinit -kt
/etc/security/keytabs/smokeuser.headless.keytab ambari-qa-kar...@godofwar.com;
'] {'user': 'ambari-qa'}
2018-09-14 11:50:21,816 - Execute['! beeline -u
'jdbc:hive2://hiveinteractive.openstacklocal:10500/;transportMode=binary;principal=hive/_h...@godofwar.com'
-e '' 2>&1| awk '{print}'|grep -i -e 'Connection refused' -e 'Invalid URL'']
{'path': ['/bin/', '/usr/bin/', '/usr/lib/hive/bin/', '/usr/sbin/'],
'timeout_kill_strategy': 2, 'timeout': 30, 'user': 'ambari-qa'}
{code}
ambari should connect through to LLAP through http and port 10501 as my LLAP
server is in http mode
> hive service check failing related to LLAP in Ambari
>
>
> Key: AMBARI-24642
> URL: https://issues.apache.org/jira/browse/AMBARI-24642
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.2
>Reporter: Akhil S Naik
>Assignee: Akhil S Naik
>Priority: Major
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> I have following configuration in ambari for my Hive
> Default group: hive.server2.transport.mode=binary
> LLAP group: hive.server2.transport.mode=http (by adding this property in
> Custom hive-interactive-site )
> The issue here is that when I'm doing a service check of Hive, this is what
> ambari is trying to do is trying to connect to the interactive server with
> transport mode 'binary' and port 10500 through it's in http mode.
> {code:java}
> 2018-09-14 11:50:21,639 - Running Hive Server2 checks
> 2018-09-14 11:50:21,639 - --
> 2018-09-14 11:50:21,641 - Server Address List :
> ['hiveinteractive.openstacklocal'], Port : 10500, SSL KeyStore : None
> 2018-09-14 11:50:21,641 - Waiting for the Hive Server2 to start...
> 2018-09-14 11:50:21,641 - Execute['/usr/bin/kinit -kt
> /etc/security/keytabs/smokeuser.headless.keytab
> ambari-qa-kar...@godofwar.com; '] {'user': 'ambari-qa'}
> 2018-09-14 11:50:21,816 - Execute['! beeline -u
> 'jdbc:hive2://hiveinteractive.openstacklocal:10500/;transportMode=binary;principal=hive/_h...@godofwar.com'
> -e '' 2>&1| awk '{print}'|grep -i -e 'Connection refused' -e 'Invalid
> URL''] {'path': ['/bin/', '/usr/bin/', '/usr/lib/hive/bin/', '/usr/sbin/'],
> 'timeout_kill_strategy': 2, 'timeout': 30, 'user': 'ambari-qa'}
> {code}
> ambari should connect through to LLAP through http and port 10501 as my LLAP
> server is in http mode
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24639) Not able to turn off maintenance mode for a host.
[
https://issues.apache.org/jira/browse/AMBARI-24639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16614939#comment-16614939
]
Hudson commented on AMBARI-24639:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #257 (See
[https://builds.apache.org/job/Ambari-branch-2.7/257/])
AMBARI-24639 Not able to turn off maintenance mode for a host. (1963907+atkach:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=9622786afbfdb1b33fd877c67a9cc8dc5be4bcb5])
* (edit) ambari-web/app/controllers/main/host/details.js
> Not able to turn off maintenance mode for a host.
> -
>
> Key: AMBARI-24639
> URL: https://issues.apache.org/jira/browse/AMBARI-24639
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.2
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.2
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> In the cluster , while trying to turn off maintenance mode on host , nothing
> happens and below error is seen in the console.
> Initial analysis indicate that this could be because some host components are
> out of sync. But this may or may not be RC. Kindly check.
> {code:java}
> Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.onOffPassiveModeForHost (app.js:26825)
> at Class.doAction (app.js:26800)
> at handler (vendor.js:31554)
> at HTMLAnchorElement. (vendor.js:23346)
> at HTMLDivElement.dispatch (vendor.js:3178)
> at HTMLDivElement.elemData.handle (vendor.js:2854)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24639) Not able to turn off maintenance mode for a host.
[
https://issues.apache.org/jira/browse/AMBARI-24639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach resolved AMBARI-24639.
---
Resolution: Fixed
> Not able to turn off maintenance mode for a host.
> -
>
> Key: AMBARI-24639
> URL: https://issues.apache.org/jira/browse/AMBARI-24639
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.2
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.2
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> In the cluster , while trying to turn off maintenance mode on host , nothing
> happens and below error is seen in the console.
> Initial analysis indicate that this could be because some host components are
> out of sync. But this may or may not be RC. Kindly check.
> {code:java}
> Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.onOffPassiveModeForHost (app.js:26825)
> at Class.doAction (app.js:26800)
> at handler (vendor.js:31554)
> at HTMLAnchorElement. (vendor.js:23346)
> at HTMLDivElement.dispatch (vendor.js:3178)
> at HTMLDivElement.elemData.handle (vendor.js:2854)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24639) Not able to turn off maintenance mode for a host.
[
https://issues.apache.org/jira/browse/AMBARI-24639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16614869#comment-16614869
]
Andrii Tkach commented on AMBARI-24639:
---
committed to trunk and branch-2.7
> Not able to turn off maintenance mode for a host.
> -
>
> Key: AMBARI-24639
> URL: https://issues.apache.org/jira/browse/AMBARI-24639
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.2
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.2
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> In the cluster , while trying to turn off maintenance mode on host , nothing
> happens and below error is seen in the console.
> Initial analysis indicate that this could be because some host components are
> out of sync. But this may or may not be RC. Kindly check.
> {code:java}
> Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.onOffPassiveModeForHost (app.js:26825)
> at Class.doAction (app.js:26800)
> at handler (vendor.js:31554)
> at HTMLAnchorElement. (vendor.js:23346)
> at HTMLDivElement.dispatch (vendor.js:3178)
> at HTMLDivElement.elemData.handle (vendor.js:2854)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (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:comment-tabpanel=16614837#comment-16614837
]
Hudson commented on AMBARI-24640:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #256 (See
[https://builds.apache.org/job/Ambari-branch-2.7/256/])
AMBARI-24640. Log Search: support to remove suffixes from field names. (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=08be81d899f12102e3eabff5693776f2f98c06cc])
* (edit)
ambari-logsearch/ambari-logsearch-server/src/test/java/org/apache/ambari/logsearch/common/LabelFallbackHandlerTest.java
* (edit)
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/common/LogSearchConstants.java
* (edit)
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/common/LabelFallbackHandler.java
* (edit)
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/manager/AuditLogsManager.java
* (edit)
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/conf/UIMappingConfig.java
* (edit)
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/manager/ServiceLogsManager.java
> 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-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:comment-tabpanel=16614825#comment-16614825
]
Hudson commented on AMBARI-24640:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9950 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9950/])
AMBARI-24640. Log Search: support to remove suffixes from field names. (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=8add52c94b204eba6931a379602ff39c94cd9592])
* (edit)
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/manager/AuditLogsManager.java
* (edit)
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/common/LogSearchConstants.java
* (edit)
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/conf/UIMappingConfig.java
* (edit)
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/manager/ServiceLogsManager.java
* (edit)
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/common/LabelFallbackHandler.java
* (edit)
ambari-logsearch/ambari-logsearch-server/src/test/java/org/apache/ambari/logsearch/common/LabelFallbackHandlerTest.java
> 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] [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:
--
Status: Patch Available (was: In Progress)
> 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] [Created] (AMBARI-24644) Log Search: support trusted knox proxy
Olivér Szabó created AMBARI-24644: - Summary: 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ó Fix For: 2.7.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24642) hive service check failing related to LLAP in Ambari
[
https://issues.apache.org/jira/browse/AMBARI-24642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akhil S Naik updated AMBARI-24642:
--
Status: Patch Available (was: In Progress)
> hive service check failing related to LLAP in Ambari
>
>
> Key: AMBARI-24642
> URL: https://issues.apache.org/jira/browse/AMBARI-24642
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.2
>Reporter: Akhil S Naik
>Assignee: Akhil S Naik
>Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I have following configuration in ambari for my Hive
> Default group: hive.server2.transport.mode=binary
> LLAP group: hive.server2.transport.mode=http
> The issue here is that when I'm doing a service check of Hive, this is what
> ambari is trying to do is trying to connect to the interactive server with
> transport mode 'binary' and port 10500 through it's in http mode.
> {code:java}
> 2018-09-14 11:50:21,639 - Running Hive Server2 checks
> 2018-09-14 11:50:21,639 - --
> 2018-09-14 11:50:21,641 - Server Address List :
> ['hiveinteractive.openstacklocal'], Port : 10500, SSL KeyStore : None
> 2018-09-14 11:50:21,641 - Waiting for the Hive Server2 to start...
> 2018-09-14 11:50:21,641 - Execute['/usr/bin/kinit -kt
> /etc/security/keytabs/smokeuser.headless.keytab
> ambari-qa-kar...@godofwar.com; '] {'user': 'ambari-qa'}
> 2018-09-14 11:50:21,816 - Execute['! beeline -u
> 'jdbc:hive2://hiveinteractive.openstacklocal:10500/;transportMode=binary;principal=hive/_h...@godofwar.com'
> -e '' 2>&1| awk '{print}'|grep -i -e 'Connection refused' -e 'Invalid
> URL''] {'path': ['/bin/', '/usr/bin/', '/usr/lib/hive/bin/', '/usr/sbin/'],
> 'timeout_kill_strategy': 2, 'timeout': 30, 'user': 'ambari-qa'}
> {code}
> ambari should connect through to LLAP through http and port 10501 as my LLAP
> server is in http mode
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24643) Ambari doesn't update Kerberos rules when multiple KDCs in are in place
Taylor created AMBARI-24643: --- Summary: Ambari doesn't update Kerberos rules when multiple KDCs in are in place Key: AMBARI-24643 URL: https://issues.apache.org/jira/browse/AMBARI-24643 Project: Ambari Issue Type: Bug Environment: HDF 3.2 / HDP 3.0 Reporter: Taylor Kerberos rules for components are by default configured to this value:RULE:[1:$1@$0](.*@REALM)s/@.*// or RULE:[2:$1@$0]([jt]t@.*[EXAMPLE.COM|http://example.com/])s/.*/$MAPRED_USER/ RULE:[2:$1@$0]([nd]n@.*[EXAMPLE.COM|http://example.com/])s/.*/$HDFS_USER/DEFAULT When multiple KDCs are in place, this value needs to be changed in all locations to match the following: RULE:[1:$1@$0](.*@HDPCLOUD)s/@.*// DEFAULT When using the default rule errors are seen accessing Schema Registry and SAM, and rules need to be changed for Storm / Kafka / HDFS and others. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24642) hive service check failing related to LLAP in Ambari
[
https://issues.apache.org/jira/browse/AMBARI-24642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24642:
Labels: pull-request-available (was: )
> hive service check failing related to LLAP in Ambari
>
>
> Key: AMBARI-24642
> URL: https://issues.apache.org/jira/browse/AMBARI-24642
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.2
>Reporter: Akhil S Naik
>Assignee: Akhil S Naik
>Priority: Major
> Labels: pull-request-available
>
> I have following configuration in ambari for my Hive
> Default group: hive.server2.transport.mode=binary
> LLAP group: hive.server2.transport.mode=http
> The issue here is that when I'm doing a service check of Hive, this is what
> ambari is trying to do is trying to connect to the interactive server with
> transport mode 'binary' and port 10500 through it's in http mode.
> {code:java}
> 2018-09-14 11:50:21,639 - Running Hive Server2 checks
> 2018-09-14 11:50:21,639 - --
> 2018-09-14 11:50:21,641 - Server Address List :
> ['hiveinteractive.openstacklocal'], Port : 10500, SSL KeyStore : None
> 2018-09-14 11:50:21,641 - Waiting for the Hive Server2 to start...
> 2018-09-14 11:50:21,641 - Execute['/usr/bin/kinit -kt
> /etc/security/keytabs/smokeuser.headless.keytab
> ambari-qa-kar...@godofwar.com; '] {'user': 'ambari-qa'}
> 2018-09-14 11:50:21,816 - Execute['! beeline -u
> 'jdbc:hive2://hiveinteractive.openstacklocal:10500/;transportMode=binary;principal=hive/_h...@godofwar.com'
> -e '' 2>&1| awk '{print}'|grep -i -e 'Connection refused' -e 'Invalid
> URL''] {'path': ['/bin/', '/usr/bin/', '/usr/lib/hive/bin/', '/usr/sbin/'],
> 'timeout_kill_strategy': 2, 'timeout': 30, 'user': 'ambari-qa'}
> {code}
> ambari should connect through to LLAP through http and port 10501 as my LLAP
> server is in http mode
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24642) hive service check failing related to LLAP in Ambari
[
https://issues.apache.org/jira/browse/AMBARI-24642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akhil S Naik updated AMBARI-24642:
--
Summary: hive service check failing related to LLAP in Ambari (was:
service check related to LLAP in Ambari)
> hive service check failing related to LLAP in Ambari
>
>
> Key: AMBARI-24642
> URL: https://issues.apache.org/jira/browse/AMBARI-24642
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.2
>Reporter: Akhil S Naik
>Assignee: Akhil S Naik
>Priority: Major
>
> I have following configuration in ambari for my Hive
> Default group: hive.server2.transport.mode=binary
> LLAP group: hive.server2.transport.mode=http
> The issue here is that when I'm doing a service check of Hive, this is what
> ambari is trying to do is trying to connect to the interactive server with
> transport mode 'binary' and port 10500 through it's in http mode.
> {code:java}
> 2018-09-14 11:50:21,639 - Running Hive Server2 checks
> 2018-09-14 11:50:21,639 - --
> 2018-09-14 11:50:21,641 - Server Address List :
> ['hiveinteractive.openstacklocal'], Port : 10500, SSL KeyStore : None
> 2018-09-14 11:50:21,641 - Waiting for the Hive Server2 to start...
> 2018-09-14 11:50:21,641 - Execute['/usr/bin/kinit -kt
> /etc/security/keytabs/smokeuser.headless.keytab
> ambari-qa-kar...@godofwar.com; '] {'user': 'ambari-qa'}
> 2018-09-14 11:50:21,816 - Execute['! beeline -u
> 'jdbc:hive2://hiveinteractive.openstacklocal:10500/;transportMode=binary;principal=hive/_h...@godofwar.com'
> -e '' 2>&1| awk '{print}'|grep -i -e 'Connection refused' -e 'Invalid
> URL''] {'path': ['/bin/', '/usr/bin/', '/usr/lib/hive/bin/', '/usr/sbin/'],
> 'timeout_kill_strategy': 2, 'timeout': 30, 'user': 'ambari-qa'}
> {code}
> ambari should connect through to LLAP through http and port 10501 as my LLAP
> server is in http mode
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24642) service check related to LLAP in Ambari
Akhil S Naik created AMBARI-24642:
-
Summary: service check related to LLAP in Ambari
Key: AMBARI-24642
URL: https://issues.apache.org/jira/browse/AMBARI-24642
Project: Ambari
Issue Type: Bug
Affects Versions: 2.6.2
Reporter: Akhil S Naik
Assignee: Akhil S Naik
I have following configuration in ambari for my Hive
Default group: hive.server2.transport.mode=binary
LLAP group: hive.server2.transport.mode=http
The issue here is that when I'm doing a service check of Hive, this is what
ambari is trying to do is trying to connect to the interactive server with
transport mode 'binary' and port 10500 through it's in http mode.
{code:java}
2018-09-14 11:50:21,639 - Running Hive Server2 checks
2018-09-14 11:50:21,639 - --
2018-09-14 11:50:21,641 - Server Address List :
['hiveinteractive.openstacklocal'], Port : 10500, SSL KeyStore : None
2018-09-14 11:50:21,641 - Waiting for the Hive Server2 to start...
2018-09-14 11:50:21,641 - Execute['/usr/bin/kinit -kt
/etc/security/keytabs/smokeuser.headless.keytab ambari-qa-kar...@godofwar.com;
'] {'user': 'ambari-qa'}
2018-09-14 11:50:21,816 - Execute['! beeline -u
'jdbc:hive2://hiveinteractive.openstacklocal:10500/;transportMode=binary;principal=hive/_h...@godofwar.com'
-e '' 2>&1| awk '{print}'|grep -i -e 'Connection refused' -e 'Invalid URL'']
{'path': ['/bin/', '/usr/bin/', '/usr/lib/hive/bin/', '/usr/sbin/'],
'timeout_kill_strategy': 2, 'timeout': 30, 'user': 'ambari-qa'}
{code}
ambari should connect through to LLAP through http and port 10501 as my LLAP
server is in http mode
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (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
]
ASF GitHub Bot updated AMBARI-24641:
Labels: pull-request-available (was: )
> 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
>
>
> 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] [Created] (AMBARI-24641) Stackadvisor error while trying to add atlas service. Error - "if mountPoints[mountPoint] < reqiuredDiskSpace: KeyError: None"
Attila Magyar created AMBARI-24641:
--
Summary: 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
Fix For: 2.7.2
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-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
]
ASF GitHub Bot updated AMBARI-24640:
Labels: pull-request-available (was: )
> 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
>
>
> 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] [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:
--
Summary: Log Search: support to remove suffixes from field names (was: Log
Search: support to remove suffixes from field names mapping)
> 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
> Fix For: 2.7.2
>
>
> 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] [Created] (AMBARI-24640) Log Search: support to remove suffixes from field names mapping
Olivér Szabó created AMBARI-24640:
-
Summary: Log Search: support to remove suffixes from field names
mapping
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ó
Fix For: 2.7.2
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] [Updated] (AMBARI-24640) Log Search: support to remove suffixes from field names mapping
[
https://issues.apache.org/jira/browse/AMBARI-24640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-24640:
--
Description:
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}}
was:
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}}
> Log Search: support to remove suffixes from field names mapping
> ---
>
> 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
> Fix For: 2.7.2
>
>
> 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] [Resolved] (AMBARI-24626) Log Search: some solr fields are missing from service log / audit log response
[ https://issues.apache.org/jira/browse/AMBARI-24626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-24626. --- Resolution: Fixed > Log Search: some solr fields are missing from service log / audit log response > -- > > Key: AMBARI-24626 > URL: https://issues.apache.org/jira/browse/AMBARI-24626 > 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 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24639) Not able to turn off maintenance mode for a host.
[
https://issues.apache.org/jira/browse/AMBARI-24639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24639:
Labels: pull-request-available (was: )
> Not able to turn off maintenance mode for a host.
> -
>
> Key: AMBARI-24639
> URL: https://issues.apache.org/jira/browse/AMBARI-24639
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.2
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.2
>
>
> In the cluster , while trying to turn off maintenance mode on host , nothing
> happens and below error is seen in the console.
> Initial analysis indicate that this could be because some host components are
> out of sync. But this may or may not be RC. Kindly check.
> {code:java}
> Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.onOffPassiveModeForHost (app.js:26825)
> at Class.doAction (app.js:26800)
> at handler (vendor.js:31554)
> at HTMLAnchorElement. (vendor.js:23346)
> at HTMLDivElement.dispatch (vendor.js:3178)
> at HTMLDivElement.elemData.handle (vendor.js:2854)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24639) Not able to turn off maintenance mode for a host.
Andrii Tkach created AMBARI-24639:
-
Summary: Not able to turn off maintenance mode for a host.
Key: AMBARI-24639
URL: https://issues.apache.org/jira/browse/AMBARI-24639
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.7.2
Reporter: Andrii Tkach
Assignee: Andrii Tkach
Fix For: 2.7.2
In the cluster , while trying to turn off maintenance mode on host , nothing
happens and below error is seen in the console.
Initial analysis indicate that this could be because some host components are
out of sync. But this may or may not be RC. Kindly check.
{code:java}
Uncaught TypeError: Cannot read property 'get' of undefined
at Class.onOffPassiveModeForHost (app.js:26825)
at Class.doAction (app.js:26800)
at handler (vendor.js:31554)
at HTMLAnchorElement. (vendor.js:23346)
at HTMLDivElement.dispatch (vendor.js:3178)
at HTMLDivElement.elemData.handle (vendor.js:2854)
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24638) Ambari-agent process memory leak
[ https://issues.apache.org/jira/browse/AMBARI-24638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24638: - Summary: Ambari-agent process memory leak (was: Ambari-agent process consuming more memory.) > 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: 0.5h > 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] [Updated] (AMBARI-24638) Ambari-agent process consuming more memory.
[ https://issues.apache.org/jira/browse/AMBARI-24638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24638: Labels: pull-request-available (was: ) > Ambari-agent process consuming more memory. > --- > > 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 > > > 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] [Updated] (AMBARI-24638) Ambari-agent process consuming more memory.
[ https://issues.apache.org/jira/browse/AMBARI-24638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24638: - Attachment: AMBARI-24638.patch > Ambari-agent process consuming more memory. > --- > > 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 > Fix For: 2.7.2 > > Attachments: AMBARI-24638.patch, AMBARI-24638.patch > > > 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] [Updated] (AMBARI-24638) Ambari-agent process consuming more memory.
[ https://issues.apache.org/jira/browse/AMBARI-24638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24638: - Affects Version/s: 2.7.0 > Ambari-agent process consuming more memory. > --- > > 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 > Fix For: 2.7.2 > > Attachments: AMBARI-24638.patch, AMBARI-24638.patch > > > 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] [Created] (AMBARI-24638) Ambari-agent process consuming more memory.
Andrew Onischuk created AMBARI-24638: Summary: Ambari-agent process consuming more memory. Key: AMBARI-24638 URL: https://issues.apache.org/jira/browse/AMBARI-24638 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.7.2 Attachments: AMBARI-24638.patch 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. (docker)[root@hcube2-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] [Updated] (AMBARI-24638) Ambari-agent process consuming more memory.
[ https://issues.apache.org/jira/browse/AMBARI-24638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24638: - Status: Patch Available (was: Open) > Ambari-agent process consuming more memory. > --- > > Key: AMBARI-24638 > URL: https://issues.apache.org/jira/browse/AMBARI-24638 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.2 > > Attachments: AMBARI-24638.patch > > > 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. > (docker)[root@hcube2-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] [Updated] (AMBARI-24638) Ambari-agent process consuming more memory.
[ https://issues.apache.org/jira/browse/AMBARI-24638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24638: - Description: 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. was: 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. (docker)[root@hcube2-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. > Ambari-agent process consuming more memory. > --- > > Key: AMBARI-24638 > URL: https://issues.apache.org/jira/browse/AMBARI-24638 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.2 > > Attachments: AMBARI-24638.patch > > > 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]):
[jira] [Updated] (AMBARI-24638) Ambari-agent process consuming more memory.
[ https://issues.apache.org/jira/browse/AMBARI-24638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24638: - Attachment: AMBARI-24638.patch > Ambari-agent process consuming more memory. > --- > > Key: AMBARI-24638 > URL: https://issues.apache.org/jira/browse/AMBARI-24638 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.2 > > Attachments: AMBARI-24638.patch > > > 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. > (docker)[root@hcube2-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)
