MySQL Forums
Forum List  »  NDB clusters

Re: Error with "Read Backup"
Posted by: Mikael Ronström
Date: August 31, 2017 04:59PM

Jeff Steele Wrote:
-------------------------------------------------------
> Thanks again for your assistance.

No problem, it's fun to be working with real issues every now and then.
I mostly work on new features,
so it is nice to see some real world issues from time to time.

Also interesting to see what kind of issues user hits.

>
> I set all tables to READ_BACKUP=0, but the
> resource usage didn't return to normal. I then
> restarted the cluster. While the first data node
> was restarting, the second one crashed. I then
> restarted both of them and the cluster seemed
> fine. Resource usage stayed high until I ran
> "analyze tables". Then resource usage dropped, but
> I don't know if it was because of the analyze
> command or just a coincidence. I then made a few
> tables READ_BACKUP=1. At the moment, ndbmtd is
> only using 17% of CPU. That is compared to 500%
> earlier.
>

Yep, pretty sure that READ_BACKUP should only
help.

Sounds interesting, if you have any data that you can share
about what happened it could be interesting. Use the bug report
in that case.

Obviously ANALYZE TABLE can help if something was wrong
with statistics on tables.

I'll see if I can find out if the index statistics is affected
by ALTER TABLE REORG.

> Since CPU usage is low now, I'll leave
> NoOfFragmentLogParts alone for now.

Sounds like a good plan, it is not really an issue to keep
this forever if it works fine.

Options: ReplyQuote


Subject
Views
Written By
Posted
1033
August 29, 2017 03:25PM
549
August 29, 2017 03:50PM
470
August 30, 2017 08:52AM
565
August 31, 2017 03:15AM
503
August 31, 2017 04:30AM
587
August 31, 2017 10:52AM
549
August 31, 2017 12:41PM
617
August 31, 2017 01:57PM
628
August 31, 2017 02:00PM
587
August 31, 2017 04:37PM
Re: Error with "Read Backup"
571
August 31, 2017 04:59PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.