[jira] [Created] (IOTDB-4715) Refactor the invoking of ConfigPhysicalPlanType.ordinal() to avoid the incompatibility when restarted.

2022-10-21 Thread Gaofei Cao (Jira)
Gaofei Cao created IOTDB-4715:
-

 Summary: Refactor the invoking of ConfigPhysicalPlanType.ordinal() 
to avoid the incompatibility when restarted.
 Key: IOTDB-4715
 URL: https://issues.apache.org/jira/browse/IOTDB-4715
 Project: Apache IoTDB
  Issue Type: Improvement
Reporter: Gaofei Cao
Assignee: Gaofei Cao






--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (IOTDB-4714) [sync] Rename TPipeInfo to TCreatePipeReq

2022-10-21 Thread yanze chen (Jira)
yanze chen created IOTDB-4714:
-

 Summary: [sync] Rename TPipeInfo to TCreatePipeReq
 Key: IOTDB-4714
 URL: https://issues.apache.org/jira/browse/IOTDB-4714
 Project: Apache IoTDB
  Issue Type: Improvement
Reporter: yanze chen
Assignee: yanze chen






--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (IOTDB-4713) Log TException in ConfigNodeClient

2022-10-21 Thread Yongzao Dan (Jira)
Yongzao Dan created IOTDB-4713:
--

 Summary: Log TException in ConfigNodeClient
 Key: IOTDB-4713
 URL: https://issues.apache.org/jira/browse/IOTDB-4713
 Project: Apache IoTDB
  Issue Type: Improvement
Reporter: Yongzao Dan
Assignee: Quan Siyi
 Fix For: 0.14.0
 Attachments: image-2022-10-21-16-50-52-031.png, 
image-2022-10-21-16-53-58-279.png, image-2022-10-21-16-57-19-896.png

The current retry logic in ConfigNodeClient is as following:

 

!image-2022-10-21-16-50-52-031.png!

 

As we can see, this block of code ignores the TException, which might be import 
sometimes. Take the register process as example: 

 

!image-2022-10-21-16-53-58-279.png!

 

The above screenshot doesn't contain anything valuable since the error log for 
expressing why fail to communicate with ConfigNode-leader is ignored. 
Therefore, we should add log that record the TException:

!image-2022-10-21-16-57-19-896.png!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (IOTDB-4712) Add size limit of trigger jar on ConfigNode

2022-10-21 Thread Jira
李伟豪 created IOTDB-4712:
--

 Summary: Add size limit of trigger jar on ConfigNode
 Key: IOTDB-4712
 URL: https://issues.apache.org/jira/browse/IOTDB-4712
 Project: Apache IoTDB
  Issue Type: Sub-task
Reporter: 李伟豪






--
This message was sent by Atlassian Jira
(v8.20.10#820010)