diff options
| author | dark-angel <70754989+inferno-umar@users.noreply.github.com> | 2024-02-07 14:27:16 +0530 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-02-07 08:57:16 +0000 |
| commit | 5c0fc9087211f01375f208d679a1e6de0685320c (patch) | |
| tree | e35f59688febc6b66e8bc0a5be2fbe0b4e61d59f /routers/web/repo/middlewares.go | |
| parent | 2bac85dc3339ecb1cb1418524b2a7966aed9963a (diff) | |
| download | gitea-5c0fc9087211f01375f208d679a1e6de0685320c.tar.gz gitea-5c0fc9087211f01375f208d679a1e6de0685320c.zip | |
fix: Elasticsearch: Request Entity Too Large #28117 (#29062)
Fix for gitea putting everything into one request without batching and
sending it to Elasticsearch for indexing as issued in #28117
This issue occured in large repositories while Gitea tries to
index the code using ElasticSearch.
I've applied necessary changes that takes batch length from below config
(app.ini)
```
[queue.code_indexer]
BATCH_LENGTH=<length_int>
```
and batches all requests to Elasticsearch in chunks as configured in the
above config
Diffstat (limited to 'routers/web/repo/middlewares.go')
0 files changed, 0 insertions, 0 deletions