[
https://issues.apache.org/jira/browse/HBASE-14623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15015245#comment-15015245
]
stack commented on HBASE-14623:
-------------------------------
[~mbertozzi] On the failure above, I see this in log only:
https://builds.apache.org/job/PreCommit-HBASE-Build/16602/artifact/hbase/hbase-procedure/target/surefire-reports/org.apache.hadoop.hbase.procedure2.store.wal.TestWALProcedureStore-output.txt
Is that what you'd expect?
[~tedyu] Suggest add to the description here why would want to do something as
extreme as a WAL per system tables -- currently points at parent issue and
points at Stephen 'suggestion'. Would think would need more than a 'suggestion'
to bring on such a significant change. How about also listing them all out,
their rate of change, size, etc.
> Implement dedicated WAL for system tables
> -----------------------------------------
>
> Key: HBASE-14623
> URL: https://issues.apache.org/jira/browse/HBASE-14623
> Project: HBase
> Issue Type: Sub-task
> Reporter: Ted Yu
> Assignee: Ted Yu
> Fix For: 2.0.0
>
> Attachments: 14623-v1.txt, 14623-v2.txt, 14623-v2.txt, 14623-v2.txt,
> 14623-v2.txt
>
>
> As Stephen suggested in parent JIRA, dedicating separate WAL for system
> tables (other than hbase:meta) should be done in new JIRA.
> This task is to fulfill the system WAL separation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
