Issues
- Error when using Smart memory.PXB-3430Aaditya Dubey
- Error when using Smart memory.PXB-3429Resolved issue: PXB-3429
- Parallelize incremental delta apply in incremental backup preparePXB-3427Satya Bodapati
- When running XtraBackup on unsupported MySQL 9 version, it shows a message to use 9.1 version that doesn't existsPXB-3423
- PXB 84 Creating Backup on replica failsPXB-3399Resolved issue: PXB-3399Satya Bodapati
- Slave (replica) backup fails (8.4)PXB-3377Resolved issue: PXB-3377
- Documentation bug for xtrabackup 8.4.0PXB-3363Resolved issue: PXB-3363patrick.birch
- percona-release setup pxb84-lts fails due to directory namingPXB-3361Resolved issue: PXB-3361Vadim Yalovets
- Allow for snapshots/incremental backups for myrocks enginePXB-3358Resolved issue: PXB-3358
- Document that xtrabackup --decompress requires the zstd to be installedPXB-3357Resolved issue: PXB-3357alina.derkach
- Marking master and slave terminology as deprecatedPXB-3347Resolved issue: PXB-3347
Error when using Smart memory.
Description
Environment
duplicates
Details
Details
Assignee
Reporter
Needs QA
Affects versions
Priority
Smart Checklist
Smart Checklist
Activity
Aaditya Dubey January 3, 2025 at 5:26 AMEdited
Hi @Charles Rodrigues
We have removed your password from the comment and made it private so that it can’t be seen by anyone outside Percona. Please ensure that you remove all sensitive information before adding it to the public report. Just removing the sensitive information from the comment or any other field makes things visible in the history, so we need to make your comment private for safety and security.
Thank you for providing more information; we will try adding data and see if this can be repeated.
Charles Rodrigues January 2, 2025 at 7:08 PM
@Aaditya Dubey Is it possible to remove the password from my last comment, I can't edit it
Aaditya Dubey January 1, 2025 at 12:01 PM
Hi @Charles Rodrigues
Thank you for the report.
Unfortunately, I'm unable to repeat the issue. Please find my steps below:
mysql [localhost:8400] {msandbox} (test) > select @@version;
+-----------+
| @@version |
+-----------+
| 8.4.0-1 |
+-----------+
1 row in set (0.00 sec)
./xtrabackup version 8.4.0-1 based on MySQL server 8.4.0 Linux (x86_64) (revision id: da6e1abd)
#Backup command:
./xtrabackup --defaults-file=/home/xxxx/sandboxes/msb_ps8_4_0/my.sandbox.cnf --backup --datadir=/home/xxxx/sandboxes/msb_ps8_4_0/data --target-dir=/home/xxxx/backup --databases=test --user=msandbox --password=msandbox --socket=/tmp/mysql_sandbox8400.sock
...
2025-01-01T11:55:54.084436-00:00 0 [Note] [MY-011825] [Xtrabackup] Transaction log of lsn (98011814) to (98011879) was copied.
2025-01-01T11:55:54.295938-00:00 0 [Note] [MY-011825] [Xtrabackup] completed OK!
# Prepare Backup:
./xtrabackup --parallel=8 --use-free-memory-pct=50 --prepare --apply-log-only --target-dir=/home/xxxx/backup
2025-01-01T11:56:06.922489-00:00 0 [Note] [MY-011825] [Xtrabackup] recognized server arguments: --innodb_checksum_algorithm=crc32 --innodb_log_checksums=1 --innodb_data_file_path=ibdata1:12M:autoextend --innodb_log_file_size=50331648 --innodb_page_size=16384 --innodb_undo_directory=./ --innodb_undo_tablespaces=2 --server-id=0 --innodb_log_checksums=ON --innodb_redo_log_encrypt=0 --innodb_undo_log_encrypt=0
2025-01-01T11:56:06.922636-00:00 0 [Note] [MY-011825] [Xtrabackup] recognized client arguments: --parallel=8 --use-free-memory-pct=50 --prepare=1 --apply-log-only=1 --target-dir=/home/xxxx/backup
./xtrabackup version 8.4.0-1 based on MySQL server 8.4.0 Linux (x86_64) (revision id: da6e1abd)
...
2025-01-01T11:56:08.257162-00:00 0 [Note] [MY-015020] [Server] MySQL Server: Plugins Shutdown - end.
2025-01-01T11:56:08.257951-00:00 0 [Note] [MY-011825] [Xtrabackup] completed OK!
Please share the exact reproducible steps to debug the issue further.
Charles Rodrigues December 26, 2024 at 11:31 AM
xtrabackup version 8.4.0-1 based on MySQL server 8.4.0 Linux (x86_64) (revision id: da6e1abd)
xtrabackup --parallel=8 --use-free-memory-pct=50 --prepare --apply-log-only --target-dir=/backup-mysql/
Error when using Smart memory.2024-12-20T17:31:58.145973-03:00 0 [Note] [MY-012955] [InnoDB] Initializing buffer pool, total size = 17179869183.875000G, instances = 1, chunk size =128.000000M 2024-12-20T20:31:58Z UTC - mysqld got signal 11 ; Signal SIGSEGV (unknown siginfo_t::si_code) at address 0x0 Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware. BuildID[sha1]= Thread pointer: 0x0 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 = 0 thread_stack 0x100000 #0 0x5e1d81363370 <unknown> #1 0x79a20e84531f <unknown> at sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0 #2 0x5e1d814b9fa5 <unknown> #3 0x5e1d814bfc76 <unknown> #4 0x5e1d814dca3d <unknown> #5 0x79a20ececdb3 <unknown> #6 0x79a20e89ca93 start_thread at ./nptl/pthread_create.c:447 #7 0x79a20e929c3b clone3 at sysdeps/unix/sysv/linux/x86_64/clone3.S:78 #8 0xffffffffffffffff <unknown>