Unsupported Screen Size: The viewport size is too small for the theme to render properly.

Forum Replies Created

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • in reply to: Very Heavy Disk Activity When Running Sqlyog #35654
    tom.bodley
    Member

    Thanks Peter, I was running 12.11 – upgrading to 12.18 has fixed it.

    in reply to: Rds Through Monyog #34203
    tom.bodley
    Member

    Thanks Peter, that sounds great. Could you keep me updated with any progress and/or changes to the expected timefreame.

    Thanks again,

    Tom

    in reply to: Rds Through Monyog #34200
    tom.bodley
    Member

    Hi Peter,

    Just wondering whether there has been any progress on this request?

    Let me know if you have any more questions.

    Thanks,

    Tom

    in reply to: Rds Through Monyog #34198
    tom.bodley
    Member

    Hi Peter,

    Execute privilege is enough to use mysql.rds_kill(PROCESS_ID), by default the RDS root user has global execute privileges so can call this command.

    The stored procedures baked-in to RDS by Amazon are as follows (SELECT `name` FROM mysql.proc WHERE `name` LIKE 'rds_%'):

    • rds_kill – Terminate user session
    • rds_kill_query – Terminate query
    • rds_collect_global_status_history – Takes a snapshot of global status on demand
    • rds_disable_gsh_collector – Disables global status snapshots
    • rds_disable_gsh_rotation – Disables global status table rotation (mysql.rds_global_status_history & mysql.rds_global_status_history_old)
    • rds_enable_gsh_collector – Enables snapshots of global status at intervals specified by rds_set_gsh_collector
    • rds_enable_gsh_rotation – Enabled global status table rotation (mysql.rds_global_status_history & mysql.rds_global_status_history_old) at intervals set by rds_set_gsh_rotation
    • rds_rotate_general_log – Copies mysql.general_log to mysql.general_log_backup and clears down mysql.general_log
    • rds_rotate_global_status_history – Copies mysql.rds_global_status_history to mysql.rds_global_status_history and clears down mysql.rds_global_status_history
    • rds_rotate_slow_log- Copies mysql.slow_log to mysql.slow_log_backup and clears down mysql.slow_log
    • rds_set_gsh_collector – Interval used by rds_enable_gsh_collector
    • rds_set_gsh_rotation – Interval used by rds_enable_gsh_rotation
    • rds_skip_repl_error – Skips a replication error

    'FLUSH STATUS' works in RDS, but will only clear down the local variables. 'FLUSH GLOBAL STATUS' doesn't appear to be a valid command (We're running 5.5.27, is it available in a newer release?).

    If you are using the RDS provided GSH table (mysql.rds_global_status_history) then 'FLUSH GLOBAL STATUS' can be imitated by executing 'CALL mysql.rds_rotate_global_status_history'

    Thanks,

    Tom

    in reply to: Rds Through Monyog #34196
    tom.bodley
    Member

    Hi Peter,

    Thanks for your replies.

    AWS is a collection of services Amazon have put together to create their cloud solution (e.g. RDS, Route53, S3, VPC). The fully-fledged virtualized OS you are referring to is EC2 not AWS.

    I understand we'll never have shell access to RDS, but the feature I was requesting doesn't require shell access, it requries a user with the correct privileges to call mysql.rds_kill(PROCESS_ID) or mysql.rds_kill_query(PROCESS_ID).

    Thanks,

    Tom

Viewing 5 posts - 1 through 5 (of 5 total)