We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-20336

Searching and Mentioning users may cause performance issues and high CPU load

XMLWordPrintable

      Issue Summary

      Certain functionalities in Jira, such as trying to mention users or otherwise typing usernames into user fields, allow Jira to return user suggestions as usernames are being typed out.

      As the searching user types, Jira will use a thread to perform a search against what they've typed and return possible results back to the user. In instances with many users, directories, or nested groups, these searches may be computationally expensive and may run for several seconds in order to return results.

      It is possible for the searching user to continue typing and end up making multiple user search requests before the previous requests ever complete and return. Jira will not cancel or otherwise terminate previously ongoing search threads in this case.

      The instance may experience high CPU load and thread utilization if too many of these threads are working on these searches concurrently.

      Steps to Reproduce

      1. Have many users, groups/nested groups, and directories.
      2. Attempt to search for a user (i.e. by mentioning or perhaps trying to assign an issue), by typing a character out at a pace of 2-3 characters/second.

      Expected Results

      Suggested users will be returned, and no other behaviors (high CPU/thread usage) are observed.

      Actual Results

      Suggested users may be returned, but CPU and thread usage run high. Excessive usage may cause the system to become unresponsive.

      Thread Dumps show many threads like the following, which showcase a user mention being searched against nested groups in this particular example:

      "http-nio-8080-exec-20 url:/rest/internal/2/user/mention/search username:" #49 daemon prio=5 os_prio=0 tid=0x00007f8210b43000 nid=0x5d85 runnable [0x00007f810e1e1000]
   java.lang.Thread.State: RUNNABLE
	...
	at com.atlassian.crowd.search.EntityDescriptor.toString(EntityDescriptor.java:103)
	at java.lang.String.valueOf(String.java:2994)
	at java.lang.StringBuilder.append(StringBuilder.java:131)
	at com.atlassian.crowd.search.query.membership.MembershipQuery.(MembershipQuery.java:60)
	at com.atlassian.crowd.search.query.membership.GroupMembershipQuery.(GroupMembershipQuery.java:19)
	at com.atlassian.crowd.search.builder.QueryBuilder.createMembershipQuery(QueryBuilder.java:177)
	at com.atlassian.crowd.search.builder.QueryBuilder$PartialMembershipQueryWithNameToMatch.returningAtMost(QueryBuilder.java:285)
	at com.atlassian.crowd.manager.directory.RemoteDirectorySearcher.findNestedGroupMembershipsIncludingGroups(RemoteDirectorySearcher.java:278)
	at com.atlassian.crowd.manager.directory.RemoteDirectorySearcher.findNestedGroupMembershipsOfUser(RemoteDirectorySearcher.java:300)
	at com.atlassian.crowd.manager.directory.RemoteDirectorySearcher.getParentDirectoryEntities(RemoteDirectorySearcher.java:203)
	at com.atlassian.crowd.manager.directory.RemoteDirectorySearcher.getRelatedDirectoryEntities(RemoteDirectorySearcher.java:191)
	at com.atlassian.crowd.manager.directory.RemoteDirectorySearcher.searchNestedGroupRelationships(RemoteDirectorySearcher.java:170)
	at com.atlassian.crowd.manager.directory.DirectoryManagerGeneric.searchNestedGroupRelationships(DirectoryManagerGeneric.java:750)
	at com.atlassian.crowd.manager.application.SingleDirectorySearchStrategy.searchNestedGroupRelationships(SingleDirectorySearchStrategy.java:71)

      Access Logs show individual HTTP requests being made for each character typed:

      /rest/api/latest/user/assignable/search?username=j
