MetricDataLoader captures all error and log exceptions. I was naïve to think that error log can feedback into Chukwa to monitor the error and reload the data from /chukwa/repos. Of course, that idea faded in my mind and forgot about it.
MetricDataLoader can be modified to throw IOException to the executor class MetricDataLoaderPool, which can throw exception to PostProcessor Manager. PostProcessorManager moves the data to a temp directory. The retry logic can be added to PostProcessorManager by counting the number of retry with the error out sequence file before sending it to InError directory. It should be the better route to manages error conditions. It seems like a lot of people are using MySQL part of Chukwa. I am wondering what are the use cases? If we can have a driver on this part of the project, it could be better supported without fragment the community. Regards, Eric On 7/22/10 8:25 PM, "William Bajzek" <williambaj...@gmail.com> wrote: > Hello. I'm working with a modified version of the chukwa trunk which outputs > mysql using the MetricDataLoader. Before suggesting the obvious, these things > are out of my control :) > > I'm just exploring how Chukwa handles various error conditions. For instance, > if the chukwa machine lost contact with the mysql server because of a network > failure and the MDL threw an error. My assumption was that on a subsequent > running of the MDL, when the database was available again, it would pick up > processing where it left off. That doesn't seem to be the case, though. Can > anyone tell me how to recover from such an error? > > > - William Bajzek > williambaj...@gmail.com > > > >
