You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
TraceReactorConfiguration configures Hooks for reactor based on the spring.sleuth.reactor.instrumentation-type property.
However on RefreshScopeRefreshedEvent the HooksRefresher bean decorates reactor with bothDECORATE_QUEUES and DECORATE_ON_EACH when the spring.sleuth.reactor.instrumentation-type is set to DECORATE_QUEUES.
The switch statement is missing a break when the DECORATE_QUEUES is done.
This causes Applications that have DECORATE_QUEUES set and get a RefreshScopeRefreshedEvent to spike in cpu usage due hooks added from both DECORATE_QUEUES and DECORATE_QUEUES.
The text was updated successfully, but these errors were encountered:
Describe the bug
TraceReactorConfiguration configures Hooks for reactor based on the
spring.sleuth.reactor.instrumentation-type
property.However on RefreshScopeRefreshedEvent the HooksRefresher bean decorates reactor with both
DECORATE_QUEUES
andDECORATE_ON_EACH
when thespring.sleuth.reactor.instrumentation-type
is set toDECORATE_QUEUES
.The switch statement is missing a
break
when theDECORATE_QUEUES
is done.See:
spring-cloud-sleuth/spring-cloud-sleuth-autoconfigure/src/main/java/org/springframework/cloud/sleuth/autoconfig/instrument/reactor/TraceReactorAutoConfiguration.java
Line 142 in 4446b76
This causes Applications that have
DECORATE_QUEUES
set and get a RefreshScopeRefreshedEvent to spike in cpu usage due hooks added from bothDECORATE_QUEUES
andDECORATE_QUEUES
.The text was updated successfully, but these errors were encountered: