No your await
has no impact on other processes.
But you seem to have a misconception: Not only does await
not block the other process you got using cluster.fork
, but it doesn't either halt your current process.
The code after your await
won't be executed until the passed promise is resolved but other promises might be resolved before this one, or other events may be produced by the underlying IO system, even in the same process.
Remember: node was able to handle concurrent requests even before the node cluster system.
Related: Why node.js is fast when it's single threaded?