[
https://issues.apache.org/jira/browse/JAMES-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16706629#comment-16706629
]
Tellier Benoit commented on JAMES-2555:
---------------------------------------
@mbaechler is not happy with the webadmin ReIndexing API cf
https://github.com/linagora/james-project/pull/1948#discussion_r236977988
Proposal that emerged from PR comments:
{code:java}
#ReIndex all mailboxes
POST /mailboxes?task=reIndex
# A single mailbox
POST /mailboxes/id?task=reIndex
# A single message in a mailbox
POST /mailboxes/id/messages/mId?task=reIndex
# A single message
POST /messages/id/?task=reIndex
# A single user
POST /mailboxes?task=reIndex&[email protected]
{code}
> Re-indexing big mailboxes fails
> -------------------------------
>
> Key: JAMES-2555
> URL: https://issues.apache.org/jira/browse/JAMES-2555
> Project: James Server
> Issue Type: Bug
> Components: CLI, mailbox
> Affects Versions: 3.0.0, master, 3.0.1, 3.1.0
> Reporter: Tellier Benoit
> Priority: Major
> Labels: perf
> Fix For: 3.2.0
>
>
> Reported internally:
> {code:java}
> Doing a reindex via the CLI on a mailbox which contains ~24000 mails does not
> work.
> - heap out of memory issue
> Heap increased, then:
> - cassandra timeout when increasing heap
> Timeout increased, then:
> - heap out of memory issue
> Heap increased, then:
> - GC overhead limit exceeded
> {code}
> In ReIndexerImpl instead of doing a FULL read to reindex the all mailbox (AND
> all of the related data) we should rather do a first metadata query to load
> uids then perform subsequent single reads.
> That is the root issue: trying to load 11 Go of mails in memory.
> Furthermore, a simple error should not trigger the end of a ReIndexing.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
