Back to bug 1300679

Who When What Removed Added
Nagaprasad Sathyanarayana 2016-01-21 12:48:43 UTC CC nsathyan
Version unspecified 3.1
Manoj Pillai 2016-01-21 19:17:57 UTC CC dlambrig, rcyriac, vagarwal
Red Hat Bugzilla Rules Engine 2016-01-21 23:04:51 UTC Keywords ZStream
Nithya Balachandran 2016-01-22 10:44:03 UTC Status NEW ASSIGNED
CC nbalacha
Assignee rhs-bugs josferna
Nithya Balachandran 2016-01-22 10:49:26 UTC CC nchilaka
Nithya Balachandran 2016-01-22 10:49:46 UTC CC annair
Dan Lambright 2016-01-23 20:22:33 UTC CC dlambrig
Dan Lambright 2016-01-23 20:27:07 UTC CC dlambrig
Manoj Pillai 2016-01-24 07:27:58 UTC Summary promotions happening only to one sub-volume on hot tier promotions not balanced across hot tier sub-volumes
Mohammed Rafi KC 2016-01-25 11:44:14 UTC CC rkavunga
Red Hat Bugzilla Rules Engine 2016-01-25 12:01:42 UTC Target Release --- RHGS 3.1.2
Vivek Agarwal 2016-01-27 08:59:30 UTC Status ASSIGNED POST
Joseph Elwin Fernandes 2016-01-28 15:20:13 UTC Blocks 1302772
Red Hat Bugzilla Rules Engine 2016-02-01 12:01:40 UTC Target Release RHGS 3.1.2 ---
Vivek Agarwal 2016-02-03 12:17:58 UTC Blocks 1268895
Laura Bailey 2016-02-04 10:27:42 UTC Doc Text When the files that are candidates for migration exceed the number defined by tier-max-files or the size defined by tier-max-mb, files stop being migrated to the hot tier after one of these limits is reached. In some circumstances this results in files being unevenly distributed across the sub-volumes that make up the hot tier. For example, if tier-max-mb is set to 10GB, migration will stop after 10GB of files have been migrated. If the hot tier has two sub-volumes, it is highly likely that one sub-volume will receive all or the bulk of the migrated files.
Doc Type Bug Fix Known Issue
Flags needinfo?(nbalacha)
Nithya Balachandran 2016-02-05 08:37:23 UTC Flags needinfo?(nbalacha)
Laura Bailey 2016-02-08 00:02:54 UTC Doc Text When the files that are candidates for migration exceed the number defined by tier-max-files or the size defined by tier-max-mb, files stop being migrated to the hot tier after one of these limits is reached. In some circumstances this results in files being unevenly distributed across the sub-volumes that make up the hot tier. For example, if tier-max-mb is set to 10GB, migration will stop after 10GB of files have been migrated. If the hot tier has two sub-volumes, it is highly likely that one sub-volume will receive all or the bulk of the migrated files. If the hot and cold tiers in a tiered volume have the same number of sub-volumes, the first group of files migrated in a single cycle is likely to be migrated to the same sub-volume on the hot tier rather than being distributed across multiple sub-volumes. This is particularly noticeable when the files that are candidates for migration exceed the number defined by tier-max-files or the size defined by tier-max-mb. Files are migrated to other sub-volumes as the migration cycle continues.
Laura Bailey 2016-02-08 06:04:35 UTC CC mpillai
Flags needinfo?(mpillai)
Manoj Pillai 2016-02-08 06:28:21 UTC Flags needinfo?(mpillai)
Laura Bailey 2016-02-09 00:16:10 UTC Flags needinfo?(mpillai)
Laura Bailey 2016-02-09 00:17:04 UTC Doc Text If the hot and cold tiers in a tiered volume have the same number of sub-volumes, the first group of files migrated in a single cycle is likely to be migrated to the same sub-volume on the hot tier rather than being distributed across multiple sub-volumes. This is particularly noticeable when the files that are candidates for migration exceed the number defined by tier-max-files or the size defined by tier-max-mb. Files are migrated to other sub-volumes as the migration cycle continues. If the hot and cold tiers in a tiered volume have the same number of sub-volumes, the first group of files migrated in a single cycle is likely to be migrated to the same sub-volume on the hot tier rather than being distributed across multiple sub-volumes. This is particularly noticeable when the files that are candidates for migration exceed the number defined by tier-max-files or the size defined by tier-max-mb.
Manoj Pillai 2016-02-09 03:18:50 UTC Flags needinfo?(mpillai)
Joseph Elwin Fernandes 2016-02-11 06:13:52 UTC Blocks 1306514
Bhaskarakiran 2016-02-11 08:59:08 UTC CC byarlaga
Blocks 1299184
John Skeoch 2016-02-18 00:08:54 UTC CC vagarwal sankarshan
John Skeoch 2016-02-18 00:23:12 UTC CC nsathyan smohan
Joseph Elwin Fernandes 2016-02-18 08:57:35 UTC Whiteboard tier-migration
Joseph Elwin Fernandes 2016-03-01 02:40:51 UTC Blocks 1299184
Joseph Elwin Fernandes 2016-03-07 14:52:09 UTC Blocks 1299184
Rahul Hinduja 2016-03-07 14:53:22 UTC CC rhinduja
Alok 2016-03-08 07:22:16 UTC CC asrivast
Red Hat Bugzilla Rules Engine 2016-03-08 08:16:31 UTC Target Release --- RHGS 3.1.3
Joseph Elwin Fernandes 2016-03-23 07:41:12 UTC Status POST MODIFIED
errata-xmlrpc 2016-03-24 13:16:07 UTC Status MODIFIED ON_QA
Satish Mohan 2016-03-24 15:59:25 UTC Fixed In Version glusterfs-3.7.9-1
Rahul Hinduja 2016-03-27 15:17:15 UTC QA Contact nchilaka kramdoss
krishnaram Karthick 2016-04-11 08:54:35 UTC CC josferna
Flags needinfo?(josferna)
Joseph Elwin Fernandes 2016-04-16 06:36:04 UTC Flags needinfo?(josferna)
krishnaram Karthick 2016-04-21 06:04:58 UTC Status ON_QA VERIFIED
Rejy M Cyriac 2016-05-30 20:27:47 UTC Doc Text If the hot and cold tiers in a tiered volume have the same number of sub-volumes, the first group of files migrated in a single cycle is likely to be migrated to the same sub-volume on the hot tier rather than being distributed across multiple sub-volumes. This is particularly noticeable when the files that are candidates for migration exceed the number defined by tier-max-files or the size defined by tier-max-mb.
Doc Type Known Issue Bug Fix
John Skeoch 2016-06-20 00:02:25 UTC CC josferna
John Skeoch 2016-06-20 00:03:19 UTC Assignee josferna sankarshan
errata-xmlrpc 2016-06-23 00:47:17 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2016-06-23 05:03:16 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2016-06-23 01:03:16 UTC
Rejy M Cyriac 2016-09-17 15:34:40 UTC Sub Component tiering
CC rhs-bugs, storage-qa-internal
Component glusterfs tier

Back to bug 1300679