@PitaJ Out of town on a big project at the moment - have limited time and connectivity. I'll update this weekend.
okay, upgrade completed - took almost 3 hours to delete the sessions, took the site down to do it, now running at 1.5.0.
New problem, when uploading images my users are getting: "something went wrong trying to parse the server response" - the upload URL appears in the post, but no pic. eg:
@Haitch there was a bug which caused the sessions to be stored for 1000x the time they were supposed to be. That's why we're clearing the sessions in the first place.
that's definitely an oops - but been, there done that in my own code.
Guess it's just bite the bullet and do it. I imagine not having to track over 5 million phantom sessions should make the site more responsive .....
./redis-cli KEYS "sess:*" | wc -l
The clone finally did completely process the upgrade - so I guess I'm just going to have to bite the bullet and take my site down for as long as it takes.
As for the "redis-cli KEYS "sess:*" | wc -l" command: 5,379,194
What the heck could have caused that many "long-lived" sessions?
I'm running the upgrade (to 1.5.0) on a clone of the VM, it's been sitting at "Deleting accidently long-lived sessions" for over 2 hours. No sign of a progress bar. Just that message. Is there anything that can be done prior to running the upgrade? I really don't want to take my site down for this long.
I've a 1.4.5 instance of NodeBB that I tried previously tried to upgrade to 1.4.6 and again today tried to upgrade to 1.5.0. In both instances I ran into the same issue. During the schema update it gets to "Delete Sessions" and never moves beyond there. The CPU is running at 100%, but there appears to be no disk activity. I've left it running for over an hour and 0 progress past that step.