Connection refused to client
- Lenguaje dominante
- Java
- Estrellas
- 6.4k
- Forks
- 1.2k
- Merge medio
- 1 d 23 h
- PR fusionados (30 d)
- 115
Descripción
I am testing IotDB in standalone mode. The server works flawlessly whenever launched, but after a while client connections are refused either locally or remotely. I have the following errors logs:
Confignode logs:
`
2023-12-17 00:02:16,149 [AsyncDataNodeInternalServiceClientPool-selector-63] ERROR o.a.i.c.c.a.AsyncDataNodeInternalServiceClient:126 - Unexpected exception occurs in AsyncDataNodeInternalServiceClient{TEndPoint(ip:127.0.0.1, port:10730)} : Client has an error! 2023-12-17 00:02:16,149 [AsyncDataNodeInternalServiceClientPool-selector-63] ERROR o.a.i.c.c.a.h.r.PipePushMetaRPCHandler:78 - Failed to PIPE_PUSH_ALL_META on DataNode: {id=1, internalEndPoint=TEndPoint(ip:127.0.0.1, port:10730)}, exception: Connection refused
`
Datanode Logs:
`
2023-12-16 00:20:27,850 [pool-30-IoTDB-ClientRPC-Processor-14] ERROR o.a.t.s.TThreadPoolServer$WorkerProcess:258 - Thrift Error occurred during processing of message. org.apache.thrift.transport.TTransportException: Frame size (1129270862) larger than protect max size (536870912)! 2023-12-16 11:59:28,470 [pool-30-IoTDB-ClientRPC-Processor-15] ERROR o.a.i.c.c.t.WrappedThreadPoolExecutor:111 - Exception in thread pool org.apache.iotdb.threadpool:type=ClientRPC-Processor 2023-12-16 11:59:28,471 [pool-30-IoTDB-ClientRPC-Processor-15] ERROR o.a.i.c.c.IoTDBDefaultThreadExceptionHandler:31 - Exception in thread pool-30-IoTDB-ClientRPC-Processor-15-97
`
I am hosting IoTDB on a VPS server with limited ressources (1GB ram). Although, when I run the start-stanadlone script the only ports that is open is port 6667, all other ports are closed. Any hints?
Thanks for your help.
Alexis
Guía de contribución
Línea de trabajo
Comienza con el script start-standalone y compara los logs de ConfigNode y DataNode alrededor de la primera conexión rechazada. Comprueba si los recursos limitados del VPS de 1 GB, los errores del procesador RPC del cliente o los puertos de servicio cerrados explican el fallo; se considera terminado cuando se haya identificado la causa y documentado una corrección o cambio de configuración reproducible.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- java
- Área
- databases
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 25/100