I have created new stable branches for the upcoming release.
From now on *all* bug fixes and *only* bug fixes *must* go to this new
stable branch. I reserve the right to undo any changes that do not
comply with this rule.
All packages use the same name for the branch: Feb2009. So in each of
your stable checkout directories you can do
cvs update -rFeb2009
to update to the new branch.
I have created branches for the following packages: MonetDB MonetDB4
MonetDB5 TestTools buildtools clients geom java pathfinder sql template
testing.
Note that datacell is missing from this list. It is not yet released
and will not be released in this round.
Also note that two packages now have stable branches that didn't use to
have them: java and testing. Testing is a new package (split off from
MonetDB) and java is now also incorporated in the release cycle.
--
Sjoerd Mullender
On Thu, Jan 22, 2009 at 03:06:44PM +0100, Ying Zhang wrote:
> On Thu, Jan 22, 2009 at 12:30:21PM +0000, Ying Zhang wrote:
> > Update of /cvsroot/monetdb/pathfinder/runtime
> > In directory 23jxhf1.ch3.sourceforge.com:/tmp/cvs-serv16608
> >
> > Modified Files:
> > serialize.mx xrpc_server.mx
> > Log Message:
> > Added a new env. var. to make the root directory, from which the XRPC HTTP
> > server serves files, configurable.
> >
> > This was (mainly) needed to get the xrpc admin tests run with RunMtest, since RunMtest doesn't have monet installed yet (i.e., there is no $prefix/share/ MonetDB/xrpc/ yet), so we need a way to tell the xrpc server to serve file from
> > a different directory, in this case, from $srcdir/runtime/xrpc.
>
> Sorry, I forgot to mention that this checkin requires an update and a
> rebuild of MonetDB4, because changes in MonetDB4/conf/MonetDB.conf.in
> are needed.
question is why are they needed?
or differently, why is the default (only) set in MonetDB.conf, rather then
where it is (first) used in Pathfinder/XRPC?
I would have expected that the newly added code in Pathfinder/XRPC, just
checks, whether the new environment variable is set; if so, it uses that
value; otherwise, it uses a default (defined there).
In case your code does already exactly this, the changes in MonetDB.conf,
should not be required for the new PF/XRPC code to work, rather, they mainly
document the new variable and its default value.
Stefan
> Jennie
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> Monetdb-pf-checkins mailing list
> Monetdb-pf-checkins(a)lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/monetdb-pf-checkins
--
| Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl |
| CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ |
| 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 |
| The Netherlands | Fax : +31 (20) 592-4312 |
On Thu, Jan 22, 2009 at 12:30:21PM +0000, Ying Zhang wrote:
> Update of /cvsroot/monetdb/pathfinder/runtime
> In directory 23jxhf1.ch3.sourceforge.com:/tmp/cvs-serv16608
>
> Modified Files:
> serialize.mx xrpc_server.mx
> Log Message:
> Added a new env. var. to make the root directory, from which the XRPC HTTP
> server serves files, configurable.
>
> This was (mainly) needed to get the xrpc admin tests run with RunMtest, since RunMtest doesn't have monet installed yet (i.e., there is no $prefix/share/ MonetDB/xrpc/ yet), so we need a way to tell the xrpc server to serve file from
> a different directory, in this case, from $srcdir/runtime/xrpc.
>
[...]
>
> U xrpc_server.mx
> Index: xrpc_server.mx
> ===================================================================
> RCS file: /cvsroot/monetdb/pathfinder/runtime/xrpc_server.mx,v
> retrieving revision 1.85
> retrieving revision 1.86
> diff -u -d -r1.85 -r1.86
> --- xrpc_server.mx 8 Jan 2009 16:54:18 -0000 1.85
> +++ xrpc_server.mx 22 Jan 2009 12:30:19 -0000 1.86
> @@ -89,6 +89,10 @@
> xrpc_trusted.append(prefix);
> }
>
> +proc set_xrpc_docroot(str new_docroot) : void {
> +
> +}
> +
Jennie,
what is the purpose of the above *empty* MIL proc?
Stefan
> proc get_xrpc_open() : bit {
> if (monet_environment.exist("xrpc_open")){
> return bit(monet_environment.find("xrpc_open"));
[...]
--
| Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl |
| CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ |
| 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 |
| The Netherlands | Fax : +31 (20) 592-4312 |
Hi,
I've finally found a better way to bulk load records via perl & odbc - a lot more stable.
However, I've noticed many times mclient crashing mserver5 when loading records via the interactive interface. For instance, I tried to load about 130 inserts from a sql file using this command :
mclient -lsql -d mydb < public_sysuser.sql
After few seconds I started to see :
#BBPTRIM: memtarget=17978753 vmtarget=0
#BBPTRIM_EXIT: memsize=24100864,vmsize=273741960
[ 1 ]
[ 1 ]
[ 1 ]
[ 1 ]
[ 1 ]
[ 1 ]
[ 1 ]
[ 1 ]
[ 1 ]
#BBPTRIM_ENTER: memsize=275281456,vmsize=275166768
#BBPTRIM: memtarget=19273201 vmtarget=0
#BBPTRIM_EXIT: memsize=24100864,vmsize=275158816
[ 1 ]
[ 1 ]
[ 1 ]
[ 1 ]
[ 1 ]
[ 1 ]
[ 1 ]
#BBPTRIM_ENTER: memsize=276161752,vmsize=276047064
#BBPTRIM: memtarget=20153497 vmtarget=0
#BBPTRIM_EXIT: memsize=24100864,vmsize=276056368
[ 1 ]
#BBPTRIM_ENTER: memsize=276322608,vmsize=276207920
#BBPTRIM: memtarget=20314353 vmtarget=0
#BBPTRIM_EXIT: memsize=24100864,vmsize=276198064
Top is showing :
top - 23:26:14 up 249 days, 9:57, 5 users, load average: 0.00, 0.20, 0.45
Tasks: 96 total, 1 running, 95 sleeping, 0 stopped, 0 zombie
Cpu(s): 0.0%us, 0.0%sy, 0.0%ni,100.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 4025600k total, 2433324k used, 1592276k free, 191788k buffers
Swap: 9502408k total, 92k used, 9502316k free, 1993392k cached
I don't think i'm running out of memory. I had to stop and restart mserver5, flush the table, then re-run the command - all the records were inserted. Also I noticed this type of messages on the mserver5 console when piping records through the mclient (over 1million records) . It seems that the mclient is quiet instable (cf my post about "COPY, terminating connection" few months ago).
So, is there a way to increase the memory limit or make sure mserver5 won't crash when running bash inserts via a cron job ?
Please advise,
Thank you
SB