Re: We got MessageLossException from task Some(TaskId(0,0)), replaying application...
Hi Ramin, and also would you mind pasting the whole exception trace here? Karol Brejna 于2017年5月6日周六 上午2:32写道: > Ramin, > Is there a chance for you to share the code? > > What is your datasource? > > Regards, > Karol > > W dniu pt., 5.05.2017 o 18:06 Ramin Etemaadi > napisał(a): > > > Hi team, > > > > Thanks for your great job on Gearpump project. > > > > After upgrading from 0.8.1 to 0.8.3 (and adjusting changing interfaces), > I > > got this error in the logs: > > "We got MessageLossException from task Some(TaskId(0,0)), replaying > > application..." > > > > This causes the failure of the pipeline. > > > > I searched the internet and I couldn't find any clue, can you help me > with > > a indicator that what could be a stating point to debug this issue? > > > > Regards, > > Ramin > > >
Re: We got MessageLossException from task Some(TaskId(0,0)), replaying application...
Ramin, Is there a chance for you to share the code? What is your datasource? Regards, Karol W dniu pt., 5.05.2017 o 18:06 Ramin Etemaadi napisał(a): > Hi team, > > Thanks for your great job on Gearpump project. > > After upgrading from 0.8.1 to 0.8.3 (and adjusting changing interfaces), I > got this error in the logs: > "We got MessageLossException from task Some(TaskId(0,0)), replaying > application..." > > This causes the failure of the pipeline. > > I searched the internet and I couldn't find any clue, can you help me with > a indicator that what could be a stating point to debug this issue? > > Regards, > Ramin >
We got MessageLossException from task Some(TaskId(0,0)), replaying application...
Hi team, Thanks for your great job on Gearpump project. After upgrading from 0.8.1 to 0.8.3 (and adjusting changing interfaces), I got this error in the logs: "We got MessageLossException from task Some(TaskId(0,0)), replaying application..." This causes the failure of the pipeline. I searched the internet and I couldn't find any clue, can you help me with a indicator that what could be a stating point to debug this issue? Regards, Ramin