Member since
09-12-2016
8
Posts
6
Kudos Received
2
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1691 | 02-12-2018 10:39 PM | |
1684 | 12-05-2017 11:25 PM |
02-12-2018
10:39 PM
1 Kudo
Hi, @Emilio Lopez, The agent log looks OK, it's sending hearbeats with different "id" each time. Please take a look at the contents of /var/lib/ambari-agent/data -- look for output*txt which contain "Host checks started.", and corresponding error*txt files (eg. output-2.txt and error-2.txt). Those might have some info about the problem. Also search for check_host in ambari-agent.log.
... View more
02-09-2018
05:25 PM
3 Kudos
Hi @Gonzalo Herreros, You are right, there is a deadlock between threads 139795204400896 and 139794642351872 in your dump. One of the locks is the Ambari-specific lock added as an attempt to workaround threading issues in the subprocess module that we have run into. The other one is required for imports. It turns out that os.fork tries to acquire the import lock. Thread 139795204400896 calls subprocess.Popen from a module being imported. Lock order is: import, subprocess. Thread 139794642351872 simply calls subprocess.Popen, which calls os.fork. Lock order is: subprocess, import. We are now dropping the custom lock in favor of the subprocess32 module, which is the backport of Python 3.2 subprocess implementation, and is recommended even in the Python 2 docs. Thanks for reporting this, and sorry for taking so long to answer.
... View more
12-11-2017
09:15 AM
The file in Ambari Agent's cache seems to be leftover from HDF 3.0.1 or earlier. Any idea how it could get there if it's a clean install on a newly installed machine?
... View more
12-11-2017
07:36 AM
@Markus Wilhelm Can you please share the exact version numbers (HDF, Ambari)?
... View more
12-05-2017
11:25 PM
1 Kudo
$ grep authentication.jwt /etc/ambari-server/conf/ambari.properties
authentication.jwt.enabled=true
authentication.jwt.providerUrl=https://somehost:8443/gw-os06/knoxsso/api/v1/websso
authentication.jwt.publicKey=/etc/ambari-server/conf/jwt-cert.pem
$ cat /etc/ambari-server/conf/jwt-cert.pem
-----BEGIN CERTIFICATE-----
MIICnTCCAYWgAwIBAgIBATANBgkqhkiG9w0BAQsFADASMRAwDgYDVQQDDAdzaWdu
aW5nMB4XDTE3MTIwNTE3NDUwMloXDTI3MTIwNTE3NDUwMlowEjEQMA4GA1UEAxMH
...
60v5bHlGkAKgdziCm1DZbxmTjcjLdxZAU7NrOlhSicZl17Yym1nmT8Cq2PkSDRaZ
rA==
-----END CERTIFICATE----
Adding the above to ambari.properties and creating the certificate file jwt-cert.pem has the same effect as running ambari-server setup-sso interactively. For complete list of properties, including "advanced" ones, see https://github.com/apache/ambari/blob/release-2.6.0/ambari-server/src/main/python/ambari_server/setupSso.py
... View more
08-08-2017
10:52 AM
If I understand correctly, you create a cluster using some initial blueprint, change some configuration parameters for services, and would like to get a blueprint with the updated parameters? If so, then you need to export the blueprint from the cluster, which is explained eg. in this answer.
... View more
08-08-2017
10:20 AM
Hi @uri ben-ari, Your link and example are about IBM UrbanCode Deploy, not Apache Ambari. Blueprints in Ambari are immutable, cannot be updated. You can POST the updated blueprint with a new name and use that to deploy the cluster.
... View more
04-25-2017
06:09 AM
1 Kudo
@Daniel Müller look for these properties (the ones present in hive-site.xml) on Hive's config page, not Spark, within Ambari.
... View more