Yeah it looks like you will need to regenerate it.
On Jan 2, 2018, 9:19 PM -0800, Mohit Jaggi <mohit.ja...@uber.com>, wrote: > Yes. I had linked to that in my email. I was hoping to retrieve it from > "storage", but if it is not stored then I will try to use that logic to > create one. I don't want to add it to storage if it is not there to avoid > handling db migration. > > On Tue, Jan 2, 2018 at 8:05 PM, Bill Farner <wfar...@apache.org> wrote: > > > Did your code search lead you here > > <https://github.com/apache/aurora/blob/2e1ca42887bc8ea1e8c6cddebe9d1c > > f29268c714/src/main/java/org/apache/aurora/scheduler/mesos/ > > MesosTaskFactory.java#L112>? > > It should show how the executor and task IDs relate. > > > > On Tue, Jan 2, 2018 at 1:08 PM, Mohit Jaggi <mohit.ja...@uber.com> wrote: > > > > > Happy new year folks! Help with the following will be much appreciated. > > > > > > ---------- Forwarded message ---------- > > > From: Mohit Jaggi <mohit.ja...@uber.com > > > Date: Sat, Dec 23, 2017 at 9:08 PM > > > Subject: executor id from task id? > > > To: u...@aurora.apache.org > > > > > > > > > Folks, > > > I am trying to work on this: > > > https://issues.apache.org/jira/browse/AURORA-1960 > > > > > > In VersionedSchedulerDriver > > > <https://github.com/apache/aurora/blob/47c689956f77ed635d26f7ec659689 > > > 002bd047af/src/main/java/org/apache/aurora/scheduler/mesos/ > > > VersionedSchedulerDriverService.java#L180-L185 > > > killTask() gets a taskId but the SHUTDOWN > > > <https://mesos.apache.org/documentation/latest/ > > > scheduler-http-api/#shutdown > > > call requires an executor id. How do I get that? I see it is created here > > > <https://github.com/apache/aurora/blob/47c689956f77ed635d26f7ec659689 > > > 002bd047af/src/main/java/org/apache/aurora/scheduler/mesos/ > > > MesosTaskFactory.java#L111 > > > but > > > I am not sure how to find it in the killTask() call. > > > > > > Mohit. > > > > >
