Postgres-XL adding GTM Proxy seems to do nothing
I've set up a Postgres-XL cluster using this recipe:
GTM:
hostname=host1
nodename=gtm
Coordinator：
hostname=host2
nodename=coord1
Datanode1：
hostname=host3
nodename=datanode1
Datanode2：
hostname=host4
nodename=datanode2
When I ran a load test against it, the GTM would fallover. I tweak settings until the GTM didn't fall over but only reported errors - thus kept on working after the load test.
I the added a GTM Proxy. I did not do init all but rather only init the proxy. When I restarted the cluster, the GTM reported that the GTM proxy was up and running. When I looked at the GTM proxy's log, it looked like it started up and was connected.
But when I ran the load test again, I got the same result with no log entries for the GTM proxy. Thus it seems like the GTM Proxy didn't pick up the load processing as I expected it to do.
I don't know how to trouble shoot this. Any pointers on where to look next?
(I don't know what extra info to post here)
clustering proxy postgres-xl
asked Jun 30 '17 at 11:15
TungstenXTungstenX
617
bumped to the homepage by Community♦ 6 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I've set up a Postgres-XL cluster using this recipe:
GTM:
hostname=host1
nodename=gtm
Coordinator：
hostname=host2
nodename=coord1
Datanode1：
hostname=host3
nodename=datanode1
Datanode2：
hostname=host4
nodename=datanode2
When I ran a load test against it, the GTM would fallover. I tweak settings until the GTM didn't fall over but only reported errors - thus kept on working after the load test.
I the added a GTM Proxy. I did not do init all but rather only init the proxy. When I restarted the cluster, the GTM reported that the GTM proxy was up and running. When I looked at the GTM proxy's log, it looked like it started up and was connected.
But when I ran the load test again, I got the same result with no log entries for the GTM proxy. Thus it seems like the GTM Proxy didn't pick up the load processing as I expected it to do.
I don't know how to trouble shoot this. Any pointers on where to look next?
(I don't know what extra info to post here)
clustering proxy postgres-xl
asked Jun 30 '17 at 11:15
TungstenXTungstenX
617
bumped to the homepage by Community♦ 6 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I've set up a Postgres-XL cluster using this recipe:
GTM:
hostname=host1
nodename=gtm
Coordinator：
hostname=host2
nodename=coord1
Datanode1：
hostname=host3
nodename=datanode1
Datanode2：
hostname=host4
nodename=datanode2
When I ran a load test against it, the GTM would fallover. I tweak settings until the GTM didn't fall over but only reported errors - thus kept on working after the load test.
I the added a GTM Proxy. I did not do init all but rather only init the proxy. When I restarted the cluster, the GTM reported that the GTM proxy was up and running. When I looked at the GTM proxy's log, it looked like it started up and was connected.
But when I ran the load test again, I got the same result with no log entries for the GTM proxy. Thus it seems like the GTM Proxy didn't pick up the load processing as I expected it to do.
I don't know how to trouble shoot this. Any pointers on where to look next?
(I don't know what extra info to post here)
clustering proxy postgres-xl
asked Jun 30 '17 at 11:15
TungstenXTungstenX
617
I've set up a Postgres-XL cluster using this recipe:
GTM:
hostname=host1
nodename=gtm
Coordinator：
hostname=host2
nodename=coord1
Datanode1：
hostname=host3
nodename=datanode1
Datanode2：
hostname=host4
nodename=datanode2
When I ran a load test against it, the GTM would fallover. I tweak settings until the GTM didn't fall over but only reported errors - thus kept on working after the load test.
I the added a GTM Proxy. I did not do init all but rather only init the proxy. When I restarted the cluster, the GTM reported that the GTM proxy was up and running. When I looked at the GTM proxy's log, it looked like it started up and was connected.
But when I ran the load test again, I got the same result with no log entries for the GTM proxy. Thus it seems like the GTM Proxy didn't pick up the load processing as I expected it to do.
I don't know how to trouble shoot this. Any pointers on where to look next?
(I don't know what extra info to post here)
clustering proxy postgres-xl
clustering proxy postgres-xl
asked Jun 30 '17 at 11:15
TungstenXTungstenX
617
asked Jun 30 '17 at 11:15
TungstenXTungstenX
617
asked Jun 30 '17 at 11:15
TungstenXTungstenX
617
asked Jun 30 '17 at 11:15
TungstenXTungstenX
617
asked Jun 30 '17 at 11:15
TungstenXTungstenX
617
617
bumped to the homepage by Community♦ 6 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 6 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
This is known bug/feature: pgxc_ctl does not know which proxy should be used by each coordinator / datanode (it does not assume that it is supposed to use a local one).
GTM proxy does not 'pick' the config; you need to instruct others to use the proxy.
You can fix it manually by editing postgresql.conf located in data directories for your datanodes and coordinators.
Find gtm_host and gtm_port and replace real GTM values with IP and port of your proxy. Or you can add these lines to the end of the file if this makes your scripts easier. Reload datanodes and coordinators to update their config (pg_ctl reload -D /data/directory/path)
Ideally you should have a proxy configured on every physical host, and instruct your datanode and coordinators to use the local proxy.
answered Aug 2 '17 at 16:00
JulianJulian
1
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2fdba.stackexchange.com%2fquestions%2f177675%2fpostgres-xl-adding-gtm-proxy-seems-to-do-nothing%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
This is known bug/feature: pgxc_ctl does not know which proxy should be used by each coordinator / datanode (it does not assume that it is supposed to use a local one).
GTM proxy does not 'pick' the config; you need to instruct others to use the proxy.
You can fix it manually by editing postgresql.conf located in data directories for your datanodes and coordinators.
Find gtm_host and gtm_port and replace real GTM values with IP and port of your proxy. Or you can add these lines to the end of the file if this makes your scripts easier. Reload datanodes and coordinators to update their config (pg_ctl reload -D /data/directory/path)
Ideally you should have a proxy configured on every physical host, and instruct your datanode and coordinators to use the local proxy.
answered Aug 2 '17 at 16:00
JulianJulian
1
add a comment |
This is known bug/feature: pgxc_ctl does not know which proxy should be used by each coordinator / datanode (it does not assume that it is supposed to use a local one).
GTM proxy does not 'pick' the config; you need to instruct others to use the proxy.
You can fix it manually by editing postgresql.conf located in data directories for your datanodes and coordinators.
Find gtm_host and gtm_port and replace real GTM values with IP and port of your proxy. Or you can add these lines to the end of the file if this makes your scripts easier. Reload datanodes and coordinators to update their config (pg_ctl reload -D /data/directory/path)
Ideally you should have a proxy configured on every physical host, and instruct your datanode and coordinators to use the local proxy.
answered Aug 2 '17 at 16:00
JulianJulian
1
add a comment |
This is known bug/feature: pgxc_ctl does not know which proxy should be used by each coordinator / datanode (it does not assume that it is supposed to use a local one).
GTM proxy does not 'pick' the config; you need to instruct others to use the proxy.
You can fix it manually by editing postgresql.conf located in data directories for your datanodes and coordinators.
Find gtm_host and gtm_port and replace real GTM values with IP and port of your proxy. Or you can add these lines to the end of the file if this makes your scripts easier. Reload datanodes and coordinators to update their config (pg_ctl reload -D /data/directory/path)
Ideally you should have a proxy configured on every physical host, and instruct your datanode and coordinators to use the local proxy.
answered Aug 2 '17 at 16:00
JulianJulian
1
This is known bug/feature: pgxc_ctl does not know which proxy should be used by each coordinator / datanode (it does not assume that it is supposed to use a local one).
GTM proxy does not 'pick' the config; you need to instruct others to use the proxy.
You can fix it manually by editing postgresql.conf located in data directories for your datanodes and coordinators.
Find gtm_host and gtm_port and replace real GTM values with IP and port of your proxy. Or you can add these lines to the end of the file if this makes your scripts easier. Reload datanodes and coordinators to update their config (pg_ctl reload -D /data/directory/path)
Ideally you should have a proxy configured on every physical host, and instruct your datanode and coordinators to use the local proxy.
answered Aug 2 '17 at 16:00
JulianJulian
1
answered Aug 2 '17 at 16:00
JulianJulian
1
answered Aug 2 '17 at 16:00
JulianJulian
1
answered Aug 2 '17 at 16:00
JulianJulian
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Database Administrators Stack Exchange!
- 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%2fdba.stackexchange.com%2fquestions%2f177675%2fpostgres-xl-adding-gtm-proxy-seems-to-do-nothing%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
