Controlling --dbextras Using MonetDB(D)
Hi,
I use wrapper shell in such case. May be useful for you.
$ mv /usr/bin/mserver5 /usr/bin/mserver5.bin
$ vim /usr/bin/mserver5
#!/usr/bin/env bash
exec /usr/bin/mserver5.bin --set gdk_vmtrim yes --set gdk_vm_maxsize 200000000000 --dbextra=/mnt/data/monetdb/extra $@
Alexey Manaev, Head of software development CJSC "RUTUBE"
Alex,
Thanks for the suggestion. I ended up adding a dbextra property to databases so that we can use the same mechanism of "monetdb set dbextra=…." to control.
It was a pretty simple patch. If you compile the source, I'd be happy to get it to you.
Thanks, Vince
From: users-list <users-list-bounces+vincent.sheffer=sysorex.com@monetdb.orgmailto:users-list-bounces+vincent.sheffer=sysorex.com@monetdb.org> on behalf of Alex Manaev <amanaev@rutube.rumailto:amanaev@rutube.ru> Reply-To: Communication channel for MonetDB users <users-list@monetdb.orgmailto:users-list@monetdb.org> Date: Friday, April 1, 2016 at 6:58 AM To: "users-list@monetdb.orgmailto:users-list@monetdb.org" <users-list@monetdb.orgmailto:users-list@monetdb.org> Subject: Controlling --dbextras Using MonetDB(D)
Hi,
I use wrapper shell in such case. May be useful for you.
$ mv /usr/bin/mserver5 /usr/bin/mserver5.bin
$ vim /usr/bin/mserver5
#!/usr/bin/env bash
exec /usr/bin/mserver5.bin --set gdk_vmtrim yes --set gdk_vm_maxsize 200000000000 --dbextra=/mnt/data/monetdb/extra $@
Alexey Manaev, Head of software development CJSC "RUTUBE"
The information transmitted, including any attachments, is intended only for the individual or entity to which it is addressed, and may contain confidential and/or privileged information. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by individuals or entities other than the intended recipient is prohibited, and all liability arising therefrom is disclaimed. If you have received this communication in error, please delete the information from any computer and notify the sender.
Digging further into the source code, there are a lot of arguments to mserver5 that are not settable by any means other than directly invoking the mserver5 executable. Some, such as --single-user aren't even in the man pages, at least not the man pages I have.
Given that monetdbd seems to be the preferred method for invoking and controlling mserver5 processes, why are so many arguments to mserver5 not manageable via the combination of monetdbd and monetdb properties?
From: users-list <users-list-bounces+vincent.sheffer=sysorex.com@monetdb.orgmailto:users-list-bounces+vincent.sheffer=sysorex.com@monetdb.org> on behalf of Vincent Sheffer <Vincent.Sheffer@sysorex.commailto:Vincent.Sheffer@sysorex.com> Reply-To: Communication channel for MonetDB users <users-list@monetdb.orgmailto:users-list@monetdb.org> Date: Friday, April 1, 2016 at 7:57 AM To: Communication channel for MonetDB users <users-list@monetdb.orgmailto:users-list@monetdb.org> Subject: Re: Controlling --dbextras Using MonetDB(D)
Alex,
Thanks for the suggestion. I ended up adding a dbextra property to databases so that we can use the same mechanism of "monetdb set dbextra=…." to control.
It was a pretty simple patch. If you compile the source, I'd be happy to get it to you.
Thanks, Vince
From: users-list <users-list-bounces+vincent.sheffer=sysorex.com@monetdb.orgmailto:users-list-bounces+vincent.sheffer=sysorex.com@monetdb.org> on behalf of Alex Manaev <amanaev@rutube.rumailto:amanaev@rutube.ru> Reply-To: Communication channel for MonetDB users <users-list@monetdb.orgmailto:users-list@monetdb.org> Date: Friday, April 1, 2016 at 6:58 AM To: "users-list@monetdb.orgmailto:users-list@monetdb.org" <users-list@monetdb.orgmailto:users-list@monetdb.org> Subject: Controlling --dbextras Using MonetDB(D)
Hi,
I use wrapper shell in such case. May be useful for you.
$ mv /usr/bin/mserver5 /usr/bin/mserver5.bin
$ vim /usr/bin/mserver5
#!/usr/bin/env bash
exec /usr/bin/mserver5.bin --set gdk_vmtrim yes --set gdk_vm_maxsize 200000000000 --dbextra=/mnt/data/monetdb/extra $@
Alexey Manaev, Head of software development CJSC "RUTUBE"
The information transmitted, including any attachments, is intended only for the individual or entity to which it is addressed, and may contain confidential and/or privileged information. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by individuals or entities other than the intended recipient is prohibited, and all liability arising therefrom is disclaimed. If you have received this communication in error, please delete the information from any computer and notify the sender.
Dear Vincent,
your analysis is correct: there are several mserver5 options that cannot (yet?) be set / changed via monetdb(d). The reason is twofold. First, ome are (or at least were) considered mainly development & debugging rather than "production" options (though we more and more realize that some of the development / debugging options might also be useful to analyse production deployments of MonetDB). Second, there are finite (human) resources available to maintain, develop, improve, extend the entire MonetDB code base, and these extensions of monetdb(d) have not yet reached the top of our priority list.
Please consider filing a feature request via http://bugs.monedb.org/ .
Also, external contributions are welcome --- though we realize that the threshold to dive into the MonetDB code base is rather high …
Regards,
Jennie
On Apr 05, 2016, at 00:58 , Vincent Sheffer Vincent.Sheffer@sysorex.com wrote:
Digging further into the source code, there are a lot of arguments to mserver5 that are not settable by any means other than directly invoking the mserver5 executable. Some, such as --single-user aren't even in the man pages, at least not the man pages I have.
Given that monetdbd seems to be the preferred method for invoking and controlling mserver5 processes, why are so many arguments to mserver5 not manageable via the combination of monetdbd and monetdb properties?
From: users-list users-list-bounces+vincent.sheffer=sysorex.com@monetdb.org on behalf of Vincent Sheffer Vincent.Sheffer@sysorex.com Reply-To: Communication channel for MonetDB users users-list@monetdb.org Date: Friday, April 1, 2016 at 7:57 AM To: Communication channel for MonetDB users users-list@monetdb.org Subject: Re: Controlling --dbextras Using MonetDB(D)
Alex,
Thanks for the suggestion. I ended up adding a dbextra property to databases so that we can use the same mechanism of "monetdb set dbextra=…." to control.
It was a pretty simple patch. If you compile the source, I'd be happy to get it to you.
Thanks, Vince
From: users-list users-list-bounces+vincent.sheffer=sysorex.com@monetdb.org on behalf of Alex Manaev amanaev@rutube.ru Reply-To: Communication channel for MonetDB users users-list@monetdb.org Date: Friday, April 1, 2016 at 6:58 AM To: "users-list@monetdb.org" users-list@monetdb.org Subject: Controlling --dbextras Using MonetDB(D)
Hi,
I use wrapper shell in such case. May be useful for you.
$ mv /usr/bin/mserver5 /usr/bin/mserver5.bin
$ vim /usr/bin/mserver5
#!/usr/bin/env bash
exec /usr/bin/mserver5.bin --set gdk_vmtrim yes --set gdk_vm_maxsize 200000000000 --dbextra=/mnt/data/monetdb/extra $@
Alexey Manaev, Head of software development CJSC "RUTUBE"
The information transmitted, including any attachments, is intended only for the individual or entity to which it is addressed, and may contain confidential and/or privileged information. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by individuals or entities other than the intended recipient is prohibited, and all liability arising therefrom is disclaimed. If you have received this communication in error, please delete the information from any computer and notify the sender.
users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list
Ying,
Thanks for the response and I totally understand about priorities and resource constraints.
I already have a patch that adds dbextra as a property for monetdb. Having done it once, I can add others pretty easily. I will continue to work to add support for arguments that my company needs and at some point supply a patch that can be included in the main MonetDB code base.
And, by the way, you did answer my more implied question, which was whether the omission was intentional or more a case of prioritization.
Regards, Vince
On 4/6/16, 8:19 AM, "users-list on behalf of Ying Zhang" <users-list-bounces+vincent.sheffer=sysorex.com@monetdb.org on behalf of y.zhang@cwi.nl> wrote:
Dear Vincent,
your analysis is correct: there are several mserver5 options that cannot (yet?) be set / changed via monetdb(d). The reason is twofold. First, ome are (or at least were) considered mainly development & debugging rather than "production" options (though we more and more realize that some of the development / debugging options might also be useful to analyse production deployments of MonetDB). Second, there are finite (human) resources available to maintain, develop, improve, extend the entire MonetDB code base, and these extensions of monetdb(d) have not yet reached the top of our priority list.
Please consider filing a feature request via http://bugs.monedb.org/ .
Also, external contributions are welcome --- though we realize that the threshold to dive into the MonetDB code base is rather high …
Regards,
Jennie
On Apr 05, 2016, at 00:58 , Vincent Sheffer Vincent.Sheffer@sysorex.com wrote:
Digging further into the source code, there are a lot of arguments to mserver5 that are not settable by any means other than directly invoking the mserver5 executable. Some, such as --single-user aren't even in the man pages, at least not the man pages I have.
Given that monetdbd seems to be the preferred method for invoking and controlling mserver5 processes, why are so many arguments to mserver5 not manageable via the combination of monetdbd and monetdb properties?
From: users-list users-list-bounces+vincent.sheffer=sysorex.com@monetdb.org on behalf of Vincent Sheffer Vincent.Sheffer@sysorex.com Reply-To: Communication channel for MonetDB users users-list@monetdb.org Date: Friday, April 1, 2016 at 7:57 AM To: Communication channel for MonetDB users users-list@monetdb.org Subject: Re: Controlling --dbextras Using MonetDB(D)
Alex,
Thanks for the suggestion. I ended up adding a dbextra property to databases so that we can use the same mechanism of "monetdb set dbextra=…." to control.
It was a pretty simple patch. If you compile the source, I'd be happy to get it to you.
Thanks, Vince
From: users-list users-list-bounces+vincent.sheffer=sysorex.com@monetdb.org on behalf of Alex Manaev amanaev@rutube.ru Reply-To: Communication channel for MonetDB users users-list@monetdb.org Date: Friday, April 1, 2016 at 6:58 AM To: "users-list@monetdb.org" users-list@monetdb.org Subject: Controlling --dbextras Using MonetDB(D)
Hi,
I use wrapper shell in such case. May be useful for you.
$ mv /usr/bin/mserver5 /usr/bin/mserver5.bin
$ vim /usr/bin/mserver5
#!/usr/bin/env bash
exec /usr/bin/mserver5.bin --set gdk_vmtrim yes --set gdk_vm_maxsize 200000000000 --dbextra=/mnt/data/monetdb/extra $@
Alexey Manaev, Head of software development CJSC "RUTUBE"
The information transmitted, including any attachments, is intended only for the individual or entity to which it is addressed, and may contain confidential and/or privileged information. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by individuals or entities other than the intended recipient is prohibited, and all liability arising therefrom is disclaimed. If you have received this communication in error, please delete the information from any computer and notify the sender.
users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list
users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list
participants (3)
-
Alex Manaev -
Vincent Sheffer -
Ying Zhang