apache / apache/incubator-pegasus

Pegasus crashed when I use the incorrect cluster

Open
#413 1 comment 0 reactions 0 assignees View on GitHub
type/bug
Dominant language
C++
Stars
2.1k
Forks
328
PR merge metrics
No merged PRs in 30d

Description

## Bug Report

Please answer these questions before submitting your issue. Thanks!

1. What did you do?
If possible, provide a recipe for reproducing the error.
```
./run.sh shell
>>> cc 23232323
```
2. What did you expect to see?
some Error messages,like 'Cluster dosen't exist'
3. What did you see instead?
Pegasus crashed
```
>>> cc 23232323
F2019-11-01 15:36:15.609 (1572593775609414389 4057) mimic.io-thrd.16471: replication_common.cpp:573:load_meta_servers(): assertion expression: servers.size() > 0
F2019-11-01 15:36:15.609 (1572593775609467709 4057) mimic.io-thrd.16471: replication_common.cpp:573:load_meta_servers(): no meta server specified in config [pegasus.clusters].23232323
./run.sh: 行 1621: 16471 已放弃 (核心已转储) ./pegasus_shell ${CONFIG} $CLUSTER_NAME
```

4. What version of Pegasus are you using?
Pegasus Shell 1.12.SNAPSHOT (404079781f91cd869949eb00c525155b330c9d7a) Release

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the invalid-cluster command with ./run.sh shell and cluster name 23232323, then inspect replication_common.cpp:573 and the Pegasus shell path shown in the report. Trace how a missing cluster configuration is handled. Done means the command reports that the cluster does not exist instead of crashing.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
cli, databases, distributed-systems
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.