-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
HBASE-25980 Master table.jsp pointed at meta throws 500 when no all r… #3374
Conversation
…eplicas are online
🎊 +1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
try { | ||
metaLocation = MetaTableLocator.waitMetaRegionLocation(master.getZooKeeper(), j, 1); | ||
} catch (NotAllMetaRegionsOnlineException e) { | ||
//Should ignore this Exception for we don't need to display rit meta region info in UI |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should ignore this Exception for we don't need to display rit meta region info in UI
=>
Should ignore this Exception as we don't need to display rit meta region info in UI
Use 'as' instead of 'for'.
And mind explaining a bit more on why we do not need to dispay rit meta region info? And what is going on if metaLocation is null?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok! Thansk for your comments
try { | ||
metaLocation = MetaTableLocator.waitMetaRegionLocation(master.getZooKeeper(), j, 1); | ||
} catch (NotAllMetaRegionsOnlineException e) { | ||
//Since a region in transition state throw a NotAllMetaRegionsOnlineException then |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Apache9 What about this explanation here? By the way, I added a 'continue' here to skip to display rit region. IMHO, we do not need to show region info here since the home page of master status UI has show which region is in transition and why
🎊 +1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
//could cause the whole UI crash, and the operator could have learned that this | ||
//region is in transition state from the master status UI. We should ignore to display | ||
//this region info. | ||
continue; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In this case, the user is looking at the meta table specifically. Maybe the below if (metaLocation != null) {... needs an else block that prints a message stating that some region location(s) could not be identified?
@ndimiduk Since the user may learn the meta region is in transition state from the transition list in Master status UI, Should we still show any details here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After I check the current implementation it shows that If a region of user-level table is in transition, it does not be displayed in its table details page. So I think the meta region should be the same.
🎊 +1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
…eplicas are online