[jira] Commented: (COUCHDB-963) Erlang processes crash when running the delayed_commits test on Windows Server 2008
[ https://issues.apache.org/jira/browse/COUCHDB-963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12994715#comment-12994715 ] Dave Cottlehuber commented on COUCHDB-963: -- Looks like a suitable workaround will be to adapt erlsrv.exe build process (in windows.iss.tpl) to set onfail restart service. Erlang processes crash when running the delayed_commits test on Windows Server 2008 --- Key: COUCHDB-963 URL: https://issues.apache.org/jira/browse/COUCHDB-963 Project: CouchDB Issue Type: Bug Components: Infrastructure Affects Versions: 1.0.1 Environment: This Windows box is a virtual machine Windows Server 2008 Standard without Hyper-V Service Pack 2 64-bit 2 GB RAM 2 Core Intel Xeon CPU @ 2.53GHz each Reporter: Terry Smith Attachments: Apache CouchDB.debug.2, couch.log, dch_couch.log The debugging I've done points to this being an erlsrv.exe bug. Here my steps to recreate. Install 1.0.1 CouchDB as a service using the Windows Binary Installer. I did not select to Start service after installation. Edit the local.ini to set the logging level to debug. Go to the service control panel and start the Apache CouchDB service. Go to Test Suite in Futon and run the delayed_commits test. After about 15 - 20 seconds go to the service control panel and refresh to see that the service is no longer running. ProcessExplorer verifies the erlsrv.exe and erl.exe processes are not running. The last message in the log is a _restart command that returns 200. When I run CouchDB using CouchDB.bat. The test completes without crashing. When I set the DebugType in the registry HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Ericsson\Erlang\ErlSrv\1.1\Apache CouchDB to 1 (DEBUG_TYPE_NEW) to get a erlsrv.exe log, the test completes without crashing. I will attach the log files from CouchDB and erlsrv.exe. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
couchdb conflict resolution
Hello, I am very interested in understanding how conflict resolution works in couchdb: Is there a technical overview, somewhere, of how a node decides which revision wins? After a conflict is resolved, are old revisions discarded? Any technical details, short of slogging through the code, would be very welcome. Thanks, Aaron
Re: couchdb conflict resolution
Here is some high level text on it. https://issues.apache.org/jira/browse/COUCHDB-988 On Feb 15, 2011, at 10:14 AM, Aaron Boxer boxe...@gmail.com wrote: Hello, I am very interested in understanding how conflict resolution works in couchdb: Is there a technical overview, somewhere, of how a node decides which revision wins? After a conflict is resolved, are old revisions discarded? Any technical details, short of slogging through the code, would be very welcome. Thanks, Aaron
[jira] Commented: (COUCHDB-1013) branch 1.1.x with worse database read/write performance
[ https://issues.apache.org/jira/browse/COUCHDB-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12994886#comment-12994886 ] Jan Lehnardt commented on COUCHDB-1013: --- The following setup: relaximation runs on a dual 2.13Ghz MacBook Unibody, SSD, 4GB RAM with Mac OS X 10.6.6. It is connected to an Core 2 Duo 3.06Ghz iMac via GigE withMac OS X 10.6.5 on R14B01 Default configuration: http://graphs.mikeal.couchone.com/#/graph/a3dccb9cef53a4910706152d90003649 delayed_commits = false: http://graphs.mikeal.couchone.com/#/graph/a3dccb9cef53a4910706152d900036aa I don't know if these show anything conclusive. I'm happy to run other configurations if it helps. branch 1.1.x with worse database read/write performance --- Key: COUCHDB-1013 URL: https://issues.apache.org/jira/browse/COUCHDB-1013 Project: CouchDB Issue Type: Bug Reporter: Filipe Manana Fix For: 1.1, 1.2 The issue is described in an e-mail sent to the development mailing list: http://mail-archives.apache.org/mod_mbox/couchdb-dev/201012.mbox/%3caanlktim5unvkscvhhuu_1ga1xkvfjfbwe2-wtb4vv...@mail.gmail.com%3E It also affects trunk. Would love to have results from other on Linux/ext4, and other OSes/filesystems besides Mac OS X. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: couchdb conflict resolution
On Tue, Feb 15, 2011 at 5:14 PM, Aaron Boxer boxe...@gmail.com wrote: I am very interested in understanding how conflict resolution works in couchdb: Is there a technical overview, somewhere, of how a node decides which revision wins? After a conflict is resolved, are old revisions discarded? Any technical details, short of slogging through the code, would be very welcome. I'm not sure if this is the right level of detail for your purposes, but I found http://guide.couchdb.org/draft/conflicts.html very interesting. -- Stefan
Re: couchdb conflict resolution
Thanks, Stefan! I did see this already. Good for a high level view; but I am looking for the gory details. Cheers, Aaron On Tue, Feb 15, 2011 at 2:18 PM, Stefan Kögl koeglste...@gmail.com wrote: On Tue, Feb 15, 2011 at 5:14 PM, Aaron Boxer boxe...@gmail.com wrote: I am very interested in understanding how conflict resolution works in couchdb: Is there a technical overview, somewhere, of how a node decides which revision wins? After a conflict is resolved, are old revisions discarded? Any technical details, short of slogging through the code, would be very welcome. I'm not sure if this is the right level of detail for your purposes, but I found http://guide.couchdb.org/draft/conflicts.html very interesting. -- Stefan
Re: couchdb conflict resolution
Thanks, Paul! This is exactly the level of detail and granularity I am looking for. GIT is mentioned a few times in this issue write-up. So, does couch now use a modified form of GIT revision tracking? On Tue, Feb 15, 2011 at 12:11 PM, Paul J. Davis paul.joseph.da...@gmail.com wrote: Here is some high level text on it. https://issues.apache.org/jira/browse/COUCHDB-988 On Feb 15, 2011, at 10:14 AM, Aaron Boxer boxe...@gmail.com wrote: Hello, I am very interested in understanding how conflict resolution works in couchdb: Is there a technical overview, somewhere, of how a node decides which revision wins? After a conflict is resolved, are old revisions discarded? Any technical details, short of slogging through the code, would be very welcome. Thanks, Aaron
Re: couchdb conflict resolution
On Tue, Feb 15, 2011 at 3:11 PM, Aaron Boxer boxe...@gmail.com wrote: Thanks, Paul! This is exactly the level of detail and granularity I am looking for. GIT is mentioned a few times in this issue write-up. So, does couch now use a modified form of GIT revision tracking? Its similar in theory but you'd be a bit hard pressed to pick that out without an pretty good understanding of both. Its merely just a reference that they both use a form of inverted-merkle tree, but beyond that the similarities are generally thin.
Re: couchdb conflict resolution
Thanks. So, if I learn me some Erlang and read couch_key_tree.erl, I will understand how merging is done? Also, where is the code for generating a version id? appreciate the help, Aaron On Tue, Feb 15, 2011 at 3:33 PM, Paul Davis paul.joseph.da...@gmail.com wrote: On Tue, Feb 15, 2011 at 3:11 PM, Aaron Boxer boxe...@gmail.com wrote: Thanks, Paul! This is exactly the level of detail and granularity I am looking for. GIT is mentioned a few times in this issue write-up. So, does couch now use a modified form of GIT revision tracking? Its similar in theory but you'd be a bit hard pressed to pick that out without an pretty good understanding of both. Its merely just a reference that they both use a form of inverted-merkle tree, but beyond that the similarities are generally thin.
Re: couchdb conflict resolution
On Tue, Feb 15, 2011 at 3:45 PM, Aaron Boxer boxe...@gmail.com wrote: Thanks. So, if I learn me some Erlang and read couch_key_tree.erl, I will understand how merging is done? There is no merging. Conflicts are resolved by deleting one of the conflicted revisions. This being a major departure from the Git model. Also, where is the code for generating a version id? couch_db:new_revid/1 appreciate the help, Aaron On Tue, Feb 15, 2011 at 3:33 PM, Paul Davis paul.joseph.da...@gmail.com wrote: On Tue, Feb 15, 2011 at 3:11 PM, Aaron Boxer boxe...@gmail.com wrote: Thanks, Paul! This is exactly the level of detail and granularity I am looking for. GIT is mentioned a few times in this issue write-up. So, does couch now use a modified form of GIT revision tracking? Its similar in theory but you'd be a bit hard pressed to pick that out without an pretty good understanding of both. Its merely just a reference that they both use a form of inverted-merkle tree, but beyond that the similarities are generally thin.
Re: couchdb conflict resolution
ahhh, ok. So key tree is used to detect conflict, and to reference different conflicted versions. Got it, thanks. On Tue, Feb 15, 2011 at 3:50 PM, Paul Davis paul.joseph.da...@gmail.com wrote: On Tue, Feb 15, 2011 at 3:45 PM, Aaron Boxer boxe...@gmail.com wrote: Thanks. So, if I learn me some Erlang and read couch_key_tree.erl, I will understand how merging is done? There is no merging. Conflicts are resolved by deleting one of the conflicted revisions. This being a major departure from the Git model. Also, where is the code for generating a version id? couch_db:new_revid/1 appreciate the help, Aaron On Tue, Feb 15, 2011 at 3:33 PM, Paul Davis paul.joseph.da...@gmail.com wrote: On Tue, Feb 15, 2011 at 3:11 PM, Aaron Boxer boxe...@gmail.com wrote: Thanks, Paul! This is exactly the level of detail and granularity I am looking for. GIT is mentioned a few times in this issue write-up. So, does couch now use a modified form of GIT revision tracking? Its similar in theory but you'd be a bit hard pressed to pick that out without an pretty good understanding of both. Its merely just a reference that they both use a form of inverted-merkle tree, but beyond that the similarities are generally thin.
[jira] Created: (COUCHDB-1067) CouchDB 1.0.1 Futon does not work with jQuery 1.5
CouchDB 1.0.1 Futon does not work with jQuery 1.5 - Key: COUCHDB-1067 URL: https://issues.apache.org/jira/browse/COUCHDB-1067 Project: CouchDB Issue Type: Bug Components: Futon Affects Versions: 1.0.1 Environment: Ubuntu 11.04 Reporter: Stuart Langridge Futon in CouchDB 1.0.1 does not work with jQuery 1.5. This is a problem for Ubuntu 11.04, which ships a system version of jQuery on which all projects depend (rather than one jQuery per project). Symptom is a JavaScript error: $.httpData is not a function when viewing Futon. Downstream bug report: https://bugs.launchpad.net/ubuntu/+source/couchdb/+bug/716237 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (COUCHDB-1067) CouchDB 1.0.1 Futon does not work with jQuery 1.5
[ https://issues.apache.org/jira/browse/COUCHDB-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12995072#comment-12995072 ] Robert Newson commented on COUCHDB-1067: This is resolved on trunk at r1067420. Should be backported to 1.0.x and 1.1.x CouchDB 1.0.1 Futon does not work with jQuery 1.5 - Key: COUCHDB-1067 URL: https://issues.apache.org/jira/browse/COUCHDB-1067 Project: CouchDB Issue Type: Bug Components: Futon Affects Versions: 1.0.1 Environment: Ubuntu 11.04 Reporter: Stuart Langridge Futon in CouchDB 1.0.1 does not work with jQuery 1.5. This is a problem for Ubuntu 11.04, which ships a system version of jQuery on which all projects depend (rather than one jQuery per project). Symptom is a JavaScript error: $.httpData is not a function when viewing Futon. Downstream bug report: https://bugs.launchpad.net/ubuntu/+source/couchdb/+bug/716237 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] Commented: (COUCHDB-1067) CouchDB 1.0.1 Futon does not work with jQuery 1.5
Replace old jquery.couch.js file(in /usr/share/couchdb/www/script directory or in couchdb installed directory). Get the new version from https://github.com/apache/couchdb/blob/trunk/share/www/script/jquery.couch.js On Wed, Feb 16, 2011 at 5:42 AM, Robert Newson (JIRA) j...@apache.orgwrote: [ https://issues.apache.org/jira/browse/COUCHDB-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12995072#comment-12995072] Robert Newson commented on COUCHDB-1067: This is resolved on trunk at r1067420. Should be backported to 1.0.x and 1.1.x CouchDB 1.0.1 Futon does not work with jQuery 1.5 - Key: COUCHDB-1067 URL: https://issues.apache.org/jira/browse/COUCHDB-1067 Project: CouchDB Issue Type: Bug Components: Futon Affects Versions: 1.0.1 Environment: Ubuntu 11.04 Reporter: Stuart Langridge Futon in CouchDB 1.0.1 does not work with jQuery 1.5. This is a problem for Ubuntu 11.04, which ships a system version of jQuery on which all projects depend (rather than one jQuery per project). Symptom is a JavaScript error: $.httpData is not a function when viewing Futon. Downstream bug report: https://bugs.launchpad.net/ubuntu/+source/couchdb/+bug/716237 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Regards Aravinda | ಅರವಿಂದ http://aravindavk.in
[jira] Commented: (COUCHDB-1067) CouchDB 1.0.1 Futon does not work with jQuery 1.5
[ https://issues.apache.org/jira/browse/COUCHDB-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12995185#comment-12995185 ] Aravinda commented on COUCHDB-1067: --- As a temporary solution, search for jquery.couch.js in Apache CouchDb installed directory(In Ubuntu, /usr/share/couchdb/www/script/). And replace that file with new JS file from the link below https://github.com/apache/couchdb/blob/trunk/share/www/script/jquery.couch.js CouchDB 1.0.1 Futon does not work with jQuery 1.5 - Key: COUCHDB-1067 URL: https://issues.apache.org/jira/browse/COUCHDB-1067 Project: CouchDB Issue Type: Bug Components: Futon Affects Versions: 1.0.1 Environment: Ubuntu 11.04 Reporter: Stuart Langridge Futon in CouchDB 1.0.1 does not work with jQuery 1.5. This is a problem for Ubuntu 11.04, which ships a system version of jQuery on which all projects depend (rather than one jQuery per project). Symptom is a JavaScript error: $.httpData is not a function when viewing Futon. Downstream bug report: https://bugs.launchpad.net/ubuntu/+source/couchdb/+bug/716237 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
