Bug 1273967 - translator libraries should use versioned symbols instead of path specific library versions
translator libraries should use versioned symbols instead of path specific li...
Status: NEW
Product: GlusterFS
Classification: Community
Component: core (Show other bugs)
mainline
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: bugs@gluster.org
: FutureFeature, RFE, Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-10-21 11:29 EDT by Joe Julian
Modified: 2016-01-11 04:12 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Joe Julian 2015-10-21 11:29:40 EDT
Because we version our libraries by path, updates without remounts can cause issues during volume changes:

[2015-10-21 14:29:26.844977] I [glusterfsd-mgmt.c:56:mgmt_cbk_spec] 0-mgmt: Volume file changed
[2015-10-21 14:29:26.886861] W [MSGID: 101095] [xlator.c:194:xlator_dynload] 0-xlator: /usr/lib64/glusterfs/3.7.4/xlator/cluster/replicate.so: cannot open shared object file: No such file or directory
[2015-10-21 14:29:26.886909] E [graph.y:212:volume_type] 0-parser: Volume 'public-replicate-0', line 70: type 'cluster/replicate' is not valid or not found on this machine
[2015-10-21 14:29:26.886934] E [graph.y:321:volume_end] 0-parser: "type" not specified for volume public-replicate-0

If we used versioned symbol tables, we could theoretically support this scenario - unless I completely misunderstand their use.
Comment 1 Kaleb KEITHLEY 2015-11-03 08:43:37 EST
Yes, symbol versions would do that.

They also add a lot of complexity to writing and maintaining xlators.

Maybe we can or should consider it for 4.0 and hit the ground running with them from the start?

Note You need to log in before you can comment on or make changes to this bug.