[ClusterLabs] Q: crm_compress_string

[Andrew Beekhof]

On Tue, Nov 15, 2016 at 6:35 PM, Ulrich Windl
<Ulrich.Windl at rz.uni-regensburg.de> wrote:
>
> Hi!
>
> I have a question regarding SLES11 SP4: In pacemaker log I see many messages like these:
>
> Nov 14 00:00:02 [22409] h04        cib:     info: crm_compress_string:     Compressed 162583 bytes into 13009 (ratio 12:1) in 27ms
> Nov 14 01:00:01 [22409] h04        cib:     info: cib_process_request:     Forwarding cib_query operation for section configuration to master (origin=local/cibadmin/2)
> Nov 14 01:00:02 [22409] h04        cib:     info: crm_compress_string:     Compressed 162583 bytes into 12960 (ratio 12:1) in 33ms
> Nov 14 02:00:01 [22409] h04        cib:     info: cib_process_request:     Forwarding cib_query operation for section configuration to master (origin=local/cibadmin/2)
>
> So it seems something is happening every hour. That's OK, and I think it's a "cibadmin -Q" or "crm configure show" operation run by some cron job. But what about the compression message: First is it so important that it has to be logged?

Not anymore

>
> Second: Why is this kind of compression done?

Corosync has a maximum message size and it cuts down on the amount of
bandwidth we're consuming.

>
> cibadmin -Q displays plain XML.

Its automatically decompressed on the other end.

>
>
> Regards,
> Ulrich
>
>
>
>
> _______________________________________________
> Users mailing list: Users at clusterlabs.org
> http://clusterlabs.org/mailman/listinfo/users
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org