Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-53548

Allow GC Logging or Java agent configuration for Synchrony

    • 8
    • 4
    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      We should allow free-form JVM arguments instead of the ones defined with -D prefix in the synchrony-args.properties.

      Workaround

      It is possible to add the GC Logging JVM arguments in the start-synchrony.sh for Data Center if you choose to setup the Synchrony Cluster yourself in the Confluence Data Center.

      1. Locate the line JAVA_OPTS="-Xss2048k -Xmx2g"
      2. Modify it as below:
        Example of adding GC Logging arguments
        JAVA_OPTS="-Xss2048k -Xmx2g -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintGCCause -XX:+PrintTenuringDistribution -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=2M -Xloggc:<synchrony-directory-path>/gc.log"
        

      This workaround doesn't apply to :

      • Confluence Standalone Server
      • Confluence Managed Synchrony in Data Center from v6.12 and above

      Other options: How to monitor the Synchrony cluster health

          Form Name

            [CONFSERVER-53548] Allow GC Logging or Java agent configuration for Synchrony

            A fix for this issue is available in Confluence Server and Data Center 7.20.0.
            Upgrade now or check out the Release Notes to see what other issues are resolved.

            James Whitehead added a comment - A fix for this issue is available in Confluence Server and Data Center 7.20.0. Upgrade now or check out the Release Notes to see what other issues are resolved.

            Please get this implemented. We need to be able to monitor this separate jvm for all the reasons already mentioned. We're running confluence 7.3.1 and believe synchrony is the culprit of crashing our confluence instance. We lose edit/save functionality regularly and are forced to restart.

             

            Ryan Goodwin added a comment - Please get this implemented. We need to be able to monitor this separate jvm for all the reasons already mentioned. We're running confluence 7.3.1 and believe synchrony is the culprit of crashing our confluence instance. We lose edit/save functionality regularly and are forced to restart.  

            I would like to monitor the Synchrony GC memory usage as our Synchrony keeps dying in last months couple of times and server went to hung state where no user can do anything on confluence.

            Chander Korshika added a comment - I would like to monitor the Synchrony GC memory usage as our Synchrony keeps dying in last months couple of times and server went to hung state where no user can do anything on confluence.

            I would like to monitor the Synchrony GC memory usage through JMX for external monitoring.

            James Brown added a comment - I would like to monitor the Synchrony GC memory usage through JMX for external monitoring.

            Really need this – I feel like I'm debugging a blackbox.

            Steven F Behnke added a comment - Really need this – I feel like I'm debugging a blackbox.

            +1. Our Synchrony keeps dying with OutOfMemoryErrors despite increased heap. I'd like to pass -Xloggc or -XX:+HeapDumpOnOutOfMemoryError to the JVM to debug further.{{}}

            Jeff Turner added a comment - +1. Our Synchrony keeps dying with OutOfMemoryErrors despite increased heap. I'd like to pass -Xloggc or -XX:+HeapDumpOnOutOfMemoryError to the JVM to debug further.{{}}

              ablekhman@atlassian.com Alex Blekhman (Inactive)
              ttranminh Tam Tran
              Votes:
              53 Vote for this issue
              Watchers:
              46 Start watching this issue

                Created:
                Updated:
                Resolved: