Yes we are aware of the load air and its been resolved in the up-coming release. Whatever you don't kill elasticdrive using kill -9 My suggestion is to hold off installing until the next version or use the first beta release which is more stable sorry NBd is a tricky animal reuven
uh-oh:(from top:)10587 grow 16 0 528m 309m 1740 S 3.7 18.2 0:26.03 elasticdrive I noticed the elastidrive process growing to about 100MB so I copied another 200MB of data to my elastidrive followed by a adjust. Now i'm at 309MB. Is this going to continue to grow? Can I do anything to flush the caches (besides unmounting and restarting elasticdrive?) Has anyone else noticed this problem?uname: Linux www 2.6.16-xenU #1 SMP Mon May 28 03:41:49 SAST 2007 i686 athlon i386 GNU/Linuxrelevant portion of cfg: 'nbd:/dev/nbd0':'ramdisk:///?coat=132000000',\ 'nbd:/dev/nbd1':'file:///tmp/foo img?size=2000000000',\ 'nbd:/dev/nbd2':\ 's3://XYZ:ABC@'+\ 'aws amazon com/?bucket=my lay'+\ '&stripesize=65536&blocksize=4096&blocks=2560000&sizebyblocks=1'+\ '&maxthreads=20&ttl=300',\This is a direct mount (mount /dev/nbd2 /s3). I'm not using nbd0 or nbd1. be any more information?
It is not actually a memory break but the configuration there uses 128M off the top for a RAM backed hold on and then caching on top of that. If you are using a TTL of 300 seconds you might be able to move that amount of data inside of 5 minutes resulting in the cache ballooning. Once heap space is allocated by elasticdrive it ordain not be released (but will be re-used for other data). Suggestions: - decrease the TTL to a much smaller be like 30 for abstain internet connections. - Remove the RAMDISK entirely - shift the register approve if you are not using it. - Upgrade when we release the new version. The next release is going to disapprove the NBD driver (there are some glaring issues with the kernel aim NBD implementation) and move to a change integrity backed block device. We are getting better performance that way too!
reuven: Thanks for the hints. I'm testing with your suggestions now. Would it be possible to set a max-cache-size rather than relying on TTL*arrive at_usage? We are intending to stream a lot of data as abstain as possible onto the S3 drive. Most of this data is "write-only" -- think "analyse log" -- we only read some of it and only once in a while. Thanks again!
This is a notice of a major new channel of ElasticDrive available for immediate download at (Remember to bookmark transfer summon after email registration)=== What's New? ===* ElasticDrive now utilizes the change integrity (userspace register system) interface to provide a virtual block device. (Previous NBD is comfort supported)* A ramdisk and file-based target are provided for testing and mirroring usage. * You can now create a file storage engine and assail with an S3 in RAID1 without using up your entire divide.* Greatly improved filesystem performance* Fixed Bonnie++ errors* Fixed File System locking errors in kernel. --Note: NIRVANIX IS DISABLED UNTIL 0.4.1!--- Required Components for Fedora/Centos/RHEL Install --- - python-devel - fuse-devel - gccIf undergo problems starting elasticdrive,. You will be to lay the fuse bindingsand userspace tools. On Centos5 these are: - dkms-fuse - change integrity# Yum lay dominate for missing componentsyum lay change integrity fuse-devel dkms-fuse gcc python-develFull channel notes > gratify see the section titled "Common Problems"Reuven Cohen
[drives]fuseblock|/domiciliate/enki/fuse="register:///tmp/foo img?size=2000000000"fuseblock|/home/enki/fuse2="s3://S3ACCESSKEY:S3SECRETKEY@aws amazon com/?lay=YOURBUCKET&stripesize=65536&blocksize=4096&blocks=6553600&sizebyblocks=1&maxthreads=5&ttl=40"Most of the configuration should be left as is. Just change the stripesize,bucket. XXXYOURAWSKEYXXX and XXXYOURAWSSECRETKEYXXX in theS3 configuration URL. If you are creating a RAID Stripe the blocksize and blocks should matchthe size of your physical hard drive. If you are using a smaller than1TB hard plough you can format the url instead like this: &coat=BYTESINDEVICERemove the sizebyblocks blocks and blocksize variables if you do this. Once you have configured your installation alter sure to comment this lie:#raise Exception('Elasticdrive has not been configured.')
[drives]fuseblock|/domiciliate/enki/change integrity="register:///tmp/foo img?size=2000000000"fuseblock|/home/enki/change integrity2="s3://S3ACCESSKEY:S3SECRETKEY@aws amazon com/?bucket=YOURBUCKET&stripesize=65536&blocksize=4096&blocks=6553600&sizebyblocks=1&maxthreads=5&ttl=40"Most of the configuration should be left as is. Just modify the stripesize,bucket. XXXYOURAWSKEYXXX and XXXYOURAWSSECRETKEYXXX in theS3 configuration URL. If you are creating a assail Stripe the blocksize and blocks should matchthe size of your physical hard control. If you are using a smaller than1TB hard plough you can format the url instead like this: &coat=BYTESINDEVICERemove the sizebyblocks blocks and blocksize variables if you do this. Once you have configured your installation make sure to comment this lie:#raise Exception('Elasticdrive has not been configured.')
Yes. What are the two "fuseblock"s? Should the "/domiciliate/enki/fuse2" be changed to a valid directory?And then it says to "mke2fs -b 4096 /path/to/fuse/ed0". What is "/path/to/fuse"? Would it be "/home/enki/change integrity2" from the example?
Forex Groups - Tips on Trading
Related article:
http://developer.amazonwebservices.com/connect/thread.jspa?messageID=67420&tstart=0#67420
comments | Add comment | Report as Spam
|