- With gerrit https://git.opendaylight.org/gerrit/#/c/1366/ i have
introduced a log error, to spot inconsistent hashcode but indeed it
turn out is getting exercised also during a normal code path,
basically when:
<command orginator> --> <key owner> --> <all the other members>
all the other members when getting the replication from the non-key
owner will end up in this case. So that cannot be actually considered
an error.
Change-Id: Id38b45066164cb4998fdcdbb356bdf7af720b8c5
Signed-off-by: Giovanni Meo <gmeo@cisco.com>
rpcManager.invokeRemotely(recipientGenerator.generateRecipients(), command,
rpcManager.getDefaultRpcOptions(isSync));
} else {
rpcManager.invokeRemotely(recipientGenerator.generateRecipients(), command,
rpcManager.getDefaultRpcOptions(isSync));
} else {
- log.errorf("Didn't invoke RPC because primaryOwner (%s) didn't match this node (%s)", primaryOwner,
+ log.tracef("Didn't invoke RPC because primaryOwner (%s) didn't match this node (%s)", primaryOwner,
rpcManager.getAddress());
rpcManager.getAddress());
- log.errorf("Hashcode is (%s) for Key (%s) .. it could be inconsistent in the cluster!",
+ log.tracef("Hashcode is (%s) for Key (%s)",
command.getKey().hashCode(), command.getKey());
}
return returnValue;
command.getKey().hashCode(), command.getKey());
}
return returnValue;
// Return the known status
return retStatus;
} else {
// Return the known status
return retStatus;
} else {
- logger.error("Timing out, the workStatus for order {} has not come back in time!", this.order);
+ logger.error("Timing out, the workStatus for order {} has not come back in time!, it's hashcode is {}",
+ this.order, this.order.hashCode());
return new Status(StatusCode.TIMEOUT);
}
}
return new Status(StatusCode.TIMEOUT);
}
}