[BUG] Running grape_engine after installing analytical engine results in an abortion

[TaoLbr1993]

Describe the bug
grape_engine got abortion.

To Reproduce

1. Install analytical engine (make analytical and got success info)
2. enter grape_engine dir (cd analytical_engine/build)
3. run ./grape_engine -p port 12306

Expected behavior
An abortion happens.

A process has executed an operation involving a call
to the fork() system call to create a child process.

As a result, the libfabric EFA provider is operating in
a condition that could result in memory corruption or
other system errors.

For the libfabric EFA provider to work safely when fork()
is called, you will need to set the following environment
variable:
          RDMAV_FORK_SAFE

However, setting this environment variable can result in
signficant performance impact to your application due to
increased cost of memory registration.

You may want to check with your application vendor to see
if an application-level alternative (of not using fork)
exists.

Your job will now abort.
*** Aborted at 1685965599 (unix time) try "date -d @1685965599" if you are using GNU date ***
PC: @                0x0 (unknown)
*** SIGABRT (@0x5aca1) received by PID 371873 (TID 0x7f1127062e40) from PID 371873; stack trace: ***
    @     0x7f112b04c046 (unknown)
    @     0x7f112abfe520 (unknown)
    @     0x7f112ac52a7c pthread_kill
    @     0x7f112abfe476 raise
    @     0x7f112abe47f3 abort
    @     0x7f111de91b4e (unknown)
    @     0x7f112aca6fb8 (unknown)
    @     0x7f112aca6781 __libc_fork
    @     0x7f112effee60 boost::process::detail::basic_execute_impl<>()
    @     0x7f112efe33af gs::VineyardServer::Start()
    @     0x55b0c572fdb6 gs::GrapeEngine::Start()
    @     0x55b0c572850a main
    @     0x7f112abe5d90 (unknown)
    @     0x7f112abe5e40 __libc_start_main
    @     0x55b0c5728d15 _start
Aborted

Environment (please complete the following information):

• GraphScope version: v0.21.0
• OS: Ubuntu 18.04

[welcome]

Thanks for opening your first issue here! Be sure to follow the issue template! And a maintainer will get back to you shortly!
Please feel free to contact us on DingTalk, WeChat account(graphscope) or Slack. We are happy to answer your questions responsively.