Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BugFix] mkdir $STARROCKS_HOME/meta in bin/start_fe.sh #48940

Merged
merged 1 commit into from
Jul 29, 2024

Conversation

jiangyinzuo
Copy link
Contributor

@jiangyinzuo jiangyinzuo commented Jul 25, 2024

Why I'm doing:

When I run ./bin/start_fe.sh after running build.sh, it reports an error:

2024-07-25 16:57:39.027Z ERROR (main|1) [MetaHelper.checkMetaDir():166] meta dir /data/starrocks/output/fe/meta does not exist
2024-07-25 16:57:39.031Z ERROR (main|1) [StarRocksFE.start():185] StarRocksFE start failed
com.starrocks.common.InvalidMetaDirException: null
        at com.starrocks.leader.MetaHelper.checkMetaDir(MetaHelper.java:167) ~[starrocks-fe.jar:?]
        at com.starrocks.StarRocksFE.start(StarRocksFE.java:120) ~[starrocks-fe.jar:?]
        at com.starrocks.StarRocksFE.main(StarRocksFE.java:83) ~[starrocks-fe.jar:?]

This is because we have not created meta directory.

What I'm doing:

Add mkdir $STARROCKS_HOME/meta command in bin/start_fe.sh

What type of PR is this:

  • BugFix
  • Feature
  • Enhancement
  • Refactor
  • UT
  • Doc
  • Tool

Does this PR entail a change in behavior?

  • Yes, this PR will result in a change in behavior.
  • No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

  • Interface/UI changes: syntax, type conversion, expression evaluation, display information
  • Parameter changes: default values, similar parameters but with different default values
  • Policy changes: use new policy to replace old one, functionality automatically enabled
  • Feature removed
  • Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

  • I have added test cases for my bug fix or my new feature
  • This pr needs user documentation (for new or modified features or behaviors)
    • I have added documentation for my new feature or new function
  • This is a backport pr

Bugfix cherry-pick branch check:

  • I have checked the version labels which the pr will be auto-backported to the target branch
    • 3.3
    • 3.2
    • 3.1
    • 3.0
    • 2.5

@CLAassistant
Copy link

CLAassistant commented Jul 25, 2024

CLA assistant check
All committers have signed the CLA.

bin/start_fe.sh Outdated Show resolved Hide resolved
@jiangyinzuo jiangyinzuo force-pushed the patch-1 branch 2 times, most recently from e2a4a4e to 0a05aff Compare July 26, 2024 08:56
bin/start_fe.sh Outdated Show resolved Hide resolved
@jiangyinzuo jiangyinzuo force-pushed the patch-1 branch 2 times, most recently from 91d0a2d to 174bf2a Compare July 27, 2024 04:30
bin/common.sh Show resolved Hide resolved
bin/start_fe.sh Show resolved Hide resolved
bin/start_fe.sh Outdated Show resolved Hide resolved
@github-actions github-actions bot added the 3.3 label Jul 27, 2024
Copy link

[FE Incremental Coverage Report]

pass : 0 / 0 (0%)

Copy link

[BE Incremental Coverage Report]

pass : 0 / 0 (0%)

@kevincai kevincai requested review from wyb and trueeyu July 29, 2024 06:13
@github-actions github-actions bot added the 3.2 label Jul 29, 2024
@alvin-celerdata alvin-celerdata merged commit d55f33c into StarRocks:main Jul 29, 2024
62 of 63 checks passed
Copy link

@Mergifyio backport branch-3.3

Copy link

@Mergifyio backport branch-3.2

Copy link
Contributor

mergify bot commented Jul 29, 2024

backport branch-3.3

✅ Backports have been created

Copy link
Contributor

mergify bot commented Jul 29, 2024

backport branch-3.2

✅ Backports have been created

mergify bot pushed a commit that referenced this pull request Jul 29, 2024
## Why I'm doing:
When I run `./bin/start_fe.sh` after running `build.sh`, it reports an error:

```
2024-07-25 16:57:39.027Z ERROR (main|1) [MetaHelper.checkMetaDir():166] meta dir /data/starrocks/output/fe/meta does not exist
2024-07-25 16:57:39.031Z ERROR (main|1) [StarRocksFE.start():185] StarRocksFE start failed
com.starrocks.common.InvalidMetaDirException: null
        at com.starrocks.leader.MetaHelper.checkMetaDir(MetaHelper.java:167) ~[starrocks-fe.jar:?]
        at com.starrocks.StarRocksFE.start(StarRocksFE.java:120) ~[starrocks-fe.jar:?]
        at com.starrocks.StarRocksFE.main(StarRocksFE.java:83) ~[starrocks-fe.jar:?]
```

This is because we have not created `meta` directory.

## What I'm doing:

Add `mkdir $STARROCKS_HOME/meta` command in bin/start_fe.sh

Signed-off-by: Yinzuo Jiang <[email protected]>
(cherry picked from commit d55f33c)
mergify bot pushed a commit that referenced this pull request Jul 29, 2024
## Why I'm doing:
When I run `./bin/start_fe.sh` after running `build.sh`, it reports an error:

```
2024-07-25 16:57:39.027Z ERROR (main|1) [MetaHelper.checkMetaDir():166] meta dir /data/starrocks/output/fe/meta does not exist
2024-07-25 16:57:39.031Z ERROR (main|1) [StarRocksFE.start():185] StarRocksFE start failed
com.starrocks.common.InvalidMetaDirException: null
        at com.starrocks.leader.MetaHelper.checkMetaDir(MetaHelper.java:167) ~[starrocks-fe.jar:?]
        at com.starrocks.StarRocksFE.start(StarRocksFE.java:120) ~[starrocks-fe.jar:?]
        at com.starrocks.StarRocksFE.main(StarRocksFE.java:83) ~[starrocks-fe.jar:?]
```

This is because we have not created `meta` directory.

## What I'm doing:

Add `mkdir $STARROCKS_HOME/meta` command in bin/start_fe.sh

Signed-off-by: Yinzuo Jiang <[email protected]>
(cherry picked from commit d55f33c)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants