Skip to content
This repository has been archived by the owner on Sep 19, 2019. It is now read-only.

Commit

Permalink
Fix rexi_EXIT handling for db/group info and doc_count
Browse files Browse the repository at this point in the history
  • Loading branch information
kocolosk committed Feb 9, 2012
1 parent 8fea39c commit e479a04
Show file tree
Hide file tree
Showing 3 changed files with 5 additions and 5 deletions.
2 changes: 1 addition & 1 deletion src/fabric_db_doc_count.erl
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ handle_message({rexi_DOWN, _, {_,NodeRef},_}, _Shard, {Counters, Acc}) ->
end;

handle_message({rexi_EXIT, Reason}, Shard, {Counters, Acc}) ->
NewCounters = lists:keydelete(Shard, 1, Counters),
NewCounters = lists:keydelete(Shard, #shard.ref, Counters),
case fabric_view:is_progress_possible(NewCounters) of
true ->
{ok, {NewCounters, Acc}};
Expand Down
4 changes: 2 additions & 2 deletions src/fabric_db_info.erl
Original file line number Diff line number Diff line change
Expand Up @@ -39,8 +39,8 @@ handle_message({rexi_DOWN, _, {_,NodeRef},_}, _Shard, {Counters, Acc}) ->
end;

handle_message({rexi_EXIT, Reason}, Shard, {Counters, Acc}) ->
NewCounters = lists:keydelete(Shard,1,Counters),
case fabric_view:is_progress_possible(Counters) of
NewCounters = lists:keydelete(Shard, #shard.ref, Counters),
case fabric_view:is_progress_possible(NewCounters) of
true ->
{ok, {NewCounters, Acc}};
false ->
Expand Down
4 changes: 2 additions & 2 deletions src/fabric_group_info.erl
Original file line number Diff line number Diff line change
Expand Up @@ -45,8 +45,8 @@ handle_message({rexi_DOWN, _, {_,NodeRef},_}, _Shard, {Counters, Acc}) ->
end;

handle_message({rexi_EXIT, Reason}, Shard, {Counters, Acc}) ->
NewCounters = lists:keydelete(Shard,1,Counters),
case fabric_view:is_progress_possible(Counters) of
NewCounters = lists:keydelete(Shard, #shard.ref, Counters),
case fabric_view:is_progress_possible(NewCounters) of
true ->
{ok, {NewCounters, Acc}};
false ->
Expand Down

0 comments on commit e479a04

Please sign in to comment.