Please take this survey to help us learn more about how you use third party tools. Your input is greatly appreciated!

Cannot recover yet, some non-current nodes have LGE behind

karthikkarthik
edited November 12 in General Discussion

Hi,
I'm seeing startup.log throwing the below error. Due to the urgency, the cluster was restored using LGE.
a) Under what scenario do we see the below message and what should be the ideal troubleshooting steps to perform?
b) Was restoring LGE the right thing to do or was there a better solution than this?


tail -f startup.log
_________________________________________________________________________________________________"stage" : "Plan Recovery",
"text" : "Cannot recover yet, some non-current nodes: node0002: LGE is behind: 214191296 instead of 214199608: ",
"timestamp" : "2020-11-09 05:03:58.447"
}
{ "node" : "node0002", "stage" : "Plan Recovery", "text" : "Cannot recover yet, some non-current nodes: node0002: LGE is behind: 214191296 instead of 214199608: ", "timestamp" : "2020-11-09 05:04:03.448" }


Best Answers

  • karthikkarthik
    Accepted Answer

    @Nimmi_gupta , Thanks. This helps.

Answers

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Emoji
Image
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file

Can't find what you're looking for? Search the Vertica Documentation, Knowledge Base, or Blog for more information.