[
https://issues.apache.org/jira/browse/CHUKWA-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ahmed Fathalla updated CHUKWA-4:
--------------------------------
Attachment: CHUKWA-4.2.patch
I've uploaded a new patch where I have moved the close() methods as Jerome
advised. I've also moved the cleanup code that was in the unit test into a
separate tearDown() method.
I've tested my code with an empty .chukwa file and it correctly converts it to
.done.
Regarding creating an InErrorDirectory, do we actually need that or would it be
an unnecessary complication? This also depends on how you would define an
invalid .chukwa file?
> Collectors don't finish writing .done datasink from last .chukwa datasink
> when stopped using bin/stop-collectors
> ----------------------------------------------------------------------------------------------------------------
>
> Key: CHUKWA-4
> URL: https://issues.apache.org/jira/browse/CHUKWA-4
> Project: Hadoop Chukwa
> Issue Type: Bug
> Components: data collection
> Environment: I am running on our local cluster. This is a linux
> machine that I also run Hadoop cluster from.
> Reporter: Andy Konwinski
> Priority: Minor
> Attachments: CHUKWA-4.2.patch, CHUKWA-4.patch
>
>
> When I use start-collectors, it creates the datasink as expected, writes to
> it as per normal, i.e. writes to the .chukwa file, and roll overs work fine
> when it renames the .chukwa file to .done. However, when I use
> bin/stop-collectors to shut down the running collector it leaves a .chukwa
> file in the HDFS file system. Not sure if this is a valid sink or not, but I
> think that the collector should gracefully clean up the datasink and rename
> it .done before exiting.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
