translator libraries should use versioned symbols instead of path specific library versions (Bugzilla Bug 1273967)

[vbellur]

This issue was created automatically with bugzilla2github

Bugzilla Bug 1273967

Date: 2015-10-21 11:29:00 -0400
From: Joe Julian
To: bugs@gluster.org
CC: bugs@gluster.org

Last updated: 2016-01-11 04:12:36 -0500

Comment 8742282

Date: 2015-10-21 11:29:40 -0400
From: Joe Julian

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 8778449

Date: 2015-11-03 08:43:37 -0500
From: Kaleb KEITHLEY

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?

[stale]

Thank you for your contributions.
Noticed that this issue is not having any activity in last ~6 months! We are marking this issue as stale because it has not had recent activity.
It will be closed in 2 weeks if no one responds with a comment here.

[stale]

Closing this issue as there was no update since my last update on issue. If this is an issue which is still valid, feel free to open it.