Uploaded image for project: 'Teiid'
  1. Teiid
  2. TEIID-1654

CLONE - EDS - Node returns 0 rows for cached view when other node had it loaded and leaves cluster

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.4.1, 7.5
    • 7.1
    • Server
    • None
    • Hide

      To recreate:

      1. Start 2 nodes in a cluster with a vdb deployed which has an internal materialized view (IMV).

      2. Query the IMV on node 1 to populate the cache on node 1.

      3. Shutdown node 1

      4. Query the IMV on node 2
      Expectation: node 2 doesn't have a copy of the cache and populates from the sources
      Actual: node 2 returns a successful result with 0 rows. No warning or error is found in the logs.

      Note: this behavior happens when the shutting down in step 3 is done gracefully (and node 2 is notified node 1 is leaving the cluster) as well as when it's done with an kill -9 (simulating a failure)

      Show
      To recreate: 1. Start 2 nodes in a cluster with a vdb deployed which has an internal materialized view (IMV). 2. Query the IMV on node 1 to populate the cache on node 1. 3. Shutdown node 1 4. Query the IMV on node 2 Expectation: node 2 doesn't have a copy of the cache and populates from the sources Actual: node 2 returns a successful result with 0 rows. No warning or error is found in the logs. Note: this behavior happens when the shutting down in step 3 is done gracefully (and node 2 is notified node 1 is leaving the cluster) as well as when it's done with an kill -9 (simulating a failure)

      Using an internal materialized view in EDS 5.1 with CP2, a node which never had a copy of an IMV cache will return 0 rows when it should be querying the source in situations where another node in the cluster had cached the IMV but is no longer in the cluster

              rhn-engineering-shawkins Steven Hawkins
              rhn-support-dsteigner Deborah Steigner (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: