Re: [gpdb-users] Performance issue with Greenplum 6.17.2 & Gpbackup 1.21.0
Shivram Mani
The main difference between gpbackup versions 1.20.0 and 1.21.0 was we gave end users the ability to control over all restore throughput by exposing addition configuration parameters:
restore_multipart_chunksize which defaults to 500MB and restore_max_concurrent_requests which defaults to 6. Please refer to https://gpdb.docs.pivotal.io/backup-restore/1-21/admin_guide/managing/backup-s3-plugin.html#topic_ur2_fsn_ndb__s3-plugin-config for more details.
Can you share your s3 plugin configuration and possibly your gpbackup log files as well for us to validate your configurations.
Thanks
Shivram
From:
Bill Bailey <bba...@xanadu.ie>
Date: Friday, August 20, 2021 at 1:25 AM
To: Greenplum Users <gpdb-...@greenplum.org>
Subject: [gpdb-users] Performance issue with Greenplum 6.17.2 & Gpbackup 1.21.0
Just testing the latest releases of Greenplum and gpbackup
I'm finding that I am completely unable to restore data from a backup on S3
The process works fine with Greenplum 6.14 and gpbackup 1.20.0
With these latest versions the streaming rate is 20x slower and the process hangs after 10 minutes
Anyone else seen any such issues ?
***** Email confidentiality notice *****
Xanadu Consultancy Limited is a limited company registered in Ireland with registered number 500416 and VAT registered number IE 9793319P. Our registered office is at Floor 2, River House, Blackpool Retail & Business Park, Cork, Ireland. We have a branch office
registered in England and Wales with company number FC030315, whose address is at International House, 24 Holborn Viaduct, London EC1A 2BN.
This message is intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to us, and immediately and permanently delete it. Do not use, copy or disclose the information contained
in this message or in any attachment. Xanadu Consultancy Limited cannot accept liability for any statements made which are clearly the sender’s own and not expressly made on behalf of Xanadu Consultancy Limited.
--
You received this message because you are subscribed to the Google Groups "Greenplum Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
gpdb-users+...@greenplum.org.
To view this discussion on the web visit
https://groups.google.com/a/greenplum.org/d/msgid/gpdb-users/8d984768-ac0d-4c84-b75e-a00578491361n%40greenplum.org.
Shivram Mani
Thanks for identifying the specific s3 plugin version. We did make some changes to how we use the underlying s3 api during downloads(restore) to ensure we don’t throttle the s3 bucket. It would
It would be helpful if you can give us a general sense of your workload for us to investigate this as well (# of segments, ~ Number of tables, average size of tables) along with the most recent logs under ~/gpAdminLogs/ specifically the log file with the prefix `gpbackup_s3_plugin_`
Thanks
Shivram
From:
Bill Bailey <bba...@xanadu.ie>
Date: Friday, August 20, 2021 at 3:25 PM
To: Shivram Mani <shiv...@vmware.com>
Subject: Re: [gpdb-users] Performance issue with Greenplum 6.17.2 & Gpbackup 1.21.0
I have tested with restore_max_concurrent_requests and backup_max_concurrent_requests both set to the default value of 6
I tried three settings of backup_multipart_chunksize and restore_multipart_chunksize - 10MB, 100MB and 500MB
I have narrowed down the cause of the performance issue:-
If use gpbackup 1.20 or gpbackup 1.21 with gpbackup_s3_plugin 1.6.0 then everything works fine
If I use either gpbackup 1.20 or gpbackup 1.21 with gpbackup_s3_plugin 1.7.0 then performance drops considerably
--
Bill Bailey
Xanadu Consultancy Limited
3rd Floor
River House
Blackpool Retail & Business Park
Blackpool
Cork
(E) bba...@xanadu.ie
(T) 086 892 5989
