You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Dennis Kubes (JIRA)" <ji...@apache.org> on 2010/07/19 23:00:50 UTC
[jira] Created: (NUTCH-857) DistributedBeans should not close their
RPC counterparts
DistributedBeans should not close their RPC counterparts
--------------------------------------------------------
Key: NUTCH-857
URL: https://issues.apache.org/jira/browse/NUTCH-857
Project: Nutch
Issue Type: Bug
Affects Versions: 1.1
Environment: All
Reporter: Dennis Kubes
Assignee: Dennis Kubes
Fix For: 1.2
Attachments: NUTCH-857-1-20100619.patch
DistributedSearch and Segment Beans currently call close on their RPC counterparts from their own close methods. This results in killing (closing) all distributed servers when the main bean (website, application, etc) is shutdown. DistributedSearchServer (SegmentServer) are run independent from the main NutchBean or website calling those servers in shard type environments. With the current code the distributed servers are closed and any further search requests throw IndexAlreadyClosed exceptions. The distributed servers have to be restarted before searching can resume. Obviously this doesn't work in a large distributed search where multiple beans could be called the distributed servers and where distributed servers could be coming up and down frequently.
The solution is simple though. The Distributed beans shouldn't call close on their RPC counterparts. Patch is attached.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Created: (NUTCH-857) DistributedBeans should not close
their RPC counterparts
Posted by Andrzej Bialecki <ab...@getopt.org>.
On 2010-07-23 02:27, Dennis Kubes wrote:
> If nobody objects I am going to commit this in the next 24 hours.
+1 this looks fine to me.
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __________________________________
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Embedded Unix, System Integration
http://www.sigram.com Contact: info at sigram dot com
Re: [jira] Created: (NUTCH-857) DistributedBeans should not close
their RPC counterparts
Posted by Dennis Kubes <ku...@apache.org>.
If nobody objects I am going to commit this in the next 24 hours.
Dennis
On 07/19/2010 04:00 PM, Dennis Kubes (JIRA) wrote:
> DistributedBeans should not close their RPC counterparts
> --------------------------------------------------------
>
> Key: NUTCH-857
> URL: https://issues.apache.org/jira/browse/NUTCH-857
> Project: Nutch
> Issue Type: Bug
> Affects Versions: 1.1
> Environment: All
> Reporter: Dennis Kubes
> Assignee: Dennis Kubes
> Fix For: 1.2
> Attachments: NUTCH-857-1-20100619.patch
>
> DistributedSearch and Segment Beans currently call close on their RPC counterparts from their own close methods. This results in killing (closing) all distributed servers when the main bean (website, application, etc) is shutdown. DistributedSearchServer (SegmentServer) are run independent from the main NutchBean or website calling those servers in shard type environments. With the current code the distributed servers are closed and any further search requests throw IndexAlreadyClosed exceptions. The distributed servers have to be restarted before searching can resume. Obviously this doesn't work in a large distributed search where multiple beans could be called the distributed servers and where distributed servers could be coming up and down frequently.
>
> The solution is simple though. The Distributed beans shouldn't call close on their RPC counterparts. Patch is attached.
>
>
[jira] Resolved: (NUTCH-857) DistributedBeans should not close
their RPC counterparts
Posted by "Dennis Kubes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NUTCH-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Kubes resolved NUTCH-857.
--------------------------------
Resolution: Fixed
Committed with revision 979252
> DistributedBeans should not close their RPC counterparts
> --------------------------------------------------------
>
> Key: NUTCH-857
> URL: https://issues.apache.org/jira/browse/NUTCH-857
> Project: Nutch
> Issue Type: Bug
> Affects Versions: 1.1
> Environment: All
> Reporter: Dennis Kubes
> Assignee: Dennis Kubes
> Fix For: 1.2
>
> Attachments: NUTCH-857-1-20100619.patch
>
>
> DistributedSearch and Segment Beans currently call close on their RPC counterparts from their own close methods. This results in killing (closing) all distributed servers when the main bean (website, application, etc) is shutdown. DistributedSearchServer (SegmentServer) are run independent from the main NutchBean or website calling those servers in shard type environments. With the current code the distributed servers are closed and any further search requests throw IndexAlreadyClosed exceptions. The distributed servers have to be restarted before searching can resume. Obviously this doesn't work in a large distributed search where multiple beans could be called the distributed servers and where distributed servers could be coming up and down frequently.
> The solution is simple though. The Distributed beans shouldn't call close on their RPC counterparts. Patch is attached.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (NUTCH-857) DistributedBeans should not close their
RPC counterparts
Posted by "Dennis Kubes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NUTCH-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Kubes updated NUTCH-857:
-------------------------------
Attachment: NUTCH-857-1-20100619.patch
Fixes distributed search bug calling close on RPC counterparts.
> DistributedBeans should not close their RPC counterparts
> --------------------------------------------------------
>
> Key: NUTCH-857
> URL: https://issues.apache.org/jira/browse/NUTCH-857
> Project: Nutch
> Issue Type: Bug
> Affects Versions: 1.1
> Environment: All
> Reporter: Dennis Kubes
> Assignee: Dennis Kubes
> Fix For: 1.2
>
> Attachments: NUTCH-857-1-20100619.patch
>
>
> DistributedSearch and Segment Beans currently call close on their RPC counterparts from their own close methods. This results in killing (closing) all distributed servers when the main bean (website, application, etc) is shutdown. DistributedSearchServer (SegmentServer) are run independent from the main NutchBean or website calling those servers in shard type environments. With the current code the distributed servers are closed and any further search requests throw IndexAlreadyClosed exceptions. The distributed servers have to be restarted before searching can resume. Obviously this doesn't work in a large distributed search where multiple beans could be called the distributed servers and where distributed servers could be coming up and down frequently.
> The solution is simple though. The Distributed beans shouldn't call close on their RPC counterparts. Patch is attached.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (NUTCH-857) DistributedBeans should not close their
RPC counterparts
Posted by "Dennis Kubes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NUTCH-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Kubes closed NUTCH-857.
------------------------------
done
> DistributedBeans should not close their RPC counterparts
> --------------------------------------------------------
>
> Key: NUTCH-857
> URL: https://issues.apache.org/jira/browse/NUTCH-857
> Project: Nutch
> Issue Type: Bug
> Affects Versions: 1.1
> Environment: All
> Reporter: Dennis Kubes
> Assignee: Dennis Kubes
> Fix For: 1.2
>
> Attachments: NUTCH-857-1-20100619.patch
>
>
> DistributedSearch and Segment Beans currently call close on their RPC counterparts from their own close methods. This results in killing (closing) all distributed servers when the main bean (website, application, etc) is shutdown. DistributedSearchServer (SegmentServer) are run independent from the main NutchBean or website calling those servers in shard type environments. With the current code the distributed servers are closed and any further search requests throw IndexAlreadyClosed exceptions. The distributed servers have to be restarted before searching can resume. Obviously this doesn't work in a large distributed search where multiple beans could be called the distributed servers and where distributed servers could be coming up and down frequently.
> The solution is simple though. The Distributed beans shouldn't call close on their RPC counterparts. Patch is attached.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Work started: (NUTCH-857) DistributedBeans should not close
their RPC counterparts
Posted by "Dennis Kubes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NUTCH-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on NUTCH-857 started by Dennis Kubes.
> DistributedBeans should not close their RPC counterparts
> --------------------------------------------------------
>
> Key: NUTCH-857
> URL: https://issues.apache.org/jira/browse/NUTCH-857
> Project: Nutch
> Issue Type: Bug
> Affects Versions: 1.1
> Environment: All
> Reporter: Dennis Kubes
> Assignee: Dennis Kubes
> Fix For: 1.2
>
> Attachments: NUTCH-857-1-20100619.patch
>
>
> DistributedSearch and Segment Beans currently call close on their RPC counterparts from their own close methods. This results in killing (closing) all distributed servers when the main bean (website, application, etc) is shutdown. DistributedSearchServer (SegmentServer) are run independent from the main NutchBean or website calling those servers in shard type environments. With the current code the distributed servers are closed and any further search requests throw IndexAlreadyClosed exceptions. The distributed servers have to be restarted before searching can resume. Obviously this doesn't work in a large distributed search where multiple beans could be called the distributed servers and where distributed servers could be coming up and down frequently.
> The solution is simple though. The Distributed beans shouldn't call close on their RPC counterparts. Patch is attached.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.