RavenDB 1.2 storage changes

162 views
Skip to first unread message

Oren Eini (Ayende Rahien)

unread,
Apr 30, 2012, 1:15:16 AM4/30/12
to ravendb
Guys,
We are going to do some changes to the way we are actually storing data on the disk.
In particular, we are moving things so we would have less reliance on system culture settings (more freedom to move things around), increased document key size, etc.

After looking at what we want, I don't think we can do this sort of update in place, and it would means that upgrading from 1.0 to 1.2 would be an import / export operation, and now an in place upgrade like we had for 1.0

Oren Eini (Ayende Rahien)

unread,
Apr 30, 2012, 1:43:42 AM4/30/12
to ravendb
Typo:

After looking at what we want, I don't think we can do this sort of update in place, and it would means that upgrading from 1.0 to 1.2 would be an import / export operation, and not an in place upgrade like we had for 1.0

Justin A

unread,
Apr 30, 2012, 3:16:16 AM4/30/12
to rav...@googlegroups.com
NP from me. (But i don't have any live systems running).

Could we get some preliminary timings (with the standard disclaimers of course .. ie. on my crappy laptop, etc..) for the process, like using the music database u downloaded?

Just so we can all plan on some downtime and have some initial rough guestimates.

(of course, people will practice the procedure, before .. which will give them accurate timings..) 

just curious.

Wayne Douglas

unread,
Apr 30, 2012, 3:31:54 AM4/30/12
to rav...@googlegroups.com

Wouldn't that be too hardware dependant to be of any use?

Justin A

unread,
Apr 30, 2012, 7:32:12 AM4/30/12
to rav...@googlegroups.com
IMO, nope. Ayende gave us some stats when he improved the Indexes a few weeks back. Disclaimers and all.

It wasn't so much the numbers then, it was more a percentage.

at least now we could get an idea that on a XXX machine, export took 1 hour, import 1 1/2 hours or whatever. and then related that to our own hardware: Oh! my hardware is just a wee bit more modern ... so lets say it will probably be a wee bit better but not too much. So now i know that if it takes more than 30 mins .. don't freak out.

devm...@hotmail.com

unread,
Apr 30, 2012, 7:54:35 AM4/30/12
to rav...@googlegroups.com
What Ever makes RavenDB better, is a welcome change and thank you in advanced for it, 

i think best solution for migration is to set a temporary new IIS RavenDB on different Port, then use Export/Import to work things out then just turn off the old Raven Server and things will work smooth right ?

Nic Wise

unread,
Apr 30, 2012, 8:22:06 AM4/30/12
to rav...@googlegroups.com
Changing the backup (or smuggler) to allow it to backup to another
raven instance would be useful in this case...

Actually, it'd be useful in a lot of cases, I suspect :)

Or maybe replication would work for this? Replicate to the new one,
wait for it to finish, turn off the old one, use the new one?
--
Nic Wise
t.  +44 7788 592 806 | @fastchicken | http://www.linkedin.com/in/nicwise
b. http://www.fastchicken.co.nz/

Earnest: Self-employed? Track your business expenses and income.
http://earnestapp.com
Nearest Bus: find when the next bus is coming to your stop. http://goo.gl/Vcz1p
mobileAgent (for FreeAgent): get your accounts in your pocket.
http://goo.gl/IuBU
Trip Wallet: Keep track of your budget on the go: http://goo.gl/ePhKa
London Bike App: Find the nearest Boris Bike, and get riding! http://goo.gl/Icp2

Oren Eini (Ayende Rahien)

unread,
Apr 30, 2012, 8:34:28 AM4/30/12
to rav...@googlegroups.com
It takes ~18 minutes to export the 3.1 milliion docs.
And about 30 minutes to import it, figures from my memory.

Oren Eini (Ayende Rahien)

unread,
Apr 30, 2012, 8:34:46 AM4/30/12
to rav...@googlegroups.com
Not sure that I am following?

Oren Eini (Ayende Rahien)

unread,
Apr 30, 2012, 8:35:38 AM4/30/12
to rav...@googlegroups.com
Yes, that is the recommended scenario for zero downtime scenarios.

Tobi

unread,
May 1, 2012, 3:08:12 AM5/1/12
to rav...@googlegroups.com
On 30.04.2012 07:15, Oren Eini (Ayende Rahien) wrote:

> After looking at what we want, I don't think we can do this sort of update
> in place, and it would means that upgrading from 1.0 to 1.2 would be an
> import / export operation, and now an in place upgrade like we had for 1.0

This is going to be hard. An export/import can potentially take hours.
Wouldn't it be possible to at least avoid to re-index all docs or will the
index storage change as well?

Will there still be bug fixes for 1.0?

Tobias

Oren Eini (Ayende Rahien)

unread,
May 1, 2012, 3:50:07 AM5/1/12
to rav...@googlegroups.com
Yes, there are going to be fixes to 1.0 as needed for at least 18 months after the 1.2 release.

We can't avoid re-indexing, because one of the things that we are changing it the actual on index format (for things like dates, for example.

Mark

unread,
May 1, 2012, 5:16:26 AM5/1/12
to ravendb
Hi,

When is the release for 1.2 planned?

Thanks

On May 1, 8:50 am, "Oren Eini (Ayende Rahien)" <aye...@ayende.com>
wrote:

Oren Eini (Ayende Rahien)

unread,
May 1, 2012, 5:20:39 AM5/1/12
to rav...@googlegroups.com
We want it in a month or two, but I don't want to commit to a date yet

Beyers

unread,
May 1, 2012, 8:50:07 AM5/1/12
to rav...@googlegroups.com
Oren, 

Are your plans to introduce the updated pricing models with v1.2 or will that come at a later stage? 

Itamar Syn-Hershko

unread,
May 1, 2012, 11:05:37 AM5/1/12
to rav...@googlegroups.com
The new pricing model will start with v1.2
Reply all
Reply to author
Forward
0 new messages