abdasgupta commented on issue #68: Provide and publish ppc64le images
URL: https://github.com/apache/couchdb-docker/issues/68#issuecomment-391670042
Hi @wohali Currently I am pursuing this task. Can I get an update on the
progress of this issue??
iilyak commented on issue #1338: Configuring node "flavors" in a cluster
URL: https://github.com/apache/couchdb/issues/1338#issuecomment-391691432
I think that we need to specialize type of nodes for following reasons:
1. we want to modernize CouchDB API and deprecate not scalable
ericdai opened a new issue #1339: if will support arm
URL: https://github.com/apache/couchdb/issues/1339
## Expected Behavior
## Current Behavior
## Possible Solution
## Steps to Reproduce (for bugs)
1.
2.
3.
4.
wohali closed issue #1339: if will support arm linux?
URL: https://github.com/apache/couchdb/issues/1339
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
wohali commented on issue #68: Provide and publish ppc64le images
URL: https://github.com/apache/couchdb-docker/issues/68#issuecomment-391749321
Still blocked by everything stated in my last update.
This is an automated
abdasgupta commented on issue #68: Provide and publish ppc64le images
URL: https://github.com/apache/couchdb-docker/issues/68#issuecomment-391761181
Hi @wohali , Can we work to solve the first problem of the list at first?
Can I know what is to be done yet to close the first problem?
wohali commented on issue #68: Provide and publish ppc64le images
URL: https://github.com/apache/couchdb-docker/issues/68#issuecomment-391770967
Start with: If you have access to a ppc64le machine, run `make check` and
confirm that all tests pass. If some fail, log them here:
wohali commented on issue #1339: if will support arm linux?
URL: https://github.com/apache/couchdb/issues/1339#issuecomment-391749726
Duplicate of #1103 and #892.
This is an automated message from the Apache Git Service.
To
wohali commented on issue #1340: View creation failed on CentOS 7 - CouchDB
2.1.1
URL: https://github.com/apache/couchdb/issues/1340#issuecomment-391826998
Duplicate of #1293.
This is an automated message from the Apache Git
wohali closed issue #1340: View creation failed on CentOS 7 - CouchDB 2.1.1
URL: https://github.com/apache/couchdb/issues/1340
This is an automated message from the Apache Git Service.
To respond to the message, please log
plcollard opened a new issue #1340: View creation failed on CentOS 7 - CouchDB
2.1.1
URL: https://github.com/apache/couchdb/issues/1340
CouchDB failed to create views on fresh and updated server with CentOS 7.
## Expected Behavior
Verification of the setup should work .
##
pzduniak opened a new issue #1341: CouchDB degrades and starts timeouting on
all index operations
URL: https://github.com/apache/couchdb/issues/1341
## Expected Behavior
CouchDB should start up with ~100 records in its databases and ~14 views.
2.1.1 in Docker. Doesn't work as both root
[
https://issues.apache.org/jira/browse/COUCHDB-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489870#comment-16489870
]
ASF subversion and git services commented on COUCHDB-3326:
--
Commit
[
https://issues.apache.org/jira/browse/COUCHDB-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489877#comment-16489877
]
ASF subversion and git services commented on COUCHDB-3326:
--
Commit
[
https://issues.apache.org/jira/browse/COUCHDB-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489878#comment-16489878
]
ASF subversion and git services commented on COUCHDB-3326:
--
Commit
wohali commented on issue #1341: CouchDB degrades and starts timeouting on all
index operations
URL: https://github.com/apache/couchdb/issues/1341#issuecomment-391861526
How are you launching your container? What is your host's CPU/RAM/disk setup?
I don't have time to look at your
wohali closed issue #1341: CouchDB degrades and starts timeouting on all index
operations
URL: https://github.com/apache/couchdb/issues/1341
This is an automated message from the Apache Git Service.
To respond to the
[
https://issues.apache.org/jira/browse/COUCHDB-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489880#comment-16489880
]
ASF subversion and git services commented on COUCHDB-3326:
--
Commit
[
https://issues.apache.org/jira/browse/COUCHDB-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489871#comment-16489871
]
ASF subversion and git services commented on COUCHDB-3326:
--
Commit
[
https://issues.apache.org/jira/browse/COUCHDB-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489872#comment-16489872
]
ASF subversion and git services commented on COUCHDB-3326:
--
Commit
[
https://issues.apache.org/jira/browse/COUCHDB-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489875#comment-16489875
]
ASF subversion and git services commented on COUCHDB-3326:
--
Commit
[
https://issues.apache.org/jira/browse/COUCHDB-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489873#comment-16489873
]
ASF subversion and git services commented on COUCHDB-3326:
--
Commit
[
https://issues.apache.org/jira/browse/COUCHDB-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489874#comment-16489874
]
ASF subversion and git services commented on COUCHDB-3326:
--
Commit
[
https://issues.apache.org/jira/browse/COUCHDB-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489879#comment-16489879
]
ASF subversion and git services commented on COUCHDB-3326:
--
Commit
pzduniak commented on issue #1341: CouchDB degrades and starts timeouting on
all index operations
URL: https://github.com/apache/couchdb/issues/1341#issuecomment-39103
Let me rephrase: the database doesn't start at all. The view functionality
is dead. This should not happen. This is
pzduniak commented on issue #1341: CouchDB degrades and starts timeouting on
all index operations
URL: https://github.com/apache/couchdb/issues/1341#issuecomment-391889983
Alright, what the hell, if CouchDB can't even start on a single core (it
worked just fine on 1.x), then why is this
wohali commented on issue #1341: CouchDB degrades and starts timeouting on all
index operations
URL: https://github.com/apache/couchdb/issues/1341#issuecomment-391900971
@pzduniak I'll remind you we have a [Code of
Conduct](https://couchdb.apache.org/conduct.html) at this project. Please
pzduniak commented on issue #1341: CouchDB degrades and starts timeouting on
all index operations
URL: https://github.com/apache/couchdb/issues/1341#issuecomment-391888317
>How are you launching your container?
Default Docker image params + my small script, basically the
pzduniak commented on issue #1341: CouchDB degrades and starts timeouting on
all index operations
URL: https://github.com/apache/couchdb/issues/1341#issuecomment-391888317
>How are you launching your container?
Default Docker image params + my small script, basically the
pzduniak commented on issue #1341: CouchDB degrades and starts timeouting on
all index operations
URL: https://github.com/apache/couchdb/issues/1341#issuecomment-391945581
Thank you, limiting the process count seems to work. But:
1) What's up with the sudden CoC mention? Are we
30 matches
Mail list logo
