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

Try get rid of custom discovery message for client cache start

    XMLWordPrintableJSON

Details

    • Task
    • Status: Resolved
    • Critical
    • Resolution: Fixed
    • None
    • 2.1
    • cache

    Description

      Currently both server and client caches are started in the same way - using custom discovery message. Most probably for client caches we do not need strong ordering guarentees which discovery messages provide.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. IGNITE-5763 Race in concurrent client cache start

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: