Uploaded image for project: 'Percona Server for MySQL'
  1. Percona Server for MySQL
  2. PS-7057

PS 5.7 to 8.0 upgrade failed with crash when innodb_track_changed_pages =1


    • Bug
    • Status: On Hold
    • Medium
    • Resolution: Unresolved
    • 8.0.19-10
    • None
    • None


      Issue: With innodb_track_changed_pages =1  setting  Percona server inplace upgrade from 5.7 to 8.0 failing.


      Test case:

      1. Start Percona server 5.7.29 with    innodb_track_changed_pages =1 , load some data 
      2. Do a clean mysql shutdown for  5.7 
      3. Upgrade binary/package to 8.0.19 and start PS 8.0 with the existing 5.7 data-dir and innodb_track_changed_pages =1  setting 
      4. and PS 8.0.19 crash as follows at the time of startup.


      2020-05-14T07:59:03.074459Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
      2020-05-14T07:59:03.074474Z 0 [Note] Shutting down plugin 'MEMORY'
      2020-05-14T07:59:03.074480Z 0 [Note] Shutting down plugin 'CSV'
      2020-05-14T07:59:03.074484Z 0 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
      2020-05-14T07:59:03.074508Z 0 [Note] Shutting down plugin 'sha256_password'
      2020-05-14T07:59:03.074511Z 0 [Note] Shutting down plugin 'mysql_native_password'
      2020-05-14T07:59:03.074669Z 0 [Note] Shutting down plugin 'binlog'
      2020-05-14T07:59:03.076195Z 0 [Note] /home/lalit/mysql_tar/percona/5.7.29/bin/mysqld: Shutdown complete
      2020-05-14T07:59:03.137997Z mysqld_safe mysqld from pid file /home/lalit/sandboxes/msb_5_7_29/data/mysql_sandbox5729.pid ended
      2020-05-14T08:11:41.489675Z mysqld_safe Logging to '/home/lalit/sandboxes/msb_8_0_19/data/msandbox.err'.
      2020-05-14T08:11:41.525271Z mysqld_safe Starting mysqld daemon with databases from /home/lalit/sandboxes/msb_8_0_19/data
      2020-05-14T08:11:41.810897Z 0 [System] [MY-010116] [Server] /home/lalit/mysql_tar/percona/8.0.19/bin/mysqld (mysqld 8.0.19-10) starting as process 21761
      2020-05-14T08:11:41.842775Z 1 [System] [MY-011012] [Server] Starting upgrade of data directory.
      08:11:41 UTC - mysqld got signal 11 ;
      Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
      Thread pointer: 0x7f2a247fc000
      Attempting backtrace. You can use the following information to find out
      where mysqld died. If you see no messages after this, something went
      terribly wrong...
      stack_bottom = 7f2a1b3feca0 thread_stack 0x46000
      /home/lalit/mysql_tar/percona/8.0.19/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x2e) [0x5616a592a46e]
      /home/lalit/mysql_tar/percona/8.0.19/bin/mysqld(handle_fatal_signal+0x351) [0x5616a4bebd91]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x12890) [0x7f2a334e3890]
      /home/lalit/mysql_tar/percona/8.0.19/bin/mysqld(log_online_follow_redo_log_one_pass()+0xfa) [0x5616a5aaa20a]
      /home/lalit/mysql_tar/percona/8.0.19/bin/mysqld(srv_start(bool)+0x2a91) [0x5616a5bb9291]
      /home/lalit/mysql_tar/percona/8.0.19/bin/mysqld(+0x1feeb17) [0x5616a59fbb17]
      /home/lalit/mysql_tar/percona/8.0.19/bin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0x97) [0x5616a56c7d87]
      /home/lalit/mysql_tar/percona/8.0.19/bin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x654) [0x5616a58f5714]
      /home/lalit/mysql_tar/percona/8.0.19/bin/mysqld(+0x129ee06) [0x5616a4cabe06]
      /home/lalit/mysql_tar/percona/8.0.19/bin/mysqld(+0x2430fb5) [0x5616a5e3dfb5]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x76db) [0x7f2a334d86db]
      /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7f2a3127f88f]
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0): Connection ID (thread ID): 1
      Status: NOT_KILLED
      Please help us make Percona Server better by reporting any
      bugs at https://bugs.percona.com/
      You may download the Percona Server operations manual by visiting
      http://www.percona.com/software/percona-server/. You may find information
      in the manual which will help you identify the cause of the crash.
      2020-05-14T08:11:42.084300Z mysqld_safe mysqld from pid file /home/lalit/sandboxes/msb_8_0_19/data/mysql_sandbox8019.pid ended with return value of 2



      We found this issue while checking https://jira.percona.com/browse/PXC-3248  which affected due to this.


        Issue Links



              Unassigned Unassigned
              lalit.choudhary Lalit Choudhary
              0 Vote for this issue
              2 Start watching this issue



                Smart Checklist