ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "matteo brancaleoni (JIRA)" <>
Subject [jira] [Created] (AMBARI-14926) ambari cached conflicts with python hdfs lib resulting into monitoring errors
Date Thu, 04 Feb 2016 16:33:39 GMT
matteo brancaleoni created AMBARI-14926:

             Summary: ambari cached conflicts with python hdfs lib resulting into
monitoring errors
                 Key: AMBARI-14926
             Project: Ambari
          Issue Type: Bug
          Components: ambari-agent
    Affects Versions: 2.2.0
         Environment: Linux CentOS 7 x86_64
            Reporter: matteo brancaleoni

On systems with datanode and journal node monitored by ambari-agent,
if in the standard python path the hdfs lib is installed (
) it makes datanode + journalnode and monitoring fails:
* datanodes are seen up in global live datanodes
* but the service is down into the host service list

looking into the logs I get:

DEBUG 2016-02-04 16:54:49,160 - Running command reflectively
DEBUG 2016-02-04 16:54:49,170 - Reflective command failed with
Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/ambari_agent/", line 55,
in run_file
    imp.load_source('__main__', script)
  File "/var/lib/ambari-agent/cache/common-services/HDFS/",
line 30, in <module>
    from utils import service
  File "/var/lib/ambari-agent/cache/common-services/HDFS/",
line 37, in <module>
    from zkfc_slave import ZkfcSlave
  File "/var/lib/ambari-agent/cache/common-services/HDFS/",
line 21, in <module>
    from hdfs import hdfs
ImportError: cannot import name hdfs

I think that ambari is including its cache files after the python path, so if an hdfs module
is present into python path makes the scripts goes crazy.
(basically using the system hdfs py module and not his own)

maybe cache files path must be included before the python path or imported with local imports?

This message was sent by Atlassian JIRA

View raw message