Carrot2

DCS uses Jetty's built-in thread pool and allows too many concurrent connections.

Details

  • Type: Improvement Improvement
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 3.1.1
  • Component/s: Document Clustering Server
  • Labels:
    None

Description

The DCS (or rather the default container we ship - Jetty), accepts too many concurrent connections; when the clustered documents are big this can lead to memory leaks because of data structures kept concurrently in memory.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Dawid Weiss added a comment -

Resolved in trunk.

Show
Dawid Weiss added a comment - Resolved in trunk.
Hide
Permalink
Stanisław Osiński added a comment -

Out of curiosity, was this a proper memory leak or simply high memory usage (also aggravated by CARROT-571)?

Show
Stanisław Osiński added a comment - Out of curiosity, was this a proper memory leak or simply high memory usage (also aggravated by CARROT-571)?
Hide
Permalink
Dawid Weiss added a comment -

It was not strictly a memory leak, but could lead to out of memory exceptions when too many concurrent threads were fired with their own independent clustering task. Since clustering is mostly computational and takes all the available CPU power, there is little gain in using concurrent threads anyway.

Show
Dawid Weiss added a comment - It was not strictly a memory leak, but could lead to out of memory exceptions when too many concurrent threads were fired with their own independent clustering task. Since clustering is mostly computational and takes all the available CPU power, there is little gain in using concurrent threads anyway.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Carrot2. Try JIRA - bug tracking software for your team.