-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
app: node: Add raft snapshot parameter options #143
Conversation
@MathieuBordere hmm, to me moving from Unless we need to move to |
I'll experiment some more with it, I need |
@stgraber So there's the There's another alternative, link but that doesn't seem to be available on all platforms, so some more configuration magic would be needed in libraries that want to use this and it won't work immediately, it will work once 2 versions of the library have applied this method. There's no clear winning alternative for me, what would you prefer? |
@MathieuBordere I think if we can tweak the Makefile in lxd that may be good enough. |
92c9143
to
dafc275
Compare
Let me have a look at those |
Adapting |
f9e69f7
to
604df1c
Compare
|
604df1c
to
c0a36f0
Compare
A user should set the environment variable CGO_LDFLAGS_ALLOW="-Wl,-z,now" see https://github.com/golang/go/wiki/InvalidFlag Signed-off-by: Mathieu Borderé <mathieu.bordere@canonical.com>
c0a36f0
to
54a1454
Compare
This PR uses the new dqlite API
dqlite_node_set_snapshot_params
available from dqlite1.8.0
.I want to update the SONAME of dqlite from
libdqlite.so.0
tolibdqlite.so.1
so that go-dqlite binaries built against a version of dqlite that contain this API fail when ran against an older version of the dqlite library. The problem is, I already released a version of libdqlite with SONAMElibdqlite.so.0
that contains thedqlite_node_set_snapshot_params
functionality.I'm not entirely sure if I should:
a) make a new dqlite release
1.9.0
and update the SONAME ? <-- This probably seems most reasonableb) just update the SONAME on master and not make a release ?
c) ... ?