glusterfs.git/xlators/features, branch v3.7.5

features/shard: Use the xattr rsp dict to pick shard xattrs in xattrop cbk

2015-10-06T11:48:26+00:00

        Backport of: http://review.gluster.org/#/c/12300/

The change http://review.gluster.org/#/c/11938/ makes a fix in posix translator
which would cause sharding to fail fops post xattrop without this patch.

Change-Id: Id86b332a14b190694f5098e94bceb86e5b73e127
BUG: 1268804
Signed-off-by: Krutika Dhananjay 
Reviewed-on: http://review.gluster.org/12301
Reviewed-by: Vijay Bellur 
Tested-by: Vijay Bellur

fd: Do fd_bind on successful open

2015-10-06T06:11:02+00:00

- fd_unref should decrement fd->inode->fd_count only if it is present in the
inode's fd list.
- successful open/opendir should perform fd_bind.

 >Change-Id: I81dd04f330e2fee86369a6dc7147af44f3d49169
 >BUG: 1207735
 >Signed-off-by: Pranith Kumar K 
 >Reviewed-on: http://review.gluster.org/11044
 >Reviewed-by: Anoop C S 
 >Tested-by: NetBSD Build System 
 >Tested-by: Gluster Build System 
 >Reviewed-by: Raghavendra G 

BUG: 1259697
Change-Id: I73b79dd3519aa085fb84dde74b321511cbccce1a
Signed-off-by: Pranith Kumar K 
Reviewed-on: http://review.gluster.org/12100
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System 
Reviewed-by: Raghavendra G

features/shard: Port log messages to new framework

2015-09-30T06:04:36+00:00

        Backport of: http://review.gluster.org/12217

Change-Id: I129ff0d6d1cab15078fa474132c290950f5e1137
BUG: 1266822
Signed-off-by: Krutika Dhananjay 
Reviewed-on: http://review.gluster.org/12236
Reviewed-by: Pranith Kumar Karampuri 
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System

features/shard: Performance improvements in IO path - Part 2

2015-09-28T06:07:15+00:00

        Backport of: http://review.gluster.org/#/c/12138/

This is change 2/2 of the performance improvements for sharding.

The changes are with respect to maintaining up-to-date values of
file attributes in [f]stat, [f]setattr, link, and [f]truncate
codepaths.

Change-Id: I67de99e969b54d65f30fdcd63bc83d247afa84de
BUG: 1261716
Signed-off-by: Krutika Dhananjay 
Reviewed-on: http://review.gluster.org/12214
Tested-by: NetBSD Build System 
Reviewed-by: Pranith Kumar Karampuri 
Tested-by: Gluster Build System

features/shard: Performance improvements in IO path

2015-09-28T06:06:57+00:00

         Backport of: http://review.gluster.org/#/c/12126/

This is patch 1/2 of the performance improvement work
for sharding in the IO path.
What this patch does:
Since the primary use-case where sharding is targeted -
VM store - is a single-writer workload, instead of
performing lookup on the base file everytime to gather the
size and block count from the backend in reads, writes and
truncate, now the size and block count is also cached and
kept up-to-date after every inode write in the inode ctx.

TO-DO:
Make changes in rename, link, unlink, [f]setattr and [f]stat
to keep the relevant iatt members up-to-date in the inode ctx.

Change-Id: Id4f5c33044411b87b55968083a70a0a11a335ab2
BUG: 1261716
Signed-off-by: Krutika Dhananjay 
Reviewed-on: http://review.gluster.org/12213
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System 
Reviewed-by: Pranith Kumar Karampuri

marker: don't account destination linkto-file during internal migration

2015-09-22T11:59:53+00:00

This is a backport of http://review.gluster.org/#/c/12113/

During a DHT re-balance operation, quota accounts for the destination.
Problem of accounting this destination file are:
1) Migration is an internal operation, 'quota list' shows more usage on the CLI
   and this will come to the normal numbers once the migration is complete
2) If the usage is close to the limit set, then we can get 'Disk Quota
   Exceeded' errors in the I/O path during file migration

Solution is we should not account of the usage on the destination file
during migration, at the end of the migration. We need to reduce size of
the source directory and accounting for the migrated dest file

We assume that there are sufficent disk space in the back-end. DHT
migrator should make sure that there are sufficient disk space before it
starts the migration process.

> Change-Id: Ie3cfe3e4ab5241c2a127ba0edc599a053d30c3a0
> BUG: 1260545
> Signed-off-by: vmallika 

Change-Id: I2254392ada61a40ce259003c6b5787ecf6dc6376
BUG: 1260919
Signed-off-by: vmallika 
Reviewed-on: http://review.gluster.org/12204
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System 
Reviewed-by: Dan Lambright 
Tested-by: Dan Lambright

features/shard: Filter internal shard xattrs in {get,remove,set}xattr

2015-09-14T05:02:43+00:00

        Backport of: http://review.gluster.org/#/c/12121/ and
                     http://review.gluster.org/#/c/12136/

Change-Id: Ifadebe1cda80fa4a525605e10513e6e64ee72709
BUG: 1261008
Signed-off-by: Krutika Dhananjay 
Reviewed-on: http://review.gluster.org/12127
Tested-by: Gluster Build System 
Reviewed-by: Pranith Kumar Karampuri 
Tested-by: NetBSD Build System

tier/ctr: Solving DB Lock issue due to write contention from db connections

2015-09-11T20:46:50+00:00

This is a backport of 12031.

> Problem: The DB on the brick is been accessed by CTR, for write and
> tier migrator, for read and write. The write from tier migrator is reseting
> the heat counters after a cycle. Since we are using sqlite, two connections
> trying to write would cause a db lock contention. As a result CTR used to fail
> to update the db.

> Solution: Using the same db connection of CTR for reseting the heat counters.
> 1) Introducted a new IPC FOP for CTR
> 2) After the query do a ipc syncop to the underlying client xlator associated
>    to the brick.
> 3) CTR in brick will catch the IPC FOP and cleat the heat counters.

> Change-Id: I53306bfc08dcdba479deb4ccc154896521336150
> BUG: 1260730
> Signed-off-by: Joseph Fernandes 
> Reviewed-on: http://review.gluster.org/12031
> Tested-by: NetBSD Build System 
> Tested-by: Gluster Build System 

Signed-off-by: Dan Lambright 

Conflicts:
	xlators/cluster/dht/src/tier.c

Change-Id: I88aa289cdf21e216b42c3d8ccfb4e7e828b43772
BUG: 1262341
Reviewed-on: http://review.gluster.org/12161
Reviewed-by: Joseph Fernandes
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System 
Tested-by: Dan Lambright

features/shard: Do not return non-negative status on failure in writev

2015-09-11T12:54:43+00:00

        Backport of: http://review.gluster.org/#/c/12140/

Change-Id: I7c49a083894cead528901ebc0a88fcfa17e53da3
BUG: 1261715
Signed-off-by: Krutika Dhananjay 
Reviewed-on: http://review.gluster.org/12144
Reviewed-by: Pranith Kumar Karampuri 
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System

uss : handle `buf` variable properly in svs_glfs_readdir()

2015-09-09T12:16:39+00:00

The svs_glfs_readdir() is a generic function which is called from
svs_readdir() and svs_readdirp(). But in svs_readdir 'buf' variable
is passed as NULL, then glfs_read_readdir() will fail. This patch
will fix the same.

It is backport of http://review.gluster.org/12117

Upstream Reference:
> Change-Id: Id02e4e17e30c85de117db5ddd9f97b578622dff9
> BUG: 1260611
> Signed-off-by: Jiffin Tony Thottan 
> cherry-picked as 7b6183c36ebfe020b724c95b018a8cd535e1ecdd

Change-Id: Iee08d5c29cad0376ca9d378c8f17b0820eebc88a
BUG: 1260859
Signed-off-by: Jiffin Tony Thottan 
Reviewed-on: http://review.gluster.org/12122
Tested-by: NetBSD Build System 
Reviewed-by: Niels de Vos 
Reviewed-by: Raghavendra Bhat 
Tested-by: Gluster Build System