Skip to Main Content
HCL Domino Ideas Portal

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Status Needs Review
Workspace Sametime
Created by Guest
Created on Nov 27, 2025

Let Sametime re-create the indexes when TTL or HISTORY settings are changed

When you change parameters for Mongo TTL or User History, you need to remove 2 indexes in order to let Sametime work with the new settings. If you forget that, and start Sametime again, Sametime will not start at all. You see many exceptions in the logs regarding wrong indexes.


If you remove those indexes, Sametime can create them automatically with the new parameters. That part is already working fine.


Please let Sametime do a pre-check on those 2 indexes if all settings are correct. If not: remove those indexes and create them afterwards again with the new parameters.

It's a simple check and action and would make our work so much easier. :-)


Here you can set the values and remove the indexes afterwards.

custom.env:

CLI__Chatlogging__CL_MONGO_HISTORY_TTL=365

STI__stconvomap__CONVOMAP_MAX_DAYS=365

CL__MONGO_USER_HISTORY_TIMELIMIT=90

CL__MONGO_USER_HISTORY_TIMEUNIT=DAYS


Mongosh:

use chatlogging

db.EVENTS.getIndexes()

db.EVENTS.dropIndex("TimeStamp_1")

db.USERS.dropIndex("date_1")



  • Attach files