Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-62707

As an JIRA Administrator for JIRA Datacenter I want to log User cache flush events

XMLWordPrintable

    • We collect Jira 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.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Problem Definition

      In JIRA Datacenter cache for Users and Group is a core for many functionality. Cache flush for them is vert expensive and lead to significant performance degradation of the whole cluster.

      Suggested Solution

      Add INFO logging event for each cache flush event and additional DEBUG logging with stackrace to track source the flush event.

      Implemented solution

      • In fixed JIRA version, there is a logging for cache flush events. 
        2017-01-25 23:55:19,583 http-nio-8090-exec-1 INFO      [c.a.c.e.c.a.j.c.e.ofbiz.EagerOfBizUserCache.userCache] Cache com.atlassian.jira.crowd.embedded.ofbiz.EagerOfBizUserCache.userCache was flushed
      • Please note that this logging has no performance impact.
      • How to enable logging for cache flush events:
        1. Navigate to Cog Icon > System > Logging and profiling
        2. Find com.atlassian.cache.event and set it to INFO level

        1. upload.png
          upload.png
          1.37 MB

          Form Name

            [JRASERVER-62707] As an JIRA Administrator for JIRA Datacenter I want to log User cache flush events

            Andriy Yakovlev [Atlassian] made changes -
            Link New: This issue is related to JRASERVER-70298 [ JRASERVER-70298 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3062118 ] New: JAC Suggestion Workflow 3 [ 3691843 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2617918 ] New: JAC Suggestion Workflow [ 3062118 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2587382 ] New: Confluence Workflow - Public Facing v4 [ 2617918 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2352603 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2587382 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Andriy Yakovlev [Atlassian] made changes -
            Remote Link New: This issue links to "Page (Extranet)" [ 323498 ]
            Andriy Yakovlev [Atlassian] made changes -
            Link New: This issue was cloned as JRASERVER-66031 [ JRASERVER-66031 ]
            Andriy Yakovlev [Atlassian] made changes -
            Description Original: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-62707].
              {panel}

            h3. Problem Definition
            In JIRA Datacenter cache for Users and Group is a core for many functionality. Cache flush for them is vert expensive and lead to significant performance degradation of the whole cluster.

            h3. Suggested Solution
            Add _INFO_ logging event for each cache flush event and additional _DEBUG_ logging with stackrace to track source the flush event.
             
            h3. Implemented solution
            In fixed JIRA version, there is a logging for cache flush events.
            {noformat}
            2017-01-25 23:55:19,583 http-nio-8090-exec-1 INFO [c.a.c.e.c.a.j.c.e.ofbiz.EagerOfBizUserCache.userCache] Cache com.atlassian.jira.crowd.embedded.ofbiz.EagerOfBizUserCache.userCache was flushed
            {noformat}
            How to enable logging for cache flush events:
            # Navigate to Cog Icon > System > Logging and profiling
            # Find *com.atlassian.cache.event* and set it to _INFO_ level             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-62707].
              {panel}

            h3. Problem Definition
            In JIRA Datacenter cache for Users and Group is a core for many functionality. Cache flush for them is vert expensive and lead to significant performance degradation of the whole cluster.

            h3. Suggested Solution
            Add _INFO_ logging event for each cache flush event and additional _DEBUG_ logging with stackrace to track source the flush event.
             
            h3. Implemented solution
            * In fixed JIRA version, there is a logging for cache flush events.
            {noformat}
            2017-01-25 23:55:19,583 http-nio-8090-exec-1 INFO [c.a.c.e.c.a.j.c.e.ofbiz.EagerOfBizUserCache.userCache] Cache com.atlassian.jira.crowd.embedded.ofbiz.EagerOfBizUserCache.userCache was flushed
            {noformat}
            * Please note that this logging has no performance impact.
            * How to enable logging for cache flush events:
            *# Navigate to Cog Icon > System > Logging and profiling
            *# Find *com.atlassian.cache.event* and set it to _INFO_ level
            Andriy Yakovlev [Atlassian] made changes -
            Description Original: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-62707].
              {panel}

            h3. Problem Definition
            In JIRA Datacenter cache for Users and Group is a core for many functionality. Cache flush for them is vert expensive and lead to significant performance degradation of the whole cluster.

            h3. Suggested Solution
            Add _INFO_ logging event for each cache flush event and additional _DEBUG_ logging with stackrace to track source the flush event.
             
            h3. Implemented solution
            In fixed JIRA version, there is a logging for cache flush events.
            {noformat}
            2017-01-25 23:55:19,583 http-nio-8090-exec-1 INFO [c.a.c.e.c.a.j.c.e.ofbiz.EagerOfBizUserCache.userCache] Cache com.atlassian.jira.crowd.embedded.ofbiz.EagerOfBizUserCache.userCache was flushed
            {noformat}
            How to enable logging for cache flush events: Set *com.atlassian.cache.event* to _INFO_ level
            # Navigate to Cog Icon > System > Logging and profiling
            # Click Configure logging level for another package.
            # Fill the form as follows:
            #* Package name: com.atlassian.cache.event
            #* Logging Level:INFO
            		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-62707].
              {panel}

            h3. Problem Definition
            In JIRA Datacenter cache for Users and Group is a core for many functionality. Cache flush for them is vert expensive and lead to significant performance degradation of the whole cluster.

            h3. Suggested Solution
            Add _INFO_ logging event for each cache flush event and additional _DEBUG_ logging with stackrace to track source the flush event.
             
            h3. Implemented solution
            In fixed JIRA version, there is a logging for cache flush events.
            {noformat}
            2017-01-25 23:55:19,583 http-nio-8090-exec-1 INFO [c.a.c.e.c.a.j.c.e.ofbiz.EagerOfBizUserCache.userCache] Cache com.atlassian.jira.crowd.embedded.ofbiz.EagerOfBizUserCache.userCache was flushed
            {noformat}
            How to enable logging for cache flush events:
            # Navigate to Cog Icon > System > Logging and profiling
            # Find *com.atlassian.cache.event* and set it to _INFO_ level
            Andriy Yakovlev [Atlassian] made changes -
            Description Original: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-62707].
              {panel}

            h3. Problem Definition
            In JIRA Datacenter cache for Users and Group is a core for many functionality. Cache flush for them is vert expensive and lead to significant performance degradation of the whole cluster.

            h3. Suggested Solution
            Add _INFO_ logging event for each cache flush event and additional _DEBUG_ logging with stackrace to track source the flush event.
             
            h3. Workaround
            None             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-62707].
              {panel}

            h3. Problem Definition
            In JIRA Datacenter cache for Users and Group is a core for many functionality. Cache flush for them is vert expensive and lead to significant performance degradation of the whole cluster.

            h3. Suggested Solution
            Add _INFO_ logging event for each cache flush event and additional _DEBUG_ logging with stackrace to track source the flush event.
             
            h3. Implemented solution
            In fixed JIRA version, there is a logging for cache flush events.
            {noformat}
            2017-01-25 23:55:19,583 http-nio-8090-exec-1 INFO [c.a.c.e.c.a.j.c.e.ofbiz.EagerOfBizUserCache.userCache] Cache com.atlassian.jira.crowd.embedded.ofbiz.EagerOfBizUserCache.userCache was flushed
            {noformat}
            How to enable logging for cache flush events: Set *com.atlassian.cache.event* to _INFO_ level
            # Navigate to Cog Icon > System > Logging and profiling
            # Click Configure logging level for another package.
            # Fill the form as follows:
            #* Package name: com.atlassian.cache.event
            #* Logging Level:INFO

              Unassigned Unassigned
              ayakovlev@atlassian.com Andriy Yakovlev [Atlassian]
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: