We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
None
Yes
I0815 16:52:16.666848 12547 /Users/sanyue/code/qihoo/pikiwidb2/src/praft/praft.cc:741] Node start following { leader_id=127.0.0.1:7231:0:0, term=2, status=Follower/Learner receives message from new leader with the same term.} W0815 16:52:16.667021 13571 /Users/sanyue/code/qihoo/pikiwidb2/build-debug/Source/extern_brpc/src/brpc/policy/baidu_rpc_protocol.cpp:278] Fail to write into Socket{id=93 fd=209 addr=127.0.0.1:51211:8231} (0x1401a8000): Got EOF I0815 16:52:16.667133 12035 /Users/sanyue/code/qihoo/pikiwidb2/build-debug/Source/extern_braft/src/braft/node.cpp:2321] node pikiwidb:127.0.0.1:8231:0 received PreVote from 127.0.0.1:7231:0:0 in term 3 current_term 2 granted 0 rejected_by_lease 1 W0815 16:52:16.667153 12035 /Users/sanyue/code/qihoo/pikiwidb2/build-debug/Source/extern_brpc/src/brpc/policy/baidu_rpc_protocol.cpp:278] Fail to write into Socket{id=186 fd=219 addr=127.0.0.1:51237:8231} (0x150028000): Got EOF I0815 16:52:16.667120 12547 /Users/sanyue/code/qihoo/pikiwidb2/build-debug/Source/extern_braft/src/braft/node.cpp:2321] node pikiwidb:127.0.0.1:8231:0 received PreVote from 127.0.0.1:7231:0:0 in term I0815 16:52:16.667207 12803 /Users/sanyue/code/qihoo/pikiwidb2/build-debug/Source/extern_braft/src/braft/node.cpp:2321] node pikiwidb:127.0.0.1:8231:0:0 received PreVote from 127.0.0.1:7231:0:0 in term 3 current_term 2 granted 0 rejected_by_lease 1 I0815 16:52:16.667176 12035 /Users/sanyue/code/qihoo/pikiwidb2/build-debug/Source/extern_braft/src/braft/node.cpp:2321] node pikiwidb: Exception: EXC_BAD_ACCESS (code=1, address=0x11) Exception: EXC_BAD_ACCESS (code=1, address=0xeae0c0474800)
No response
The text was updated successfully, but these errors were encountered:
OpenAtomFoundation/pikiwidb#420
Sorry, something went wrong.
No branches or pull requests
Is this a regression?
None
Description
Is this a regression?
Yes
Description
I0815 16:52:16.666848 12547 /Users/sanyue/code/qihoo/pikiwidb2/src/praft/praft.cc:741] Node start following { leader_id=127.0.0.1:7231:0:0, term=2, status=Follower/Learner receives message from new leader with the same term.}
W0815 16:52:16.667021 13571 /Users/sanyue/code/qihoo/pikiwidb2/build-debug/Source/extern_brpc/src/brpc/policy/baidu_rpc_protocol.cpp:278] Fail to write into Socket{id=93 fd=209 addr=127.0.0.1:51211:8231} (0x1401a8000): Got EOF
I0815 16:52:16.667133 12035 /Users/sanyue/code/qihoo/pikiwidb2/build-debug/Source/extern_braft/src/braft/node.cpp:2321] node pikiwidb:127.0.0.1:8231:0 received PreVote from 127.0.0.1:7231:0:0 in term 3 current_term 2 granted 0 rejected_by_lease 1
W0815 16:52:16.667153 12035 /Users/sanyue/code/qihoo/pikiwidb2/build-debug/Source/extern_brpc/src/brpc/policy/baidu_rpc_protocol.cpp:278] Fail to write into Socket{id=186 fd=219 addr=127.0.0.1:51237:8231} (0x150028000): Got EOF
I0815 16:52:16.667120 12547 /Users/sanyue/code/qihoo/pikiwidb2/build-debug/Source/extern_braft/src/braft/node.cpp:2321] node pikiwidb:127.0.0.1:8231:0 received PreVote from 127.0.0.1:7231:0:0 in term
I0815 16:52:16.667207 12803 /Users/sanyue/code/qihoo/pikiwidb2/build-debug/Source/extern_braft/src/braft/node.cpp:2321] node pikiwidb:127.0.0.1:8231:0:0 received PreVote from 127.0.0.1:7231:0:0 in term 3 current_term 2 granted 0 rejected_by_lease 1
I0815 16:52:16.667176 12035 /Users/sanyue/code/qihoo/pikiwidb2/build-debug/Source/extern_braft/src/braft/node.cpp:2321] node pikiwidb:
Exception: EXC_BAD_ACCESS (code=1, address=0x11)
Exception: EXC_BAD_ACCESS (code=1, address=0xeae0c0474800)
Please provide a link to a minimal reproduction of the bug
No response
Screenshots or videos
Please provide the version you discovered this bug in (check about page for version information)
No response
Anything else?
No response
Please provide a link to a minimal reproduction of the bug
No response
Screenshots or videos
Please provide the version you discovered this bug in (check about page for version information)
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: