Open reetp opened 6 months ago
I wanted to work in thus issue please Assign this issue to me.
I wanted to work in thus issue please Assign this issue to me.
No one assigns issues here.
The answer is to delete the old indexes and let Rocket re-create them.
Possibly needs manual intervention in the DB.
So I went through the DB using Studio3T and dropped each index.
Some new ones re-appeared =on restart so I stopped, removed and started again until they were all cleared. Seems quite happy now.
Not sure how this occurred, and why Rocket can't heal itself?
this is weird.. maybe a bug on MongoDB? a few errors from your logs are like this one:
Requested index: { v: 2, key: { desktopNotifications: 1 }, name: "desktopNotifications_1", sparse: true },
existing index: { v: 2, key: { desktopNotifications: 1 }, name: "desktopNotifications_1", sparse: 1 }
as we can see the index is the exact the same, but MongoDB might have converted during migration to sparse: 1
and since the code didn't change we know we've always been providing sparse: true
.. so it is either a bug during MongoDB migration or during the validation I'd say..
Hello Mr Sampiao ;-)
Hope you are well!!
Yup. Very strange.
Seemed to occur around when I upgraded to 5.x
I have a native mongo from rpms and rocket in docker.
I deleted the logged index issues and then new ones appeared.
Work docker container took about 10 rocket restarts to clear them all.
I have some old backups if you want to look further. You can get me on open at reetp :-)
After upgrade of Mongo DB from 4 to 5 I get errors in the logs. Full log below.
This is repeatable and has occurred on 3 different instances.
Steps to reproduce:
Upgrade Mongo DB from 4 to 5
Restart rocket with docker-compose
Expected behavior:
No errors
Actual behavior:
As per logs below
Server Setup Information:
Deployment Version 6.6.2 Apps Engine Version 1.41.0 Node Version v14.21.3 Database Migration 304 (March 2, 2024 10:10 PM) MongoDB 5.0.25 / wiredTiger (oplog Enabled) Commit Details HEAD: (44b682f6b) Branch: HEAD Release 6.6.2
Client Setup Information
NA
Additional context
3 rocket.chat servers all upgraded from prior versions - one from around 0.32 or possibly earlier!
Relevant logs:
Seems the same error but different collections depening on the server
Server 1
Server 2