[
https://issues.apache.org/jira/browse/GEODE-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928652#comment-15928652
]
ASF GitHub Bot commented on GEODE-2674:
---------------------------------------
Github user upthewaterspout commented on a diff in the pull request:
https://github.com/apache/geode/pull/427#discussion_r106504069
--- Diff:
geode-lucene/src/main/java/org/apache/geode/cache/lucene/internal/LuceneEventSubstitutionFilter.java
---
@@ -0,0 +1,37 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
contributor license
+ * agreements. See the NOTICE file distributed with this work for
additional information regarding
+ * copyright ownership. The ASF licenses this file to You under the Apache
License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance with the
License. You may obtain a
+ * copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
distributed under the License
+ * is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF
ANY KIND, either express
+ * or implied. See the License for the specific language governing
permissions and limitations under
+ * the License.
+ */
+
+package org.apache.geode.cache.lucene.internal;
+
+import org.apache.geode.cache.EntryEvent;
+import org.apache.geode.cache.wan.GatewayEventSubstitutionFilter;
+import org.apache.geode.internal.cache.Token;
+
+/**
+ * A substitution filter which throws away the value of the entry and
replaces it with an INVALID
--- End diff --
Hmm, I was thinking null would just mean remove the event or don't
substitute the value. But maybe the gateway actually handles that
appropriately. Let me test that.
> Lucene index is out of sync with data region due to retried event
> -----------------------------------------------------------------
>
> Key: GEODE-2674
> URL: https://issues.apache.org/jira/browse/GEODE-2674
> Project: Geode
> Issue Type: Bug
> Reporter: Dan Smith
> Assignee: Dan Smith
> Fix For: 1.2.0
>
>
> We're seeing issues where the data in the lucene index does not match the
> data in a region. Here's what I see happening
> # An accessor starts doing a put
> # The put goes to the current primary
> # Primary distributes the put to the secondary
> # Primary closes it's cache
> # New primary does a destroy on the same entry
> # The accessor retries the put because the old primary closed the cache
> # The retried put is added to the queue, after the destroy. But it is not
> added to the region, because the region detects that it is a retry.
> # The lucene index applies the put. Now there is an extra entry in the index
> that is not in the region.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
