I've answered your question here.
Type: Posts; User: pzhao
I've answered your question here.
I'd be happy to help you. I think the first thing to do is upgrade to the latest version of Voltdb via github. Yes, you can deploy a cluster with VoltDB community version. Can you provide...
Please refer to this link for increasing temp table memory in VoltDB.
VoltDB has a capped collection via create table's limit constraint. More information is located here.
Q1: Correct, it is not in memory. Just a clarification, export tables are...
Sounds like your all set but if you need assistance, please reach out to us.
Unfortunately, this is not a currently feature. We will consider this in a future release.
The specific section you are referring to is about manual backups. Automated Snapshots can be configured via deployment file. Please look at this.
In addition to using filters, you can also use limit/offset to divide up the data. Here is the documentation.
Currently, VoltDB has limitations on large data sets but will improve in the coming months. As a workaround you can break up the query and divide the data using filters. Breaking up...
Please take a look at the bottom of @Statistics.
You'll find some sample code that calls @Statistics and try the MEMORY parameter. See if that helps.
We do not have SQL statement style syntax as you've described. Besides using stored procedure or our VMC, you can also use sqlcmd tool:
echo "exec @statistics memory, 0;" | sqlcmd
When you develop stored procedures, you must decide if they are to be partitioned or not, in which case it will run as a multi-partition transaction. If the procedure needs to access data...
Doumentation for VoltDB contains alot of the information you are looking for. There is also a search if you need to find something specific. If you find something you need further help on,...
Did you do jar the class files after javac? It appears you were able to compile properly using javac. I was able to compile your code properly as well.
Here is a guide on...
I suspect there is more to the crash then just this warning message. Within your working directory, there should be a log/volt.log file present you can check.
Alternatively, you can run...
Added, you could define row limits on tables to prevent over utilizing heap size.
Ultimately, an undersized Java heap memory (VOLTDB_HEAPMAX) leads to VoltDB crashing due to not enough heap memory or VoltDB performance will suffer due to java garbage collection being...
My name is Peter from VoltDB. I'd love to help you out with your setup.
What version of voltdb is being run?
Try simpler setup to just prove that,voltdb is...
One suggestion is to check if swapping is enabled using the command 'swapon -s'. Memory swapping is enabled by default for most linux distributions and hinder VoltDB performance.
Thanks for your response. Could you do a simple count(*) on your 'store' table just to verify the row count?
Added, would it be possible to send us all the necessary files via zip so that...
I think our best approach here is to reproduce this problem. Just a few questions/information I'd like to gather:
After 1.6billion rows, can you validate that there are indeed values...
Can you send show me your deployment file? It appears the userid is not present in your deployment.xml file.
There are 2 things you could do. One option is to put callprocedure1/callprocedure2/dootherimportantthings in one stored procedure. This will either all succeed or all fail. The other...
It seems like the port being used is either not listening or being used for something else, ie another application.
Please verify that voltdb is running, ie 'ps aux | grep voltdb' or...
Sorry for the late reply to your question.
Here is a quick example of assumeunique index:
CREATE TABLE T38
C6 DECIMAL ASSUMEUNIQUE NOT NULL