geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (GEODE-2674) Lucene index is out of sync with data region due to retried event
Date Thu, 16 Mar 2017 17:43:41 GMT


ASF GitHub Bot commented on GEODE-2674:

Github user upthewaterspout commented on a diff in the pull request:
    --- Diff: geode-lucene/src/main/java/org/apache/geode/cache/lucene/internal/
    @@ -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
    + * 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
    + *
    + *
    + *
    + * Unless required by applicable law or agreed to in writing, software distributed under
the License
either express
    + * or implied. See the License for the specific language governing permissions and limitations
    + * 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
    --- End diff --
    You are right. I tried Token.NOT_AVAILABLE and then Token.INVALID, but that made the queue
unhappy. I'll change the comment. I thought I was using a static string? Is there something
that would be better to use here?

> Lucene index is out of sync with data region due to retried event
> -----------------------------------------------------------------
>                 Key: GEODE-2674
>                 URL:
>             Project: Geode
>          Issue Type: Bug
>            Reporter: Dan Smith
>            Assignee: Dan Smith
> 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

View raw message