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

Nebula crash when configure firewall to accept raft election port #815

Closed
yixinglu opened this issue Aug 21, 2019 · 1 comment
Closed

Nebula crash when configure firewall to accept raft election port #815

yixinglu opened this issue Aug 21, 2019 · 1 comment

Comments

@yixinglu
Copy link
Contributor

Describe the bug(must be provided)

Nebula processes crash after accepting raft election port.

Your Environments(must be provided)

  • OS: CentOS
  • Compliler: Installed by RPM

How To Reproduce(must be provided)
Steps to reproduce the behavior:

  1. Make firewall block the raft election port(metad_port + 1).
  2. Configure metad multiple peers in nebula-metad.conf, set wal_ttl default value, start nebula processes.
  3. Then update firewall rule to accept the election port.
  4. Nebula processes crash

Expected behavior

Nebula metad work well.

Additional context

Clean the meta data and restart all nebula processes to fix it.

metad-crash

@dangleptr
Copy link
Contributor

dangleptr commented Aug 21, 2019

The reason is that WALs have been removed during this time. Leader has to send snapshot when catching up data, and the logic will be implemented in #795

liwenhui-soul pushed a commit to liwenhui-soul/nebula that referenced this issue May 10, 2022
* Add constraint which group should output to same variable. Clone
PlanNode will output to new variable.

* Check input relationship of plan from transform.

* Collect boundary from MatchResult directly.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants