[JIRA] Created: (MINION-2) Concurrency issue with manual call to dump
- From: "jhalex (JIRA)" <jira-no-reply@kenai.com>
- To: issues@minion.kenai.com
- Subject: [JIRA] Created: (MINION-2) Concurrency issue with manual call to dump
- Date: Tue, 13 Apr 2010 20:48:53 +0000 (GMT+00:00)
Concurrency issue with manual call to dump
------------------------------------------
Key: MINION-2
URL: http://kenai.com/jira/browse/MINION-2
Project: minion
Issue Type: Bug
Components: Indexing
Reporter: jhalex
Assignee: jhalex
The scenario is that one thread begins to index a document (in this case,
passing in an indexable map). It calls startDocument. Another thread wakes
up and tells the engine to do a dump. That checks the indexing queue for a
new doc, determines there isn't one (the AbstractPipelineImpl is already
holding on to it), and goes ahead and does a realDump. That sticks a new
InvFileMemoryPartition into the pipeline. Now the first thread calls
handleField, sends its data down to the InvFileMemoryPartition, and it throws
an NPE when it tries to get a dockey (which is probably for the best since
otherwise it'd be pretty screwed up!).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://kenai.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
[JIRA] Created: (MINION-2) Concurrency issue with manual call to dump |
jhalex (JIRA) | 04/13/2010 |





