arextest / arextest/arex-agent-java
[Bug] ES查询失败问题
- Dominant language
- Java
- Stars
- 564
- Forks
- 140
- Avg merge
- 36m
- Merged PRs (30d)
- 2
Description
### Search before asking
- [X] I have searched the existing [issues](https://github.com/arextest/arex-agent-java/issues) before asking.
### AREX Test Service
AREX Java Agent (arextest/arex-agent-java)
### Current Behavior
本问题是这样的:服务中有一接口,里面调用了es,然后接入arex之后出现现象:调用es时,数据量越大,接口失败的次数越高,数据量小的时候,10次有一次有问题;将arex录制关闭,接口正常。
集成es的方式为:
@Autowired
ElasticsearchRestTemplate elasticsearchRestTemplate;
Maven坐标为:
org.springframework.boot
spring-boot-starter-data-elasticsearch
2.5.1
### Expected Behavior
本问题是这样的:服务中有一接口,里面调用了es,然后接入arex之后出现现象:调用es时,数据量越大,接口失败的次数越高,数据量小的时候,10次有一次有问题;将arex录制关闭,接口正常。
集成es的方式为:
@Autowired
ElasticsearchRestTemplate elasticsearchRestTemplate;
Maven坐标为:
org.springframework.boot
spring-boot-starter-data-elasticsearch
2.5.1
### Steps To Reproduce
本问题是这样的:服务中有一接口,里面调用了es,然后接入arex之后出现现象:调用es时,数据量越大,接口失败的次数越高,数据量小的时候,10次有一次有问题;将arex录制关闭,接口正常。
集成es的方式为:
@Autowired
ElasticsearchRestTemplate elasticsearchRestTemplate;
Maven坐标为:
org.springframework.boot
spring-boot-starter-data-elasticsearch
2.5.1
### Anything else
本问题是这样的:服务中有一接口,里面调用了es,然后接入arex之后出现现象:调用es时,数据量越大,接口失败的次数越高,数据量小的时候,10次有一次有问题;将arex录制关闭,接口正常。
集成es的方式为:
@Autowired
ElasticsearchRestTemplate elasticsearchRestTemplate;
Maven坐标为:
org.springframework.boot
spring-boot-starter-data-elasticsearch
2.5.1
### Are you willing to submit a pull request to fix on your own?
- [X] Yes I am willing to submit a pull request on my own!
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the failure through the mentioned ElasticsearchRestTemplate integration with AREX recording enabled, comparing small and large result sets against recording-disabled runs. Inspect the Java agent’s Elasticsearch handling and capture the relevant failure details. Done means the interface remains reliable for large Elasticsearch responses, with regression coverage for the observed behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch, java
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100