Red Hat Bugzilla – Bug 865321
Eager locking lk-owner decision is taken before transaction type is set
Last modified: 2015-08-10 15:30:15 EDT
+++ This bug was initially created as a clone of Bug #864786 +++
Description of problem:
Eager locking lk-owner decision is taken before transaction type is set.
Default transaction type is DATA so all transactions are treated as DATA transactions at the time of eager-locking decision.
Breakpoint 1, afr_transaction (frame=0x7f45fd7f8008, this=0x1f73e90, type=AFR_ENTRY_TRANSACTION) at afr-transaction.c:1452
1452 afr_local_t * local = NULL;
1453 afr_private_t * priv = NULL;
1454 fd_t *fd = NULL;
1456 local = frame->local;
1457 priv = this->private;
1459 if (local->fd && priv->eager_lock &&
1463 afr_set_lk_owner (frame, this, frame->root);
(gdb) p local->transaction.type
$1 = AFR_DATA_TRANSACTION
Version-Release number of selected component (if applicable):
Steps to Reproduce:
--- Additional comment from firstname.lastname@example.org on 2012-10-10 22:11:40 EDT ---
CHANGE: http://review.gluster.org/4053 (cluster/afr: check transaction type for eager-lock after it is set) merged in master by Anand Avati (email@example.com)
Pranith, can you please provide the steps to verify this bug.