Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-10034

On Windows agents should use per-logfile locks instead of common locks between all agents in session

    Details

    • Type: Incident report
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.2.10
    • Fix Version/s: 3.0.0alpha5
    • Component/s: Agent (G)
    • Labels:
    • Environment:
      Windows Server 2008.

      Description

      See sub-issue (133) of ZBXNEXT-1263, ZBX-10033.

      Currently on Windows all agents running in the same session (same lock namespace) use common locks: ZBX_MUTEX_LOG, ZBX_MUTEX_PERFSTAT.

      This is a risky dependency between agents. Possible effects:

      • reduced performance due to all agents waiting in line to acquire the same lock;
      • stalls of all agents in case one of them gets stuck after acquiring lock (due to debugging, stopping from process manager by user, etc.);
      • in case of problem with the lock itself (it is removed by admin, abandoned by one agent, etc.) all agents are affected.

      In Unix we use SysV mutexes with limited namespace. On Windows we can convert at least ZBX_MUTEX_LOG to the name of the log file that this lock is protecting.

      We could also use configuration file or hostname (if -m was used) as a prefix for these locks.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              sandis.neilands Sandis Neilands (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: