PostgreSQL does not pick data written by another PostgreSQL container at /var/lib/postgresql/data/
I have set two postgresql docker containers to write to a mounted nfs volume at /var/lib/postgresql/data/ in a Kubernetes Cluster.
I noted that new changes are written correctly but data written by one container does not reflect on the database of the other container.
On deleting the pods/containers and recreating other two containers, the new containers do not reflect data in the database that was contained in database of previous containers even though the data files do exist.
Why does this happen?
postgresql docker kubernetes nfs persistent-volumes
asked Nov 13 '18 at 20:48
SamwelOpiyoSamwelOpiyo
264
add a comment |
I have set two postgresql docker containers to write to a mounted nfs volume at /var/lib/postgresql/data/ in a Kubernetes Cluster.
I noted that new changes are written correctly but data written by one container does not reflect on the database of the other container.
On deleting the pods/containers and recreating other two containers, the new containers do not reflect data in the database that was contained in database of previous containers even though the data files do exist.
Why does this happen?
postgresql docker kubernetes nfs persistent-volumes
asked Nov 13 '18 at 20:48
SamwelOpiyoSamwelOpiyo
264
add a comment |
I have set two postgresql docker containers to write to a mounted nfs volume at /var/lib/postgresql/data/ in a Kubernetes Cluster.
I noted that new changes are written correctly but data written by one container does not reflect on the database of the other container.
On deleting the pods/containers and recreating other two containers, the new containers do not reflect data in the database that was contained in database of previous containers even though the data files do exist.
Why does this happen?
postgresql docker kubernetes nfs persistent-volumes
asked Nov 13 '18 at 20:48
SamwelOpiyoSamwelOpiyo
264
I have set two postgresql docker containers to write to a mounted nfs volume at /var/lib/postgresql/data/ in a Kubernetes Cluster.
I noted that new changes are written correctly but data written by one container does not reflect on the database of the other container.
On deleting the pods/containers and recreating other two containers, the new containers do not reflect data in the database that was contained in database of previous containers even though the data files do exist.
Why does this happen?
postgresql docker kubernetes nfs persistent-volumes
postgresql docker kubernetes nfs persistent-volumes
asked Nov 13 '18 at 20:48
SamwelOpiyoSamwelOpiyo
264
asked Nov 13 '18 at 20:48
SamwelOpiyoSamwelOpiyo
264
edited Nov 13 '18 at 20:53
SamwelOpiyo
asked Nov 13 '18 at 20:48
SamwelOpiyoSamwelOpiyo
264
asked Nov 13 '18 at 20:48
SamwelOpiyoSamwelOpiyo
264
asked Nov 13 '18 at 20:48
SamwelOpiyoSamwelOpiyo
264
264
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
In short, you can't share the file system between 2 postgres instance.
Binding 2 instances to the same volume is referred as Shared Disk Failover (ref): the second instance is a backup and should only be put in use after the first one stops. The pair is by no mean to be used together, doing so will cause "severe data corruption".
If you are looking for ways to speed up database read / write, search for replication and sharding.
answered Nov 13 '18 at 21:43
SiyuSiyu
2,90311227
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53289274%2fpostgresql-does-not-pick-data-written-by-another-postgresql-container-at-var-li%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
In short, you can't share the file system between 2 postgres instance.
Binding 2 instances to the same volume is referred as Shared Disk Failover (ref): the second instance is a backup and should only be put in use after the first one stops. The pair is by no mean to be used together, doing so will cause "severe data corruption".
If you are looking for ways to speed up database read / write, search for replication and sharding.
answered Nov 13 '18 at 21:43
SiyuSiyu
2,90311227
add a comment |
In short, you can't share the file system between 2 postgres instance.
Binding 2 instances to the same volume is referred as Shared Disk Failover (ref): the second instance is a backup and should only be put in use after the first one stops. The pair is by no mean to be used together, doing so will cause "severe data corruption".
If you are looking for ways to speed up database read / write, search for replication and sharding.
answered Nov 13 '18 at 21:43
SiyuSiyu
2,90311227
add a comment |
In short, you can't share the file system between 2 postgres instance.
Binding 2 instances to the same volume is referred as Shared Disk Failover (ref): the second instance is a backup and should only be put in use after the first one stops. The pair is by no mean to be used together, doing so will cause "severe data corruption".
If you are looking for ways to speed up database read / write, search for replication and sharding.
answered Nov 13 '18 at 21:43
SiyuSiyu
2,90311227
In short, you can't share the file system between 2 postgres instance.
Binding 2 instances to the same volume is referred as Shared Disk Failover (ref): the second instance is a backup and should only be put in use after the first one stops. The pair is by no mean to be used together, doing so will cause "severe data corruption".
If you are looking for ways to speed up database read / write, search for replication and sharding.
answered Nov 13 '18 at 21:43
SiyuSiyu
2,90311227
answered Nov 13 '18 at 21:43
SiyuSiyu
2,90311227
answered Nov 13 '18 at 21:43
SiyuSiyu
2,90311227
answered Nov 13 '18 at 21:43
SiyuSiyu
2,90311227
2,90311227
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53289274%2fpostgresql-does-not-pick-data-written-by-another-postgresql-container-at-var-li%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
