Why does gluster CLI try to obtain lock without verifying the argument vector validness?

Solution Verified - Updated -

Issue

  • Command executed to test
# gluster volume set <vol_name> feature.root-squash on
  • tcpdump on GlusterFS traffic
650400  14722.592537000 10.235.46.217   10.225.51.108   GlusterD Management 198 V2 CLUSTER_LOCK Call (Reply In 650401)
650401  14722.595894000 10.225.51.108   10.235.46.217   GlusterD Management 166 V2 CLUSTER_LOCK Reply (Call In 650400)
650403  14722.600435000 10.235.46.217   10.225.51.108   GlusterD Management 198 V2 CLUSTER_UNLOCK Call (Reply In 650404)
650404  14722.601269000 10.225.51.108   10.235.46.217   GlusterD Management 166 V2 CLUSTER_UNLOCK Reply (Call In 650403)

Environment

Red Hat Storage Server 2.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.