Glusterfs threads steadily consume swap space until it runs out

Issue

We have two-node distributed-replicated gluster volumes that we've recently updated from RHGS 3.2 to RHGS 3.3.1 (we tried RHGS 3.3.0 on a test system as well).

Since the upgrade, glusterfs processes consume much more swap space than previously, and continue to consume swap until each machine runs out entirely -- it takes about 24 hours for the combined glusterfs threads on each node to consume all the available swap space. Even when increasing the swap space, the swap is still consumed until it runs out.

The swap consumption appears to speed up when doing a backup which enumerates the filesystem.

Other than the swap consumption, the volumes seem to be functioning normally.