> is there any lock for that part which will prevent it be involved any merge or mutation process , so part on new node will have safe data consistency with old one ?
There is no lock on the part level. You can stop all merges for the specific table using SYSTEM STOP MERGES query (don't forget to start them again after copy operation is done). But this approach won't work well if you ingest data into the table during copying, because you'll end up with TOO MANY PARTS.
You may also take a look at the clickhouse-copier.