{"action":"created","issue":{"url":"https://api.github.com/repos/minio/minio/issues/2685","repository_url":"https://api.github.com/repos/minio/minio","labels_url":"https://api.github.com/repos/minio/minio/issues/2685/labels{/name}","comments_url":"https://api.github.com/repos/minio/minio/issues/2685/comments","events_url":"https://api.github.com/repos/minio/minio/issues/2685/events","html_url":"https://github.com/minio/minio/issues/2685","id":176706956,"number":2685,"title":"[distributed] get-bucket-location hangs when N/2 servers are down","user":{"login":"krishnasrinivas","id":634494,"avatar_url":"https://avatars.githubusercontent.com/u/634494?v=3","gravatar_id":"","url":"https://api.github.com/users/krishnasrinivas","html_url":"https://github.com/krishnasrinivas","followers_url":"https://api.github.com/users/krishnasrinivas/followers","following_url":"https://api.github.com/users/krishnasrinivas/following{/other_user}","gists_url":"https://api.github.com/users/krishnasrinivas/gists{/gist_id}","starred_url":"https://api.github.com/users/krishnasrinivas/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/krishnasrinivas/subscriptions","organizations_url":"https://api.github.com/users/krishnasrinivas/orgs","repos_url":"https://api.github.com/users/krishnasrinivas/repos","events_url":"https://api.github.com/users/krishnasrinivas/events{/privacy}","received_events_url":"https://api.github.com/users/krishnasrinivas/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/minio/minio/labels/bug","name":"bug","color":"fc2929"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2016-09-13T17:54:25Z","updated_at":"2016-09-13T19:16:54Z","closed_at":null,"body":"* start 3:3 minio distributed XL \r\n* copy a file into a bucket\r\n* bring down 3 minio instances\r\n* mc cat on the copied file hangs\r\n\r\nThis is the call that hangs:\r\n```\r\nREQUEST : GET path:/testbucket/?location=\r\nHost: 127.0.0.1:9000\r\nX-Amz-Date: 20160913T175226Z\r\nAccept-Encoding: gzip\r\nUser-Agent: Minio (linux; amd64) minio-go/2.0.1 mc/DEVELOPMENT.GOGET\r\nAuthorization: AWS4-HMAC-SHA256 Credential=SXO8VW2OFKKP2OG7AC85/20160913/us-east-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=4e1457da2e6092c8f4df2744d94b8241523fd16d597b74836a5b80be4b5048d8\r\nX-Amz-Content-Sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855\r\n\r\n\r\n```\r\n"},"comment":{"url":"https://api.github.com/repos/minio/minio/issues/comments/246792849","html_url":"https://github.com/minio/minio/issues/2685#issuecomment-246792849","issue_url":"https://api.github.com/repos/minio/minio/issues/2685","id":246792849,"user":{"login":"krisis","id":522593,"avatar_url":"https://avatars.githubusercontent.com/u/522593?v=3","gravatar_id":"","url":"https://api.github.com/users/krisis","html_url":"https://github.com/krisis","followers_url":"https://api.github.com/users/krisis/followers","following_url":"https://api.github.com/users/krisis/following{/other_user}","gists_url":"https://api.github.com/users/krisis/gists{/gist_id}","starred_url":"https://api.github.com/users/krisis/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/krisis/subscriptions","organizations_url":"https://api.github.com/users/krisis/orgs","repos_url":"https://api.github.com/users/krisis/repos","events_url":"https://api.github.com/users/krisis/events{/privacy}","received_events_url":"https://api.github.com/users/krisis/received_events","type":"User","site_admin":false},"created_at":"2016-09-13T19:16:54Z","updated_at":"2016-09-13T19:16:54Z","body":"@harshavardhana The erasure code algorithm is capable of reconstructing data in the absence of up to N/2 disks. But to provide a consistent view of data, we need quorum (N/2+1) or more number of disks to be in agreement with the data that is being served. It makes sense to 'hang' the reads in favour of consistency. It isn't data loss, it is temporary data unavailability. if we replaced one of the disks, with a fresh one, we can read data without a 'hang'. Would it make sense to document this as the expected behaviour? "}}
{"actor":{"display_login":"krisis"}}