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

Graphd crashed executing match query #5558

Closed
nebula-bots opened this issue May 22, 2023 · 0 comments · Fixed by #5557
Closed

Graphd crashed executing match query #5558

nebula-bots opened this issue May 22, 2023 · 0 comments · Fixed by #5557
Labels
affects/master PR/issue: this bug affects master version. auto-sync process/done Process of bug severity/blocker Severity of bug type/bug Type: something is unexpected

Comments

@nebula-bots
Copy link
Contributor

nebula-bots commented May 22, 2023

Your Environments (required)
nebula 3.5 d1e2118

How To Reproduce(required)
use nba, graph crashes when the following two statements are executed(sometimes it may be necessary to repeat these two statements to reproduce) :

match (v.player) return v
match (v:player) where v.player.name == "Tim Duncan" return v;

(root@nebula) [(none)]> use nba
Execution succeeded (time spent 782µs/14.696875ms)

Mon, 22 May 2023 10:01:58 CST

(root@nebula) [nba]> show tag indexes
+---------------------+----------+----------+
| Index Name          | By Tag   | Columns  |
+---------------------+----------+----------+
| "player_age_index"  | "player" | ["age"]  |
| "player_name_index" | "player" | ["name"] |
| "team_name_index"   | "team"   | ["name"] |
+---------------------+----------+----------+
Got 3 rows (time spent 597µs/15.761625ms)

Mon, 22 May 2023 10:02:03 CST

(root@nebula) [nba]> match (v.player) return v
[ERROR (-1004)]: SyntaxError: Invalid node pattern near `(v.player)'

Mon, 22 May 2023 10:02:06 CST

(root@nebula) [nba]> match (v:player) where v.player.name == "Tim Duncan" return v;
[ERROR (-1005)]: Error found in optimization stage: The output columns of the OptGroupNode is different from OptGroup when applying the rule: RemoveNoopProjectRule, (null) vs. __IndexScan_1

Mon, 22 May 2023 10:02:08 CST

(root@nebula) [nba]> match (v:player) where v.player.name == "Tim Duncan" return v;
2023/05/22 10:02:09 Loop error, failed to reconnect, failed to open transport, error: dial tcp 192.168.15.31:10050: connect: connection refused

Bye root!
Mon, 22 May 2023 10:02:09 CST

2023/05/22 10:02:09 [WARNING] Sign out failed, write tcp 10.8.0.26:60744->192.168.15.31:10050: write: broken pipe
panic: Loop error, failed to reconnect, failed to open transport, error: dial tcp 192.168.15.31:10050: connect: connection refused

goroutine 1 [running]:
log.Panicf(0x13815e8, 0xe, 0xc0000a9e38, 0x1, 0x1)
	/opt/hostedtoolcache/go/1.16.4/x64/src/log/log.go:361 +0xc5
main.main()
	/home/runner/work/nebula-console/nebula-console/main.go:569 +0x5c8

core dump

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
--Type <RET> for more, q to quit, c to continue without paging--
Core was generated by `bin/nebula-graphd -flagfile /data2/luban/knife/nebula-ent-3.5.0-rc/etc/graphd2/'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x0000000001259776 in std::_Function_handler<void (void*), nebula::ObjectPool::OwnershipHolder::OwnershipHolder<nebula::ConstantExpression>(nebula::ConstantExpression*)::{lambda(void*)#1}>::_M_invoke(std::_Any_data const&, void*&&) ()
[Current thread is 1 (Thread 0x7f58073ff700 (LWP 3354998))]
(gdb) bt
#0  0x0000000001259776 in std::_Function_handler<void (void*), nebula::ObjectPool::OwnershipHolder::OwnershipHolder<nebula::ConstantExpression>(nebula::ConstantExpression*)::{lambda(void*)#1}>::_M_invoke(std::_Any_data const&, void*&&) ()
#1  0x000000000126501d in std::__cxx11::_List_base<nebula::ObjectPool::OwnershipHolder, std::allocator<nebula::ObjectPool::OwnershipHolder> >::_M_clear() ()
#2  0x00000000015f0947 in nebula::graph::QueryContext::~QueryContext() ()
#3  0x00000000015f0b39 in nebula::graph::QueryContext::~QueryContext() ()
#4  0x00000000012b6424 in nebula::graph::QueryInstance::onError(nebula::Status) ()
#5  0x00000000012b8da4 in nebula::graph::QueryInstance::execute() ()
#6  0x00000000012b2f05 in nebula::graph::QueryEngine::execute(std::unique_ptr<nebula::graph::RequestContext<nebula::ExecutionResponse>, std::default_delete<nebula::graph::RequestContext<nebula::ExecutionResponse> > >) ()
#7  0x00000000012832b6 in ?? ()
#8  0x00000000012839dc in ?? ()
#9  0x000000000254586c in ?? ()
#10 0x00000000022d72a7 in virtual thunk to apache::thrift::concurrency::FunctionRunner::run() ()
#11 0x0000000002416678 in apache::thrift::concurrency::ThreadManager::Impl::Worker::run() ()
#12 0x000000000241877e in apache::thrift::concurrency::PthreadThread::threadMain(void*) ()
#13 0x00007f5841183609 in start_thread (arg=<optimized out>) at pthread_create.c:477
#14 0x00007f58410a8133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Expected behavior
graphd won't crash.

@nebula-bots nebula-bots added affects/master PR/issue: this bug affects master version. auto-sync severity/blocker Severity of bug type/bug Type: something is unexpected labels May 22, 2023
@github-actions github-actions bot added the process/fixed Process of bug label May 22, 2023
@nebula-bots nebula-bots added process/done Process of bug and removed process/fixed Process of bug labels Jun 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects/master PR/issue: this bug affects master version. auto-sync process/done Process of bug severity/blocker Severity of bug type/bug Type: something is unexpected
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant