Remove MessageBus sequencing for read only operations

We cannot guarantee sequencing when operations hit different SourceSessions
in the first place, so we should not sacrifice performance and parallelism
by chasing an unreachable goal. Clients should only rely on the standard
mechanism for write visibility, which is to receive an ACK.

Add ACK barriers to AsyncSession test to avoid implicit sequencing requirement.

1 files changed, 0 insertions, 10 deletions

diff --git a/documentapi/src/main/java/com/yahoo/documentapi/messagebus/protocol/StatBucketMessage.java b/documentapi/src/main/java/com/yahoo/documentapi/messagebus/protocol/StatBucketMessage.java
index ed08c23504e..9b2176d85f6 100755
--- a/documentapi/src/main/java/com/yahoo/documentapi/messagebus/protocol/StatBucketMessage.java
+++ b/documentapi/src/main/java/com/yahoo/documentapi/messagebus/protocol/StatBucketMessage.java
@@ -44,16 +44,6 @@ public class StatBucketMessage extends DocumentMessage {
     }
 
     @Override
-    public boolean hasSequenceId() {
-        return true;
-    }
-
-    @Override
-    public long getSequenceId() {
-        return bucketId.getRawId();
-    }
-
-    @Override
     public int getType() {
         return DocumentProtocol.MESSAGE_STATBUCKET;
     }