[Bugs] [Bug 1218475] New: [FEAT] - Sharding xlator
bugzilla at redhat.com
bugzilla at redhat.com
Tue May 5 02:41:52 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1218475
Bug ID: 1218475
Summary: [FEAT] - Sharding xlator
Product: GlusterFS
Version: 3.7.0
Component: sharding
Keywords: Triaged
Assignee: kdhananj at redhat.com
Reporter: kdhananj at redhat.com
QA Contact: bugs at gluster.org
CC: bugs at gluster.org, gluster-bugs at redhat.com,
sasundar at redhat.com
Depends On: 1200082
Blocks: 1199352 (glusterfs-3.7.0)
+++ This bug was initially created as a clone of Bug #1200082 +++
Description of problem:
This is a bug that is to be associated with the ongoing efforts w.r.t sharding
translator.
https://gist.github.com/avati/af04f1030dcf52e16535#sharding-xlator-stripe-20
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--- Additional comment from Anand Avati on 2015-03-09 12:59:11 EDT ---
REVIEW: http://review.gluster.org/9841 (WIP: Sharding xlator) posted (#1) for
review on master by Krutika Dhananjay (kdhananj at redhat.com)
--- Additional comment from Anand Avati on 2015-03-16 11:24:51 EDT ---
REVIEW: http://review.gluster.org/9841 (WIP: Sharding xlator) posted (#2) for
review on master by Krutika Dhananjay (kdhananj at redhat.com)
--- Additional comment from Anand Avati on 2015-03-16 11:36:46 EDT ---
REVIEW: http://review.gluster.org/9841 (WIP: Sharding xlator) posted (#3) for
review on master by Krutika Dhananjay (kdhananj at redhat.com)
--- Additional comment from Anand Avati on 2015-03-19 05:35:42 EDT ---
REVIEW: http://review.gluster.org/9841 (WIP: Sharding xlator) posted (#4) for
review on master by Krutika Dhananjay (kdhananj at redhat.com)
--- Additional comment from Anand Avati on 2015-03-19 06:33:52 EDT ---
REVIEW: http://review.gluster.org/9841 (features/shard: Introducing sharding
translator) posted (#5) for review on master by Krutika Dhananjay
(kdhananj at redhat.com)
--- Additional comment from Anand Avati on 2015-03-19 07:43:26 EDT ---
REVIEW: http://review.gluster.org/9841 (features/shard: Introducing sharding
translator) posted (#6) for review on master by Pranith Kumar Karampuri
(pkarampu at redhat.com)
--- Additional comment from Anand Avati on 2015-03-19 13:59:35 EDT ---
COMMIT: http://review.gluster.org/9841 committed in master by Vijay Bellur
(vbellur at redhat.com)
------
commit 6f389fbb812b384bdd9bf4a20e86930505531996
Author: Krutika Dhananjay <kdhananj at redhat.com>
Date: Fri Nov 21 11:47:23 2014 +0530
features/shard: Introducing sharding translator
Based on the high-level design by Anand V. Avati which can be found @
https://gist.github.com/avati/af04f1030dcf52e16535#sharding-xlator-stripe-20
Still to-do:
* complete implementation of inode write fops - [f]truncate,
zerofill, fallocate, discard
* introduce transaction mechanism in inode write fops
* complete readv
* Handle open with O_TRUNC
* Handle unlinking of all shards during unlink/rename
* Compute total ia_size and ia_blocks in lookup, readdirp, etc
* wind fsync/flush on all shards
Note: Most of the items above are related. Once we come up
with a clean way to determine the last shard/shard count for
a file/file size and the mgmt of sparse regions of the file,
implementing them becomes trivial.
Change-Id: Id871379b53a4a916e4baa2e06f197dd8c0043b0f
BUG: 1200082
Signed-off-by: Krutika Dhananjay <kdhananj at redhat.com>
Reviewed-on: http://review.gluster.org/9841
Tested-by: Gluster Build System <jenkins at build.gluster.com>
Reviewed-by: Vijay Bellur <vbellur at redhat.com>
--- Additional comment from Anand Avati on 2015-05-04 22:34:51 EDT ---
REVIEW: http://review.gluster.org/10537 (doc: Feature doc for shard translator)
posted (#1) for review on master by Krutika Dhananjay (kdhananj at redhat.com)
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1199352
[Bug 1199352] GlusterFS 3.7.0 tracker
https://bugzilla.redhat.com/show_bug.cgi?id=1200082
[Bug 1200082] [FEAT] - Sharding xlator
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
More information about the Bugs
mailing list