[jira] [Commented] (COUCHDB-690) replication fail -- couchdb crashed
[ https://issues.apache.org/jira/browse/COUCHDB-690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13118066#comment-13118066 ] Patrick de Lanauze commented on COUCHDB-690: :( this is a showstopper for the use of couchdb in my project.. any progress on this issue ? replication fail -- couchdb crashed --- Key: COUCHDB-690 URL: https://issues.apache.org/jira/browse/COUCHDB-690 Project: CouchDB Issue Type: Bug Components: Replication Affects Versions: 0.10.1 Environment: linux 2.6.30.7 - debian 5.0 Reporter: linkfluence Priority: Critical Labels: couchdb, replication Attachments: couch.log We have a database on host A with 8.5 millions document. The size of the database is ~450GO. We first tried to start a continuous replication on a second host B. The replication stoped after only 1Go have been copied, and the replication never started again. We then copied the database file from host A on host B. When the file was copied, we started a replication from A to B, then the couchdb on host B crashed. It tooks a long time to fetch a list of IDs, then it appears in the logfile that a time out occured on host B, and immediatly after the couchdb instance on host B crashed. -- 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] [Updated] (COUCHDB-1285) Allow configuration of vendor and module version in the welcome message
[
https://issues.apache.org/jira/browse/COUCHDB-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Young updated COUCHDB-1285:
Attachment: vendor_and_modules_objects.patch
This patch makes Vendors and Modules JSON objects inside the Welcome JSON
object returned from /
Vendors has been made an object to allow more consistent referencing of the
vendor version number and other potential vendor specific information without
the need to reference the vendor name in client-side code (namely, Futon).
The version number can now be retrieved at doc.vendor.version vs. doc.refuge
(or similar).
Allow configuration of vendor and module version in the welcome message
---
Key: COUCHDB-1285
URL: https://issues.apache.org/jira/browse/COUCHDB-1285
Project: CouchDB
Issue Type: Improvement
Reporter: Jan Lehnardt
Attachments: vendor_and_modules_objects.patch
The patch below allows to configure vendor and module version information
into the GET / welcome message.
E.g.
[vendor]
name = refuge
version = 2.0.0
[modules]
geocouch = 1.2.1
would produce:
{couchdb:Welcome,version:1.2.0,refuge:2.0.0,modules:{geocouch:1.2.1}}
--
--- a/src/couchdb/couch_httpd_misc_handlers.erl
+++ b/src/couchdb/couch_httpd_misc_handlers.erl
@@ -30,9 +30,23 @@
% httpd global handlers
handle_welcome_req(#httpd{method='GET'}=Req, WelcomeMessage) -
+Vendor = case couch_config:get(vendor) of
+ [] - [];
+ Vendor1 - [{
+proplists:get_value(name, Vendor1),
+?l2b(proplists:get_value(version, Vendor1))
+ }]
+end,
+
+Modules = lists:map(fun({Key, Value}) -
+ {Key, ?l2b(Value)}
+end, couch_config:get(modules)),
+
send_json(Req, {[
{couchdb, WelcomeMessage},
-{version, list_to_binary(couch_server:get_version())}
+{version, list_to_binary(couch_server:get_version())}]
+++ Vendor
+++ [{modules, {Modules}}
]});
handle_welcome_req(Req, _) -
send_method_not_allowed(Req, GET,HEAD).
--
--
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
Re: Starting the Git Experiment (for realz)
On Sep 29, 2011, at 2:24 PM, Paul Davis wrote: But nothing will break and everyone will forgive me for any bugs that may crop up. I'll help support anything strange that happens (though I don't pay very close attention to this list). Thanks a lot for your efforts. -- dustin sallings
[jira] [Closed] (COUCHDB-648) _update handler ignores code in response doc
[
https://issues.apache.org/jira/browse/COUCHDB-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Randall Leeds closed COUCHDB-648.
-
Resolution: Fixed
Fixed on trunk in r1177890.
Fixed on 1.2.x in r1177891.
Fixed on 1.1.x in r1177892.
_update handler ignores code in response doc
--
Key: COUCHDB-648
URL: https://issues.apache.org/jira/browse/COUCHDB-648
Project: CouchDB
Issue Type: Bug
Components: Database Core
Environment: CouchDB from HEAD
Reporter: Cliff Stanford
Assignee: Randall Leeds
Labels: update
Fix For: 1.1.1, 1.2
Attachments:
0001-Document-update-handlers-now-honor-code-in-response-.patch, test.diff
When using an _update handler, it should be possible to return a response
code.
return [ doc, {
headers : { Location : / },
code : 303,
body : 'Redirecting'
}];
Should return 303 (the redirect for POST) but in fact, on a successful create
returns 201. This means it is not possible to use the browser to POST as you
cannot redirect on return. This feels like a bug.
In any case, I would respectfully suggest that the syntax of the _update
handler be changed so that there is a store(doc) call (or similar) which
returns a JSON object to the update handler so that the handler may redirect
appropriately. That would make it possible to do updates client-side with
little or no client-side javascript.
--
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] [Closed] (COUCHDB-990) Update handlers ignore HTTP status codes in responses
[
https://issues.apache.org/jira/browse/COUCHDB-990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Randall Leeds closed COUCHDB-990.
-
Resolution: Fixed
Fix Version/s: 1.2
1.1.1
Fixed on trunk in r1177890.
Fixed on 1.2.x in r1177891.
Fixed on 1.1.x in r1177892.
Update handlers ignore HTTP status codes in responses
-
Key: COUCHDB-990
URL: https://issues.apache.org/jira/browse/COUCHDB-990
Project: CouchDB
Issue Type: Bug
Components: JavaScript View Server
Affects Versions: 1.0.1
Environment: OSX, built using brew
Reporter: Nick Fisher
Fix For: 1.1.1, 1.2
The following update handler will always return 200
'''
function(doc, req){
return [null, {code: 400, body: 'bad user request'];
}
'''
--
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
