Best unofficial Apache Server developers community
Username
Forgot password?
Sign in with Twitter account
Sign in with Facebook account
List archives
Videos
Answers

Re: Issue 167 in redis: Dissapointing responsiveness of Redis when using append only file mode

Re: Issue 164 in redis: ZMOVE, moving between sorted sets
(20 lines)		 Re: Issue 168 in redis: Feature Request] redis-cli needs a auth-option
(14 lines)
Aug 24, 2010
Redis
Redis
 
Comment #2 on issue 167 by antirez: Dissapointing responsiveness of Redis 

when using append only file mode
http://code.google.com/p/redis/issues/detail?id=167

updates about this:

1) With the current Linux kernel it is not possible to flush on a
different  
thread, as write(2) will block anyway in the main thread. This sucks but I
 
don't think this is going to get fixed in little time.
2) We have now in Redis master an option so that fsync(2) is not called  
when there is a background saving/log-rewrite operation in progress. It's
a  
trick... but works.
3) All this is highly dependent on the file system used and the mount  
options.
4) "fsync none" is a trivial way to completely fix this problem but the  
drawback is that up to 30 seconds of logs can be lost.
5) fsync always is now optimized, it is still very very slow but much  
faster than before.

I'm leaving this open as it's an open problem but I don't think there are 

very good way to fix this at the moment, still with the latest changes we 

mitigated the problem enough. Currently when very low latency is required
a  
two box setup with a saving slave may be the best option.
Reply
Tags: flushkernellinux
Similar Threads
Issue 296 in redis: redis-cli does not handle EOF in monitor mode correctly
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 296 by bjarni.runar: redis-cli does not handle EOF in monitor  
mode correctly
http://code.google.com/p/redis/issues/detail?id=296

What steps will reproduce the problem?
1. run redis-cli in monitor mode
2. killall redis-server

What is the expected output? What do you see instead?

redis-cli should exit, as the server is no longer running. It does not,  
instead it spews infinite newlines.


What version of the product are you using? On what operating system?

redis 2.0.0rc3


Please provide any additional information below.

Patch attached, fixes the issue.

Attachments:
	redis-cli-newlines.patch  798 bytes
Re: Issue 132 in redis: Comment at the top of utils/redis-copy.rb applies to redis-sha1.rb
Updates:
	Status: Done

Comment #1 on issue 132 by antirez: Comment at the top of  
utils/redis-copy.rb applies to redis-sha1.rb
http://code.google.com/p/redis/issues/detail?id=132

done, thanks
Issue 300 in redis: redis-check-dump shows an overflowed value with huge .rdb.
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 300 by hatemogi: redis-check-dump shows an overflowed value with
 
huge .rdb.
http://code.google.com/p/redis/issues/detail?id=300

What steps will reproduce the problem?
1. make a huge dump.rdb file.
2. run redis-check-dump with that file.
3. I see an overflowed value in the result.

What is the expected output? What do you see instead?

I see below

$ ls -la data/dump.rdb
-rw-rw-r--  1 dante dante 11853271020 Aug  5 15:24 data/dump.rdb
$ ./redis-check-dump data/dump.rdb
==== Processed 9971202 valid opcodes (in -1031630877 bytes)
Re: Issue 106 in redis: Incorrect parsing of redis.conf save parameters
Updates:
	Status: Accepted

Comment #1 on issue 106 by antirez: Incorrect parsing of redis.conf save  
parameters
http://code.google.com/p/redis/issues/detail?id=106

yep not cool at all, accepted. I've some plan to rewrite most of the  
configuration file parsers and for sure sanity checks including parameters
 
types and limits will be supported as well.
Re: Issue 97 in redis: Ubuntu 9.10 /etc/init.d/redis-server [stop|restart] does not force a sync to 
Updates:
	Status: Verified

Comment #4 on issue 97 by antirez: Ubuntu 9.10 /etc/init.d/redis-server  
[stop|restart] does not force a sync to disk
http://code.google.com/p/redis/issues/detail?id=97

this is now fixed (as Chris suggested)
Re: Issue 137 in redis: redis.php: rpop and lpop method should not have $value parameter
Updates:
	Status: WontFix

Comment #1 on issue 137 by antirez: redis.php: rpop and lpop method should
 
not have $value parameter
http://code.google.com/p/redis/issues/detail?id=137

please use Predis or Rediska PHP Redis libs! The old PHP lib is
deprecated.

Cheers,
Salvatore
Re: Issue 162 in redis: need a redis-cli command to close all connection
Comment #1 on issue 162 by antirez: need a redis-cli command to close all 

connection
http://code.google.com/p/redis/issues/detail?id=162

can't find a valid use case for this ;) Care to explain?

Cheers,
Salvatore
Re: Issue 111 in redis: read-only redis.conf option
Comment #1 on issue 111 by antirez: [FEATURE REQUEST] read-only redis.conf
 
option
http://code.google.com/p/redis/issues/detail?id=111

not a bad idea indeed... I'll think a bit more about it but sounds cool
Re: Issue 147 in redis: redis-cli should be able to connect to slave
Updates:
	Status: Invalid

Comment #4 on issue 147 by antirez: redis-cli should be able to connect to
 
slave
http://code.google.com/p/redis/issues/detail?id=147

(No comment was entered for this change.)
Issue 302 in redis: redis-cli cause a seg fault on netbsd X64
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 302 by charpentier.claude: redis-cli cause  a seg fault on
netbsd  
X64
http://code.google.com/p/redis/issues/detail?id=302

What steps will reproduce the problem?
1. launch redis-cli compiled on NetBSD X64

What is the expected output? What do you see instead?
see attached files


What version of the product are you using? On what operating system?
I use redis 1.2.6 on NetBSD amd64 but works fine on i386

zat


Attachments:
	gistd2bd3b523a52d441132a-22c8b36a5c747b3f08eef4b2767193b9faa559bc.tar.gz 
 
849 bytes
Re: Issue 128 in redis: Redis doesn't save on SIGTERM
Updates:
	Status: Verified

Comment #5 on issue 128 by antirez: Redis doesn't save on SIGTERM
http://code.google.com/p/redis/issues/detail?id=128

fixed in Redis master
Re: Issue 145 in redis: redis-1.2.0 Makefile fixes
Updates:
	Status: WontFix

Comment #2 on issue 145 by antirez: [patch] redis-1.2.0 Makefile fixes
http://code.google.com/p/redis/issues/detail?id=145

(No comment was entered for this change.)
Re: Issue 276 in redis: redis as embedded database
Comment #1 on issue 276 by mvolmaro: [Feature Request] redis as embedded  
database
http://code.google.com/p/redis/issues/detail?id=276

Indeed. Having Redis available as embedded DB opens up a lot of  
possibilities that are not possible with the server only version.
Issue 309 in redis: would redis support plugins?
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 309 by everw### @gmail.com: would redis support plugins?
http://code.google.com/p/redis/issues/detail?id=309

Redis is an outstanding storage solution. High performance, atomic  
operations, data structures, replication, etc.

But it does not support transactions very well. The MULTI/EXEC mechanism
is  
too simple. It cannot handle complex situations. Data structures support
is  
somewhat limited.

I think, supporting complex operations and data structures with plugins
may  
be a better way, like stored procedures in RDB.

Actually, I'm working on this feature now.

Any comments?
Re: Issue 299 in redis: Redis 2.0.1 RC 4 crashing
Comment #1 on issue 299 by kickasspixels: Redis 2.0.1 RC 4 crashing
http://code.google.com/p/redis/issues/detail?id=299

Process:         redis-server [65443]
Path:            /usr/local/redis/redis-server
Identifier:      redis-server
Version:         ??? (???)
Code Type:       X86 (Native)
Parent Process:  launchd [1]

Date/Time:       2010-08-04 17:54:22.572 -0400
OS Version:      Mac OS X Server 10.5.8 (9L34)
Report Version:  6
Anonymous UUID:  0B57F7D5-CA9F-418D-B840-AD60267E68E1

Exception Type:  EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Crashed Thread:  0

Thread 0 Crashed:
0   libSystem.B.dylib                   0x9426ce42 __kill + 10
1   libSystem.B.dylib                   0x942df23a raise + 26
2   libSystem.B.dylib                   0x942eb679 abort + 73
3   redis-server                        0x0001f02f zmalloc_oom + 63
4   redis-server                        0x0001f0c6 zmalloc + 150
5   redis-server                        0x0001e646 sdsnewlen + 22
6   redis-server                        0x0000fdba  
rdbGenericLoadStringObject + 202
7   redis-server                        0x0000fe49  
rdbLoadEncodedStringObject + 25
8   redis-server                        0x00010195 rdbLoadObject + 837
9   redis-server                        0x0001b1ec rdbLoad + 348
10  redis-server                        0x0001c78e main + 334
11  redis-server                        0x00001ca6 start + 54

Thread 0 crashed with X86 Thread State (32-bit):
   eax: 0x00000000  ebx: 0x942eb639  ecx: 0xbffff5cc  edx: 0x9426ce42
   edi: 0x00000030  esi: 0xa05025b8  ebp: 0xbffff5e8  esp: 0xbffff5cc
    ss: 0x0000001f  efl: 0x00000282  eip: 0x9426ce42   cs: 0x00000007
    ds: 0x0000001f   es: 0x0000001f   fs: 0x00000000   gs: 0x00000037
   cr2: 0x03488000

Binary Images:
     0x1000 -    0x27fff +redis-server ??? (???)  
<e597b8f24768a19a6f450eeed5650e8c> /usr/local/redis/redis-server
0x8fe00000 - 0x8fe2db43  dyld 97.1 (???)
<458eed38a009e5658a79579e7bc26603>  
/usr/lib/dyld
0x91175000 - 0x9117cfe9  libgcc_s.1.dylib ??? (???)  
<f53c808e87d1184c0f9df63aef53ce0b> /usr/lib/libgcc_s.1.dylib
0x941fe000 - 0x94365ff3  libSystem.B.dylib ??? (???)  
<c8f52e158bf540cc000146ca8a705958> /usr/lib/libSystem.B.dylib
0x9746f000 - 0x97473fff  libmathCommon.A.dylib ??? (???)  
/usr/lib/system/libmathCommon.A.dylib
0xffff0000 - 0xffff1780  libSystem.B.dylib ??? (???)  
/usr/lib/libSystem.B.dylib
Re: Issue 152 in redis: Save file not is checked for validity/write-ability on start up
Updates:
	Status: WontFix

Comment #1 on issue 152 by antirez: Save file not is checked for  
validity/write-ability on start up
http://code.google.com/p/redis/issues/detail?id=152

IMHO to check for this condition at runtime, like it happens already, is  
the way to go as anyway the permissions may change (or the disk may get  
full) while running, so it is not a proof that everything will work  
forever...

Also with the CONFIG command will be even possible to change such a  
location at runtime in the future.

Cheers,
Salvatore
Issue 298 in redis: redis-cli "Error setting DB num" when authentication (-a) specified
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 298 by rocklob: redis-cli "Error setting DB num" when  
authentication (-a) specified
http://code.google.com/p/redis/issues/detail?id=298

What steps will reproduce the problem?

1. Configure redis with these options:
      requirepass password
      databases 16
2. Start redis-server
3. Attempt to use redis-cli while specifying a database number other than 

0.  Example:
      redis-cli -n 1 -a password info

What is the expected output? What do you see instead?

      Output of info command should be shown.  Instead, you will see:
           Error setting DB num
           Error setting DB num

What version of the product are you using? On what operating system?

      Redis 1.2.6 on 64-bit RedHat EL 5.

Please provide any additional information below.

      In redis-cli.c, cliSendCommand() tries to call selectDb before it  
issues the AUTH command.
Re: Issue 110 in redis: Tries
Comment #7 on issue 110 by antirez: [Feature Request] Tries
http://code.google.com/p/redis/issues/detail?id=110

Hello Dan,

sorted sets should be able to fix this issues, or if they are not, should 

be extended to fix this issues.

I'm currently not closing this issue to reason on it better for some time,
 
btw what you can already use is converting the first N digits of the words
 
you are storing into a score, with sorted sets, and then get ranges of  
words by score.

Cheers,
Salvatore
Re: Issue 71 in redis: SSL Support
Comment #11 on issue 71 by kkirancse: [Feature Request] SSL Support
http://code.google.com/p/redis/issues/detail?id=71

Hi guys,

i couldn't use redis in my company just because there is no SSL  
communication support. I feel it adds value.
Re: Issue 101 in redis: Key info
Updates:
	Status: WontFix

Comment #2 on issue 101 by antirez: [Feature Request] Key info
http://code.google.com/p/redis/issues/detail?id=101

(No comment was entered for this change.)