Is setting "Compression" bundle in Raven.Server.exe.config not suggested?

[Brian Connolly]

I inherited the job of administering a Raven 2.5 server a year ago, and I've come to question the practice of putting "Compression" in the "ActiveBundles" setting in Raven.Server.exe.config.  

Is the default use of Compression known to lead to confusion or complications when upgrading?

The decision to enable Compression by default predated my time, but it seems to be the root cause of many failed attempts to upgrade servers from 2.5 (2996) to 3.x.  The workaround that finally found was to restore backups to a fresh server, with Compression not configured by default in Raven.Server.config.

More specifically, and if someone experience the same scenario, this was my path:

1. Backup all 2.5 databases
   
2. STOP Raven
3. Remove the 2.5 installation that had "Compression" configured as default
4. Create a new (and empty) installation of 3.x, making sure to NOT include "Compress" as a default
5. START Raven, creating a new 'system' database
6. Restore each database from backups, excluding the old 'system' database

All of the documented or suggested methods of upgrading resulted in errors for me.  Even using the export&import approach resulted in issues.

So.. I'm rather happy to have found an upgrade method that works.  But I'm never leaving Compression turned on at the server level ever again.  The migrated databases will need to put into compressed versions next, but I'm planning to do that on the individual database level.  A practice that I have a feeling is more the standard.

[Oren Eini (Ayende Rahien)]

Compression on by default is strange, because it will not be included in the db settings, which can cause issues if you are moving to a server that doesn't have this by default, since it will consider the data corrupted.

Hibernating Rhinos Ltd  

Oren Eini l CEO l Mobile: + 972-52-548-6969

Office: +972-4-622-7811 l Fax: +972-153-4-622-7811

 

--
You received this message because you are subscribed to the Google Groups "RavenDB - 2nd generation document database" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Brian Connolly]

I also suspect that the compression setting was implemented after a few of the databases I'm working with had already been created.  This might explain why the oldest databases were failing to restore, but any new database I created would restore fine.  

If the server is set to assume everything is compressed, I could image the backup process treating all databases that way.  The result being the creation of backups that could not be restored.

I have only done a little digging through the RavenDB to find where a safeguard may be implemented, but I'll give it another try when I have some time.   In the meantime, knowing to not change the ActiveBundles setting for an existing server was an important lesson.

To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+u...@googlegroups.com.