/rest/api/latest/user/assignable/search?username=ji
/rest/api/latest/user/assignable/search?username=jir
/rest/api/latest/user/assignable/search?username=jira
/rest/api/latest/user/assignable/search?username=jiraa

      Workaround

      Reducing the complexity and dataset of users, groups, nested groups, and directories may help reduce the calculation cost and time of these searches.

      Suggested Solution

      Allow administrators to configure the frequency at which the browser may submit search requests.

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Jira Software Data Center'
            1. Jira Software Data Center
            2. JSWSERVER-20336

            Searching and Mentioning users may cause performance issues and high CPU load

            XMLWordPrintable

                Issue Summary

                Certain functionalities in Jira, such as trying to mention users or otherwise typing usernames into user fields, allow Jira to return user suggestions as usernames are being typed out.

                As the searching user types, Jira will use a thread to perform a search against what they've typed and return possible results back to the user. In instances with many users, directories, or nested groups, these searches may be computationally expensive and may run for several seconds in order to return results.

                It is possible for the searching user to continue typing and end up making multiple user search requests before the previous requests ever complete and return. Jira will not cancel or otherwise terminate previously ongoing search threads in this case.

                The instance may experience high CPU load and thread utilization if too many of these threads are working on these searches concurrently.

                Steps to Reproduce

                1. Have many users, groups/nested groups, and directories.
                2. Attempt to search for a user (i.e. by mentioning or perhaps trying to assign an issue), by typing a character out at a pace of 2-3 characters/second.

                Expected Results

                Suggested users will be returned, and no other behaviors (high CPU/thread usage) are observed.

                Actual Results

                Suggested users may be returned, but CPU and thread usage run high. Excessive usage may cause the system to become unresponsive.

                Thread Dumps show many threads like the following, which showcase a user mention being searched against nested groups in this particular example:

                "http-nio-8080-exec-20 url:/rest/internal/2/user/mention/search username:" #49 daemon prio=5 os_prio=0 tid=0x00007f8210b43000 nid=0x5d85 runnable [0x00007f810e1e1000]
   java.lang.Thread.State: RUNNABLE
	...
	at com.atlassian.crowd.search.EntityDescriptor.toString(EntityDescriptor.java:103)
	at java.lang.String.valueOf(String.java:2994)
	at java.lang.StringBuilder.append(StringBuilder.java:131)
	at com.atlassian.crowd.search.query.membership.MembershipQuery.(MembershipQuery.java:60)
	at com.atlassian.crowd.search.query.membership.GroupMembershipQuery.(GroupMembershipQuery.java:19)
	at com.atlassian.crowd.search.builder.QueryBuilder.createMembershipQuery(QueryBuilder.java:177)
	at com.atlassian.crowd.search.builder.QueryBuilder$PartialMembershipQueryWithNameToMatch.returningAtMost(QueryBuilder.java:285)
	at com.atlassian.crowd.manager.directory.RemoteDirectorySearcher.findNestedGroupMembershipsIncludingGroups(RemoteDirectorySearcher.java:278)
	at com.atlassian.crowd.manager.directory.RemoteDirectorySearcher.findNestedGroupMembershipsOfUser(RemoteDirectorySearcher.java:300)
	at com.atlassian.crowd.manager.directory.RemoteDirectorySearcher.getParentDirectoryEntities(RemoteDirectorySearcher.java:203)
	at com.atlassian.crowd.manager.directory.RemoteDirectorySearcher.getRelatedDirectoryEntities(RemoteDirectorySearcher.java:191)
	at com.atlassian.crowd.manager.directory.RemoteDirectorySearcher.searchNestedGroupRelationships(RemoteDirectorySearcher.java:170)
	at com.atlassian.crowd.manager.directory.DirectoryManagerGeneric.searchNestedGroupRelationships(DirectoryManagerGeneric.java:750)
	at com.atlassian.crowd.manager.application.SingleDirectorySearchStrategy.searchNestedGroupRelationships(SingleDirectorySearchStrategy.java:71)

                Access Logs show individual HTTP requests being made for each character typed:

                /rest/api/latest/user/assignable/search?username=j
/rest/api/latest/user/assignable/search?username=ji
/rest/api/latest/user/assignable/search?username=jir
/rest/api/latest/user/assignable/search?username=jira
/rest/api/latest/user/assignable/search?username=jiraa

                Workaround

                Reducing the complexity and dataset of users, groups, nested groups, and directories may help reduce the calculation cost and time of these searches.

                Suggested Solution

                Allow administrators to configure the frequency at which the browser may submit search requests.

                        Unassigned Unassigned
                        kliou Kevin Liou
                        Votes:
                        30 Vote for this issue
                        Watchers:
                        52 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Unassigned Unassigned
                            kliou Kevin Liou
                            Affected customers:
                            30 This affects my team
                            Watchers:
                            52 Start watching this issue

                              Created:
                              Updated:
                              Resolved: