[jira] [Created] (COUCHDB-3236) update node metadata to use new node fails in _users
Anielkis Herrera created COUCHDB-3236: - Summary: update node metadata to use new node fails in _users Key: COUCHDB-3236 URL: https://issues.apache.org/jira/browse/COUCHDB-3236 Project: CouchDB Issue Type: Bug Components: Database Core, Fauxton Reporter: Anielkis Herrera When I restart a couchdb one node cluster running in a docker container it changed the ip address and I needed to update the shards metadata to use the new node, it works in almost every database.. but can't do it in _users.. Fauxton says: "Only reserved document ids may start with underscore" is there another way to update this databases? I tried to edit _dbs.couch with a hexadecimal editor, but this approach didn't work -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (COUCHDB-3236) update node metadata to use new node fails in _users
[ https://issues.apache.org/jira/browse/COUCHDB-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15667141#comment-15667141 ] Robert Newson commented on COUCHDB-3236: Two things conspire against us here, the longstanding prohibition of _ prefix document ids and the fact that the new 'dbs' metadata database uses a document named exactly the same as the database. For system databases like _users and _replicator we have special clauses to allow db creation/deletion. we need a similar set of exceptions for the respective documents within the 'dbs' db. I don't think you'll have much luck in a hex editor given the tricky on disk structure but kudos for trying. > update node metadata to use new node fails in _users > > > Key: COUCHDB-3236 > URL: https://issues.apache.org/jira/browse/COUCHDB-3236 > Project: CouchDB > Issue Type: Bug > Components: Database Core, Fauxton >Reporter: Anielkis Herrera > > When I restart a couchdb one node cluster running in a docker container it > changed the ip address and I needed to update the shards metadata to use the > new node, it works in almost every database.. but can't do it in _users.. > Fauxton says: "Only reserved document ids may start with underscore" > is there another way to update this databases? > I tried to edit _dbs.couch with a hexadecimal editor, but this approach > didn't work -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] couchdb-fauxton pull request #806: db-list: expose elements to make them reu...
Github user robertkowalski closed the pull request at: https://github.com/apache/couchdb-fauxton/pull/806 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-fauxton issue #806: db-list: expose elements to make them reusable
Github user robertkowalski commented on the issue: https://github.com/apache/couchdb-fauxton/pull/806 merged :) --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (COUCHDB-3236) update node metadata to use new node fails in _users
[ https://issues.apache.org/jira/browse/COUCHDB-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15667218#comment-15667218 ] Anielkis Herrera commented on COUCHDB-3236: --- Thanks, Robert, yes .. Couchdb appends new changes to the files.. but even if there was almost cero probability, I didn't lose anything trying I don't know erlang.. but if I can help ... just tell me > update node metadata to use new node fails in _users > > > Key: COUCHDB-3236 > URL: https://issues.apache.org/jira/browse/COUCHDB-3236 > Project: CouchDB > Issue Type: Bug > Components: Database Core, Fauxton >Reporter: Anielkis Herrera > > When I restart a couchdb one node cluster running in a docker container it > changed the ip address and I needed to update the shards metadata to use the > new node, it works in almost every database.. but can't do it in _users.. > Fauxton says: "Only reserved document ids may start with underscore" > is there another way to update this databases? > I tried to edit _dbs.couch with a hexadecimal editor, but this approach > didn't work -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (COUCHDB-3237) Shard remapping and underscores conflict
Robert Kowalski created COUCHDB-3237: Summary: Shard remapping and underscores conflict Key: COUCHDB-3237 URL: https://issues.apache.org/jira/browse/COUCHDB-3237 Project: CouchDB Issue Type: Bug Reporter: Robert Kowalski via irc: 14:08:45 < P0w3r3d> Hello.. when I restart a couchdb one node cluster running in a docker container it changed the ip address and I needed to update the shards metadata to use the new node, it works in almost every database.. but can't do it in _users.. Fauxton says: "Only reserved document ids may start with underscore" 14:09:11 < P0w3r3d> is there another way to update this databases? I tried to edit _dbs.couch with a hexadecimal editor, but this approach didn't work 14:10:46 < P0w3r3d> couchdb version 2.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] couchdb-fauxton issue #761: New replication
Github user robertkowalski commented on the issue: https://github.com/apache/couchdb-fauxton/pull/761 when i forget to add a database name to the url, it will still accept the url: remote target: ``` https://mypassw...@rockoartischocko.cloudant.com ``` expected: error that i have to specify a database name --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-fauxton issue #761: New replication
Github user robertkowalski commented on the issue: https://github.com/apache/couchdb-fauxton/pull/761 https://cloud.githubusercontent.com/assets/298166/20309147/28b87920-ab47-11e6-8fcc-bcd9cf9aa2dd.png";> typo: Replcator DB Activity. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-fauxton issue #761: New replication
Github user robertkowalski commented on the issue: https://github.com/apache/couchdb-fauxton/pull/761 update: discussed with garren, the validation shoudl happen on the serverside. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-fauxton issue #761: New replication
Github user robertkowalski commented on the issue: https://github.com/apache/couchdb-fauxton/pull/761 +1 after fixing the typo --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-fauxton issue #761: New replication
Github user robertkowalski commented on the issue: https://github.com/apache/couchdb-fauxton/pull/761 wow @garrensmith and @justin-mcdavid-ibm that is really cool stuff i am super excited --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Resolved] (COUCHDB-3237) Shard remapping and underscores conflict
[ https://issues.apache.org/jira/browse/COUCHDB-3237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kowalski resolved COUCHDB-3237. -- Resolution: Duplicate dupe of https://issues.apache.org/jira/browse/COUCHDB-3236 > Shard remapping and underscores conflict > > > Key: COUCHDB-3237 > URL: https://issues.apache.org/jira/browse/COUCHDB-3237 > Project: CouchDB > Issue Type: Bug >Reporter: Robert Kowalski > > via irc: > 14:08:45 < P0w3r3d> Hello.. when I restart a couchdb one node cluster running > in a docker container it changed the ip address and I needed to update the > shards metadata to use the new node, it works in almost > every database.. but can't do it in _users.. Fauxton says: "Only reserved > document ids may start with underscore" > 14:09:11 < P0w3r3d> is there another way to update this databases? I tried to > edit _dbs.couch with a hexadecimal editor, but this approach didn't work > 14:10:46 < P0w3r3d> couchdb version 2.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] couchdb-fauxton pull request #807: Couchdb 3224
GitHub user robertkowalski opened a pull request: https://github.com/apache/couchdb-fauxton/pull/807 Couchdb 3224 You can merge this pull request into a Git repository by running: $ git pull https://github.com/robertkowalski/couchdb-fauxton COUCHDB-3224 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/couchdb-fauxton/pull/807.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #807 commit 4017154f096e99baf062cf4ca85d4a726b681d16 Author: Sergey Safarov Date: 2016-11-06T10:04:42Z COUCHDB-3224: Fixed view displaying for database with "/" symbols in name commit cb3d45d86f98fcdda33ff18ba744624eb416bff0 Author: Robert Kowalski Date: 2016-11-15T15:59:43Z fix sidebar for databases with special chars COUCHDB-3229 commit fb30344302f199fdd06634c23b5be0c7bcaef427 Author: Robert Kowalski Date: 2016-11-15T16:04:19Z wip commit 2096dae28f13d149736ecd10acb1c3f524135c07 Author: Robert Kowalski Date: 2016-11-15T16:12:28Z fix issue for breadcrumbs and encoded db names COUCHDB-3146 commit 357180db7dbfa535f2a02ac62011e55ebe985a57 Author: Robert Kowalski Date: 2016-11-15T16:13:07Z encoding: fix cancel button in doc editor commit 0cf4b7485b2026f3af1eb142fb539bdd2e24671b Author: Robert Kowalski Date: 2016-11-15T16:17:06Z tests: seed databases with slash in name --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-fauxton issue #802: COUCHDB-3224: Fixed view displaying for database...
Github user robertkowalski commented on the issue: https://github.com/apache/couchdb-fauxton/pull/802 @sergey-safarov the PR looks good, it will be superseeded by https://github.com/apache/couchdb-fauxton/pull/807 which contains more fixes and changes our integration tests to default to database names with special chars. your commit will land seperately together with the other commits :) --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (COUCHDB-3224) Fauxton not correctly display database with "-" and "/" symbol in name
[ https://issues.apache.org/jira/browse/COUCHDB-3224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15667555#comment-15667555 ] ASF GitHub Bot commented on COUCHDB-3224: - Github user robertkowalski commented on the issue: https://github.com/apache/couchdb-fauxton/pull/802 @sergey-safarov the PR looks good, it will be superseeded by https://github.com/apache/couchdb-fauxton/pull/807 which contains more fixes and changes our integration tests to default to database names with special chars. your commit will land seperately together with the other commits :) > Fauxton not correctly display database with "-" and "/" symbol in name > -- > > Key: COUCHDB-3224 > URL: https://issues.apache.org/jira/browse/COUCHDB-3224 > Project: CouchDB > Issue Type: Bug > Components: Fauxton >Reporter: Sergey Safarov > > Fauxton cannot display database with "-" symbol in name and cannot display > view with "/" simbol in database name. > Tu reproduce execute "curl -X PUT > http://127.0.0.1:5984/mytest%2Fdata%2Fbase-201609"; ant try open this database > via fauxton. > Also if you create view for this database then this view wont work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] couchdb-fabric issue #78: 77984 upgrade mrargs record phase2
Github user davisp commented on the issue: https://github.com/apache/couchdb-fabric/pull/78 +1 for posterity. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-fauxton issue #761: New replication
Github user justin-mcdavid-ibm commented on the issue: https://github.com/apache/couchdb-fauxton/pull/761 Hey Garren, Great work. Thanks for all the effort that you put into this. The UI looks ready to go. Everything appears to be behaving as it should. +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-fauxton issue #807: Couchdb 3224
Github user sergey-safarov commented on the issue: https://github.com/apache/couchdb-fauxton/pull/807 @robertkowalski could you also look to case when file attachments can not be downloaded when database see contains "/" symbols. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (COUCHDB-3235) Replication with filters based on Mango selectors does not persist
[ https://issues.apache.org/jira/browse/COUCHDB-3235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668231#comment-15668231 ] Tony Sun commented on COUCHDB-3235: --- This seems to occur when using the _replicate endpoint. The replication persists when POSTing the document to the _replicator db. > Replication with filters based on Mango selectors does not persist > -- > > Key: COUCHDB-3235 > URL: https://issues.apache.org/jira/browse/COUCHDB-3235 > Project: CouchDB > Issue Type: Bug > Components: Mango, Replication >Affects Versions: 2.0.0 > Environment: Windows, Mac, Cloudant >Reporter: David Squier > > Issue found in CouchDB 2.0 involving using Mango query syntax selectors used > in filtered replication. Specifically, replication setup using mango query > syntax-based filters does not persist. > Conversely, using the older JavaScript-based filters in replication streams > appears to work as expected (i.e., they persist). > I've created a reproducible test-case on GitHub here: > https://github.com/dsquier/couchdb-mango-testcase > This test case has been confirmed in multiple environments, including: > - Windows 10 > - MacOS > - Cloudant -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (COUCHDB-3235) Replication with filters based on Mango selectors does not persist
[ https://issues.apache.org/jira/browse/COUCHDB-3235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668261#comment-15668261 ] Tony Sun commented on COUCHDB-3235: --- Upon further investigation...it doesn't seem like anything related to mango selectors. I removed the selector and started the replication without filtering and the same thing occurs. > Replication with filters based on Mango selectors does not persist > -- > > Key: COUCHDB-3235 > URL: https://issues.apache.org/jira/browse/COUCHDB-3235 > Project: CouchDB > Issue Type: Bug > Components: Mango, Replication >Affects Versions: 2.0.0 > Environment: Windows, Mac, Cloudant >Reporter: David Squier > > Issue found in CouchDB 2.0 involving using Mango query syntax selectors used > in filtered replication. Specifically, replication setup using mango query > syntax-based filters does not persist. > Conversely, using the older JavaScript-based filters in replication streams > appears to work as expected (i.e., they persist). > I've created a reproducible test-case on GitHub here: > https://github.com/dsquier/couchdb-mango-testcase > This test case has been confirmed in multiple environments, including: > - Windows 10 > - MacOS > - Cloudant -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (COUCHDB-3238) os_process_limit documentation wrong
Jay Doane created COUCHDB-3238: -- Summary: os_process_limit documentation wrong Key: COUCHDB-3238 URL: https://issues.apache.org/jira/browse/COUCHDB-3238 Project: CouchDB Issue Type: Bug Components: Documentation Reporter: Jay Doane http://docs.couchdb.org/en/2.0.0/config/query-servers.html#query_server_config/os_process_limit incorrectly states "Amount of time in seconds that the Query Server may process CouchDB command" But in fact the os_process_limit is the hard limit on the number of os processes created. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] couchdb-documentation pull request #88: Fix os_process_limit documentation
GitHub user jaydoane opened a pull request: https://github.com/apache/couchdb-documentation/pull/88 Fix os_process_limit documentation Update documentation with correct description of os_process_limit parameter function, correct default value, and hints for typical production values. COUCHDB-3238 You can merge this pull request into a Git repository by running: $ git pull https://github.com/cloudant/couchdb-documentation 3238-fix-os_process_limit-docs Alternatively you can review and apply these changes as the patch at: https://github.com/apache/couchdb-documentation/pull/88.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #88 commit e883c89f6b00edd48650dd951aca4c8ee321ef15 Author: Jay Doane Date: 2016-11-15T23:43:19Z Fix os_process_limit documentation Update documentation with correct description of os_process_limit parameter function, correct default value, and hints for typical production values. COUCHDB-3238 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (COUCHDB-3238) os_process_limit documentation wrong
[ https://issues.apache.org/jira/browse/COUCHDB-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668784#comment-15668784 ] ASF GitHub Bot commented on COUCHDB-3238: - GitHub user jaydoane opened a pull request: https://github.com/apache/couchdb-documentation/pull/88 Fix os_process_limit documentation Update documentation with correct description of os_process_limit parameter function, correct default value, and hints for typical production values. COUCHDB-3238 You can merge this pull request into a Git repository by running: $ git pull https://github.com/cloudant/couchdb-documentation 3238-fix-os_process_limit-docs Alternatively you can review and apply these changes as the patch at: https://github.com/apache/couchdb-documentation/pull/88.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #88 commit e883c89f6b00edd48650dd951aca4c8ee321ef15 Author: Jay Doane Date: 2016-11-15T23:43:19Z Fix os_process_limit documentation Update documentation with correct description of os_process_limit parameter function, correct default value, and hints for typical production values. COUCHDB-3238 > os_process_limit documentation wrong > > > Key: COUCHDB-3238 > URL: https://issues.apache.org/jira/browse/COUCHDB-3238 > Project: CouchDB > Issue Type: Bug > Components: Documentation >Reporter: Jay Doane > > http://docs.couchdb.org/en/2.0.0/config/query-servers.html#query_server_config/os_process_limit > incorrectly states "Amount of time in seconds that the Query Server may > process CouchDB command" > But in fact the os_process_limit is the hard limit on the number of os > processes created. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] couchdb-documentation pull request #88: Fix os_process_limit documentation
Github user rnewson commented on a diff in the pull request: https://github.com/apache/couchdb-documentation/pull/88#discussion_r8819 --- Diff: src/config/query-servers.rst --- @@ -82,16 +82,19 @@ Query Servers Configuration [query_server_config] commit_freq = 5 -.. config:option:: os_process_limit :: Query Server operation timeout +.. config:option:: os_process_limit :: Query Server process limit -Amount of time in seconds that the Query Server may process CouchDB -command:: +Hard limit on the number of OS processes usable by Query +Servers. The default value is ``25``:: [query_server_config] -os_process_limit = 10 +os_process_limit = 25 --- End diff -- the default is 100. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-documentation pull request #88: Fix os_process_limit documentation
Github user rnewson commented on a diff in the pull request: https://github.com/apache/couchdb-documentation/pull/88#discussion_r88144487 --- Diff: src/config/query-servers.rst --- @@ -82,16 +82,19 @@ Query Servers Configuration [query_server_config] commit_freq = 5 -.. config:option:: os_process_limit :: Query Server operation timeout +.. config:option:: os_process_limit :: Query Server process limit -Amount of time in seconds that the Query Server may process CouchDB -command:: +Hard limit on the number of OS processes usable by Query +Servers. The default value is ``25``:: [query_server_config] -os_process_limit = 10 +os_process_limit = 25 -CouchDB will raise `os_process_timeout` error and kill the process in -case the Query Server doesn't return any result within this limit. +Setting `os_process_limit` too low can result in starvation of +Query Servers, and manifest in `os_process_timeout` errors, +while setting it too high can potentially use too many system +resources. Production settings are typically 10-100 times the +default value. --- End diff -- could you add a section for os_process_soft_limit too? (also defaults to 100) --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-documentation issue #88: Fix os_process_limit documentation
Github user jaydoane commented on the issue: https://github.com/apache/couchdb-documentation/pull/88 While the internal default is indeed 100, it's set to 25 in rel/overlay/etc/default.ini -- so I guess it depends on what you mean by "default". I'm happy to change it to 100, though. Also, added a section on os_process_soft_limit, which could probably use better word-smithing. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (COUCHDB-3235) Replication with filters based on Mango selectors does not persist
[ https://issues.apache.org/jira/browse/COUCHDB-3235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668931#comment-15668931 ] Tony Sun commented on COUCHDB-3235: --- When we do _replicate with an "_id" in the post, the replication does not persist. > Replication with filters based on Mango selectors does not persist > -- > > Key: COUCHDB-3235 > URL: https://issues.apache.org/jira/browse/COUCHDB-3235 > Project: CouchDB > Issue Type: Bug > Components: Mango, Replication >Affects Versions: 2.0.0 > Environment: Windows, Mac, Cloudant >Reporter: David Squier > > Issue found in CouchDB 2.0 involving using Mango query syntax selectors used > in filtered replication. Specifically, replication setup using mango query > syntax-based filters does not persist. > Conversely, using the older JavaScript-based filters in replication streams > appears to work as expected (i.e., they persist). > I've created a reproducible test-case on GitHub here: > https://github.com/dsquier/couchdb-mango-testcase > This test case has been confirmed in multiple environments, including: > - Windows 10 > - MacOS > - Cloudant -- This message was sent by Atlassian JIRA (v6.3.4#6332)
