-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
Affects Version/s: 1.9.1
-
Component/s: Stability
-
Environment:Single-core VMWare 4GB RAM Ubuntu 10.04.3 LTS instance
2.6.32-33-server #71-Ubuntu SMP Wed Jul 20 17:42:25 UTC 2011 x86_64 GNU/Linux
Single stand-alone mongod, no sharding, no replica
Using auth, noprealloc, nosmallfiles, directoryperdb
mongod --version
db version v1.9.0, pdfile version 4.5
Mon Aug 15 10:52:08 git version: 434d8b47e569578d932e3caedd3bb16e8c0836a3
This is from mongodb-10gen-unstable package
Foswiki trunk svn rev 12313 with CPAN MongoDB version 0.43Single-core VMWare 4GB RAM Ubuntu 10.04.3 LTS instance 2.6.32-33-server #71-Ubuntu SMP Wed Jul 20 17:42:25 UTC 2011 x86_64 GNU/Linux Single stand-alone mongod, no sharding, no replica Using auth, noprealloc, nosmallfiles, directoryperdb mongod --version db version v1.9.0, pdfile version 4.5 Mon Aug 15 10:52:08 git version: 434d8b47e569578d932e3caedd3bb16e8c0836a3 This is from mongodb-10gen-unstable package Foswiki trunk svn rev 12313 with CPAN MongoDB version 0.43
We have reverted to MongoDB 1.9.0 because of a new crash in 1.9.1, triggered during the initial import of our data. The crash happened reliably (even after stopping & deleting /var/lib/mongodb/* & reimporting) until downgrading to 1.9.0.
Running the import - it works okay initially, until it gets to some 'interesting' data (attached an example), which is interesting because it has many fields which Foswiki indexes (many more than the 64 limit; basically, all the FIELD.<foo>.value fields). For what it's worth, the code that adds these indexes is at https://github.com/foswiki/MongoDBPlugin/blob/master/lib/Foswiki/Plugins/MongoDBPlugin.pm#L309
I have been trying to reproduce on our test environment so I can get some verbose log output, but as usual, it's working fine there...
- is related to
-
-
- Closed
-