hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ChiaPing Tsai (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-17174) Refactor the AsyncProcess, BufferedMutatorImpl, and HTable
Date Sat, 17 Dec 2016 09:40:58 GMT

     [ https://issues.apache.org/jira/browse/HBASE-17174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

ChiaPing Tsai updated HBASE-17174:
----------------------------------
    Description: 
The following are reasons of refactoring.
# A update-heavy application, for example, loader, creates many BufferedMutator for batch
updates. But these BufferedMutators can’t share a large threadpool because the shutdown()
method will be called when closing any BufferedMutator. This patch adds a flag into BufferedMutatorParams
for preventing calling the shutdown() method in BufferedMutatorImpl#close
# The AsyncProcess has the powerful traffic control, but the control is against the single
table currently. We should allow alternate traffic control implementation for advanced user
who want more control.

All suggestions are welcome.


  was:
The following are reasons of refactoring the AP.
# A update-heavy application, for example, loader, creates many BufferedMutator for batch
updates. But these BufferedMutators can’t share a large threadpool because the shutdown()
method will be called when closing any BufferedMutator. This patch adds a flag into BufferedMutatorParams
for preventing calling the shutdown() method in BufferedMutatorImpl#close
# The AsyncProcess has the powerful traffic control, but the control is against the single
table currently. We should allow alternate traffic control implementation for advanced user
who want more control.

All suggestions are welcome.



> Refactor the AsyncProcess, BufferedMutatorImpl, and HTable
> ----------------------------------------------------------
>
>                 Key: HBASE-17174
>                 URL: https://issues.apache.org/jira/browse/HBASE-17174
>             Project: HBase
>          Issue Type: New Feature
>    Affects Versions: 2.0.0
>            Reporter: ChiaPing Tsai
>            Assignee: ChiaPing Tsai
>            Priority: Minor
>             Fix For: 2.0.0
>
>         Attachments: HBASE-17174.v0.patch, HBASE-17174.v1.patch, HBASE-17174.v10.patch,
HBASE-17174.v11.patch, HBASE-17174.v11.patch, HBASE-17174.v11.patch, HBASE-17174.v2.patch,
HBASE-17174.v3.patch, HBASE-17174.v4.patch, HBASE-17174.v5.patch, HBASE-17174.v6.patch, HBASE-17174.v7.patch,
HBASE-17174.v8.patch, HBASE-17174.v9.patch
>
>
> The following are reasons of refactoring.
> # A update-heavy application, for example, loader, creates many BufferedMutator for batch
updates. But these BufferedMutators can’t share a large threadpool because the shutdown()
method will be called when closing any BufferedMutator. This patch adds a flag into BufferedMutatorParams
for preventing calling the shutdown() method in BufferedMutatorImpl#close
> # The AsyncProcess has the powerful traffic control, but the control is against the single
table currently. We should allow alternate traffic control implementation for advanced user
who want more control.
> All suggestions are welcome.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message