Sally MacFarlane

> I have some good news - the sdk folks are working on making it possible to disable the sdk from auto-starting here: https://github.com/open-telemetry/opentelemetry-java/blob/main/sdk-extensions/autoconfigure/README.md#disabling-opentelemetrysdk @atoulme are we still waiting on...

Another user reporting this issue on Discord https://discord.com/channels/905194001349627914/1015386305871491123 - same block number with different hashes being imported, and then a few blocks skipped, and further blocks saved for future import....

https://github.com/hyperledger/besu/pull/4228

Yes definitely welcome your input @ahamlat ! More context - this came about because @ajsutton said this worked better than the defaults ``` I’m not sure if I’ve said this...

Closing this. From testing and experiments it does not appear to impact peering significantly so we won't change the defaults.

@reductionista I'm closing this one as this ended up being resolved by this PR https://github.com/hyperledger/besu/pull/4355 - thanks for your interest in besu!

blocked by #4140 but the workaround to set fast-sync-min-peers=1 should help

👋 Hi @joyita07 are you still interested in working on this?

A similar issue here - https://stackoverflow.com/questions/60310858/possibly-consider-using-a-shorter-maxlifetime-value-hikari-connection-pool-spr Could it be that the db timeout is lower than the hikari `maxLifetime` property ``` The problem is that the default value of the...

@joshuafernandes have you got a scenario for us to reproduce with?