Uploaded image for project: 'Coopr'
  1. Coopr
  2. COOPR-749

Macros which are unresolvable should be handled better

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 0.9.9, Code Name: Ursa Major
    • Fix Version/s: 0.9.10 Code Name: Mensa
    • Component/s: server
    • Labels:
      None
    • Rank:
      1|hzypu7:

      Description

      When a macro is used in a template and refers to a missing item on the cluster, Coopr returns the unresolved macro.

      Example:

      hadoop: { mapred_site: { mapreduce.jobhistory.address: {
        %ip.bind_v4.service.hadoop-mapreduce-historyserver%:10020
      }}}
      

      When the hadoop-mapreduce-historyserver service is present on the cluster, this resolves to the address of that server. Otherwise, the following is inserted into /etc/hadoop/conf/mapred-site.xml

      <property>
        <name>mapreduce.jobhistory.address</name>
        <value>%ip.bind_v4.service.hadoop-mapreduce-historyserver%:10020</value>
      </property>
      

      This can be read by other processes, such as Hive, and prevents the service from functioning correctly. We need a better way to handle this case.

        Attachments

          Activity

            People

            • Assignee:
              nitin Nitin Motgi
              Reporter:
              chris Chris Gianelloni
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: