Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-9304

Network Partition causes Dirty Read even with DENY_READ_WRITES

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Major Major
    • None
    • None
    • None
    • None
    • Hide

      steps to reproduce
      1. start three cache instances c1, c2, and c3 with DENY_READ_WRITES and REPL_SYNC configuration
      2. on c1 write key 1
      3. on c1 read all cache keys, this will return 1
      4. on c2 write key 2
      5. on c2 read all cache keys, this will return 1 and 2
      6. cut the network communications between c1 and (c2,c3). c1 will not be able to communicate with c2 or c3
      7. on c1 write key 11, this will return a time-out error
      8. on c2 write key 22, this will return a time-out error
      9. on c1 or c2 read all cache keys, this will return 1 and 2
      10. fix the network between c1 and (c2,c3)
      11. on c1 read all cache keys, this will return 1,2,11,22, with 11 and 22 been dirty reads

      Show
      steps to reproduce 1. start three cache instances c1, c2, and c3 with DENY_READ_WRITES and REPL_SYNC configuration 2. on c1 write key 1 3. on c1 read all cache keys, this will return 1 4. on c2 write key 2 5. on c2 read all cache keys, this will return 1 and 2 6. cut the network communications between c1 and (c2,c3). c1 will not be able to communicate with c2 or c3 7. on c1 write key 11, this will return a time-out error 8. on c2 write key 22, this will return a time-out error 9. on c1 or c2 read all cache keys, this will return 1 and 2 10. fix the network between c1 and (c2,c3) 11. on c1 read all cache keys, this will return 1,2,11,22, with 11 and 22 been dirty reads

      Infinispan cache can return a dirty read under a network partition scenario even with DENY_READ_WRITES split handling option is enabled.

            Unassigned Unassigned
            c0d34 c0d34 c0d34 (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: