[jira] [Updated] (HBASE-16388) Prevent client threads being blocked by only one slow region server

[ https://issues.apache.org/jira/browse/HBASE-16388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-16388: -- Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: 1.4.0 2.0.0 St

[jira] [Commented] (HBASE-16620) Fix backup command-line tool usability issues

[ https://issues.apache.org/jira/browse/HBASE-16620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15490872#comment-15490872 ] stack commented on HBASE-16620: --- What of the issues were addressed by this patch? There is

[jira] [Commented] (HBASE-16165) Decrease RpcServer.callQueueSize before writeResponse causes OOM

[ https://issues.apache.org/jira/browse/HBASE-16165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15490880#comment-15490880 ] stack commented on HBASE-16165: --- Go for it [~Apache9] Bug fix. > Decrease RpcServer.callQu

[jira] [Commented] (HBASE-16613) Return the unused ByteBuffer to BoundedByteBufferPool when no cell is retrieved from the CellScanner

[ https://issues.apache.org/jira/browse/HBASE-16613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15490979#comment-15490979 ] stack commented on HBASE-16613: --- Agree > Return the unused ByteBuffer to BoundedByteBuffer

[jira] [Updated] (HBASE-16388) Prevent client threads being blocked by only one slow region server

[ https://issues.apache.org/jira/browse/HBASE-16388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-16388: -- Release Note: Add a new configuration, hbase.client.perserver.requests.threshold, to limit the max number of c

[jira] [Updated] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server

[ https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-10289: -- Release Note: Optional custom JMX server. Allows user to control the port used by JMX server (JMX is on RMI wh

[jira] [Commented] (HBASE-16631) Extract AsyncRequestFuture related code from AsyncProcess

[ https://issues.apache.org/jira/browse/HBASE-16631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15492077#comment-15492077 ] stack commented on HBASE-16631: --- OK. +1 I have no plan. Ijust thinking about what our asy

[jira] [Commented] (HBASE-16610) Unify append, increment with AP

[ https://issues.apache.org/jira/browse/HBASE-16610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15493166#comment-15493166 ] stack commented on HBASE-16610: --- Over on serverside, append and increment were unified. The

[jira] [Commented] (HBASE-16631) Extract AsyncRequestFuture related code from AsyncProcess

[ https://issues.apache.org/jira/browse/HBASE-16631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15493176#comment-15493176 ] stack commented on HBASE-16631: --- Is it in the set of flakey tests? > Extract AsyncRequestF

[jira] [Commented] (HBASE-16634) Speedup TestExportSnapshot

[ https://issues.apache.org/jira/browse/HBASE-16634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15493192#comment-15493192 ] stack commented on HBASE-16634: --- lgtm [~mbertozzi] Are the failures above related? > Speed

[jira] [Commented] (HBASE-16631) Extract AsyncRequestFuture related code from AsyncProcess

[ https://issues.apache.org/jira/browse/HBASE-16631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15493290#comment-15493290 ] stack commented on HBASE-16631: --- Says {code} [INFO] --- maven-surefire-plugin:2.18.1:test

[jira] [Commented] (HBASE-14328) WebUI error 500 table doesn't exist

[ https://issues.apache.org/jira/browse/HBASE-14328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15493308#comment-15493308 ] stack commented on HBASE-14328: --- done > WebUI error 500 table doesn't exist >

[jira] [Commented] (HBASE-16634) Speedup TestExportSnapshot

[ https://issues.apache.org/jira/browse/HBASE-16634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15493477#comment-15493477 ] stack commented on HBASE-16634: --- ok. +1 > Speedup TestExportSnapshot > ---

[jira] [Commented] (HBASE-16631) Extract AsyncRequestFuture related code from AsyncProcess

[ https://issues.apache.org/jira/browse/HBASE-16631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15493901#comment-15493901 ] stack commented on HBASE-16631: --- Did that change recently? > Extract AsyncRequestFuture re

[jira] [Resolved] (HBASE-16624) MVCC DeSerialization bug in the HFileScannerImpl

[ https://issues.apache.org/jira/browse/HBASE-16624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-16624. --- Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: 2.0.0 Pushed to master. I don't see this

[jira] [Commented] (HBASE-16631) Extract AsyncRequestFuture related code from AsyncProcess

[ https://issues.apache.org/jira/browse/HBASE-16631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15494935#comment-15494935 ] stack commented on HBASE-16631: --- I want to know if that setting changed recently? I am wond

[jira] [Commented] (HBASE-16644) Errors when reading legit HFile' Trailer on branch 1.3

[ https://issues.apache.org/jira/browse/HBASE-16644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15496255#comment-15496255 ] stack commented on HBASE-16644: --- Ouch. That looks like an ugly one to debug [~mantonov]. So

[jira] [Commented] (HBASE-16408) Handle On heap BucketCache size when HeapMemoryManager tunes memory

[ https://issues.apache.org/jira/browse/HBASE-16408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15496270#comment-15496270 ] stack commented on HBASE-16408: --- Will an on-heap bucketcache that does not make copies be f

[jira] [Updated] (HBASE-16631) Extract AsyncRequestFuture related code from AsyncProcess

[ https://issues.apache.org/jira/browse/HBASE-16631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-16631: -- Attachment: HBASE-16631.v2.patch Get another run in to see if the failures are related at all. > Extract Async

[jira] [Commented] (HBASE-16631) Extract AsyncRequestFuture related code from AsyncProcess

[ https://issues.apache.org/jira/browse/HBASE-16631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15496288#comment-15496288 ] stack commented on HBASE-16631: --- +1 on v1 (minus the pom change). Yeah, good idea making a

[jira] [Commented] (HBASE-16644) Errors when reading legit HFile' Trailer on branch 1.3

[ https://issues.apache.org/jira/browse/HBASE-16644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15497039#comment-15497039 ] stack commented on HBASE-16644: --- bq. Regardless of how such a file was written, still if we

[jira] [Updated] (HBASE-16264) Figure how to deal with endpoints and shaded pb

[ https://issues.apache.org/jira/browse/HBASE-16264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-16264: -- Attachment: HBASE-16264.master.008.patch > Figure how to deal with endpoints and shaded pb > --

[jira] [Commented] (HBASE-16264) Figure how to deal with endpoints and shaded pb

[ https://issues.apache.org/jira/browse/HBASE-16264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15501953#comment-15501953 ] stack commented on HBASE-16264: --- Tactic #4 seems to work: i.e. a copy of hbase-protocol rel

[jira] [Commented] (HBASE-16264) Figure how to deal with endpoints and shaded pb

[ https://issues.apache.org/jira/browse/HBASE-16264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15501981#comment-15501981 ] stack commented on HBASE-16264: --- Having trouble uploading 14.5MB patch to RB. Will work on

[jira] [Updated] (HBASE-16264) Figure how to deal with endpoints and shaded pb

[ https://issues.apache.org/jira/browse/HBASE-16264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-16264: -- Attachment: HBASE-16264.master.009.patch > Figure how to deal with endpoints and shaded pb > --

[jira] [Commented] (HBASE-16264) Figure how to deal with endpoints and shaded pb

[ https://issues.apache.org/jira/browse/HBASE-16264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15502631#comment-15502631 ] stack commented on HBASE-16264: --- I cut it by .8MB but still too big. More to do. New patch

[jira] [Commented] (HBASE-7612) [JDK8] Replace use of high-scale-lib counters with intrinsic facilities

[ https://issues.apache.org/jira/browse/HBASE-7612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15503865#comment-15503865 ] stack commented on HBASE-7612: -- Skimmed. Looks good. Counting is largest consumer of CPU so a

[jira] [Commented] (HBASE-16264) Figure how to deal with endpoints and shaded pb

[ https://issues.apache.org/jira/browse/HBASE-16264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15504507#comment-15504507 ] stack commented on HBASE-16264: --- Back up to 14.5MB. Won't go up on RB. Lets see how this ru

[jira] [Updated] (HBASE-16264) Figure how to deal with endpoints and shaded pb

[ https://issues.apache.org/jira/browse/HBASE-16264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-16264: -- Release Note: Shade/relocate the protobuf hbase uses internally. All core now refers to new module added in thi

[jira] [Updated] (HBASE-16264) Figure how to deal with endpoints and shaded pb

[ https://issues.apache.org/jira/browse/HBASE-16264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-16264: -- Attachment: HBASE-16264.master.010.patch > Figure how to deal with endpoints and shaded pb > --

[jira] [Commented] (HBASE-16264) Figure how to deal with endpoints and shaded pb

[ https://issues.apache.org/jira/browse/HBASE-16264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15504716#comment-15504716 ] stack commented on HBASE-16264: --- Good idea for getting patch up on rb. Thanks. > Figure ho

[jira] [Commented] (HBASE-16264) Figure how to deal with endpoints and shaded pb

[ https://issues.apache.org/jira/browse/HBASE-16264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15504749#comment-15504749 ] stack commented on HBASE-16264: --- Patch is just 2MB when I strip the generated content. Upda

[jira] [Updated] (HBASE-16264) Figure how to deal with endpoints and shaded pb

[ https://issues.apache.org/jira/browse/HBASE-16264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-16264: -- Attachment: HBASE-16264.master.011.patch > Figure how to deal with endpoints and shaded pb > --

[jira] [Commented] (HBASE-16134) Introduce Cell extension for server side.

[ https://issues.apache.org/jira/browse/HBASE-16134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15505832#comment-15505832 ] stack commented on HBASE-16134: --- So, if no Tags, we don't serialize any out. We are talking

[jira] [Commented] (HBASE-16134) Introduce Cell extension for server side.

[ https://issues.apache.org/jira/browse/HBASE-16134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15506953#comment-15506953 ] stack commented on HBASE-16134: --- When do we ever want to emit tags? When debugging? WAL wr

[jira] [Commented] (HBASE-16134) Introduce Cell extension for server side.

[ https://issues.apache.org/jira/browse/HBASE-16134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15507094#comment-15507094 ] stack commented on HBASE-16134: --- On #1, yeah, when is that Codec used? On #2, open a new R

[jira] [Commented] (HBASE-16134) Introduce Cell extension for server side.

[ https://issues.apache.org/jira/browse/HBASE-16134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15507150#comment-15507150 ] stack commented on HBASE-16134: --- Replication opens a new Reader, right, each time it replic

[jira] [Commented] (HBASE-15921) Add first AsyncTable impl and create TableImpl based on it

[ https://issues.apache.org/jira/browse/HBASE-15921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15507509#comment-15507509 ] stack commented on HBASE-15921: --- Our current client is bloated, hard to understand, uses to

[jira] [Commented] (HBASE-16264) Figure how to deal with endpoints and shaded pb

[ https://issues.apache.org/jira/browse/HBASE-16264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15507553#comment-15507553 ] stack commented on HBASE-16264: --- Chatting w/ Sean, the whitespace complaints against genera

[jira] [Commented] (HBASE-16650) Wrong usage of BlockCache eviction stat for heap memory tuning

[ https://issues.apache.org/jira/browse/HBASE-16650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15507567#comment-15507567 ] stack commented on HBASE-16650: --- Looking at the patch, can we update the description for th

[jira] [Updated] (HBASE-16264) Figure how to deal with endpoints and shaded pb

[ https://issues.apache.org/jira/browse/HBASE-16264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-16264: -- Attachment: HBASE-16264.master.012.patch > Figure how to deal with endpoints and shaded pb > --

[jira] [Commented] (HBASE-15638) Shade protobuf

[ https://issues.apache.org/jira/browse/HBASE-15638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15508044#comment-15508044 ] stack commented on HBASE-15638: --- Ok. Have a plan and patch for Endpoints in sub-task. Has d

[jira] [Commented] (HBASE-16264) Figure how to deal with endpoints and shaded pb

[ https://issues.apache.org/jira/browse/HBASE-16264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15508116#comment-15508116 ] stack commented on HBASE-16264: --- Tried a branch-1.x client against a master server with thi

[jira] [Commented] (HBASE-15921) Add first AsyncTable impl and create TableImpl based on it

[ https://issues.apache.org/jira/browse/HBASE-15921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15508198#comment-15508198 ] stack commented on HBASE-15921: --- Demo patch is interesting. We don't want to build a separa

[jira] [Updated] (HBASE-16264) Figure how to deal with endpoints and shaded pb

[ https://issues.apache.org/jira/browse/HBASE-16264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-16264: -- Attachment: HBASE-16264-Figure-how-to-deal-with-endpoints-and-sh.master.013.patch v013 Tried the failing test

[jira] [Commented] (HBASE-16654) Better handle channelInactive and close for netty rpc client

[ https://issues.apache.org/jira/browse/HBASE-16654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15509699#comment-15509699 ] stack commented on HBASE-16654: --- +1 Cleanup, class renames, and the continuation of the cal

[jira] [Commented] (HBASE-14734) BindException when setting up MiniKdc

[ https://issues.apache.org/jira/browse/HBASE-14734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15510943#comment-15510943 ] stack commented on HBASE-14734: --- This is great work. +1 This is an old issue that

[jira] [Commented] (HBASE-16676) All RPC requests serviced by PriorityRpcServer in some deploys after HBASE-13375

[ https://issues.apache.org/jira/browse/HBASE-16676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15513695#comment-15513695 ] stack commented on HBASE-16676: --- +1 on commit to branch-1.2. Most deploys carrying their lo

[jira] [Created] (HBASE-16689) Durability == ASYNC_WAL means no SYNC

stack created HBASE-16689: - Summary: Durability == ASYNC_WAL means no SYNC Key: HBASE-16689 URL: https://issues.apache.org/jira/browse/HBASE-16689 Project: HBase Issue Type: Bug Components:

[jira] [Commented] (HBASE-16689) Durability == ASYNC_WAL means no SYNC

[ https://issues.apache.org/jira/browse/HBASE-16689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15515385#comment-15515385 ] stack commented on HBASE-16689: --- h1. History We committed the below in time for 0.98.0: A

[jira] [Updated] (HBASE-16689) Durability == ASYNC_WAL means no SYNC

[ https://issues.apache.org/jira/browse/HBASE-16689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-16689: -- Description: Setting DURABILITY=ASYNC_WAL on a Table suspends all syncs for all table Table appends. If all ta

[jira] [Commented] (HBASE-16679) Flush throughput controller: Minor perf change and fix flaky TestFlushWithThroughputController

[ https://issues.apache.org/jira/browse/HBASE-16679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15516788#comment-15516788 ] stack commented on HBASE-16679: --- Excellent [~appy] +1 Lets try it. This is the flakey that

[jira] [Commented] (HBASE-16698) Performance issue: handlers stuck waiting for CountDownLatch inside WALKey#getWriteEntry under high writing workload

[ https://issues.apache.org/jira/browse/HBASE-16698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15517490#comment-15517490 ] stack commented on HBASE-16698: --- Thank you for digging in here [~carp84]. This bit I don't

[jira] [Commented] (HBASE-16698) Performance issue: handlers stuck waiting for CountDownLatch inside WALKey#getWriteEntry under high writing workload

[ https://issues.apache.org/jira/browse/HBASE-16698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15517531#comment-15517531 ] stack commented on HBASE-16698: --- Oh. Saw the patch. Why is this faster? I see an added reen

[jira] [Commented] (HBASE-16698) Performance issue: handlers stuck waiting for CountDownLatch inside WALKey#getWriteEntry under high writing workload

[ https://issues.apache.org/jira/browse/HBASE-16698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15517689#comment-15517689 ] stack commented on HBASE-16698: --- bq. Previously the CountDownLatch will be released one by

[jira] [Commented] (HBASE-16698) Performance issue: handlers stuck waiting for CountDownLatch inside WALKey#getWriteEntry under high writing workload

[ https://issues.apache.org/jira/browse/HBASE-16698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15517748#comment-15517748 ] stack commented on HBASE-16698: --- bq. So all CountDownLatch are released in sequential, no p

[jira] [Commented] (HBASE-16134) Introduce Cell extension for server side.

[ https://issues.apache.org/jira/browse/HBASE-16134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15519918#comment-15519918 ] stack commented on HBASE-16134: --- Sounds good. In a separate issue let us address tags curre

[jira] [Commented] (HBASE-16608) Introducing the ability to merge ImmutableSegments without copy-compaction or SQM usage

[ https://issues.apache.org/jira/browse/HBASE-16608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15521434#comment-15521434 ] stack commented on HBASE-16608: --- Did a pass on RB. Looks grand. Have we addressed the issue

[jira] [Commented] (HBASE-16684) The get() requests does not see locally buffered put() requests when autoflush is disabled

[ https://issues.apache.org/jira/browse/HBASE-16684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15521881#comment-15521881 ] stack commented on HBASE-16684: --- Yeah. What [~allan163] said. This is a duplicate of hbase

[jira] [Commented] (HBASE-16698) Performance issue: handlers stuck waiting for CountDownLatch inside WALKey#getWriteEntry under high writing workload

[ https://issues.apache.org/jira/browse/HBASE-16698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15521975#comment-15521975 ] stack commented on HBASE-16698: --- bq. but I don't think it's a good idea doing the same

[jira] [Commented] (HBASE-16698) Performance issue: handlers stuck waiting for CountDownLatch inside WALKey#getWriteEntry under high writing workload

[ https://issues.apache.org/jira/browse/HBASE-16698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15521978#comment-15521978 ] stack commented on HBASE-16698: --- On the patch, I'd be good w/ it going in as off by default

[jira] [Commented] (HBASE-16682) Fix Shell tests failure. NoClassDefFoundError for MiniKdc

[ https://issues.apache.org/jira/browse/HBASE-16682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15521985#comment-15521985 ] stack commented on HBASE-16682: --- +1 on this to fix the build. > Fix Shell tests failure. N

[jira] [Commented] (HBASE-16703) Explore object pooling of SeekerState

[ https://issues.apache.org/jira/browse/HBASE-16703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15521992#comment-15521992 ] stack commented on HBASE-16703: --- Any pictures to show us [~apurtell] w/ the hot allocations

[jira] [Commented] (HBASE-16644) Errors when reading legit HFile' Trailer on branch 1.3

[ https://issues.apache.org/jira/browse/HBASE-16644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15524001#comment-15524001 ] stack commented on HBASE-16644: --- Let me build a 0.92 and write a few examples of this file

[jira] [Commented] (HBASE-16725) Don't let flushThread hang in TestHRegion

[ https://issues.apache.org/jira/browse/HBASE-16725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15530592#comment-15530592 ] stack commented on HBASE-16725: --- The potentially hanging thread is real helpful. Sometimes

[jira] [Commented] (HBASE-16721) Concurrency issue in WAL unflushed seqId tracking

[ https://issues.apache.org/jira/browse/HBASE-16721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15531200#comment-15531200 ] stack commented on HBASE-16721: --- Good one. Rationale is reasonable. I like how 'no change',

[jira] [Commented] (HBASE-16727) Backup refactoring: move MR dependencies from HMaster

[ https://issues.apache.org/jira/browse/HBASE-16727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15531237#comment-15531237 ] stack commented on HBASE-16727: --- +1 from me. Thanks Vladimir. > Backup refactoring: move M

[jira] [Commented] (HBASE-16725) Don't let flushThread hang in TestHRegion

[ https://issues.apache.org/jira/browse/HBASE-16725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15531815#comment-15531815 ] stack commented on HBASE-16725: --- +1 I don't see how the failures are related given a patch

[jira] [Commented] (HBASE-16264) Figure how to deal with endpoints and shaded pb

[ https://issues.apache.org/jira/browse/HBASE-16264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15533292#comment-15533292 ] stack commented on HBASE-16264: --- New patch adds a hbase-endpoint module and moves all the b

[jira] [Commented] (HBASE-16721) Concurrency issue in WAL unflushed seqId tracking

[ https://issues.apache.org/jira/browse/HBASE-16721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15533672#comment-15533672 ] stack commented on HBASE-16721: --- Patch is excellent. +1. > Concurrency issue in WAL unflus

[jira] [Commented] (HBASE-16264) Figure how to deal with endpoints and shaded pb

[ https://issues.apache.org/jira/browse/HBASE-16264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15533774#comment-15533774 ] stack commented on HBASE-16264: --- Hmmm... I can't attach my patch. It is too big for JIRA. 2

[jira] [Commented] (HBASE-16264) Figure how to deal with endpoints and shaded pb

[ https://issues.apache.org/jira/browse/HBASE-16264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15533855#comment-15533855 ] stack commented on HBASE-16264: --- Pushed a dev branch HBASE-16264 Added a jenkins job HBASE

[jira] [Updated] (HBASE-16567) Upgrade to protobuf-3.1.x

[ https://issues.apache.org/jira/browse/HBASE-16567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-16567: -- Summary: Upgrade to protobuf-3.1.x (was: Upgrade to protobuf3) > Upgrade to protobuf-3.1.x > -

[jira] [Commented] (HBASE-16567) Upgrade to protobuf-3.1.x

[ https://issues.apache.org/jira/browse/HBASE-16567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15534177#comment-15534177 ] stack commented on HBASE-16567: --- pb3.1.0 just went out. On top of the current set of unsafe

[jira] [Updated] (HBASE-16567) Upgrade to protobuf-3.1.x

[ https://issues.apache.org/jira/browse/HBASE-16567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-16567: -- Attachment: 16567.patch Patch goes in nicely over the top of HBASE-16264 Regenerate all protos in this mod

[jira] [Commented] (HBASE-15638) Shade protobuf

[ https://issues.apache.org/jira/browse/HBASE-15638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15535165#comment-15535165 ] stack commented on HBASE-15638: --- Update: * HBASE-16264 subtask is good to go; does shadin

[jira] [Resolved] (HBASE-16517) Make a 1.2.3 release

[ https://issues.apache.org/jira/browse/HBASE-16517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-16517. --- Resolution: Fixed Assignee: stack Fix Version/s: 1.2.3 Resovling. Done. > Make a 1.2.3 relea

[jira] [Commented] (HBASE-16308) Contain protobuf references

[ https://issues.apache.org/jira/browse/HBASE-16308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15537150#comment-15537150 ] stack commented on HBASE-16308: --- Just to say that I have now gone back some from this idea

[jira] [Created] (HBASE-16741) Amend the generate protobufs out-of-band build step to include shade, pulling in protobuf source and a hook for patching protobuf

stack created HBASE-16741: - Summary: Amend the generate protobufs out-of-band build step to include shade, pulling in protobuf source and a hook for patching protobuf Key: HBASE-16741 URL: https://issues.apache.org/jira/b

[jira] [Commented] (HBASE-15638) Shade protobuf

[ https://issues.apache.org/jira/browse/HBASE-15638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15537173#comment-15537173 ] stack commented on HBASE-15638: --- HBASE-16741 subtask is about enhancing the build step to a

[jira] [Updated] (HBASE-16741) Amend the generate protobufs out-of-band build step to include shade, pulling in protobuf source and a hook for patching protobuf

[ https://issues.apache.org/jira/browse/HBASE-16741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-16741: -- Attachment: 16741.patch Here is patch. Means we are checking in protobuf src file. They have their 3-clause BS

[jira] [Created] (HBASE-16742) Add chapter for devs on how we do protobufs going forward

stack created HBASE-16742: - Summary: Add chapter for devs on how we do protobufs going forward Key: HBASE-16742 URL: https://issues.apache.org/jira/browse/HBASE-16742 Project: HBase Issue Type: Sub-t

[jira] [Created] (HBASE-16743) TestSimpleRpcScheduler#testCoDelScheduling is broke

stack created HBASE-16743: - Summary: TestSimpleRpcScheduler#testCoDelScheduling is broke Key: HBASE-16743 URL: https://issues.apache.org/jira/browse/HBASE-16743 Project: HBase Issue Type: Bug

[jira] [Commented] (HBASE-15536) Make AsyncFSWAL as our default WAL

[ https://issues.apache.org/jira/browse/HBASE-15536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15539179#comment-15539179 ] stack commented on HBASE-15536: --- I like the a anoop suggestion. Let's not have the mob fea

[jira] [Commented] (HBASE-15536) Make AsyncFSWAL as our default WAL

[ https://issues.apache.org/jira/browse/HBASE-15536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15539183#comment-15539183 ] stack commented on HBASE-15536: --- +1 as this on by default > Make AsyncFSWAL as our default

[jira] [Commented] (HBASE-15536) Make AsyncFSWAL as our default WAL

[ https://issues.apache.org/jira/browse/HBASE-15536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15539709#comment-15539709 ] stack commented on HBASE-15536: --- 2MB seems fine to get a warning at. In warning, it would s

[jira] [Updated] (HBASE-16742) Add chapter for devs on how we do protobufs going forward

[ https://issues.apache.org/jira/browse/HBASE-16742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-16742: -- Attachment: 16742.txt Patch on how protobuf works now and how it works in hbase-2.0.0. > Add chapter for devs

[jira] [Created] (HBASE-16756) InterfaceAudience annotate our protobuf; distinguish internal; publish public

stack created HBASE-16756: - Summary: InterfaceAudience annotate our protobuf; distinguish internal; publish public Key: HBASE-16756 URL: https://issues.apache.org/jira/browse/HBASE-16756 Project: HBase

[jira] [Updated] (HBASE-16756) InterfaceAudience annotate our protobuf; distinguish internal; publish public

[ https://issues.apache.org/jira/browse/HBASE-16756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-16756: -- Description: This is a follow-on from the work done over in HBASE-15638 Shade protobuf. Currently protobufs ar

[jira] [Created] (HBASE-16757) Integrate functionality currently done up as Coprocessor Endpoints into core.

stack created HBASE-16757: - Summary: Integrate functionality currently done up as Coprocessor Endpoints into core. Key: HBASE-16757 URL: https://issues.apache.org/jira/browse/HBASE-16757 Project: HBase

[jira] [Commented] (HBASE-16757) Integrate functionality currently done up as Coprocessor Endpoints into core.

[ https://issues.apache.org/jira/browse/HBASE-16757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15544376#comment-15544376 ] stack commented on HBASE-16757: --- These CPEPs are impure because they are not separable from

[jira] [Commented] (HBASE-15638) Shade protobuf

[ https://issues.apache.org/jira/browse/HBASE-15638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15544383#comment-15544383 ] stack commented on HBASE-15638: --- I just pushed the below set of patches: {code} HBASE-1

[jira] [Commented] (HBASE-16742) Add chapter for devs on how we do protobufs going forward

[ https://issues.apache.org/jira/browse/HBASE-16742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15544385#comment-15544385 ] stack commented on HBASE-16742: --- Pushed as part of the commit of parent: 95c1dc93fb6780f66f

[jira] [Resolved] (HBASE-16742) Add chapter for devs on how we do protobufs going forward

[ https://issues.apache.org/jira/browse/HBASE-16742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-16742. --- Resolution: Fixed Fix Version/s: 2.0.0 Resolving. > Add chapter for devs on how we do protobufs going

[jira] [Updated] (HBASE-16264) Figure how to deal with endpoints and shaded pb

[ https://issues.apache.org/jira/browse/HBASE-16264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-16264: -- Resolution: Fixed Release Note: Shade/relocate the protobuf hbase uses internally. All core now refers to

[jira] [Resolved] (HBASE-16741) Amend the generate protobufs out-of-band build step to include shade, pulling in protobuf source and a hook for patching protobuf

[ https://issues.apache.org/jira/browse/HBASE-16741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-16741. --- Resolution: Fixed Fix Version/s: 2.0.0 Pushed as part of parent commit on 95c1dc93fb6780f66fd8ebb57914

[jira] [Updated] (HBASE-15638) Shade protobuf

[ https://issues.apache.org/jira/browse/HBASE-15638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-15638: -- Resolution: Fixed Fix Version/s: 2.0.0 Release Note: Shade/relocate and include the protobuf we use

[jira] [Updated] (HBASE-16567) Upgrade to protobuf-3.1.x

[ https://issues.apache.org/jira/browse/HBASE-16567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-16567: -- Resolution: Fixed Fix Version/s: 2.0.0 Release Note: Core is now up on protobuf 3.1.0 (Coprocessor E

[jira] [Commented] (HBASE-15638) Shade protobuf

[ https://issues.apache.org/jira/browse/HBASE-15638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15544418#comment-15544418 ] stack commented on HBASE-15638: --- The above set of patches passed the jenkins build I'd made

[jira] [Commented] (HBASE-16742) Add chapter for devs on how we do protobufs going forward

[ https://issues.apache.org/jira/browse/HBASE-16742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15544426#comment-15544426 ] stack commented on HBASE-16742: --- Thanks [~anoop.hbase] I pushed an amendment. > Add chapte

<    13   14   15   16   17   18   19   20   21   22   >