alexiskhoury opened a new issue, #11733:
URL: https://github.com/apache/iotdb/issues/11733

   Hi,
   
   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


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to