Skip to content
This repository was archived by the owner on Oct 6, 2023. It is now read-only.

20.04.9

Choose a tag to compare

View all tags
@tuntoja tuntoja released this 26 Oct 15:27
· 130 commits to master since this release
20.04.9
aef6add

Known behaviours:

  • If Broker on a Poller or Remote Server is not upgraded to 20.04.9
    the communication between said Poller or Remote Server and an
    upgraded Central may not work.

    As always, we strongly recommend to upgrade all components to match
    the Central server's version.

    However, during an upgrade process, communication can be maintained
    by making sure Broker's configurations match the following conditions:

    • TLS encryption and compression are either set to
      Auto or No on Central input,
    • TLS encryption and compression are either set to
      Auto or No on Poller or Remote Server output.

    If the reversed connection mode (one peer retention) is used,
    the Broker upgrade is mandatory.

Bugfixes

One peer retention

A known regression in the 20.04 Broker release was that the one peer
retention did not work correctly. It is fixed with this version.

Columns contents too large

In case of strings too large to be inserted in database, strings are
now truncated as if the database was configured in non strict mode.

Negotiations

Compression and TLS could fail between Engine and Broker, because of
issues in the negotiation between them. This is now fixed. If you
mix previous 20.04.x cbmod/cbd with this new one, you may continue to
have issues on this subject. We recommend you to do the upgrade of cbmod/cbd
on all of your pollers.

Database deadlock

When the database connectors are configured with several connections,
a host downtime could make a deadlock on the database. This is fixed now.

Map server connection

When the Map server is restarted, there is no more duplicated connections
from centreon-broker.

BAM reporting

BAM availability reporting could miss BAs during its availabilities
computations. This is fixed.

TCP acceptors

Sometimes TCP acceptor could badly close sockets. This could lead to
difficulties to reopen connections.

INITIAL HOST STATE

If you use BAM, there was an issue on the reporting that could fail
because of a missing initial host state. This is fixed now.

Enhancements

TCP connector

The TCP connector should also be largely improved. It is multithreaded
now and this should improve its performances. A new field in the Broker
configuration file allows to set how many threads run in the pool.

TCP connections

TCP connections are managed by a thread pool. When not configured, this
thread pool contains at least 2 threads and can increase up to half the
number of server CPUs. Otherwise, it is possible to configure it in the
TCP endpoint with the 'pool_size' label.

For more information, report to the official documentation release notes.

Assets 2
Loading