Spring Data操作Elasticsearch出现脏读，删除后测试仍查询到数据

测试用例中删除Car数据后，查询结果仍显示该Car存在，测试失败。但调试时测试能成功，怀疑是Elasticsearch容器脏读问题。尝试在删除与查询间加Thread.sleep(3000)，测试依旧失败。其他查询相关测试均正常。

测试类代码 #

@ContextConfiguration(classes = {
        ElasticsearchTestSliceConfiguration.class,
        CarElasticsearchRepository.class,
        CarElasticsearchRepository.CarElasticsearchSpringRepository.class})
@DataElasticsearchTest
class CarElasticsearchRepositoryIT extends ElasticsearchContainerTest {
  
  ...

  @Test
  void shouldRemoveCarById() {
    repository.remove(carId_001);
    final Optional<Car> car = repository.findBy(carId_001);

    assertThat(car).isEmpty();
  }

}

仓库实现代码 #

@Component
class CarElasticsearchRepository {

  private final CarElasticsearchSpringRepository springRepository;
 
  CarElasticsearchRepository (CarElasticsearchSpringRepository springRepository) {
    this.springRepository = springRepository;
  }

  public Optional<Car> findBy(CarId carId) {
    return springRepository.findCarDocumentByCarId(carId.getValue())
           .map(carDocument -> carDocument.toCar())
  }

  public void remove(CarId carId) {
    springRepository.findCarDocumentByCarId(carId.getValue())
                    .ifPresent(carDocument -> springRepository.deleteCarDocumentByCarId(carId.getValue()))
  }

  interface CarElasticsearchSpringRepository extends ElasticsearchRepository<CarDocument, String> {
    Optional<Car> findCarDocumentByCarId(String carId);
    void deleteCarDocumentByCarId(String carId);
  }

}

依赖版本 #

• Java 17
• spring-data-elasticsearch 5.1.5
• org.testcontainers 1.18.3

1. 先修正Repository方法的类型错误 #

你定义的findCarDocumentByCarId方法返回Optional<Car>，但方法名明确是查询CarDocument，这是明显的类型不匹配。这种错误会导致映射异常，实际删除逻辑可能根本没执行到位。修正后：

interface CarElasticsearchSpringRepository extends ElasticsearchRepository<CarDocument, String> {
    // 把返回类型改成Optional<CarDocument>
    Optional<CarDocument> findCarDocumentByCarId(String carId);
    void deleteCarDocumentByCarId(String carId);
}

2. 解决Elasticsearch异步刷新问题 #

Elasticsearch的删除操作默认是异步写入，不会立即同步到搜索索引。调试时手动暂停给了ES足够刷新时间，但自动化测试里没有等待，导致查询到旧数据。加Thread.sleep没用，是因为无法保证ES在这段时间内完成刷新，正确的做法是强制刷新索引：

方式一：给删除方法加@Refresh注解

让Spring Data Elasticsearch在删除后立即刷新索引：

interface CarElasticsearchSpringRepository extends ElasticsearchRepository<CarDocument, String> {
    Optional<CarDocument> findCarDocumentByCarId(String carId);
    // 添加@Refresh注解
    @Refresh
    void deleteCarDocumentByCarId(String carId);
}

方式二：手动调用索引刷新

注入ElasticsearchOperations，在删除后主动刷新对应索引：

import org.springframework.data.elasticsearch.core.ElasticsearchOperations;

@Component
class CarElasticsearchRepository {

  private final CarElasticsearchSpringRepository springRepository;
  private final ElasticsearchOperations elasticsearchOperations;
 
  CarElasticsearchRepository (CarElasticsearchSpringRepository springRepository, ElasticsearchOperations elasticsearchOperations) {
    this.springRepository = springRepository;
    this.elasticsearchOperations = elasticsearchOperations;
  }

  // ...其他方法

  public void remove(CarId carId) {
    springRepository.deleteCarDocumentByCarId(carId.getValue());
    // 刷新CarDocument对应的索引
    elasticsearchOperations.indexOps(CarDocument.class).refresh();
  }

}

3. 简化删除逻辑 #

不需要先查询再删除，直接调用删除方法即可，避免冗余操作和潜在的竞态问题：

public void remove(CarId carId) {
  springRepository.deleteCarDocumentByCarId(carId.getValue());
}

内容的提问来源于stack exchange，提问作者user2054927