Actual Replication fell in 1

When one of servers in my cluster goes down, volume alarm says some of "Actual Replication" fell in 1. Replication Factor in Volume Properties is 3, so Actual Replication shouldn't fall in 1.

Do someone hit on the reason?

My MapR version is v. 1.2.2.12455.GA on CentOS 5.7 (Final).

Thank you.

maprfs

asked 23 Apr '12, 09:23

ueshin
1●1●1●1
accept rate: 0%

edited 23 Apr '12, 09:33

One Answer:

oldest newest most voted

You are right, the replication should not drop to 1 when a single server goes down. However, if the volume was already underreplicated for some reason, then some containers may only have a single copy left. If you give the command : maprcli dump volumeinfo -volumename <volumename> -json, this will give a list of all the containers in the volume and the status of the replicas. Do this to find out which containers are having problems.

link

answered 23 Apr '12, 09:47

steven
322●1●3
accept rate: 19%

Thank you for your reply. Now my cluster has fixed the problem so if next time it happen, I will check the status by the command.

(23 Apr '12, 10:00) ueshin

Your answer

toggle preview

community wiki

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

*italic* or __italic__
**bold** or __bold__
link:[text](http://url.com/ "title")
image?![alt text](/path/img.jpg "title")
numbered list: 1. Foo 2. Bar
to add a line break simply add two spaces to where you would like the new line to be.
basic HTML tags are also supported

learn more about Markdown

Tags:

maprfs ×48

Asked: 23 Apr '12, 09:23

Seen: 556 times

Last updated: 23 Apr '12, 10:00

Actual Replication fell in 1

Follow this question

Related questions