[jira] [Resolved] (JAMES-4194) Tiering: max threading window
René Cordier (Jira) <[email protected]> Wed, 1 Apr 2026 02:22:00 +0000 (UTC)
| Newsgroups | gmane.comp.jakarta.james.devel |
|---|---|
| Message-ID | <[email protected]> |
[ https://issues.apache.org/jira/browse/JAMES-4194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
René Cordier resolved JAMES-4194.
---------------------------------
Resolution: Fixed
> Tiering: max threading window
> -----------------------------
>
> Key: JAMES-4194
> URL: https://issues.apache.org/jira/browse/JAMES-4194
> Project: James Server
> Issue Type: Improvement
> Components: cassandra, JMAP
> Reporter: René Cordier
> Assignee: Antoine Duprat
> Priority: Major
> Fix For: 3.10
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> h2. Why
> The cassandra table "thread_2" for storing thread data with the threadId guessing algorithm can grow significantly large over time.
> An option for tiering data in that table after a certain amount of time should provide useful in some use cases.
> h2. How
> Proposal is to add an optional TTL to the thread_2 table.
> In `jvm.properties`:
> {code:java}
> james.thread.window=90d
> {code}
> Default to none (keep forever)
> Document this in "tiering documentation".
> Note that "thread_lookup_3" needs to be kept for correctness (it's much smaller)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)