Sakthi commented on HBASE-18864:

Hey, [~stack]. Please share your thoughts on this.

I am looking into writing test cases.

The thought process while setting scope as '1' was that when a user puts a 
non-zero value, then probably the user wanted the replication to be a part? 
Hence the '1'. But seeing it the other way, shutting down the replication by 
setting the scope to '0' would be a safer option as it would help in cases 
where '5' was a mere typo or such. 

To tackle the problem of flooding log files when a user puts in a large number 
of writes with bad scope, should the log messages be put to "LOG.debug" 
instead, or checking for redundant log message before putting in another 
"LOG.warn" would be a better option?


> NullPointerException thrown when adding rows to a table from peer cluster, 
> table with replication factor other than 0 or 1
> --------------------------------------------------------------------------------------------------------------------------
>                 Key: HBASE-18864
>                 URL: https://issues.apache.org/jira/browse/HBASE-18864
>             Project: HBase
>          Issue Type: Bug
>          Components: hbase
>    Affects Versions: 1.3.0
>            Reporter: smita
>            Assignee: Sakthi
>            Priority: Major
>              Labels: beginner
>         Attachments: hbase-18864.branch-1.2.001.patch
> Scenario:
> =============
> add_peer
> create a table
> alter table with REPLICATION_SCOPE => '5'
> enable table replication
> login to peer cluster and try putting data to the table 

This message was sent by Atlassian JIRA

Reply via email to