At the beginning of the issue, you should consider using curl to post to the address in the log that cannot be accessed. Figure out why this PD API address cannot be accessed.
The most likely reason is that your Lightning version is inconsistent with your TiDB version. Therefore, the address that Lightning needs to access does not exist on your PD.
A less likely reason is that your PD has undergone TLS security hardening, causing the PD’s HTTP address to become HTTPS, so it cannot be accessed.
In short, the root cause is the issue with accessing this URL.
The subsequent error occurs because your last Lightning import encountered an error and exited abnormally, but the checkpoint was not cleared. When you try to import again, it finds that the previous checkpoint exists, so it does not continue the import and exits directly.
You can follow the prompts in the log to clear the checkpoint data and then continue. You may need to install tidb-lightning-ctl separately.
My version was installed through the official website’s tiup component, and the versions are basically the same. I think the issue might have been caused by the incomplete data from the interrupted transmission not being cleared. Now that it has been cleared, I re-imported using the tidb mode, and so far there are no issues.