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

Cluster state (active/inactive) should be checked on individual operations rather than on facades

    XMLWordPrintableJSON

Details

    • Task
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 2.1
    • None
    • general

    Description

      When persistence is enabled cluster can be in either active or inactive state. Currently we check cluster state only when user trying to get certain facade from Ignite interface, but never check it on individual operations. This is wrong from usability perspective as facades are typically long-lived objects.

      Let's make sure that cluster state check is performed on individual operations instead.

      Attachments

        Activity

          People

            Unassigned Unassigned
            vozerov Vladimir Ozerov
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: