@Override
          public void run() {
            Region myRegion = getCache().getRegion(regionName);
            EntryEventImpl event = ((LocalRegion) myRegion).generateEvictDestroyEvent(key10);
            event.setOperation(Operation.LOCAL_DESTROY);
            if (usePR) {
              BucketRegion bucket = ((PartitionedRegion) myRegion).getBucketRegion(key10);
              if (bucket != null) {
                event.setRegion(bucket);
                org.apache.geode.test.dunit.LogWriterUtils.getLogWriter()
                    .info("performing local destroy in " + bucket + " ccEnabled="
                        + bucket.getConcurrencyChecksEnabled() + " rvv="
                        + bucket.getVersionVector());
                bucket.setConcurrencyChecksEnabled(false); // turn off cc so entry is removed
                bucket.mapDestroy(event, false, false, null);
                bucket.setConcurrencyChecksEnabled(true);
              }
            } else {
              ((LocalRegion) myRegion).setConcurrencyChecksEnabled(false); // turn off cc so entry
                                                                           // is
              // removed
              ((LocalRegion) myRegion).mapDestroy(event, false, false, null);
              ((LocalRegion) myRegion).setConcurrencyChecksEnabled(true);
            }
          }
Similar to bug #43407 but not reported in a ticket, we want a client that does a get() on a
destroyed entry to end up with a tombstone for that entry. This was already the case but there
were no unit tests covering this for different server configurations and with/without
transactions.
geode-core/src/distributedTest/java/org/apache/geode/internal/cache/ClientServerInvalidAndDestroyedEntryDUnitTest.java