Uploaded image for project: 'Falcon'
  1. Falcon
  2. FALCON-2114

Feed Instance update on titan DB based on JMS notifications on coordinator actions

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None
    • None

    Description

      In the JMS notifications from the coordinator action, there is no information on feed name and instance path (see example below). Need to obtain these information for WAITING and TIMEOUT instances before adding them to titan DB.

      2016-04-22 21:49:40,409 INFO - [ActiveMQ Session Task-1:] ~ Created context from Oozie JMS message WorkflowExecutionContext{{status=WAITING, workflowId=0000026-160419215151236-oozie-oozi-C@8, parentId=0000026-160419215151236-oozie-oozi-C, entityName=pig-process-1010, contextType=COORDINATOR_ACTION, workflowStartTime=1461361780409, workflowEndTime=1461361780409, operation=GENERATE, workflowUser=ambari-qa, entityType=PROCESS, nominalTime=2010-10-08-00-00}} (JMSMessageConsumer:120)

      Attachments

        Issue Links

          Activity

            People

              ying-eng Ying Zheng
              ying-eng Ying Zheng
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: