bug: distributed lookup join may use inconsistent vnode mapping infos

[zwang28]

Describe the bug

In frontend, distributed lookup join reads vnode mapping of inner side table twice:

1. Get ExchangeInfo:

   risingwave/src/frontend/src/optimizer/property/distribution.rs

   Line 148 in 3091f16

   let vnode_mapping =

2. Get parallelism:

   risingwave/src/frontend/src/scheduler/plan_fragmenter.rs

   Line 945 in 3091f16

   let vnode_mapping = self

If the vnode mapping changes between these 2 steps (e.g. scaling), query result may be incorrect.

To Reproduce

No response

Expected behavior

No response

Additional context

No response

[github-actions]

This issue has been open for 60 days with no activity.

If you think it is still relevant today, and needs to be done in the near future, you can comment to update the status, or just manually remove the no-issue-activity label.

You can also confidently close this issue as not planned to keep our backlog clean.
Don't worry if you think the issue is still valuable to continue in the future.
It's searchable and can be reopened when it's time. 😄