Andrew Jorgensen created AURORA-1403:
----------------------------------------

             Summary: Aurora UI cannot find task
                 Key: AURORA-1403
                 URL: https://issues.apache.org/jira/browse/AURORA-1403
             Project: Aurora
          Issue Type: Bug
            Reporter: Andrew Jorgensen


I recently upgraded from 0.7.0 -> 0.8.0 -> 0.9.0-rc0 and along the way I've 
seem to have lost the ability for the UI to find tasks.

When trying to click on a hostname in the aurora ui I get the following:
{quote}
Failed to find task 
1437491675333-asample-task-9-41bb4b53-656b-41d4-be06-a3e98ebcfcf6.  Try again 
shortly.
{quote}

The mesos worker has the same task name in its logs
{quote}
I0721 15:15:44.738039  1010 status_update_manager.cpp:389] Received status 
update acknowledgement (UUID: 6561bb99-9d6f-402e-a061-1728a675aa7d) for task 
1437491675333-sample-task-9-41bb4b53-656b-41d4-be06-a3e98ebcfcf6 of framework 
20150507-194526-3627858186-5050-8132-0000
{quote}

it looks like along the way there was a change to refactor some of the path 
detector code 
(https://github.com/apache/aurora/blob/0.8.0-rc1/src/main/python/apache/aurora/executor/common/path_detector.py#L23).
 It looks like here the default path that it looks for tasks is /var/lib/mesos 
however the root directory for our mesos installation is /mnt/mesos.

The other clue that I noticed is there seem to be two versions of the 
thermos_observer that exist.

https://github.com/apache/aurora/blob/827b9abea48babe53ad5b2c521757c60f04c6dfc/src/main/python/apache/aurora/tools/thermos_observer.py

https://github.com/apache/aurora/blob/827b9abea48babe53ad5b2c521757c60f04c6dfc/src/main/python/apache/thermos/observer/bin/thermos_observer.py

Can anyone shed some light on why these two exist separately and one of them 
exposes an option to add in --mesos-root. It feels to me that I need the 
thermos_observer with that option and to set it to /mnt/mesos to override the 
default.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to