Lukas, Ray wrote:
I started going through the source code debugging this problem.. The
extra thread comes from FetchedSegments(Configuration conf, Path
segmentsDir) constructor. This constructor creates a segmentUpdater and
then starts it.. This is the thread that I am talking about..
Does anyone know how to cleanly shut down this segment updater?
Looking at the code it's not possible right now. You need to modify the
FetchedSegment.close() to include also the shutdown of this thread.
Since the thread already loops in a while (true) loop, it's enough to
change this to a boolean flag and set this flag to false in the close()
method.
If you come up with a more or less clean patch please submit this to
JIRA as an improvement.
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __________________________________
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Embedded Unix, System Integration
http://www.sigram.com Contact: info at sigram dot com
