Open foreverneverer opened 4 years ago
What did you expect to see? The node server can be restarted and no any error.
What did you see instead? the perfcounter report the shared log too large 25853163(MB) > 50000 the log show error as soon as when the node server restart:
So what's the next result of a too-large-shared-log? Did it make the cluster unable to serve anymore? Or was the replica-server unable to restart?
I think we can consider mocking such case in replica's UT, by intentionally append some mutations only to the plog, without appending to the slog. Let the server restart then, and see what happens.
Bug Report
Please answer these questions before submitting your issue. Thanks!
Run the following commands to add the node:
remote-command -t meta-server meta.lb.only_move_primary true
set_meta_level lively
What did you expect to see? The node server can be restarted and no any error
What did you see instead?
shared log too large 25853163(MB) > 50000
What version of Pegasus are you using? pegasus-server-1.12.3-a948e89-glibc2.12-release.tar.gz
Suggestion
dessart
instead ofderror
if the shared log is damaged when restart the node server