Unicorn now appears to run by default in nightly omnibus setups
Testing today on our performance Reference Architectures with the latest had unusual results. Inspecting further on our metrics should dramatic looking stats:
Thankfully I've seen this sort of behavior before and knew this was very likely due to a component running now by default when it shouldn#t be regardless of role selected.
This looks to be exactly the case and Unicorn now looks to be enabled by default under the hood in the latest Omnibus Nightly packages. For example on a node with the role redis_sentinel_role
:
run: consul: (pid 1758) 1626s; run: log: (pid 1753) 1626s
run: logrotate: (pid 1755) 1626s; run: log: (pid 1749) 1626s
run: node-exporter: (pid 1757) 1626s; run: log: (pid 1750) 1626s
run: sentinel: (pid 1756) 1626s; run: log: (pid 1754) 1626s
run: unicorn: (pid 5199) 12s; run: log: (pid 1733) 1626s
Best I can tell this is happening across the board unless we specifically have unicorn['enable'] = false
set in config. This suggest the setting is now true under the hood. This is maybe related to the recent deprecation of Unicorn settings.