Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-22560

Processing messages to yourself in a thread pool

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • 3.0
    • None

    Description

      As a result of code analysis, it was discovered that if in org.apache.ignite.internal.network.DefaultMessagingService a message is sent to itself, then processing of the response will be performed in the same thread as the message is sent (without transferring threads to the pool). Which can affect system throughput.
      We need to fix this.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            ktkalenko@gridgain.com Kirill Tkalenko
            ktkalenko@gridgain.com Kirill Tkalenko
            Ivan Bessonov Ivan Bessonov

            Dates

              Created:
              Updated:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 10m
                10m

                Slack

                  Issue deployment