Jump to content

Upgraded to 4.6 from 4.5 - activity feed dead

Go to solution Solved by Summit360,

Recommended Posts

Recently updated from 4.5 to 4.6 and the activity feed has all but stopped working. Post content is not appearing. Like reactions are. This is on default all activity at the endpoint of:


Is it likely to be the compact vs dynamic table issue?

Other suggestions?

Edited by Summit360
Link to comment
Share on other sites

Confusing as we did the dynamic switch ages ago, so it looks like new tables created recently had the compact. Will check mysql config for a default value.


core_achievements_log however falls over due to a duplicated key

ERROR 1062 (23000): Duplicate entry '132780.2021-09-16-core_SessionStartDaily' for key 'lookup'

Please advise, and or if this impacts the search index at all... which I'm poised to run now as my gut says none of these tables should be altering activity feed or posts behaviour.

Link to comment
Share on other sites

If you are familiar with MySQL, and only after ensuring you have full backups, you can actually delete the indexes on that table while you switch it over. Once done, go to support in your Admin CP and it will prompt you to readd the keys

Incidentally, you may find this helpful with your defaulting


Link to comment
Share on other sites

Would appear the assumption that all was well was mistimed. The rebuild got underway around 3hours ago and activity appeared to flow. However checking back in, the posts and unread content are all for nought since 3hours ago. 

In lieu of any other information, further assistance is required as this is the lifeblood of figuring out what's going on in the community. Thanks.

Link to comment
Share on other sites

I'd say it's an elastic issue based on some system logs, although given that was ok before the upgrade... possibly an issue post.

IPS\Content\Search\Elastic\Exception (0) cluster_block_exception: blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];

It's a hosted cluster for what it's worth. That's not quite hit my storage alarm, but has nonetheless, hit a problem. 

Edited by Summit360
Link to comment
Share on other sites

13 hours ago, Summit360 said:

It's version 6, was fine... It was on 6Gb of 8Gb storage per node. guessing it didn't have enough storage to do the rebuild, just scaling it up to a larger storage... Still a good chance to find out a deployment isn't quite as tweaked as one hoped for 🙂

It does seem elastic will have been the issue based on what you have said, but of course let us know if you find any further problems.

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...