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

Start CacheProcessor before QueryProcessor

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

Details

    • Bug
    • Status: Closed
    • Critical
    • Resolution: Fixed
    • None
    • ignite-1.4
    • cache
    • None

    Description

      Now QueryProcessor is started before CacheProcessor. With this order cache processor can be stopped at the moment when query request is processed, and this causes sporadic errors like NPE (I see this from time to time in IgniteCacheQueryNodeRestartSelfTest).

      Looks like cache processor does not need QueryProcessor when it's 'start' method is called so I think start order should be changed.

      Attachments

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

          People

            Unassigned Unassigned
            sboikov Semen Boikov
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment