[jira] [Created] (COUCHDB-1462) Add Sharing / Reporting of CLI test results for further analysis
Add Sharing / Reporting of CLI test results for further analysis Key: COUCHDB-1462 URL: https://issues.apache.org/jira/browse/COUCHDB-1462 Project: CouchDB Issue Type: Improvement Components: Test Suite Affects Versions: 1.3 Reporter: Jan Lehnardt Assignee: Jan Lehnardt The browser based tests allowed to submit test results to a shared CouchDB instance, the CLI JS tests in 1.3/master don't do that yet. Also the etap tests don't do that either -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (COUCHDB-1445) CouchDB deletes .view files if it can't open them, even if the error is emfile.
CouchDB deletes .view files if it can't open them, even if the error is
emfile.
-
Key: COUCHDB-1445
URL: https://issues.apache.org/jira/browse/COUCHDB-1445
Project: CouchDB
Issue Type: Bug
Components: JavaScript View Server
Affects Versions: 1.2
Reporter: Jan Lehnardt
Fix For: 1.2
Via Stefan Kögl on dev@:
Another thing I noticed during my tests of CouchDB 1.2.x. I redirected
live traffic to the instance and after a rather short time, requests
were failing with the following information in the logs:
[Sun, 18 Mar 2012 16:39:24 GMT] [error] [0.27554.2]
{error_report,0.31.0,
{0.27554.2,std_error,
[{application,mochiweb},
Accept failed error,
{error,emfile}]}}
[Sun, 18 Mar 2012 16:39:24 GMT] [error] [0.27554.2]
{error_report,0.31.0,
{0.27554.2,crash_report,
[[{initial_call,
{mochiweb_acceptor,init,
['Argument__1','Argument__2',
'Argument__3']}},
{pid,0.27554.2},
{registered_name,[]},
{error_info,
{exit,
{error,accept_failed},
[{mochiweb_acceptor,init,3},
{proc_lib,init_p_do_apply,3}]}},
{ancestors,
[couch_httpd,couch_secondary_services,
couch_server_sup,0.32.0]},
{messages,[]},
{links,[0.129.0]},
{dictionary,[]},
{trap_exit,false},
{status,running},
{heap_size,233},
{stack_size,24},
{reductions,244}],
[]]}}
I think emfile means that CouchDB (or mochiweb?) couldn't open any
more files / connections. I've set the (hard and soft) nofile limit for
user couchdb to 4096, but didn't raise the ERL_MAX_PORTS accordingly.
Anyway, as soon as the error occured, CouchDB started writing most of my
view files from scratch, rendering the instance unusable.
I'd expect CouchDB to fail more gracefully when the maximum number of
open files is reached. Is this a bug or expected behaviour?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (COUCHDB-1424) make check hangs when compiling with R15B
make check hangs when compiling with R15B - Key: COUCHDB-1424 URL: https://issues.apache.org/jira/browse/COUCHDB-1424 Project: CouchDB Issue Type: Bug Components: Test Suite Affects Versions: 1.2, 1.3 Reporter: Jan Lehnardt make check hangs when running under R15B. For me it is 160-vhosts.t where execution stops, but if I recall correctly others have reported other tests. The crux here is that running the tests individually succeeds. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (COUCHDB-1418) make -j builds can cause build error with help2man
make -j builds can cause build error with help2man -- Key: COUCHDB-1418 URL: https://issues.apache.org/jira/browse/COUCHDB-1418 Project: CouchDB Issue Type: Bug Components: Build System Affects Versions: 1.1, 1.2, 1.3 Reporter: Jan Lehnardt Assignee: Noah Slater Priority: Minor make -jN enables parallel execution of build tasks. When a system has help2man installed, the build system might invoke couchjs -h to generate the help before the couchjs binary was finished building. Subsequent runs of make -jN or make without the -jN option succeed as usual. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (COUCHDB-1419) bail if g++ isn't found or use gcc for spidermonkey checks in ./configure
bail if g++ isn't found or use gcc for spidermonkey checks in ./configure - Key: COUCHDB-1419 URL: https://issues.apache.org/jira/browse/COUCHDB-1419 Project: CouchDB Issue Type: Bug Components: Build System Affects Versions: 1.1, 1.2, 1.3 Reporter: Jan Lehnardt it seems we don't bail out of ./configure if g++ isn't installed, but the ./configure checks for SpiderMonkey require g++ and report Spidermonkey not found, although it is g++ that is missing -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (COUCHDB-1409) Look into manual GC
Look into manual GC --- Key: COUCHDB-1409 URL: https://issues.apache.org/jira/browse/COUCHDB-1409 Project: CouchDB Issue Type: Improvement Reporter: Jan Lehnardt This just as a reminder to consider http://andy.wordpress.com/2012/02/13/erlang-is-a-hoarder/ (incl. comments) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (COUCHDB-1393) badmatch on big binary
badmatch on big binary
--
Key: COUCHDB-1393
URL: https://issues.apache.org/jira/browse/COUCHDB-1393
Project: CouchDB
Issue Type: Bug
Reporter: Jan Lehnardt
via dev@ by Peta Bogdan bog...@gmail.com
Hello,
I have a small database around 120 MB with approximately 16,000 documents.
However, it happens (also from futon) that I get this error:
[Tue, 17 Jan 2012 07:22:01 GMT] [error] [0.185.0] {error_report,0.30.0,
{0.185.0,crash_report,
[[{initial_call,{couch_file,init,['Argument__1']}},
{pid,0.185.0},
{registered_name,[]},
{error_info,
{exit,
{{badmatch,
{ok,
9_MEGABYTES_BINARY}},
[{couch_file,read_raw_iolist_int,3},
{couch_file,maybe_read_more_iolist,4},
{couch_file,handle_call,3},
{gen_server,handle_msg,5},
{proc_lib,init_p_do_apply,3}]},
[{gen_server,terminate,6},
{proc_lib,init_p_do_apply,3}]}},
{ancestors,[0.184.0]},
{messages,
[{'$gen_call',
{0.10840.18,#Ref0.0.3.20907},
bytes}]},
{links,[0.190.0]},
{dictionary,[]},
{trap_exit,true},
{status,running},
{heap_size,1597},
{stack_size,24},
{reductions,65666}],
[{neighbour,
[{pid,0.190.0},
{registered_name,[]},
{initial_call,
{couch_ref_counter,init,['Argument__1']}},
{current_function,{gen_server,loop,6}},
{ancestors,[0.188.0,0.187.0,0.184.0]},
{messages,[]},
{links,[0.185.0]},
{dictionary,[]},
{trap_exit,false},
{status,waiting},
{heap_size,610},
{stack_size,9},
{reductions,362}]}]]}}
If this error occurs to frequently causes couch_server to reach its max
restart frequency causing the entire supervision tree to shutdown and hence
the database server instance disappears.
The function couch_file:read_raw_iolist_int/3 calls file:pread which
returns {ok, Binary}. This Binary has almost 9 megabytes in size, which is
very strange.
I think this does mean that the function file:pread/3 is instructed to read
from wrong position.
The only reason I can think of is that the value of 'TotalBytes' from line
(1) doesn't match the value of 'TotalBytes' from line (2)
(1) TotalBytes = calculate_total_read_len(BlockOffset, Len),
(2) {ok, RawBin:TotalBytes/binary} = file:pread(Fd, Pos, TotalBytes),
The possible answer would be that in certain conditions the function
calculate_total_read_len/2 doesn't return the expected value.
Server: CouchDB/1.1.1 (Erlang OTP/R14B04)
OS: OpenBSD 5.0 GENERIC.MP#63 amd64
Now, the trouble is how to circumvent this situation.
Thank you in advance,
Bogdan
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (COUCHDB-1345) Bulk edit document on the server
Bulk edit document on the server Key: COUCHDB-1345 URL: https://issues.apache.org/jira/browse/COUCHDB-1345 Project: CouchDB Issue Type: Wish Reporter: Jan Lehnardt [moved here from the wiki] A Document Runner would provide functionality to run a transform function across all documents in the database. This way you could do maintenance and migrations, with incurring a bunch of http overhead. The idea was originally floated on the couchdb-user mailing list. Requirements Ability to specify a job in a view-server like context (Javascript other language function) and have it run across all docs (like a view is), but with the additional ability to write back to the document (through the http api, so we don't have to add a socket-based update interface). Caveat: We may not be able to guarantee that runner functions see each document only once, so functions need to be aware only to modify documents that require modification. Uses Changing the format of a timestamp across all docs Removing sensitive fields before replicating to another jurisdiction (View runner... slightly different) Materializing the results of group=true reduce queries into a dataset for further map/reduce processing (a common pattern in Hadoop) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (COUCHDB-1342) Asynchronous file writes
Asynchronous file writes Key: COUCHDB-1342 URL: https://issues.apache.org/jira/browse/COUCHDB-1342 Project: CouchDB Issue Type: Improvement Components: Database Core Reporter: Jan Lehnardt Fix For: 1.3 Attachments: COUCHDB-1342.patch This change updates the file module so that it can do asynchronous writes. Basically it replies immediately to process asking to write something to the file, with the position where the chunks will be written to the file, while a dedicated child process keeps collecting chunks and write them to the file (and batching them when possible). After issuing a series of write request to the file module, the caller can call its 'flush' function which will block the caller until all the chunks it requested to write are effectively written to the file. This maximizes the IO subsystem, as for example, while the updater is traversing and modifying the btrees and doing CPU bound tasks, the writes are happening in parallel. Originally described at http://s.apache.org/TVu Github Commit: https://github.com/fdmanana/couchdb/commit/e82a673f119b82dddf674ac2e6233cd78c123554 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (COUCHDB-1339) JS CLI Test Suite: use shell trap to catch dying beam processes during test runs
JS CLI Test Suite: use shell trap to catch dying beam processes during test runs Key: COUCHDB-1339 URL: https://issues.apache.org/jira/browse/COUCHDB-1339 Project: CouchDB Issue Type: Improvement Components: Test Suite Affects Versions: 1.3 Reporter: Jan Lehnardt Priority: Blocker Fix For: 1.3 The JS CLI test suite that now runs with make check (post 1.2.x master only) starts CouchDB using make dev utils/run -b and stops it with utils/run -d. One issue with this is that the CouchDB process might terminate in the background. The shell trap command allows the test suite to act on that accordingly, otherwise the test suite would just freeze. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (COUCHDB-1338) JS CLI test suite: have CouchDB start with port=0
JS CLI test suite: have CouchDB start with port=0 -- Key: COUCHDB-1338 URL: https://issues.apache.org/jira/browse/COUCHDB-1338 Project: CouchDB Issue Type: Improvement Components: Test Suite Affects Versions: 1.3 Reporter: Jan Lehnardt Priority: Blocker Fix For: 1.3 The JS CLI test suite that now runs with make check (post 1.2.x master only) starts CouchDB using make dev utils/run -b and stops it with utils/run -d. One issue with this is that one might have CouchDB already running on the default port 5984. The suggestion here is to start CouchDB with an additional .ini file that sets the port number to 0 to let the TCP stack figure out a free port for us. The tests then need to be updated to discover the automatic port using the couch.uri file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
