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

crash on master and 3.2.0+ #4807

Closed
wey-gu opened this issue Oct 28, 2022 · 1 comment
Closed

crash on master and 3.2.0+ #4807

wey-gu opened this issue Oct 28, 2022 · 1 comment
Labels
invalid Solution: this issue is invalid and will be closed type/bug Type: something is unexpected
Milestone

Comments

@wey-gu
Copy link
Contributor

wey-gu commented Oct 28, 2022

Describe the bug (required)

This query works fin in 3.1.0, but crashes master

Your Environments (required)

  • OS: uname -a
  • Compiler: g++ --version or clang++ --version
  • CPU: lscpu
  • Commit id (e.g. a3ffc7d8)

How To Reproduce(required)

Steps to reproduce the behavior:

  1. Step 1
match (m:`player`) where id(m) in ["player100", "player101", "player102"]
WITH collect(distinct m)[0..10] as col_appl_1st_v4,m UNWIND col_appl_1st_v4 as x
OPTIONAL MATCH (x)-[r1:follow]-(n:`player`)
RETURN n

Storaged crashed

F20221028 09:02:48.411567   158 Value.cpp:599] Check failed: type_ == Type::STRING (__EMPTY__ vs. STRING)
*** Check failure stack trace: ***
*** Aborted at 1666947768 (Unix time, try 'date -d @1666947768') ***
*** Signal 11 (SIGSEGV) (0x0) received by PID 1 (pthread TID 0x7feda27fd700) (linux TID 158) (code: 128), stack trace: ***
/usr/local/nebula/bin/nebula-storaged(_ZN5folly10symbolizer17getStackTraceSafeEPmm+0x31)[0x263a011]
/usr/local/nebula/bin/nebula-storaged(_ZN5folly10symbolizer21SafeStackTracePrinter15printStackTraceEb+0x26)[0x2631516]
/usr/local/nebula/bin/nebula-storaged[0x262f4a7]
/lib64/libpthread.so.0(+0xf62f)[0x7fede344262f]
/lib64/libc.so.6(abort+0x297)[0x7fede309cbc7]
/usr/local/nebula/bin/nebula-storaged[0x2662d19]
/usr/local/nebula/bin/nebula-storaged[0x2665e13]
/usr/local/nebula/bin/nebula-storaged[0x26627e8]
/usr/local/nebula/bin/nebula-storaged[0x26664c8]
/usr/local/nebula/bin/nebula-storaged(_ZNK6nebula5Value6getStrB5cxx11Ev+0x6f)[0x1b94fcf]
/usr/local/nebula/bin/nebula-storaged(_ZN6nebula7storage21GetNeighborsProcessor17runInSingleThreadERKNS0_4cpp219GetNeighborsRequestElb+0x526)[0x1226ce6]
/usr/local/nebula/bin/nebula-storaged(_ZN6nebula7storage21GetNeighborsProcessor9doProcessERKNS0_4cpp219GetNeighborsRequestE+0x568)[0x1228c18]
/usr/local/nebula/bin/nebula-storaged(_ZTv0_n32_N6apache6thrift11concurrency14FunctionRunner3runEv+0x96)[0x21b4556]
/usr/local/nebula/bin/nebula-storaged(_ZN6apache6thrift11concurrency13ThreadManager4Impl6Worker3runEv+0x1c7)[0x23104c7]
/usr/local/nebula/bin/nebula-storaged(_ZN6apache6thrift11concurrency13PthreadThread10threadMainEPv+0xcd)[0x23125cd]
/lib64/libpthread.so.0(+0x7ea4)[0x7fede343aea4]
/lib64/libc.so.6(clone+0x6c)[0x7fede316396c]
(safe mode, symbolizer not available)

Expected behavior

Additional context

@wey-gu wey-gu added the type/bug Type: something is unexpected label Oct 28, 2022
@Sophie-Xie Sophie-Xie added this to the v3.3.0 milestone Oct 31, 2022
@wey-gu
Copy link
Contributor Author

wey-gu commented Oct 31, 2022

I cannot reproduce this after the cleanup of the cluster(all disk files purged and re-deployed), should be related to previous data corruption.

Closing it.

@wey-gu wey-gu closed this as completed Oct 31, 2022
@jinyingsunny jinyingsunny added the invalid Solution: this issue is invalid and will be closed label Nov 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid Solution: this issue is invalid and will be closed type/bug Type: something is unexpected
Projects
None yet
Development

No branches or pull requests

3 participants