[GitHub] wohali commented on issue #73: Configuration from docker config or secret?
wohali commented on issue #73: Configuration from docker config or secret? URL: https://github.com/apache/couchdb-docker/issues/73#issuecomment-380324044 What I'm going to do is just have the chmod/chown script do a -f, which means if it fails it won't complain and won't error out. That way we both get what we want. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[Jenkins] FAILURE: CouchDB ยป master #244
Boo, we failed. https://builds.apache.org/job/CouchDB/job/master/244/
[GitHub] davisp commented on issue #1272: Record and expose last compaction time
davisp commented on issue #1272: Record and expose last compaction time URL: https://github.com/apache/couchdb/pull/1272#issuecomment-380131597 I'm also mulling over how we might make this a bit more general rather than specifically inserting a last_compaction_time or w/e. Seems like having a storage-engine-defined set of extra info would be generally useful. Only sticking point is how we combine that for the cluster endpoint. Though on a semi-related note I was wanting an option the other day to show me the db info blobs for all shards rather than the combined version. Perhaps if we do that we can make an arbitrary "engine_info" key that allows storage engines to expose any data they might feel like having there? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] davisp commented on issue #1029: Fix: Added a temporary fix to avoid compaction failures #1001
davisp commented on issue #1029: Fix: Added a temporary fix to avoid compaction failures #1001 URL: https://github.com/apache/couchdb/pull/1029#issuecomment-380130263 At the very least this should be a required flag or config setting. Preferably I'd even just never commit it and document it as a temp fix that can be compiled and dropped in separately to fix broken compactions. Having code on master that drops data during compactions scares the daylights out of me. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] nickva opened a new pull request #1277: In _scheduler/docs fix `crashing` state showing as `pending` sometimes
nickva opened a new pull request #1277: In _scheduler/docs fix `crashing` state showing as `pending` sometimes URL: https://github.com/apache/couchdb/pull/1277 Replication jobs are backed off based on the number of consecutive crashes, that is, we count the number of crashes in a row and then penalize jobs with an exponential wait based that number. After a job runs without crashing for 2 minutes, we consider it healthy and stop going back in its history and looking for crashes. Previously a job's state was set to `crashing` only if there were any consecutive errors. So it could have ran for 3 minutes, then user deletes the source database, job crashes and stops. Until it runs again the state would have been shown as `pending`. For internal accounting purposes that's correct but it is confusing for the user because the last event in its history is a crash. This commit makes sure that if the last even in job's history is a crash user will see the jobs as `crashing` with the respective crash reason. The scheduling algorithm didn't change. Fixes #1276 - [x] Code is written and works correctly; - [x] Changes are covered by tests; - [x] Documentation reflects the changes; This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] wohali closed pull request #1118: Set update_lru_on_read=false as default
wohali closed pull request #1118: Set update_lru_on_read=false as default URL: https://github.com/apache/couchdb/pull/1118 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] wohali commented on issue #74: Can you please specify the steps for setting couchdb clustering in windows, right now I have single node setup , I would like to make it 2 node cluster.
wohali commented on issue #74: Can you please specify the steps for setting couchdb clustering in windows, right now I have single node setup , I would like to make it 2 node cluster. URL: https://github.com/apache/couchdb-docker/issues/74#issuecomment-380125324 Known issue: https://github.com/apache/couchdb/issues/783 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] wohali commented on issue #1274: DB hangs while replicating
wohali commented on issue #1274: DB hangs while replicating URL: https://github.com/apache/couchdb/issues/1274#issuecomment-380123703 Can you try upgrading to 1.7.1 first? 1.6.1 has known security issues, for a start. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] olivenvrac commented on issue #1267: [ERROR] fabric_worker_timeout
olivenvrac commented on issue #1267: [ERROR] fabric_worker_timeout URL: https://github.com/apache/couchdb/issues/1267#issuecomment-380110853 there is a mistake in my introduction : i don't have any problem with the continuous replication. Just with the replication beetween PouchDB and CouchDB. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] starting commented on issue #1029: Fix: Added a temporary fix to avoid compaction failures #1001
starting commented on issue #1029: Fix: Added a temporary fix to avoid compaction failures #1001 URL: https://github.com/apache/couchdb/pull/1029#issuecomment-380071719 I too share your view @davisp. What should we do if a document not present in the db during compaction? I feel it is better to be flexible and notify the error, rather failing complete compaction process. This help for the availability of the database. In Summary, We should find and fix the root of this issue, but still a single document failure should not cause the whole DB to be unavailable. (I couldn't still find an exact location that generates this issue). This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] starting commented on issue #1029: Fix: Added a temporary fix to avoid compaction failures #1001
starting commented on issue #1029: Fix: Added a temporary fix to avoid compaction failures #1001 URL: https://github.com/apache/couchdb/pull/1029#issuecomment-380071719 I too share your view @davisp. What should we do if a document not present in the db during compaction? I feel it is better to be flexible and notify the error, rather failing complete compaction process. This help for the availability of the database. In Summary, We should find and fix the root of this issue, but still a single document failure should not cause the whole DB to be unavailable. (I couldn't still find an exact location that generates this issue. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] sainusahib commented on issue #1008: Time-out issue when running native erlang views in 2.x on
sainusahib commented on issue #1008: Time-out issue when running native erlang
views in 2.x on
URL: https://github.com/apache/couchdb/issues/1008#issuecomment-380053300
Same error , Erlang 6.2
[error] 2018-04-10T10:10:59.860288Z nonode@nohost <0.14711.9> bcb49f8b6b
rexi_server: from: nonode@nohost(<0.32062.6>) mfa: fabric_rpc:reduce_view/4
throw:{timeout,{gen_server,call,[couch_proc_manager,{get_proc,<<"javascript">>},5000]}}
[{couch_mrview_util,get_view_index_state,5,[{file,"src/couch_mrview_util.erl"},{line,101}]},{couch_mrview_util,get_view,4,[{file,"src/couch_mrview_util.erl"},{line,45}]},{couch_mrview,query_view,6,[{file,"src/couch_mrview.erl"},{line,244}]},{rexi_server,init_p,3,[{file,"src/rexi_server.erl"},{line,139}]}]
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[jira] [Commented] (COUCHDB-3326) Implement clustered purge API: _purge
[
https://issues.apache.org/jira/browse/COUCHDB-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16432006#comment-16432006
]
ASF subversion and git services commented on COUCHDB-3326:
--
Commit ee3c0994b8dd87b4d2e820dae9c29c8b573acf61 in couchdb's branch
refs/heads/COUCHDB-3326-clustered-purge-davisp-refactor from [~jiangph]
[ https://gitbox.apache.org/repos/asf?p=couchdb.git;h=ee3c099 ]
Temporarily disable failed test case
COUCHDB-3326
> Implement clustered purge API: _purge
> -
>
> Key: COUCHDB-3326
> URL: https://issues.apache.org/jira/browse/COUCHDB-3326
> Project: CouchDB
> Issue Type: New Feature
> Components: Database Core, Documentation, HTTP Interface
>Reporter: Mayya Sharipova
>Priority: Major
>
> This implements the clustered purge API:
> {code:}
> curl -H 'Content-Type: application/json' -X POST
> "http://adm:pass@127.0.0.1:5984/test1/_purge; -d
> '{"d1":["3-410e46c04b51b4c3304ed232790a49da",
> "3-420e46c04b51b4c3304ed232790a35db"],"d2":["2-a39d6d63f29a956ae39930f84dd71ec3"],
> "d3":["1-bdca7a3ac9503bf6e46d7d7a782e8f03"]}'
> {code}
> Response: status_code 201 or 202
> {code:javascript}
> {
> "purged": [
> {
> "ok": true, //Quorum was reached, at least W nodes
> successfully purged doc
> "id": "d1",
> "revs": [
> "3-410e46c04b51b4c3304ed232790a49da",
>"3-420e46c04b51b4c3304ed232790a35db"
> ]
> },
> {
> "accepted": true, //Quorum was NOT reached, but request was
> accepted
> "id": "d2",
> "revs": [
> "2-a39d6d63f29a956ae39930f84dd71ec3"
> ]
> },
> {
> "ok": true,
> "id": "d3",
> "revs": []//(DocId or Revs missing) OR (Revs are not leaf
> revisions)
> } ],
> "purge_seq":
> "6-g1BMeJzLYWBgYMpgTmHgz8tPSTV2MDQy1zMAQsMckEQiQ5L8sxKZ4UoMcSrJAgC9PRRl"
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (COUCHDB-3326) Implement clustered purge API: _purge
[
https://issues.apache.org/jira/browse/COUCHDB-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16431987#comment-16431987
]
ASF subversion and git services commented on COUCHDB-3326:
--
Commit 067303acbc75a9a75b69c7044db377d83d688cf2 in couchdb's branch
refs/heads/COUCHDB-3326-clustered-purge-davisp-refactor from [~jiangph]
[ https://gitbox.apache.org/repos/asf?p=couchdb.git;h=067303a ]
Temporarily disable failed test case
COUCHDB-3326
> Implement clustered purge API: _purge
> -
>
> Key: COUCHDB-3326
> URL: https://issues.apache.org/jira/browse/COUCHDB-3326
> Project: CouchDB
> Issue Type: New Feature
> Components: Database Core, Documentation, HTTP Interface
>Reporter: Mayya Sharipova
>Priority: Major
>
> This implements the clustered purge API:
> {code:}
> curl -H 'Content-Type: application/json' -X POST
> "http://adm:pass@127.0.0.1:5984/test1/_purge; -d
> '{"d1":["3-410e46c04b51b4c3304ed232790a49da",
> "3-420e46c04b51b4c3304ed232790a35db"],"d2":["2-a39d6d63f29a956ae39930f84dd71ec3"],
> "d3":["1-bdca7a3ac9503bf6e46d7d7a782e8f03"]}'
> {code}
> Response: status_code 201 or 202
> {code:javascript}
> {
> "purged": [
> {
> "ok": true, //Quorum was reached, at least W nodes
> successfully purged doc
> "id": "d1",
> "revs": [
> "3-410e46c04b51b4c3304ed232790a49da",
>"3-420e46c04b51b4c3304ed232790a35db"
> ]
> },
> {
> "accepted": true, //Quorum was NOT reached, but request was
> accepted
> "id": "d2",
> "revs": [
> "2-a39d6d63f29a956ae39930f84dd71ec3"
> ]
> },
> {
> "ok": true,
> "id": "d3",
> "revs": []//(DocId or Revs missing) OR (Revs are not leaf
> revisions)
> } ],
> "purge_seq":
> "6-g1BMeJzLYWBgYMpgTmHgz8tPSTV2MDQy1zMAQsMckEQiQ5L8sxKZ4UoMcSrJAgC9PRRl"
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] abhishiv commented on issue #1183: Proxy Authentication doesn't work when proxy_use_secret=true
abhishiv commented on issue #1183: Proxy Authentication doesn't work when proxy_use_secret=true URL: https://github.com/apache/couchdb/issues/1183#issuecomment-380029505 > I think the hmac encoding of the username provides only slightly better security, but it is confusing to users. Perhaps the http auth should allow both options at the same time, either the secret directly (#1174), or the encoded username. If an attacker already knows about the secret, it is trivial to generate the tokens, so there is no harm in allowing the secret as a token, if users desire it. Benefit of encoding username is that it disallows malicious users from accessing others databases. If we were to allow directly supplying secret - specially when using it with a browser client like pouchdb. If we were to allow both, at least we should document this point. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] abhishiv commented on issue #1183: Proxy Authentication doesn't work when proxy_use_secret=true
abhishiv commented on issue #1183: Proxy Authentication doesn't work when proxy_use_secret=true URL: https://github.com/apache/couchdb/issues/1183#issuecomment-380029505 > I think the hmac encoding of the username provides only slightly better security, but it is confusing to users. Perhaps the http auth should allow both options at the same time, either the secret directly (#1174), or the encoded username. If an attacker already knows about the secret, it is trivial to generate the tokens, so there is no harm in allowing the secret as a token, if users desire it. Benefit of encoding username is that it disallows malicious users from accessing others databases. If we were to allow directly supplying secret - specially when using it on client like pouchdb. If we were to allow both, at least we should document this point. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] rnewson commented on a change in pull request #1272: Record and expose last compaction time
rnewson commented on a change in pull request #1272: Record and expose last
compaction time
URL: https://github.com/apache/couchdb/pull/1272#discussion_r180344346
##
File path: src/couch/src/couch_bt_engine_header.erl
##
@@ -229,6 +236,7 @@ upgrade_disk_version(#db_header{}=Header) ->
3 -> throw({database_disk_version_error, ?OLD_DISK_VERSION_ERROR});
4 -> Header#db_header{security_ptr = nil}; % [0.10 - 0.11)
5 -> Header; % pre 1.2
+6 -> Header;
Review comment:
@davisp on reflection, I don't think I need to bump disk version as we're
only adding a new field.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[jira] [Commented] (COUCHDB-3326) Implement clustered purge API: _purge
[
https://issues.apache.org/jira/browse/COUCHDB-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16431906#comment-16431906
]
ASF subversion and git services commented on COUCHDB-3326:
--
Commit f35d8f037d17cf36743932c103706068e7783c0c in couchdb's branch
refs/heads/COUCHDB-3326-clustered-purge-davisp-refactor from [~jiangph]
[ https://gitbox.apache.org/repos/asf?p=couchdb.git;h=f35d8f0 ]
Temporarily disable failed test case
COUCHDB-3326
> Implement clustered purge API: _purge
> -
>
> Key: COUCHDB-3326
> URL: https://issues.apache.org/jira/browse/COUCHDB-3326
> Project: CouchDB
> Issue Type: New Feature
> Components: Database Core, Documentation, HTTP Interface
>Reporter: Mayya Sharipova
>Priority: Major
>
> This implements the clustered purge API:
> {code:}
> curl -H 'Content-Type: application/json' -X POST
> "http://adm:pass@127.0.0.1:5984/test1/_purge; -d
> '{"d1":["3-410e46c04b51b4c3304ed232790a49da",
> "3-420e46c04b51b4c3304ed232790a35db"],"d2":["2-a39d6d63f29a956ae39930f84dd71ec3"],
> "d3":["1-bdca7a3ac9503bf6e46d7d7a782e8f03"]}'
> {code}
> Response: status_code 201 or 202
> {code:javascript}
> {
> "purged": [
> {
> "ok": true, //Quorum was reached, at least W nodes
> successfully purged doc
> "id": "d1",
> "revs": [
> "3-410e46c04b51b4c3304ed232790a49da",
>"3-420e46c04b51b4c3304ed232790a35db"
> ]
> },
> {
> "accepted": true, //Quorum was NOT reached, but request was
> accepted
> "id": "d2",
> "revs": [
> "2-a39d6d63f29a956ae39930f84dd71ec3"
> ]
> },
> {
> "ok": true,
> "id": "d3",
> "revs": []//(DocId or Revs missing) OR (Revs are not leaf
> revisions)
> } ],
> "purge_seq":
> "6-g1BMeJzLYWBgYMpgTmHgz8tPSTV2MDQy1zMAQsMckEQiQ5L8sxKZ4UoMcSrJAgC9PRRl"
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (COUCHDB-3326) Implement clustered purge API: _purge
[
https://issues.apache.org/jira/browse/COUCHDB-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16431871#comment-16431871
]
ASF subversion and git services commented on COUCHDB-3326:
--
Commit 429dd97432df56c594805cdfb6eddc198293b683 in couchdb's branch
refs/heads/COUCHDB-3326-clustered-purge-davisp-refactor from [~jiangph]
[ https://gitbox.apache.org/repos/asf?p=couchdb.git;h=429dd97 ]
Bug fixes on clustered purge
COUCHDB-3326
> Implement clustered purge API: _purge
> -
>
> Key: COUCHDB-3326
> URL: https://issues.apache.org/jira/browse/COUCHDB-3326
> Project: CouchDB
> Issue Type: New Feature
> Components: Database Core, Documentation, HTTP Interface
>Reporter: Mayya Sharipova
>Priority: Major
>
> This implements the clustered purge API:
> {code:}
> curl -H 'Content-Type: application/json' -X POST
> "http://adm:pass@127.0.0.1:5984/test1/_purge; -d
> '{"d1":["3-410e46c04b51b4c3304ed232790a49da",
> "3-420e46c04b51b4c3304ed232790a35db"],"d2":["2-a39d6d63f29a956ae39930f84dd71ec3"],
> "d3":["1-bdca7a3ac9503bf6e46d7d7a782e8f03"]}'
> {code}
> Response: status_code 201 or 202
> {code:javascript}
> {
> "purged": [
> {
> "ok": true, //Quorum was reached, at least W nodes
> successfully purged doc
> "id": "d1",
> "revs": [
> "3-410e46c04b51b4c3304ed232790a49da",
>"3-420e46c04b51b4c3304ed232790a35db"
> ]
> },
> {
> "accepted": true, //Quorum was NOT reached, but request was
> accepted
> "id": "d2",
> "revs": [
> "2-a39d6d63f29a956ae39930f84dd71ec3"
> ]
> },
> {
> "ok": true,
> "id": "d3",
> "revs": []//(DocId or Revs missing) OR (Revs are not leaf
> revisions)
> } ],
> "purge_seq":
> "6-g1BMeJzLYWBgYMpgTmHgz8tPSTV2MDQy1zMAQsMckEQiQ5L8sxKZ4UoMcSrJAgC9PRRl"
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] Jyothishb4 commented on issue #74: Can you please specify the steps for setting couchdb clustering in windows, right now I have single node setup , I would like to make it 2 node cluster.
Jyothishb4 commented on issue #74: Can you please specify the steps for setting
couchdb clustering in windows, right now I have single node setup , I would
like to make it 2 node cluster.
URL: https://github.com/apache/couchdb-docker/issues/74#issuecomment-379993078
Hi @wohali
I have copied curl to couchdb server and tried to add the node using couchdb
documentation but I am getting one error,
curl --ssl-no-revoke -X POST -H "Content-Type: application/json"
https://admin:password@x:6984/_cluster_setup -d '{"action":
"enable_cluster", "bind_address":"x.x.x.x", "username": "admin",
"password":"password", "node_count":"2"}'
curl: (35) schannel: next InitializeSecurityContext failed: Unknown error
(0x80092013) - The revocation function was unable to check revocation because
the revocation server was offline.
curl: (6) Could not resolve host: enable_cluster,
curl: (3) Port number ended with '.'
curl: (6) Could not resolve host: username
curl: (6) Could not resolve host: admin,
curl: (3) Port number ended with 'w'
curl: (3) [globbing] unmatched close brace/bracket in column 13
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[GitHub] wohali commented on issue #74: Can you please specify the steps for setting couchdb clustering in windows, right now I have single node setup , I would like to make it 2 node cluster.
wohali commented on issue #74: Can you please specify the steps for setting couchdb clustering in windows, right now I have single node setup , I would like to make it 2 node cluster. URL: https://github.com/apache/couchdb-docker/issues/74#issuecomment-379992091 For advice with CouchDB I recommend our IRC #couchdb channel on Freenode ,the matching Slack channel, or the mailing list at u...@couchdb.apache.org. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
