You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So i have 2 main documents: A and B.
A has 200K records, while B has 17K. When I say python manage.py search_index --rebuild, A is being indexed without any problem, but B returns me: elastic_transport.ConnectionTimeout: Connection timed out.
I tried to do it one by one with this command: python manage.py search_index --rebuild --models app.B. The result is still the same. I also checked the ES logs: {"type": "server", "timestamp": "2024-04-24T00:08:26,315Z", "level": "INFO", "component": "o.e.c.r.a.AllocationService", "cluster.name": "es-docker-cluster", "node.name": "es01", "message": "Cluster health status changed from [YELLOW] to [GREEN] (reason: [shards started [[B][0]]]).", "cluster.uuid": "1WTn6GPTSWK0RdDUDditmw", "node.id": "i_ft-utwSIKBCplG7ZX2aw" } {"type": "server", "timestamp": "2024-04-24T00:09:12,400Z", "level": "INFO", "component": "o.e.c.m.MetadataDeleteIndexService", "cluster.name": "es-docker-cluster", "node.name": "es01", "message": "[B/zeHlCSrpSjuYLwpxH0ySdA] deleting index", "cluster.uuid": "1WTn6GPTSWK0RdDUDditmw", "node.id": "i_ft-utwSIKBCplG7ZX2aw" } {"type": "server", "timestamp": "2024-04-24T00:09:12,624Z", "level": "INFO", "component": "o.e.c.m.MetadataCreateIndexService", "cluster.name": "es-docker-cluster", "node.name": "es01", "message": "[B] creating index, cause [api], templates [], shards [1]/[0]", "cluster.uuid": "1WTn6GPTSWK0RdDUDditmw", "node.id": "i_ft-utwSIKBCplG7ZX2aw" } {"type": "server", "timestamp": "2024-04-24T00:09:12,776Z", "level": "INFO", "component": "o.e.c.r.a.AllocationService", "cluster.name": "es-docker-cluster", "node.name": "es01", "message": "Cluster health status changed from [YELLOW] to [GREEN] (reason: [shards started [[B][0]]]).", "cluster.uuid": "1WTn6GPTSWK0RdDUDditmw", "node.id": "i_ft-utwSIKBCplG7ZX2aw" }
It seems like, the problem is not related to ES, but something between Django and ES.
The text was updated successfully, but these errors were encountered:
So i have 2 main documents: A and B.
A has 200K records, while B has 17K. When I say
python manage.py search_index --rebuild
, A is being indexed without any problem, but B returns me:elastic_transport.ConnectionTimeout: Connection timed out.
I tried to do it one by one with this command:
python manage.py search_index --rebuild --models app.B
. The result is still the same. I also checked the ES logs:{"type": "server", "timestamp": "2024-04-24T00:08:26,315Z", "level": "INFO", "component": "o.e.c.r.a.AllocationService", "cluster.name": "es-docker-cluster", "node.name": "es01", "message": "Cluster health status changed from [YELLOW] to [GREEN] (reason: [shards started [[B][0]]]).", "cluster.uuid": "1WTn6GPTSWK0RdDUDditmw", "node.id": "i_ft-utwSIKBCplG7ZX2aw" } {"type": "server", "timestamp": "2024-04-24T00:09:12,400Z", "level": "INFO", "component": "o.e.c.m.MetadataDeleteIndexService", "cluster.name": "es-docker-cluster", "node.name": "es01", "message": "[B/zeHlCSrpSjuYLwpxH0ySdA] deleting index", "cluster.uuid": "1WTn6GPTSWK0RdDUDditmw", "node.id": "i_ft-utwSIKBCplG7ZX2aw" } {"type": "server", "timestamp": "2024-04-24T00:09:12,624Z", "level": "INFO", "component": "o.e.c.m.MetadataCreateIndexService", "cluster.name": "es-docker-cluster", "node.name": "es01", "message": "[B] creating index, cause [api], templates [], shards [1]/[0]", "cluster.uuid": "1WTn6GPTSWK0RdDUDditmw", "node.id": "i_ft-utwSIKBCplG7ZX2aw" } {"type": "server", "timestamp": "2024-04-24T00:09:12,776Z", "level": "INFO", "component": "o.e.c.r.a.AllocationService", "cluster.name": "es-docker-cluster", "node.name": "es01", "message": "Cluster health status changed from [YELLOW] to [GREEN] (reason: [shards started [[B][0]]]).", "cluster.uuid": "1WTn6GPTSWK0RdDUDditmw", "node.id": "i_ft-utwSIKBCplG7ZX2aw" }
It seems like, the problem is not related to ES, but something between Django and ES.
The text was updated successfully, but these errors were encountered: