Issues - kr/beanstalkd

kr / beanstalkd

226

Description:

Beanstalk is a simple, fast work queue.

Sort by: Priority | Votes | Last Updated

Loading…

21.

0 votes

Does not compile on FreeBSD 7 amd64
2 comments Created about 1 month ago by pkieltyka

Title

Body
reeler% git clone git://github.com/kr/beanstalkd.git reeler% cd beanstalkd reeler% ./autogen.sh configure.in:10: installing `./install-sh' configure.in:10: installing `./missing' reeler% ./configure checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... ./install-sh -c -d checking for gawk... no checking for mawk... no checking for nawk... nawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for style of include used by make... GNU checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... none checking for supported compiler flags... -Wall -Werror checking for gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking dependency style of gcc... (cached) none checking for a BSD-compatible install... /usr/bin/install -c checking if compiler supports -R... yes checking libevent install prefix... /usr/local checking for posix_fallocate... no checking for fdatasync... no checking for bind in -lsocket... no checking for inet_aton in -lnsl... no checking for event_get_version in -levent... yes checking for event_reinit in -levent... yes checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for uint16_t... yes configure: creating ./config.status config.status: creating Makefile config.status: creating beanstalkd.spec config.status: creating config.h config.status: executing depfiles commands reeler% make make all-am gcc -DHAVE_CONFIG_H -I. -g -O2 -Wall -Werror -I/usr/local/include -c -o beanstalkd.o beanstalkd.c gcc -DHAVE_CONFIG_H -I. -g -O2 -Wall -Werror -I/usr/local/include -c -o binlog.o binlog.c gcc -DHAVE_CONFIG_H -I. -g -O2 -Wall -Werror -I/usr/local/include -c -o conn.o conn.c gcc -DHAVE_CONFIG_H -I. -g -O2 -Wall -Werror -I/usr/local/include -c -o job.o job.c gcc -DHAVE_CONFIG_H -I. -g -O2 -Wall -Werror -I/usr/local/include -c -o ms.o ms.c gcc -DHAVE_CONFIG_H -I. -g -O2 -Wall -Werror -I/usr/local/include -c -o net.o net.c In file included from net.h:22, from net.c:22: /usr/include/netinet/tcp.h:40: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'tcp_seq' /usr/include/netinet/tcp.h:50: error: expected specifier-qualifier-list before 'u_short' /usr/include/netinet/tcp.h:175: error: expected specifier-qualifier-list before 'u_int8_t' *** Error code 1 Stop in /usr/home/peter/beanstalkd. *** Error code 1 Stop in /usr/home/peter/beanstalkd. reeler%
or cancel
reeler% git clone git://github.com/kr/beanstalkd.git
reeler% cd beanstalkd
reeler% ./autogen.sh
configure.in:10: installing ./install-sh'<br/> configure.in:10: installing./missing'
reeler% ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... ./install-sh -c -d
checking for gawk... no
checking for mawk... no
checking for nawk... nawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... none
checking for supported compiler flags... -Wall -Werror
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking dependency style of gcc... (cached) none
checking for a BSD-compatible install... /usr/bin/install -c
checking if compiler supports -R... yes
checking libevent install prefix... /usr/local
checking for posix_fallocate... no
checking for fdatasync... no
checking for bind in -lsocket... no
checking for inet_aton in -lnsl... no
checking for event_get_version in -levent... yes
checking for event_reinit in -levent... yes
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for uint16_t... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating beanstalkd.spec
config.status: creating config.h
config.status: executing depfiles commands
reeler% make
make all-am
gcc -DHAVE_CONFIG_H -I. -g -O2 -Wall -Werror -I/usr/local/include -c -o beanstalkd.o beanstalkd.c
gcc -DHAVE_CONFIG_H -I. -g -O2 -Wall -Werror -I/usr/local/include -c -o binlog.o binlog.c
gcc -DHAVE_CONFIG_H -I. -g -O2 -Wall -Werror -I/usr/local/include -c -o conn.o conn.c
gcc -DHAVE_CONFIG_H -I. -g -O2 -Wall -Werror -I/usr/local/include -c -o job.o job.c
gcc -DHAVE_CONFIG_H -I. -g -O2 -Wall -Werror -I/usr/local/include -c -o ms.o ms.c
gcc -DHAVE_CONFIG_H -I. -g -O2 -Wall -Werror -I/usr/local/include -c -o net.o net.c
In file included from net.h:22,
```
             from net.c:22:
```
/usr/include/netinet/tcp.h:40: error: expected '=', ',', ';', 'asm' or 'attribute' before 'tcp_seq' /usr/include/netinet/tcp.h:50: error: expected specifier-qualifier-list before 'u_short' /usr/include/netinet/tcp.h:175: error: expected specifier-qualifier-list before 'u_int8_t' *** Error code 1

Stop in /usr/home/peter/beanstalkd.
*** Error code 1

Stop in /usr/home/peter/beanstalkd.
reeler%
Comments

pkieltyka Sat Oct 10 22:28:32 -0700 2009 | link

I found a fix for this. Simply put #include <sys/types.h> under #include <sys/socket.h> in the beanstalkd source file: net.h

Comment
I found a fix for this. Simply put #include <sys/types.h> under #include <sys/socket.h> in the beanstalkd source file: net.h
or cancel

kr Sun Oct 11 17:53:55 -0700 2009 | link

Fix build on FreeBSD.

Thanks to Peter Kieltyka http://github.com/pkieltyka for the fix.
Closed by 24aa767.

Comment
Fix build on FreeBSD. Thanks to Peter Kieltyka http://github.com/pkieltyka for the fix. Closed by 24aa767cf3eb0c8fb21620c621b5b4104649f41e.
or cancel

Parsed with GitHub Flavored Markdown
19.

1 vote

Build error on Snow Leopard: fdatasync
9 comments Created about 1 month ago by topfunky

Title

Body
I get a build error on Mac OS X Snow Leopard where it says it can't find fdatasync. Output of ./configure: https://gist.github.com/0290aa815842b888eed4 Error upon running make: cc1: warnings being treated as errors binlog.c: In function ‘binlog_write_job’: binlog.c:491: warning: implicit declaration of function ‘fdatasync’ make[1]: *** [binlog.o] Error 1 make: *** [all] Error 2 Using libevent-1.4.12-stable ("make verify" passed).
or cancel
I get a build error on Mac OS X Snow Leopard where it says it can't find fdatasync.

Output of ./configure:
```
https://gist.github.com/0290aa815842b888eed4
```
Error upon running make:
```
cc1: warnings being treated as errors
binlog.c: In function ‘binlog_write_job’:
binlog.c:491: warning: implicit declaration of function ‘fdatasync’ 
make[1]: *** [binlog.o] Error 1
make: *** [all] Error 2
```
Using libevent-1.4.12-stable ("make verify" passed).
Comments
topfunky Sat Oct 03 18:58:22 -0700 2009 | link

To clarify: This was while building beanstalkd-1.4 stable release from http://kr.github.com/beanstalkd/download.html

Comment
To clarify: This was while building beanstalkd-1.4 stable release from http://kr.github.com/beanstalkd/download.html
or cancel
mloughran Mon Oct 05 05:32:14 -0700 2009 | link
I worked around this issue by removing the following from config.h after running ./configure, before running make.

/* Define to 1 if you have the `fdatasync' function. */ #define HAVE_FDATASYNC 0

Hopefully the real solution is clear to someone :)
Comment
I worked around this issue by removing the following from config.h after running ./configure, before running make. /* Define to 1 if you have the `fdatasync' function. */ #define HAVE_FDATASYNC 0 Hopefully the real solution is clear to someone :)
or cancel
kr Wed Oct 07 00:42:08 -0700 2009 | link

Does snow leopard have a man page for fdatasync? Can anyone post or send me the #include lines from the man page?

Comment
Does snow leopard have a man page for fdatasync? Can anyone post or send me the #include lines from the man page?
or cancel

topfunky Wed Oct 07 18:24:46 -0700 2009 | link

I get nothing for "man fdatasync" and a Google search appears to say that it's not available on any flavor of Mac OS X.

I couldn't find it in /usr/include/unistd.h or /usr/include/sys/unistd.h

Comment
I get nothing for "man fdatasync" and a Google search appears to say that it's not available on any flavor of Mac OS X. I couldn't find it in /usr/include/unistd.h or /usr/include/sys/unistd.h
or cancel
kr Wed Oct 07 20:40:18 -0700 2009 | link
I'm confused by the line in your configure transcript that says:

checking for fdatasync... yes

That indicates that such a function is defined somewhere in your system's header files. I think a vanilla installation of 10.6 (and for sure 10.5) doesn't have fdatasync anywhere.

The build is also getting confused; configure thinks fdatasync is defined somewhere, but then gcc doesn't have a prototype for it, hence the error message.
Comment
I'm confused by the line in your configure transcript that says: checking for fdatasync... yes That indicates that such a function is defined somewhere in your system's header files. I think a vanilla installation of 10.6 (and for sure 10.5) doesn't have fdatasync anywhere. The build is also getting confused; configure thinks fdatasync is defined somewhere, but then gcc doesn't have a prototype for it, hence the error message.
or cancel
robotadam Thu Oct 08 12:58:49 -0700 2009 | link
I can confirm this as well. The only reference to fdatasync in /usr/include is in:

include/sys/syscall.h 227:#define SYS_fdatasync 187

On my system, setting HAVE_FDATASYNC to 0 in config.h still results in a failed build:

gcc -DHAVE_CONFIG_H -I. -g -O2 -Wall -Werror -I/sw/local/include -c -o beanstalkd.o beanstalkd.c gcc -DHAVE_CONFIG_H -I. -g -O2 -Wall -Werror -I/sw/local/include -c -o binlog.o binlog.c cc1: warnings being treated as errors binlog.c: In function ‘binlog_write_job’: binlog.c:491: warning: implicit declaration of function ‘fdatasync’ make[1]: *** [binlog.o] Error 1 make: *** [all] Error 2

Edit: Of course - removing HAVE_FDATASYNC works. Thanks, mattyoho -- serves me for not doing anything in C for a long while.
Comment
I can confirm this as well. The only reference to fdatasync in /usr/include is in: include/sys/syscall.h 227:#define SYS_fdatasync 187 On my system, setting HAVE_FDATASYNC to 0 in config.h still results in a failed build: gcc -DHAVE_CONFIG_H -I. -g -O2 -Wall -Werror -I/sw/local/include -c -o beanstalkd.o beanstalkd.c gcc -DHAVE_CONFIG_H -I. -g -O2 -Wall -Werror -I/sw/local/include -c -o binlog.o binlog.c cc1: warnings being treated as errors binlog.c: In function ‘binlog_write_job’: binlog.c:491: warning: implicit declaration of function ‘fdatasync’ make[1]: *** [binlog.o] Error 1 make: *** [all] Error 2 *Edit*: Of course - removing HAVE_FDATASYNC works. Thanks, mattyoho -- serves me for not doing anything in C for a long while.
or cancel
mattyoho Thu Oct 08 14:21:24 -0700 2009 | link

robotadam: "On my system, setting HAVE_FDATASYNC to 0 in config.h still results in a failed build:"

This was true for me as well. I commented the def out instead, cleaned and ran make again and was then able to install successfully.

Comment
robotadam: "On my system, setting HAVE_FDATASYNC to 0 in config.h still results in a failed build:" This was true for me as well. I commented the def out instead, cleaned and ran make again and was then able to install successfully.
or cancel

copiousfreetime Sun Oct 11 14:56:20 -0700 2009 | link

autoconf does not check this existence correctly. I believe I have fixed this.

copiousfreetime/beanstalkd@68038c5

Comment
autoconf does not check this existence correctly. I believe I have fixed this. copiousfreetime/beanstalkd@68038c5ddcb92d789dce2f915244d4f2bbe8f016
or cancel

kr Sun Oct 11 17:51:07 -0700 2009 | link

Thank you! I just pushed this as 68038c5.

Comment
Thank you! I just pushed this as 68038c5.
or cancel

Parsed with GitHub Flavored Markdown
17.

0 votes

does not handle SIGTERM
1 comment Created 3 months ago by fnoeding

Title

Body
beanstalkd only handles SIGINT and does then a clean shutdown. The following patch adds this behavior for SIGTERM. Tested against version 1.3 Patch: --- beanstalkd.c.orig 2009-08-15 13:48:46.000000000 +0200 +++ beanstalkd.c 2009-08-15 13:49:11.000000000 +0200 @@ -120,6 +120,10 @@ sa.sa_handler = exit_cleanly; r = sigaction(SIGINT, &sa, 0); if (r == -1) twarn("sigaction(SIGINT)"), exit(111); + + sa.sa_handler = exit_cleanly; + r = sigaction(SIGTERM, &sa, 0); + if (r == -1) twarn("sigaction(SIGTERM)"), exit(111); } /* This is a workaround for a mystifying workaround in libevent's epoll
or cancel
beanstalkd only handles SIGINT and does then a clean shutdown. The following patch adds this behavior for SIGTERM. Tested against version 1.3

Patch:
```
--- beanstalkd.c.orig   2009-08-15 13:48:46.000000000 +0200
+++ beanstalkd.c        2009-08-15 13:49:11.000000000 +0200
@@ -120,6 +120,10 @@
     sa.sa_handler = exit_cleanly;
     r = sigaction(SIGINT, &sa, 0);
     if (r == -1) twarn("sigaction(SIGINT)"), exit(111);
+
+    sa.sa_handler = exit_cleanly;
+    r = sigaction(SIGTERM, &sa, 0);
+    if (r == -1) twarn("sigaction(SIGTERM)"), exit(111);
 }

 /* This is a workaround for a mystifying workaround in libevent's epoll
```
Comments

kr Wed Sep 30 19:06:45 -0700 2009 | link

Handle SIGTERM.

Thanks to http://github.com/fnoeding for the patch.

Closed by b6685fe.

Comment
Handle SIGTERM. Thanks to http://github.com/fnoeding for the patch. Closed by b6685fe3f36972f49e15381ddbc2f06345b43dcb.
or cancel

Parsed with GitHub Flavored Markdown
16.

0 votes

Add appropriate fsync calls.
1 comment Created 3 months ago by kr

Title

Body
Should have optional throttling. There should be three modes: always fsync (for best reliability), fsync at most once every N seconds, or never fsync (best performance). Could be controlled by two options: "-s 0" for always fsync, "-s N" for sync at most once every N seconds, and "-S" for never fsync.
or cancel

Should have optional throttling. There should be three modes: always fsync (for best reliability), fsync at most once every N seconds, or never fsync (best performance).

Could be controlled by two options: "-s 0" for always fsync, "-s N" for sync at most once every N seconds, and "-S" for never fsync.

Comments

kr Wed Sep 30 19:00:07 -0700 2009 | link

Add fsync options.

Closed by f54b3d9.

Comment
Add fsync options. Closed by f54b3d91dd143a5e0636879db58061befec273e0.
or cancel

Parsed with GitHub Flavored Markdown
14.

0 votes

Allow beanstalkd to reserve arbitrary amounts of binlog space
1 comment Created 3 months ago by kr

Title

Body
Currently it can only create one extra binlog file on disk. After that it will deny operations that want to reserve space. (Search for "overextended" in binlog.c.) There just needs to be a linked list of future binlog files; currently there is a pointer to (up to) one future file. In practice this only happens when the queue holds more than about 10 MB of jobs.
or cancel

Currently it can only create one extra binlog file on disk. After that it will deny operations that want to reserve space. (Search for "overextended" in binlog.c.) There just needs to be a linked list of future binlog files; currently there is a pointer to (up to) one future file. In practice this only happens when the queue holds more than about 10 MB of jobs.

Comments

kr Wed Sep 30 17:55:27 -0700 2009 | link

Fixed in a866a59.

Comment
Fixed in a866a593497efc3b476343726f9903bd27a63e5b.
or cancel

Parsed with GitHub Flavored Markdown
12.

0 votes

Peek commands leak memory
2 comments Created 4 months ago by goosmurf

Title

Body
Currently the peek commands do a job_copy() before calling reply_job() presumably to avoid a race between the job being sent back to the client, and it being DELETEd by another client. reset_conn() should free the job copy however it currently requires the job.id to be 0 before it will call job_free(). This works fine for the h_conn_timeout() case as in http://github.com/kr/beanstalkd/commit/d77814816f54c48b7bcc85c36bb681fd277d3e65 but it overloads the meaning of job.id which is an essential part of the peek responses. The result is that we can't set a copied job.id to 0 for peek responses which means it won't get freed by reset_conn(), leading to a fast memory leak if any of the peek commands are used. I'll submit a patch which adds a new job state to mark a job as copied (JOB_STATE_COPY) but I'm not sure if its the best way to solve this. http://gist.github.com/139279 will hammer peek-buried sufficiently that you'll see the beanstalkd process size grow very rapidly.
or cancel

Currently the peek commands do a job_copy() before calling reply_job() presumably to avoid a race between the job being sent back to the client, and it being DELETEd by another client.

reset_conn() should free the job copy however it currently requires the job.id to be 0 before it will call job_free(). This works fine for the h_conn_timeout() case as in http://github.com/kr/beanstalkd/commit/d77814816f54c48b7bcc85c36bb681fd277d3e65 but it overloads the meaning of job.id which is an essential part of the peek responses.

The result is that we can't set a copied job.id to 0 for peek responses which means it won't get freed by reset_conn(), leading to a fast memory leak if any of the peek commands are used.

I'll submit a patch which adds a new job state to mark a job as copied (JOB_STATE_COPY) but I'm not sure if its the best way to solve this.

http://gist.github.com/139279 will hammer peek-buried sufficiently that you'll see the beanstalkd process size grow very rapidly.

Comments

kr Tue Jul 14 23:31:19 -0700 2009 | link

Thanks for finding this and for the patch. I'm reviewing it now.

Comment
Thanks for finding this and for the patch. I'm reviewing it now.
or cancel

kr Tue Jul 14 23:40:54 -0700 2009 | link

I just pushed this. I edited your patch to delete c->out_job->id = 0, rather than just commenting it out, and I added commit message lines to close the issues.

Comment
I just pushed this. I edited your patch to delete c->out_job->id = 0, rather than just commenting it out, and I added commit message lines to close the issues.
or cancel

Parsed with GitHub Flavored Markdown
10.

0 votes

add a "reserves" counter
0 comments Created 5 months ago by kr

Title

Body
Currently, if a client reserves a job and then crashes, the job will be put in the ready queue with no indication that it had ever been reserved. This is not good; clients should be able to distinguish such a job from one that has never been reserved. So we should add a "reserves" counter and/or increment the "timeouts" counter in this situation and/or introduce a separate counter just for this situation. See http://groups.google.com/group/beanstalk-talk/t/951b6c35752257a4 for more info.
or cancel

Currently, if a client reserves a job and then crashes, the job will be put in the ready queue with no indication that it had ever been reserved. This is not good; clients should be able to distinguish such a job from one that has never been reserved.

So we should add a "reserves" counter and/or increment the "timeouts" counter in this situation and/or introduce a separate counter just for this situation.

See http://groups.google.com/group/beanstalk-talk/t/951b6c35752257a4 for more info.

Comments

Parsed with GitHub Flavored Markdown
9.

0 votes

mac os doesn't have posix_fallocate
2 comments Created 6 months ago by kr

Title

Body
See http://groups.google.com/group/beanstalk-talk/t/8210428dd5f2c98f for details.
or cancel

See http://groups.google.com/group/beanstalk-talk/t/8210428dd5f2c98f for details.

Comments

dtaylor Tue May 12 09:18:01 -0700 2009 | link

Also true for FreeBSD.

Comment
Also true for FreeBSD.
or cancel

kr Thu Oct 01 01:29:29 -0700 2009 | link

This has been fixed for a little while.

Comment
This has been fixed for a little while.
or cancel

Parsed with GitHub Flavored Markdown
8.

0 votes

make unit tests portable
2 comments Created 6 months ago by kr

Title

Body
One of them breaks on Mac OS.
or cancel

One of them breaks on Mac OS.

Comments

dtaylor Tue May 12 09:19:00 -0700 2009 | link

Same for FreeBSD. See http://groups.google.com/group/beanstalk-talk/msg/fe9bd915b2adb2fc

Comment
Same for FreeBSD. See http://groups.google.com/group/beanstalk-talk/msg/fe9bd915b2adb2fc
or cancel

kr Fri May 15 16:43:00 -0700 2009 | link

Ditch that symbol table hack. It's not portable.

In particular, Mac OS and probably BSD don't like it.

Closed by 5192ce5.

Comment
Ditch that symbol table hack. It's not portable. In particular, Mac OS and probably BSD don't like it. Closed by 5192ce554ba612b302052314564bd5eb2981b913.
or cancel

Parsed with GitHub Flavored Markdown
7.

0 votes

cutgen crashes on Solaris
1 comment Created 6 months ago by kr

Title

Body

or cancel

Comments

kr Fri May 15 16:42:59 -0700 2009 | link

Fix cutgen segfault on Solaris.

Closed by af441c9.

Comment
Fix cutgen segfault on Solaris. Closed by af441c93dc6058e882b8dc2ab84002ad1ec89e79.
or cancel

Parsed with GitHub Flavored Markdown
6.

0 votes

Re-enable compiler warnings and -werror
1 comment Created 6 months ago by kr

Title

Body
These accidentally got disabled in the switch to autoconf.
or cancel

These accidentally got disabled in the switch to autoconf.

Comments

kr Fri May 15 16:42:59 -0700 2009 | link

Enable more compiler warnings and -Werror.

Closed by 99d1191.

Comment
Enable more compiler warnings and -Werror. Closed by 99d11915a28389a1fb2bd9413d9f9b574b6f88ba.
or cancel

Parsed with GitHub Flavored Markdown
5.

1 vote

use high-resolution timeouts internally
1 comment Created 6 months ago by kr

Title

Body
Avoid stupid off-by-one errors at one-second granularity.
or cancel

Avoid stupid off-by-one errors at one-second granularity.

Comments

kr Wed Sep 30 22:17:29 -0700 2009 | link

Always use hi-res timers internally.

This helps us to avoid off-by-one and roundoff errors that crop up with
one-second-granularity timers. Also makes it easier in the future to
allow clients to specify hi-res time intervals.

Closed by 6e9339f.

Comment
Always use hi-res timers internally. This helps us to avoid off-by-one and roundoff errors that crop up with one-second-granularity timers. Also makes it easier in the future to allow clients to specify hi-res time intervals. Closed by 6e9339ff9c177cc37787ee252fd3cf3a04f17243.
or cancel

Parsed with GitHub Flavored Markdown
4.

0 votes

kr
x

Fix the build on Solaris
1 comment Created 6 months ago by kr

Title

Body
See http://groups.google.com/group/beanstalk-talk/t/e589c79f86f4d0ac for the bug report.
or cancel

See http://groups.google.com/group/beanstalk-talk/t/e589c79f86f4d0ac for the bug report.

Comments

kr Thu Apr 30 12:02:10 -0700 2009 | link

Fix the build on Solaris. Closed by a65ebca.

Comment
Fix the build on Solaris. Closed by a65ebcad0326d997c5bf6102887e3db54ccaf3fb.
or cancel

Parsed with GitHub Flavored Markdown
1.

0 votes

kr
x

carefully allocate disk space for binlog records
1 comment Created 6 months ago by kr

Title

Body
We want to handle a full disk with grace.
or cancel

We want to handle a full disk with grace.

Comments

kr Tue May 05 16:58:51 -0700 2009 | link

Allocate disk space more carefully. Closed by 12299e0.

Comment
Allocate disk space more carefully. Closed by 12299e05b4a0e472c97fe73073d5e2d5bcecd5a7.
or cancel

Parsed with GitHub Flavored Markdown