Uploaded image for project: 'ZABBIX FEATURE REQUESTS'
  1. ZABBIX FEATURE REQUESTS
  2. ZBXNEXT-4920

Configurable ZBX_MAX_RECV_DATA_SIZE (limit per connection)

XMLWordPrintable

    • Icon: New Feature Request New Feature Request
    • Resolution: Fixed
    • Icon: Critical Critical
    • 4.0.13rc1, 4.2.7rc1, 4.4.0alpha3, 4.4 (plan)
    • 4.0.1
    • Proxy (P), Server (S)
    • Sprint 55 (Aug 2019)
    • 0.125

      Related: ZBX-7777

      The following constant is defined and not configurable.

      Index: trunk/include/common.h
===================================================================
--- trunk/include/common.h	(revision 43681)
+++ trunk/include/common.h	(revision 43682)
@@ -893,7 +893,7 @@
 #define ZBX_JAN_2038		2145916800
 #define ZBX_JAN_1970_IN_SEC	2208988800.0	/* 1970 - 1900 in seconds */
 
-#define ZBX_MAX_RECV_DATA_SIZE	(64 * ZBX_MEBIBYTE)
+#define ZBX_MAX_RECV_DATA_SIZE	(128 * ZBX_MEBIBYTE)
 
 /* max length of base64 data */
 #define ZBX_MAX_B64_LEN	(16 * ZBX_KIBIBYTE)

      This is causing a major issue for large server/proxy configurations. As the proxies are unable to retrieve the configuration:

      12111:20181217:101346.318 Uncompressed message size 7464888 from zabbix-server exceeds the maximum size 134217728 bytes. Message ignored. 
12111:20181217:101346.318 cannot obtain configuration data from server at zabbix-server:

      Note: The error message uncompressed message size value was fixed in -ZBX-15138-

      So the ZBX_MAX_RECV_DATA_SIZE constant should be configurable, or better yet the limitation removed exclusively for Server/Proxy configuration dissemination to avoid this issue.

            ak Andrejs Kozlovs
            gashton Grant Ashton
            Team A
            Votes:
            6 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated:
              Resolved: