Connection refused to client
- Langage dominant
- Java
- Étoiles
- 6.4k
- Forks
- 1.2k
- Merge moyen
- 1 j 23 h
- PR mergées (30 j)
- 115
Description
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
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Commencez par le script start-standalone et comparez les logs de ConfigNode et DataNode autour de la première connexion refusée. Vérifiez si les ressources limitées du VPS de 1 Go, les erreurs du processeur RPC du client ou les ports de service fermés expliquent l’échec ; le travail est terminé lorsque la cause est identifiée et qu’une correction ou modification de configuration reproductible est documentée.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- java
- Domaine
- databases
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- À clarifier
- Accessibilité débutants
- 25/100