Github user kxepal commented on the pull request:

    https://github.com/apache/couchdb-fabric/pull/9#issuecomment-151500252
  
    @rnewson @eiri are you sure about? I replicated db from 1.6.1 to 2.0:
    ```
    $ http --json http://localhost:5984/db
    HTTP/1.1 200 OK
    Cache-Control: must-revalidate
    Content-Length: 241
    Content-Type: application/json
    Date: Tue, 27 Oct 2015 13:38:57 GMT
    Server: CouchDB/1.6.1 (Erlang OTP/18)
    
    {
        "committed_update_seq": 234,
        "compact_running": false,
        "data_size": 60152397,
        "db_name": "db",
        "disk_format_version": 6,
        "disk_size": 60702831,
        "doc_count": 143,
        "doc_del_count": 38,
        "instance_start_time": "1445950447181052",
        "purge_seq": 0,
        "update_seq": 234
    }
    
     $ http --json http://localhost:15984/db
    HTTP/1.1 200 OK
    Cache-Control: must-revalidate
    Content-Length: 464
    Content-Type: application/json
    Date: Tue, 27 Oct 2015 13:38:29 GMT
    Server: CouchDB/acfd7cb (Erlang OTP/18)
    X-Couch-Request-ID: 961f1dd096
    X-CouchDB-Body-Time: 0
    
    {
        "compact_running": false,
        "data_size": 60306985,
        "db_name": "db",
        "disk_format_version": 6,
        "disk_size": 62031400,
        "doc_count": 143,
        "doc_del_count": 38,
        "instance_start_time": "0",
        "other": {
            "data_size": 60142259
        },
        "purge_seq": 0,
        "sizes": {
            "active": 60306985,
            "external": 60142259,
            "file": 62031400
        },
        "update_seq": 
"227-g1AAAAFDeJzLYWBg4MhgTmHgz8tPSTV0MDQy1zMAQsMcoARTIkOS_P___7MSJXAqSVIAkkn2YFVquFU5gFTFg1VJ41aVAFJVD1aljFNVHguQZGgAUkCF87MShQmoXABRuT8rUZSAygMQlfezEhUIqHwAUQl0p3wWAKDvV1k"
    }
    ```
    
    All sizes looks the same and applying 
`fabric_view:remove_overlapping_shards(Shard, C1)` doesn't changes them. How to 
reproduce that issue?


---
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 [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to