[MonetDB-users] Killing long running queries
Is there any way to know the current running queries (like mysql's "show full processlist"). Also is there any way of killing long running queries. -- View this message in context: http://old.nabble.com/Killing-long-running-queries-tp31276295p31276295.html Sent from the monetdb-users mailing list archive at Nabble.com.
On 30-03-2011 04:33:08 -0700, Ramkumarlak wrote:
Is there any way to know the current running queries (like mysql's "show full processlist"). Also is there any way of killing long running queries.
Nope, sorry. The only thing you can do is shutdown the server.
On 3/30/11 1:37 PM, Fabian Groffen wrote:
On 30-03-2011 04:33:08 -0700, Ramkumarlak wrote:
Is there any way to know the current running queries (like mysql's "show full processlist"). Also is there any way of killing long running queries.
Nope, sorry. The only thing you can do is shutdown the server. nope that is not quite true, you might have a look in the MAL libraries (client) to see how to stop a client. However, it takes effect after the current MAL instruction is finished (which may take time)
------------------------------------------------------------------------------ Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
To kill the query I tried to stop the database using "monetdb stop <dbname>" When I restarted using "monetdb start <dbname>" I got the following error. 2011-03-30 17:29:02 ERR control[10339]: (local): failed to fork mserver: database 'concurrenttest' has inconsistent state (sabaoth administration reports running, but process seems gone), review merovingian's logfile for any peculiarities (Note: There were no dml queries at that time) Restarting one more time worked. Since we would like to use it in production (24/7) we have some doubts. * Are there any chances of data corruption if the server gets killed abruptly ? Is there any way to detect data corruption if it happens ? * What is your recommended way of backing up. (We use linux). * Monetdb doesn't seem to support replication. Do you have any workarounds for ensuring availability ? Any pointers would be very helpful. Regards Ram Martin Kersten wrote:
On 3/30/11 1:37 PM, Fabian Groffen wrote:
On 30-03-2011 04:33:08 -0700, Ramkumarlak wrote:
Is there any way to know the current running queries (like mysql's "show full processlist"). Also is there any way of killing long running queries.
Nope, sorry. The only thing you can do is shutdown the server. nope that is not quite true, you might have a look in the MAL libraries (client) to see how to stop a client. However, it takes effect after the current MAL instruction is finished (which may take time)
------------------------------------------------------------------------------ Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
------------------------------------------------------------------------------ Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
-- View this message in context: http://old.nabble.com/Killing-long-running-queries-tp31276295p31283612.html Sent from the monetdb-users mailing list archive at Nabble.com.
Does anyone from MonetDB team help me..? Ramkumarlak wrote:
To kill the query I tried to stop the database using "monetdb stop <dbname>"
When I restarted using "monetdb start <dbname>" I got the following error.
2011-03-30 17:29:02 ERR control[10339]: (local): failed to fork mserver: database 'concurrenttest' has inconsistent state (sabaoth administration reports running, but process seems gone), review merovingian's logfile for any peculiarities
(Note: There were no dml queries at that time)
Restarting one more time worked.
Since we would like to use it in production (24/7) we have some doubts.
* Is there any command to get the list of current running queries ?
* Are there any chances of data corruption if the server gets killed abruptly ? Is there any way to detect data corruption if it happens ?
* What is your recommended way of backing up. (We use linux).
* Monetdb doesn't seem to support replication. Do you have any workarounds for ensuring availability ?
Any pointers would be very helpful.
Regards Ram
Martin Kersten wrote:
On 3/30/11 1:37 PM, Fabian Groffen wrote:
On 30-03-2011 04:33:08 -0700, Ramkumarlak wrote:
Is there any way to know the current running queries (like mysql's "show full processlist"). Also is there any way of killing long running queries.
Nope, sorry. The only thing you can do is shutdown the server. nope that is not quite true, you might have a look in the MAL libraries (client) to see how to stop a client. However, it takes effect after the current MAL instruction is finished (which may take time)
------------------------------------------------------------------------------ Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
------------------------------------------------------------------------------ Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
-- View this message in context: http://old.nabble.com/Killing-long-running-queries-tp31276295p31330770.html Sent from the monetdb-users mailing list archive at Nabble.com.
On 06-04-2011 00:03:27 -0700, Ramkumarlak wrote:
Does anyone from MonetDB team help me..?
Sure, but we can't in this case.
Ramkumarlak wrote:
To kill the query I tried to stop the database using "monetdb stop <dbname>"
When I restarted using "monetdb start <dbname>" I got the following error.
2011-03-30 17:29:02 ERR control[10339]: (local): failed to fork mserver: database 'concurrenttest' has inconsistent state (sabaoth administration reports running, but process seems gone), review merovingian's logfile for any peculiarities
(Note: There were no dml queries at that time)
Restarting one more time worked.
Since we would like to use it in production (24/7) we have some doubts.
* Is there any command to get the list of current running queries ?
no
* Are there any chances of data corruption if the server gets killed abruptly ? Is there any way to detect data corruption if it happens ?
The answer here should be "no". Simply because the database is built upon the idea that no matter in what state the system goes down, it always remains consistent. The next startup will then cleanup.
* What is your recommended way of backing up. (We use linux).
use msqldump, and compress the output using xz or bz2.
* Monetdb doesn't seem to support replication. Do you have any workarounds for ensuring availability ?
If you maintain the replicas yourself, you can use monetdbd's sharing features to get round-robin access to a set of machines. See the manpage.
participants (3)
-
Fabian Groffen -
Martin Kersten -
Ramkumarlak