Permalink
Browse files

Downgraded BDB back to 4.0.92 [ Got some performance problems in 4.1.7 ]

  • Loading branch information...
1 parent 8fe2c08 commit e52f4911b83ca2e29427b104e129afee40cc5cfc @rsumbaly rsumbaly committed Jun 1, 2011
Showing with 1 addition and 1 deletion.
  1. +1 −1 .classpath
  2. BIN lib/je-4.0.92.jar
  3. BIN lib/je-4.1.7.jar
View
@@ -40,7 +40,7 @@
<classpathentry kind="lib" path="lib/protobuf-java-2.3.0.jar"/>
<classpathentry kind="lib" path="contrib/ec2-testing/lib/typica.jar"/>
<classpathentry kind="lib" path="lib/google-collect-1.0.jar"/>
- <classpathentry kind="lib" path="lib/je-4.1.7.jar"/>
+ <classpathentry kind="lib" path="lib/je-4.0.92.jar"/>
<classpathentry kind="lib" path="lib/paranamer-2.1.jar"/>
<classpathentry kind="lib" path="lib/jackson-mapper-asl-1.4.0.jar"/>
<classpathentry kind="lib" path="lib/jackson-core-asl-1.4.0.jar"/>
View
Binary file not shown.
View
Binary file not shown.

5 comments on commit e52f491

Collaborator

ijuma replied Jun 1, 2011

Have you reported them to the BDB JE project?

Contributor

afeinberg replied Jun 1, 2011

Yes, we've created a thread in the Bdb-JE forum (with a graph). We will need to provide them with additional data, but we noticed a slightly increase in put latency when Bdb was upgraded. The put latency increase was not significant on the first cluster we rolled the change out to, but we decided not to roll the change out further as the impact may be proportional to existing put latency.

Collaborator

ijuma replied Jun 1, 2011

OK, great.

Contributor

ctasada replied Jan 26, 2012

What about upgrading to JE 4.0.117? This upgrade should fix the "LOG_FILE_NOT_FOUND: Log file missing, log is likely invalid. Environment is invalid and must be closed" without the performance problems.

Collaborator

leigao replied Jan 26, 2012

Please sign in to comment.