Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 17 submissions in the queue.
posted by NCommander on Saturday August 08 2015, @12:06AM   Printer-friendly
from the 503s-suck dept.

For a good portion of today, SoylentNews was generating 503 errors if you either logged in or tried to post a comment. While not 100% consistent, the underlying problem is that the design of MySQL cluster requires us to manually allocate space for indexes and data storage. Today, the index storage maxed out, and MySQL refused to insert new rows stating "Table 'name' is full".

We've doubled the size of the IndexMemory which should solve this issue in the short term. Longer term, we need to migrate some data to reside permanently on HDD storage. If anyone has experience with MySQL Cluster and can offer suggestions, we're all ears.

Here's our current memory usage on the cluster for those who are interested:

ndb_mgm> all report memoryusage
Node 2: Data usage is 81%(53650 32K pages of total 65536)
Node 2: Index usage is 46%(15407 8K pages of total 32800)
Node 3: Data usage is 81%(53648 32K pages of total 65536)
Node 3: Index usage is 46%(15407 8K pages of total 32800)

Sorry for any inconvenience

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 0) by Anonymous Coward on Saturday August 08 2015, @03:39AM

    by Anonymous Coward on Saturday August 08 2015, @03:39AM (#219781)

    Might I suggest Bobby Tables [xkcd.com], a renound SQL table expert.