SourceForge has been redesigned. Learn more.
Close

#2620 Put slashlets back on reader DB, note MyISAM

Other
closed-fixed
MySQL (78)
8
2003-09-09
2003-08-12
No

The slashlet sites were pointed at their writer DB back
when replication was busted; now only one of them
points at the reader though it has been working fine.

<jamie> I think what I need to do is check the table
type on the reader for all the tables that need to be
MyISAM, on all the DBs
<jamie> and if the table type is InnoDB, make it MyISAM
<jamie> then make sure the FULLTEXT indexes are in
place, and if not, create them
<jamie> then make sure replication still works
<jamie> then go back to the writer and point all the
"dbs" tables to the reader/search where appropriate

Discussion

  • Jamie McCarthy

    Jamie McCarthy - 2003-08-30

    Logged In: YES
    user_id=3889

    OK, all done. Pudge, I'm bouncing this to you because I
    don't know why useperl2.dbs type='reader' was set to
    isalive='no' when the useperl_backup DB is clearly alive
    (and being used for other purposes on useperl). If that was
    just an oversight and nothing to worry about, reassign this
    to Rob, mark it Fixed and let's be done with it. Otherwise,
    take a look at useperl2.dbs, fix it if necessary, and get
    hold of me in IRC to explain what's up.

    Anyway, all the FULLTEXT indexes are in place -- nothing
    needed changing except for some reason users_count was Inno
    on most of the slashlets (strange). Replication is still
    working and everything is fine AFAIK.

     
  • Jamie McCarthy

    Jamie McCarthy - 2003-08-30
    • assigned_to: jamiemccarthy --> pudge
     
  • Chris Nandor

    Chris Nandor - 2003-09-02
    • assigned_to: pudge --> cmdrtaco
    • status: open --> open-fixed
     
  • Rob Malda

    Rob Malda - 2003-09-09
    • status: open-fixed --> closed-fixed
     

Log in to post a comment.