I noticed the number of views in topics (and all other apps) simply got stuck in 0 (zero) after enabling Redis in the Community.

It worked again when Redis was disabled.

Is there any particular setting I need to make for Redis and views increment to work together?

Thanks.

There shouldnt be anything you need to add, no. You dont have any background tasks showing I assume?

I ran the viewupdates task manually but didn’t change the number, that’s when I noticed the core_view_updates table is always empty. No records.

Once Redis is disabled, everything works fine.

What is the recommended Redis version for IPS 4.7.20?

Edited March 28Mar 28 by Adriano Faria

I'm using Redis 6.2.1 locally, but it should work Ok with v7 also.

 

I'm using Redis 6.2.1 locally, but it should work Ok with v7 also.

Matt, the user tested from 5.2 to 7.0, and it is all the same. Is there any special setting or something in Redis I need to do?

Views count simply stall when Redis is enabled.

I've been helping Adriano with this issue. We were able to resolve the issue with views for topics by turning off the "Use Redis to reduce MySQL overhead" setting.

We've now found another issue though. With Redis enabled as the Data Storage Method, the Queued Topic/Post numbers are incorrect. When we set the Data Storage Method back to MySQL, the issue resolves itself. We prefer to keep Redis enabled as without it enabled, unfortunately the page loading times on the forums greatly increase during peak traffic periods.

We've had a look at the Redis keys but can't find the Queued Topic/Post numbers being cached so we're unsure why this issue exists.

Any help would be greatly appreciated.

@Matt / @Marc any possible further suggestions on this please?

We're all a bit stuck on this one.

Is there a different way to go about getting some assistance with this?

3 people have requested help now, the owner of the site/license (me), the developer, and the host themselves who signed up here to try and assist us.

Edited April 15Apr 15 by Emediate

Ive tagged our developer on this, to see what they can advise

THanks Marc. Hopefully it doesn't take too long as our unapproved topic and post counts continue to rise!

 

THanks Marc. Hopefully it doesn't take too long as our unapproved topic and post counts continue to rise!

I have to admit to being somewhat confused by the statement there. If this is broken, dont keep the option switched on

@GoHosting mentioned above, they needed to enable this to solve another prior problem. But this option is not working as expected.

 

I've been helping Adriano with this issue. We were able to resolve the issue with views for topics by turning off the "Use Redis to reduce MySQL overhead" setting.

We've now found another issue though. With Redis enabled as the Data Storage Method, the Queued Topic/Post numbers are incorrect. When we set the Data Storage Method back to MySQL, the issue resolves itself. We prefer to keep Redis enabled as without it enabled, unfortunately the page loading times on the forums greatly increase during peak traffic periods.

We've had a look at the Redis keys but can't find the Queued Topic/Post numbers being cached so we're unsure why this issue exists.

Any help would be greatly appreciated.

@Marc - any update please? We need Redis, however when enabled, it breaks other functionality as outlined above.

Is there an issue with Redis and Invision? Do we need to do something on our end to resolve this? We're stuck here for nearly 1 month since this was posted here.

All of cloud uses Redis. My localhost install uses Redis. I really don’t know why it’s not working for you, but I can take another look today.

I've just checked locally, and it all works as expected. I'm using Redis 6, but 7 will work too.

I debugged the code:

And it logged as expected:

I'd add some logged in system/Content/ViewUpdates.php to see if that code is executing. You could even check the exception to make sure an error isn't being silently logged.

Matt, the views count is resolved as you can see here: https://invisioncommunity.com/forums/topic/482403-redis-x-number-of-views-of-content-item/#findComment-2996664

The problem now is this:

 

We've now found another issue though. With Redis enabled as the Data Storage Method, the Queued Topic/Post numbers are incorrect. When we set the Data Storage Method back to MySQL, the issue resolves itself. We prefer to keep Redis enabled as without it enabled, unfortunately the page loading times on the forums greatly increase during peak traffic periods.

We've had a look at the Redis keys but can't find the Queued Topic/Post numbers being cached so we're unsure why this issue exists.

This:

The pending topics/posts. This is not being updated at all. I'm not sure this is related to Redis, though.