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
show Journal Size in In-Place Migration steps #18492
Conversation
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.
Looks good, I added some suggestion that we should take care of.
fetchJournalDowntimeSize, | ||
{ | ||
onError: (errorThrown) => { | ||
UserNotification.error(`Loading Data Node failed with status: ${errorThrown}`, |
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.
UserNotification.error(`Loading Data Node failed with status: ${errorThrown}`, | |
UserNotification.error(`Loading Data Node migration journal estimate failed with status: ${errorThrown}`, |
{ | ||
onError: (errorThrown) => { | ||
UserNotification.error(`Loading Data Node failed with status: ${errorThrown}`, | ||
'Could not load Data Node'); |
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.
'Could not load Data Node'); | |
'Could not load Data Node journal size estimate.'); |
<h3>Journal downtime size warning</h3> | ||
<p>Please note that during migration data processing will stop on your Graylog node, this will result in the journal growing in size.</p> | ||
<p>Therefore increase your journal volume size.</p> | ||
<p>Size: <b>{data} KB/min</b></p> |
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.
<p>Size: <b>{data} KB/min</b></p> | |
<p>Your current journal throughput is: <b>{data} KB/min</b></p> |
</> | ||
); | ||
const JournalDowntimeWarning = ({ currentStep, onTriggerStep }: MigrationStepComponentProps) => { | ||
const { data } = useJournalDowntimeSize(); |
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.
We should also handle displaying a message when there is an error when getting the throughput estimation.
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.
LGTM!
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.
lgtm
if we get feedback from testers about how long they took on average for the restart, we could add a estimate for the journal size that multiplies this values by the needed number of minutes (plus buffer)
* show JournalDowntimeSize * changelog file * fix review comments
Types of changes
Checklist: