MichaelC

We encounter the same using CentOS 7 + PHP 7.4 + ElasticAPM 1.5.2 Early indications show a downgrade to 1.3.1 as working better...

I'm seeing an improvement, but still some new ERROR logs that are not present when using 1.3.1 (we're still on PHP 7.4 and using an ElasticAPM log level of ERROR)...

Here's more detail behind the CRITICALs we see (even on APM 1.6.1), apparently triggered during every PHP PID recycle (happens fairly often due to PHP-FPM job lifetimes). CentOS 7.9 PHP...

I bumped into and can confirm the first issue, too. And this guide here proved helpful to fill in any gaps: http://www.hawkular.org/blog/2016/04/19/jmxtrans-to-hawkular-metrics.html

We use PHP 7 and Redis 3.2 OK, but only specify a single node on save_path. Does that work for you?

That's an odd one. We just upgraded from 6.12 to 6.20 and the version continues to show fine. We re-ran the entire configure/build process as seen in the readme.

We've used it with v3 and v5 without issue. I don't know if there are specific version requirements. Guessing anything >= 3 is fine.

I've also tried spring-data-redis 1.7.11 and 1.6.6 in case newer versions of that were doing something odd with transactions. No luck. Also, the only way I'm using Jedis is for...

Yeah, it matches the list of commands Dynomite doesn't support. I was just hoping I was somehow using Jedis wrong because it's what Dyno is based on and that apparently...

I'd like to revise this post to be focused on 1 end goal: to ignore SELECT requests. This will increase the availability of using Dynomite with systems that - either...