ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hurley (JIRA)" <>
Subject [jira] [Created] (AMBARI-21951) Last Run Service Check for SPARK Picks up SPARK2
Date Wed, 13 Sep 2017 19:14:00 GMT
Jonathan Hurley created AMBARI-21951:

             Summary: Last Run Service Check for SPARK Picks up SPARK2
                 Key: AMBARI-21951
             Project: Ambari
          Issue Type: Bug
    Affects Versions: 2.6.0
            Reporter: Jonathan Hurley
            Assignee: Jonathan Hurley
            Priority: Critical
             Fix For: 2.6.0


- Install a cluster with Spark and Spark2
- Remove Spark2
- Change a Spark configuration
- Run the Spark Service check
- Attempt to perform an upgrade

The upgrade pre-checks will stop you saying something like: 
02 Aug 2017 10:17:23,701  INFO [ambari-client-thread-28] ServiceCheckValidityCheck:149 - Service
SPARK latest config change is 08-02-2017 09:45:16, latest service check executed at 12-31-1969

The start time suggests a value of -1 in my cluster. The problem is that I aborted my SPARK2
service check and then removed the service. However, the pre-check seems to be matching on
the name an incorrectly detecting the old SPARK2 check as the one for SPARK:

      boolean serviceCheckWasExecuted = false;
      for (HostRoleCommandEntity command : latestTimestamps.values()) {
        if (null !=  command.getCommandDetail() && command.getCommandDetail().contains(serviceName))

Because {{contains()}} is finding {{SPARK}} in {{SPARK2_SERVICE_CHECK}}, it's incorrectly
picking up the wrong values...

This message was sent by Atlassian JIRA

View raw message