Hosting Total Cost of Ownership Squad

Product Squads
85

1 Sep 2026 Call

Attending

Details

  • Archive

    • after 5.3 is out, what happy path will we offer?
    • Diana has old task archiving feature in beta
    • possibly not an Admin GUI, but just a config to enable specific features of archiving
    • what does “auto archive” look like?
    • UI Extension might be nice because we can iterate on it faster than CHT releases b/c it’s just app config
    • Auto archive of tasks is a 5.4 feature we hope to get merged
    • would be great to get more feedback on the forum post about how to use archive feature to direct 5.4 features
    • big question is what is most impactful to archive? how do we know that tasks will be helpful to archive?

  • Archive Box

    • greenfield project for stand alone archiving for CHT 4.21 and later
    • Diana hesitant to GA release because of maintenance burden

  • in couch 3.5.2 the changed view memory buffer size - but this can be back-ported to 3.5.0

    • private slack thread
    • we should be sure this will work, but large national deployments who are stuck on 4.21 with large data are a great candidate, like archive box
    • this is easy to test on a clone of prod b/c it’s just one setting to do A/B testing

  • Hard limits

86

8 Sep 2026 Call

Attending

Details

  • Archive

    • after 5.3 is out, and discussing national deployments use of the feature
    • started with reports that are >1yr old, but may get more aggressive
    • suggestions based on experience: archive task and target documents as they’re not used
    • PR already open on auto archiving of tasks after 3mo: adds terminal state tasks and old target documents auto archiving
    • hoping archiving at national deployment will free up CPU and memory
    • after archiving is achieved, will turn to focus to users with too many documents per the 5.2 feature.
    • suggestion: starting with users who have too many documents, show a CHT dashboard health. Does it belong in CHT Admin app or in Watchdog? For deployments with >1 deployment, watchdog seems to make more sense.
    • speaking of instance health - in this deployment there was a corrupt shard which maybe could have been exposed by ingesting couch Prometheus endpoint

  • Make downward sync time configurable

    • this was deployed to increase 5 min sync to 30 min sync in hopes of reducing CPU load on server needing to process less
    • is still useful such that should we continue with the ticket?
    • anecdotally it was successful for the national deployment in question
    • if we need it again, having it stuffed in another feature release that isn’t yet built will be too late vs if it’s already in 5.4
    • should be quantified as to when this should be turned on - or if it is a default

  • these two efforts we’re hoping to stop development on in hopes of no one needing them.

    • Archive Box
    • view memory buffer size
    • @antony to reach out to community to find deployments who all both 1) want to upgrade but are extremely disk space constrained so can’t and 2) are on 4.21 - 5.2
    • large deployments on 4.9 should just upgrade to 5.3 and archive after upgrade - the effort to upgrade from 4.9 → 4.21, archive, then 4.21 → 5.3 is the same as 4.9 → 5.3 and archiving

  • Hard limits

    • coming in 5.4!
    • is good!
88

15 Sep 2026 Call

Attending

Details

  • Make downward sync time configurable

    • still outstanding, still planned to be worked on

  • these two efforts we’re hoping to stop development on in hopes of no one needing them.

    • Archive Box & view memory buffer size
    • @antony still to reach out to community to find deployments who all both 1) want to upgrade but are extremely disk space constrained so can’t and 2) are on 4.21 - 5.2
    • note added to docs about archiving causing disk use via fragmentation

  • Hard limits

    • coming in 5.4!
    • still is good!

  • Next TCO effort: Auto archive features in 5.4 starting with tasks & targets

    • task ticket has PR created and is out for review
    • auto archive tasks does it in 50k chunks every 5 minutes in hopes of not overwhelming system
    • feature is enabled made via app settings (boolean)
    • open question about making this default on in future releases? what about default duration? Currently none is set so archiving runs all the time unless you configure it.
    • currently no other archiving features planned for 5.4 unless we hear from partners having more archiving needs