[jira] [Commented] (HBASE-19046) RegionObserver#postCompactSelection Passing an ImmutableList param of PB type
[ https://issues.apache.org/jira/browse/HBASE-19046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214687#comment-16214687 ] Anoop Sam John commented on HBASE-19046: Test failure seems not at all related.. [~chia7712] May I consider ur +1 as commit +1 for this patch? > RegionObserver#postCompactSelection Passing an ImmutableList param of PB type > -- > > Key: HBASE-19046 > URL: https://issues.apache.org/jira/browse/HBASE-19046 > Project: HBase > Issue Type: Sub-task > Components: Coprocessors >Reporter: Anoop Sam John >Assignee: Anoop Sam John > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-19046.patch, HBASE-19046.patch > > > Dont think there is any specific need for passing this PB type. We can just > pass an unmodifiableList list object. Javadoc can say this is an > unmodifiableList . Thats it . No need that the type itself to be > Immutable... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19021) Restore a few important missing logics for balancer in 2.0
[
https://issues.apache.org/jira/browse/HBASE-19021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214636#comment-16214636
]
Jerry He commented on HBASE-19021:
--
Are you good with the patch? [~stack], [~yuzhih...@gmail.com]
Any other comment from others?
> Restore a few important missing logics for balancer in 2.0
> --
>
> Key: HBASE-19021
> URL: https://issues.apache.org/jira/browse/HBASE-19021
> Project: HBase
> Issue Type: Bug
>Reporter: Jerry He
>Assignee: Jerry He
>Priority: Critical
> Attachments: HBASE-19021-master-v2.patch, HBASE-19021-master.patch,
> HBASE-19021-master.patch
>
>
> After looking at the code, and some testing, I see the following things are
> missing for balancer to work properly after AMv2.
> # hbase.master.loadbalance.bytable is not respected. It is always 'bytable'.
> Previous default is cluster wide, not by table.
> # Servers with no assignments is not added for balance consideration.
> # Crashed server is not removed from the in-memory server map in
> RegionStates, which affects balance.
> # Draining marker is not respected when balance.
> Also try to re-enable {{TestRegionRebalancing}}, which has a
> {{testRebalanceOnRegionServerNumberChange}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19021) Restore a few important missing logics for balancer in 2.0
[
https://issues.apache.org/jira/browse/HBASE-19021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry He updated HBASE-19021:
-
Attachment: HBASE-19021-master-v2.patch
v2 addressed [~yuzhih...@gmail.com]'s earlier comment.
> Restore a few important missing logics for balancer in 2.0
> --
>
> Key: HBASE-19021
> URL: https://issues.apache.org/jira/browse/HBASE-19021
> Project: HBase
> Issue Type: Bug
>Reporter: Jerry He
>Assignee: Jerry He
>Priority: Critical
> Attachments: HBASE-19021-master-v2.patch, HBASE-19021-master.patch,
> HBASE-19021-master.patch
>
>
> After looking at the code, and some testing, I see the following things are
> missing for balancer to work properly after AMv2.
> # hbase.master.loadbalance.bytable is not respected. It is always 'bytable'.
> Previous default is cluster wide, not by table.
> # Servers with no assignments is not added for balance consideration.
> # Crashed server is not removed from the in-memory server map in
> RegionStates, which affects balance.
> # Draining marker is not respected when balance.
> Also try to re-enable {{TestRegionRebalancing}}, which has a
> {{testRebalanceOnRegionServerNumberChange}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18984) [AMv2] Retain assignment does not work well in AMv2
[ https://issues.apache.org/jira/browse/HBASE-18984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214629#comment-16214629 ] ramkrishna.s.vasudevan commented on HBASE-18984: Pls see https://issues.apache.org/jira/browse/HBASE-18352. > [AMv2] Retain assignment does not work well in AMv2 > --- > > Key: HBASE-18984 > URL: https://issues.apache.org/jira/browse/HBASE-18984 > Project: HBase > Issue Type: Bug > Components: proc-v2 >Affects Versions: 2.0.0 >Reporter: Yi Liang >Assignee: Yi Liang > Fix For: 2.0.0 > > Attachments: HBASE-18984-V1-master.patch, Screen Shot 2017-10-10 at > 2.24.19 PM.png > > > work on 8.17 Retain assignment in > https://docs.google.com/document/d/1eVKa7FHdeoJ1-9o8yZcOTAQbv0u0bblBlCCzVSIn69g/edit#heading=h.epjn9nege80k > To reproduce this error, in hbase shell: > createTable t1 --> list_regions 't1' --> disable 't1' ---> enable 't1' --> > list_reigons 't1' (maybe you need to try enable/disable multiple times) > See attached images. same region assigned to different region servers -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18352) Enable Replica tests that were disabled by Proc-V2 AM in HBASE-14614
[ https://issues.apache.org/jira/browse/HBASE-18352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214627#comment-16214627 ] ramkrishna.s.vasudevan commented on HBASE-18352: This is probably because of https://issues.apache.org/jira/browse/HBASE-18984. Ping - [~easyliangjob] > Enable Replica tests that were disabled by Proc-V2 AM in HBASE-14614 > > > Key: HBASE-18352 > URL: https://issues.apache.org/jira/browse/HBASE-18352 > Project: HBase > Issue Type: Bug > Components: test >Affects Versions: 2.0.0-alpha-1 >Reporter: Stephen Yuan Jiang >Assignee: huaxiang sun > > The following replica tests were disabled by Core Proc-V2 AM in HBASE-14614: > - Disabled parts of...testCreateTableWithMultipleReplicas in > TestMasterOperationsForRegionReplicas There is an issue w/ assigning more > replicas if number of replicas is changed on us. See '/* DISABLED! FOR > NOW'. > - Disabled testRegionReplicasOnMidClusterHighReplication in > TestStochasticLoadBalancer2 > - Disabled testFlushAndCompactionsInPrimary in TestRegionReplicas > This JIRA tracks the work to enable them (or modify/remove if not applicable). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19007) Align Services Interfaces in Master and RegionServer
[ https://issues.apache.org/jira/browse/HBASE-19007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214610#comment-16214610 ] stack commented on HBASE-19007: --- Just noticed. No harm. You do loads of work around the place. I'll have someone to blame if anyone complains (smile). I could revert and fix > Align Services Interfaces in Master and RegionServer > > > Key: HBASE-19007 > URL: https://issues.apache.org/jira/browse/HBASE-19007 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack >Priority: Blocker > Labels: coprocessor > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-19007.master.001.patch, > HBASE-19007.master.002.patch, HBASE-19007.master.003.patch, > HBASE-19007.master.004.patch, HBASE-19007.master.005.patch, > HBASE-19007.master.006.patch, HBASE-19007.master.007.patch, > HBASE-19007.master.008.patch, HBASE-19007.master.009.patch, > HBASE-19007.master.009.patch, HBASE-19007.master.010.patch, > HBASE-19007.master.011.patch, HBASE-19007.master.012.patch, > HBASE-19007.master.013.patch > > > HBASE-18183 adds a CoprocessorRegionServerService to give a view on > RegionServiceServices that is safe to expose to Coprocessors. > On the Master-side, MasterServices becomes an Interface for exposing to > Coprocessors. > We need to align the two. > For background, see > https://issues.apache.org/jira/browse/HBASE-12260?focusedCommentId=16203820=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16203820 > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18989) Polish the compaction related CP hooks
[ https://issues.apache.org/jira/browse/HBASE-18989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-18989: -- Attachment: HBASE-18989-v2.patch Confirm that we pass the correct CompactionLifeCycleTracker to CP hooks in UT. > Polish the compaction related CP hooks > -- > > Key: HBASE-18989 > URL: https://issues.apache.org/jira/browse/HBASE-18989 > Project: HBase > Issue Type: Sub-task > Components: Compaction, Coprocessors >Reporter: Duo Zhang >Assignee: Duo Zhang > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-18989-v1.patch, HBASE-18989-v2.patch, > HBASE-18989.patch, HBASE-18989.patch, HBASE-18989.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19007) Align Services Interfaces in Master and RegionServer
[ https://issues.apache.org/jira/browse/HBASE-19007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214605#comment-16214605 ] Guanghao Zhang commented on HBASE-19007: [~stack] the commit 38879fb3ffa88ca95b15c61656a92e72c0ed996f author seems not right, sir. I don't know why shows my name and email.. > Align Services Interfaces in Master and RegionServer > > > Key: HBASE-19007 > URL: https://issues.apache.org/jira/browse/HBASE-19007 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack >Priority: Blocker > Labels: coprocessor > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-19007.master.001.patch, > HBASE-19007.master.002.patch, HBASE-19007.master.003.patch, > HBASE-19007.master.004.patch, HBASE-19007.master.005.patch, > HBASE-19007.master.006.patch, HBASE-19007.master.007.patch, > HBASE-19007.master.008.patch, HBASE-19007.master.009.patch, > HBASE-19007.master.009.patch, HBASE-19007.master.010.patch, > HBASE-19007.master.011.patch, HBASE-19007.master.012.patch, > HBASE-19007.master.013.patch > > > HBASE-18183 adds a CoprocessorRegionServerService to give a view on > RegionServiceServices that is safe to expose to Coprocessors. > On the Master-side, MasterServices becomes an Interface for exposing to > Coprocessors. > We need to align the two. > For background, see > https://issues.apache.org/jira/browse/HBASE-12260?focusedCommentId=16203820=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16203820 > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18690) Replace o.a.h.c.InterfaceAudience by o.a.h.h.c.InterfaceAudience
[ https://issues.apache.org/jira/browse/HBASE-18690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214600#comment-16214600 ] Hudson commented on HBASE-18690: SUCCESS: Integrated in Jenkins build HBase-1.2-IT #984 (See [https://builds.apache.org/job/HBase-1.2-IT/984/]) HBASE-18690 Replace o.a.h.c.InterfaceAudience by (chia7712: rev ddb9c49324da71c7ec1dfbc65a23356f4fc82a30) * (edit) hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/metrics/Interns.java * (edit) hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/metrics/MetricsInfoImpl.java > Replace o.a.h.c.InterfaceAudience by o.a.h.h.c.InterfaceAudience > > > Key: HBASE-18690 > URL: https://issues.apache.org/jira/browse/HBASE-18690 > Project: HBase > Issue Type: Task >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai >Priority: Minor > Fix For: 1.4.0, 1.3.2, 1.5.0, 1.2.8 > > Attachments: HBASE-18690.branch-1.v0.patch, > HBASE-18690.branch-1.v0.patch, HBASE-18690.branch-1.v0.patch, > HBASE-18690.v0.patch, HBASE-18690.v0.patch > > > Some classes still import the hadoop's InterfaceAudience. > # Interns > # MetricsInfoImpl > # RestCsrfPreventionFilter > # AbstractFileStatusFilter > # FileStatusFilter -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18690) Replace o.a.h.c.InterfaceAudience by o.a.h.h.c.InterfaceAudience
[ https://issues.apache.org/jira/browse/HBASE-18690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214598#comment-16214598 ] Hudson commented on HBASE-18690: SUCCESS: Integrated in Jenkins build HBase-1.3-IT #249 (See [https://builds.apache.org/job/HBase-1.3-IT/249/]) HBASE-18690 Replace o.a.h.c.InterfaceAudience by (chia7712: rev 7019c80b08fd9ddbeed2e0a6680a9220c8a660a0) * (edit) hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/metrics/MetricsInfoImpl.java * (edit) hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/metrics/Interns.java * (edit) hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/filter/RestCsrfPreventionFilter.java > Replace o.a.h.c.InterfaceAudience by o.a.h.h.c.InterfaceAudience > > > Key: HBASE-18690 > URL: https://issues.apache.org/jira/browse/HBASE-18690 > Project: HBase > Issue Type: Task >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai >Priority: Minor > Fix For: 1.4.0, 1.3.2, 1.5.0, 1.2.8 > > Attachments: HBASE-18690.branch-1.v0.patch, > HBASE-18690.branch-1.v0.patch, HBASE-18690.branch-1.v0.patch, > HBASE-18690.v0.patch, HBASE-18690.v0.patch > > > Some classes still import the hadoop's InterfaceAudience. > # Interns > # MetricsInfoImpl > # RestCsrfPreventionFilter > # AbstractFileStatusFilter > # FileStatusFilter -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18690) Replace o.a.h.c.InterfaceAudience by o.a.h.h.c.InterfaceAudience
[ https://issues.apache.org/jira/browse/HBASE-18690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214597#comment-16214597 ] Hudson commented on HBASE-18690: FAILURE: Integrated in Jenkins build HBase-1.3-JDK7 #318 (See [https://builds.apache.org/job/HBase-1.3-JDK7/318/]) HBASE-18690 Replace o.a.h.c.InterfaceAudience by (chia7712: rev 7019c80b08fd9ddbeed2e0a6680a9220c8a660a0) * (edit) hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/metrics/MetricsInfoImpl.java * (edit) hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/filter/RestCsrfPreventionFilter.java * (edit) hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/metrics/Interns.java > Replace o.a.h.c.InterfaceAudience by o.a.h.h.c.InterfaceAudience > > > Key: HBASE-18690 > URL: https://issues.apache.org/jira/browse/HBASE-18690 > Project: HBase > Issue Type: Task >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai >Priority: Minor > Fix For: 1.4.0, 1.3.2, 1.5.0, 1.2.8 > > Attachments: HBASE-18690.branch-1.v0.patch, > HBASE-18690.branch-1.v0.patch, HBASE-18690.branch-1.v0.patch, > HBASE-18690.v0.patch, HBASE-18690.v0.patch > > > Some classes still import the hadoop's InterfaceAudience. > # Interns > # MetricsInfoImpl > # RestCsrfPreventionFilter > # AbstractFileStatusFilter > # FileStatusFilter -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18690) Replace o.a.h.c.InterfaceAudience by o.a.h.h.c.InterfaceAudience
[ https://issues.apache.org/jira/browse/HBASE-18690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214596#comment-16214596 ] Hudson commented on HBASE-18690: FAILURE: Integrated in Jenkins build HBase-1.2-JDK8 #246 (See [https://builds.apache.org/job/HBase-1.2-JDK8/246/]) HBASE-18690 Replace o.a.h.c.InterfaceAudience by (chia7712: rev ddb9c49324da71c7ec1dfbc65a23356f4fc82a30) * (edit) hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/metrics/MetricsInfoImpl.java * (edit) hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/metrics/Interns.java > Replace o.a.h.c.InterfaceAudience by o.a.h.h.c.InterfaceAudience > > > Key: HBASE-18690 > URL: https://issues.apache.org/jira/browse/HBASE-18690 > Project: HBase > Issue Type: Task >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai >Priority: Minor > Fix For: 1.4.0, 1.3.2, 1.5.0, 1.2.8 > > Attachments: HBASE-18690.branch-1.v0.patch, > HBASE-18690.branch-1.v0.patch, HBASE-18690.branch-1.v0.patch, > HBASE-18690.v0.patch, HBASE-18690.v0.patch > > > Some classes still import the hadoop's InterfaceAudience. > # Interns > # MetricsInfoImpl > # RestCsrfPreventionFilter > # AbstractFileStatusFilter > # FileStatusFilter -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18846) Accommodate the hbase-indexer/lily/SEP consumer deploy-type
[
https://issues.apache.org/jira/browse/HBASE-18846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-18846:
--
Attachment: HBASE-18846.master.006.patch
> Accommodate the hbase-indexer/lily/SEP consumer deploy-type
> ---
>
> Key: HBASE-18846
> URL: https://issues.apache.org/jira/browse/HBASE-18846
> Project: HBase
> Issue Type: Bug
>Reporter: stack
>Assignee: stack
> Fix For: 2.0.0-alpha-4
>
> Attachments: HBASE-18846.master.001.patch,
> HBASE-18846.master.002.patch, HBASE-18846.master.003.patch,
> HBASE-18846.master.004.patch, HBASE-18846.master.005.patch,
> HBASE-18846.master.006.patch, IndexerConnection.java, hbase-site.xml,
> javadoc.txt
>
>
> This is a follow-on from HBASE-10504, Define a Replication Interface. There
> we defined a new, flexible replication endpoint for others to implement but
> it did little to help the case of the lily hbase-indexer. This issue takes up
> the case of the hbase-indexer.
> The hbase-indexer poses to hbase as a 'fake' peer cluster (For why
> hbase-indexer is implemented so, the advantage to having the indexing done in
> a separate process set that can be independently scaled, can participate in
> the same security realm, etc., see discussion in HBASE-10504). The
> hbase-indexer will start up a cut-down "RegionServer" processes that are just
> an instance of hbase RpcServer hosting an AdminProtos Service. They make
> themselves 'appear' to the Replication Source by hoisting up an ephemeral
> znode 'registering' as a RegionServer. The source cluster then streams
> WALEdits to the Admin Protos method:
> {code}
> public ReplicateWALEntryResponse replicateWALEntry(final RpcController
> controller,
> final ReplicateWALEntryRequest request) throws ServiceException {
> {code}
> The hbase-indexer relies on other hbase internals like Server so it can get a
> ZooKeeperWatcher instance and know the 'name' to use for this cut-down server.
> Thoughts on how to proceed include:
>
> * Better formalize its current digestion of hbase internals; make it so
> rpcserver is allowed to be used by others, etc. This would be hard to do
> given they use basics like Server, Protobuf serdes for WAL types, and
> AdminProtos Service. Any change in this wide API breaks (again)
> hbase-indexer. We have made a 'channel' for Coprocessor Endpoints so they
> continue to work though they use 'internal' types. They can use protos in
> hbase-protocol. hbase-protocol protos are in a limbo currently where they are
> sort-of 'public'; a TODO. Perhaps the hbase-indexer could do similar relying
> on the hbase-protocol (pb2.5) content and we could do something to reveal
> rpcserver and zk for hbase-indexer safe use.
> * Start an actual RegionServer only have it register the AdminProtos Service
> only -- not ClientProtos and the Service that does Master interaction, etc.
> [I checked, this is not as easy to do as I at first thought -- St.Ack] Then
> have the hbase-indexer implement an AdminCoprocessor to override the
> replicateWALEntry method (the Admin CP implementation may need work). This
> would narrow the hbase-indexer exposure to that of the Admin Coprocessor
> Interface
> * Over in HBASE-10504, [~enis] suggested "... if we want to provide
> isolation for the replication services in hbase, we can have a simple host as
> another daemon which hosts the ReplicationEndpoint implementation. RS's will
> use a built-in RE to send the edits to this layer, and the host will delegate
> it to the RE implementation. The flow would be something like: RS --> RE
> inside RS --> Host daemon for RE --> Actual RE implementation --> third party
> system..."
>
> Other crazy notions occur including the setup of an Admin Interface
> Coprocessor Endpoint. A new ReplicationEndpoint would feed the replication
> stream to the remote cluster via the CPEP registered channel.
> But time is short. Hopefully we can figure something that will work in 2.0
> timeframe w/o too much code movement.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (HBASE-19064) Synchronous replication for HBase
[ https://issues.apache.org/jira/browse/HBASE-19064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214595#comment-16214595 ] chunhui shen edited comment on HBASE-19064 at 10/23/17 3:38 AM: It is an useful feature if we need strong consistency with only two datacenters. Looking forward to this on 3.0.(y) was (Author: zjushch): It is an useful feature if we want strong consistency with only two datacenters. Looking forward to this on 3.0.(y) > Synchronous replication for HBase > - > > Key: HBASE-19064 > URL: https://issues.apache.org/jira/browse/HBASE-19064 > Project: HBase > Issue Type: New Feature > Components: Replication >Reporter: Duo Zhang >Assignee: Duo Zhang > Fix For: 3.0.0 > > > The guys from Alibaba made a presentation on HBaseCon Asia about the > synchronous replication for HBase. We(Xiaomi) think this is a very useful > feature for HBase so we want to bring it into the community version. > This is a big feature so we plan to do it in a feature branch. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19064) Synchronous replication for HBase
[ https://issues.apache.org/jira/browse/HBASE-19064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214595#comment-16214595 ] chunhui shen commented on HBASE-19064: -- It is an useful feature if we want strong consistency with only two datacenters. Looking forward to this on 3.0.(y) > Synchronous replication for HBase > - > > Key: HBASE-19064 > URL: https://issues.apache.org/jira/browse/HBASE-19064 > Project: HBase > Issue Type: New Feature > Components: Replication >Reporter: Duo Zhang >Assignee: Duo Zhang > Fix For: 3.0.0 > > > The guys from Alibaba made a presentation on HBaseCon Asia about the > synchronous replication for HBase. We(Xiaomi) think this is a very useful > feature for HBase so we want to bring it into the community version. > This is a big feature so we plan to do it in a feature branch. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18690) Replace o.a.h.c.InterfaceAudience by o.a.h.h.c.InterfaceAudience
[ https://issues.apache.org/jira/browse/HBASE-18690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214592#comment-16214592 ] Hudson commented on HBASE-18690: FAILURE: Integrated in Jenkins build HBase-1.3-JDK8 #333 (See [https://builds.apache.org/job/HBase-1.3-JDK8/333/]) HBASE-18690 Replace o.a.h.c.InterfaceAudience by (chia7712: rev 7019c80b08fd9ddbeed2e0a6680a9220c8a660a0) * (edit) hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/metrics/Interns.java * (edit) hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/metrics/MetricsInfoImpl.java * (edit) hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/filter/RestCsrfPreventionFilter.java > Replace o.a.h.c.InterfaceAudience by o.a.h.h.c.InterfaceAudience > > > Key: HBASE-18690 > URL: https://issues.apache.org/jira/browse/HBASE-18690 > Project: HBase > Issue Type: Task >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai >Priority: Minor > Fix For: 1.4.0, 1.3.2, 1.5.0, 1.2.8 > > Attachments: HBASE-18690.branch-1.v0.patch, > HBASE-18690.branch-1.v0.patch, HBASE-18690.branch-1.v0.patch, > HBASE-18690.v0.patch, HBASE-18690.v0.patch > > > Some classes still import the hadoop's InterfaceAudience. > # Interns > # MetricsInfoImpl > # RestCsrfPreventionFilter > # AbstractFileStatusFilter > # FileStatusFilter -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18690) Replace o.a.h.c.InterfaceAudience by o.a.h.h.c.InterfaceAudience
[ https://issues.apache.org/jira/browse/HBASE-18690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214591#comment-16214591 ] Hudson commented on HBASE-18690: FAILURE: Integrated in Jenkins build HBase-1.2-JDK7 #249 (See [https://builds.apache.org/job/HBase-1.2-JDK7/249/]) HBASE-18690 Replace o.a.h.c.InterfaceAudience by (chia7712: rev ddb9c49324da71c7ec1dfbc65a23356f4fc82a30) * (edit) hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/metrics/MetricsInfoImpl.java * (edit) hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/metrics/Interns.java > Replace o.a.h.c.InterfaceAudience by o.a.h.h.c.InterfaceAudience > > > Key: HBASE-18690 > URL: https://issues.apache.org/jira/browse/HBASE-18690 > Project: HBase > Issue Type: Task >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai >Priority: Minor > Fix For: 1.4.0, 1.3.2, 1.5.0, 1.2.8 > > Attachments: HBASE-18690.branch-1.v0.patch, > HBASE-18690.branch-1.v0.patch, HBASE-18690.branch-1.v0.patch, > HBASE-18690.v0.patch, HBASE-18690.v0.patch > > > Some classes still import the hadoop's InterfaceAudience. > # Interns > # MetricsInfoImpl > # RestCsrfPreventionFilter > # AbstractFileStatusFilter > # FileStatusFilter -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18690) Replace o.a.h.c.InterfaceAudience by o.a.h.h.c.InterfaceAudience
[ https://issues.apache.org/jira/browse/HBASE-18690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18690: --- Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Push to branch-1.2, branch-1.3, branch-1.4, and branch-1. Thanks for all reviews~ > Replace o.a.h.c.InterfaceAudience by o.a.h.h.c.InterfaceAudience > > > Key: HBASE-18690 > URL: https://issues.apache.org/jira/browse/HBASE-18690 > Project: HBase > Issue Type: Task >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai >Priority: Minor > Fix For: 1.4.0, 1.3.2, 1.5.0, 1.2.8 > > Attachments: HBASE-18690.branch-1.v0.patch, > HBASE-18690.branch-1.v0.patch, HBASE-18690.branch-1.v0.patch, > HBASE-18690.v0.patch, HBASE-18690.v0.patch > > > Some classes still import the hadoop's InterfaceAudience. > # Interns > # MetricsInfoImpl > # RestCsrfPreventionFilter > # AbstractFileStatusFilter > # FileStatusFilter -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18950) Remove Optional parameters in AsyncAdmin interface
[ https://issues.apache.org/jira/browse/HBASE-18950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214583#comment-16214583 ] Guanghao Zhang commented on HBASE-18950: Attach a 008 patch to fix the failed ut. > Remove Optional parameters in AsyncAdmin interface > -- > > Key: HBASE-18950 > URL: https://issues.apache.org/jira/browse/HBASE-18950 > Project: HBase > Issue Type: Sub-task > Components: Client >Reporter: Duo Zhang >Assignee: Guanghao Zhang >Priority: Blocker > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-18950.master.001.patch, > HBASE-18950.master.002.patch, HBASE-18950.master.003.patch, > HBASE-18950.master.004.patch, HBASE-18950.master.005.patch, > HBASE-18950.master.005.patch, HBASE-18950.master.006.patch, > HBASE-18950.master.007.patch, HBASE-18950.master.008.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18950) Remove Optional parameters in AsyncAdmin interface
[ https://issues.apache.org/jira/browse/HBASE-18950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-18950: --- Status: Open (was: Patch Available) > Remove Optional parameters in AsyncAdmin interface > -- > > Key: HBASE-18950 > URL: https://issues.apache.org/jira/browse/HBASE-18950 > Project: HBase > Issue Type: Sub-task > Components: Client >Reporter: Duo Zhang >Assignee: Guanghao Zhang >Priority: Blocker > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-18950.master.001.patch, > HBASE-18950.master.002.patch, HBASE-18950.master.003.patch, > HBASE-18950.master.004.patch, HBASE-18950.master.005.patch, > HBASE-18950.master.005.patch, HBASE-18950.master.006.patch, > HBASE-18950.master.007.patch, HBASE-18950.master.008.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18950) Remove Optional parameters in AsyncAdmin interface
[ https://issues.apache.org/jira/browse/HBASE-18950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-18950: --- Status: Patch Available (was: Open) > Remove Optional parameters in AsyncAdmin interface > -- > > Key: HBASE-18950 > URL: https://issues.apache.org/jira/browse/HBASE-18950 > Project: HBase > Issue Type: Sub-task > Components: Client >Reporter: Duo Zhang >Assignee: Guanghao Zhang >Priority: Blocker > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-18950.master.001.patch, > HBASE-18950.master.002.patch, HBASE-18950.master.003.patch, > HBASE-18950.master.004.patch, HBASE-18950.master.005.patch, > HBASE-18950.master.005.patch, HBASE-18950.master.006.patch, > HBASE-18950.master.007.patch, HBASE-18950.master.008.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18950) Remove Optional parameters in AsyncAdmin interface
[ https://issues.apache.org/jira/browse/HBASE-18950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-18950: --- Attachment: HBASE-18950.master.008.patch > Remove Optional parameters in AsyncAdmin interface > -- > > Key: HBASE-18950 > URL: https://issues.apache.org/jira/browse/HBASE-18950 > Project: HBase > Issue Type: Sub-task > Components: Client >Reporter: Duo Zhang >Assignee: Guanghao Zhang >Priority: Blocker > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-18950.master.001.patch, > HBASE-18950.master.002.patch, HBASE-18950.master.003.patch, > HBASE-18950.master.004.patch, HBASE-18950.master.005.patch, > HBASE-18950.master.005.patch, HBASE-18950.master.006.patch, > HBASE-18950.master.007.patch, HBASE-18950.master.008.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-12643) Add MR counter corresponding to failure in changing ownership for ExportSnapshot
[ https://issues.apache.org/jira/browse/HBASE-12643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-12643: --- Labels: mapreduce snapshot (was: snapshot) > Add MR counter corresponding to failure in changing ownership for > ExportSnapshot > > > Key: HBASE-12643 > URL: https://issues.apache.org/jira/browse/HBASE-12643 > Project: HBase > Issue Type: Improvement >Reporter: Ted Yu > Labels: mapreduce, snapshot > > Chatting with Tobi Vollebregt w.r.t. using ExportSnapshot, he said that if > -chuser or -chgroup on ExportSnapshot doesn't work, the warning should be > more visible to user so that manual correction can be performed. > I suggested adding MR counter which corresponds to the failure. > Tobi said adding FAILURES or ERRORS in the counter name would help with > troubleshooting. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-11129) Expose Scan conversion methods in TableMapReduceUtil as public methods
[
https://issues.apache.org/jira/browse/HBASE-11129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-11129:
---
Resolution: Implemented
Status: Resolved (was: Patch Available)
These methods are currently public.
> Expose Scan conversion methods in TableMapReduceUtil as public methods
> --
>
> Key: HBASE-11129
> URL: https://issues.apache.org/jira/browse/HBASE-11129
> Project: HBase
> Issue Type: Task
> Components: mapreduce
>Reporter: Ted Yu
>Assignee: Gustavo Anatoly
>Priority: Minor
> Attachments: HBASE-11129.patch
>
>
> Scan#readFields() from 0.92 has been removed.
> TableMapReduceUtil has the following package private methods:
> {code}
> static String convertScanToString(Scan scan) throws IOException {
> {code}
> {code}
> static Scan convertStringToScan(String base64) throws IOException {
> {code}
> We should consider exposing them as public methods so that user can interpret
> Scan objects easily in mapreduce jobs.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (HBASE-11093) FilterList#filterRow() iterates through its filters even though FilterList#hasFilterRow() returns false
[ https://issues.apache.org/jira/browse/HBASE-11093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu reassigned HBASE-11093: -- Assignee: (was: Ted Yu) > FilterList#filterRow() iterates through its filters even though > FilterList#hasFilterRow() returns false > --- > > Key: HBASE-11093 > URL: https://issues.apache.org/jira/browse/HBASE-11093 > Project: HBase > Issue Type: Bug >Reporter: Ted Yu >Priority: Minor > Attachments: 11093-v1.txt, 11093-v2.txt, 11093-v3.txt > > > FilterList#hasFilterRow() returns false when hasFilterRow() of all of > constituent filters return false. > However, FilterList#filterRow() still iterates through its filters in this > scenario. > The iteration should be skipped when FilterList#hasFilterRow() returns false. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18922) Fix all dead links in our HBase book
[ https://issues.apache.org/jira/browse/HBASE-18922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yung-An He updated HBASE-18922: --- Attachment: HBASE-18922-master_v1.patch Attach patch file. > Fix all dead links in our HBase book > > > Key: HBASE-18922 > URL: https://issues.apache.org/jira/browse/HBASE-18922 > Project: HBase > Issue Type: Bug > Components: documentation >Reporter: Chia-Ping Tsai >Assignee: Yung-An He > Labels: beginner > Fix For: 2.0.0 > > Attachments: HBASE-18922-master.patch, HBASE-18922-master_v1.patch > > > see > [here|https://paper.dropbox.com/doc/dead-links-in-HBase-book-8YcTcH5mxZKn9TYlKJJq4?_tk=share_copylink] > to find the dead links. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (HBASE-15482) Provide an option to skip calculating block locations for SnapshotInputFormat
[ https://issues.apache.org/jira/browse/HBASE-15482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiang Li reassigned HBASE-15482: Assignee: Xiang Li > Provide an option to skip calculating block locations for SnapshotInputFormat > - > > Key: HBASE-15482 > URL: https://issues.apache.org/jira/browse/HBASE-15482 > Project: HBase > Issue Type: Improvement > Components: mapreduce >Reporter: Liyin Tang >Assignee: Xiang Li >Priority: Minor > > When a MR job is reading from SnapshotInputFormat, it needs to calculate the > splits based on the block locations in order to get best locality. However, > this process may take a long time for large snapshots. > In some setup, the computing layer, Spark, Hive or Presto could run out side > of HBase cluster. In these scenarios, the block locality doesn't matter. > Therefore, it will be great to have an option to skip calculating the block > locations for every job. That will super useful for the Hive/Presto/Spark > connectors. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18690) Replace o.a.h.c.InterfaceAudience by o.a.h.h.c.InterfaceAudience
[ https://issues.apache.org/jira/browse/HBASE-18690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214501#comment-16214501 ] Sean Busbey commented on HBASE-18690: - +1 from me. I've been trying to get a precommit run in before pushing it myself. > Replace o.a.h.c.InterfaceAudience by o.a.h.h.c.InterfaceAudience > > > Key: HBASE-18690 > URL: https://issues.apache.org/jira/browse/HBASE-18690 > Project: HBase > Issue Type: Task >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai >Priority: Minor > Fix For: 1.4.0, 1.3.2, 1.5.0, 1.2.8 > > Attachments: HBASE-18690.branch-1.v0.patch, > HBASE-18690.branch-1.v0.patch, HBASE-18690.branch-1.v0.patch, > HBASE-18690.v0.patch, HBASE-18690.v0.patch > > > Some classes still import the hadoop's InterfaceAudience. > # Interns > # MetricsInfoImpl > # RestCsrfPreventionFilter > # AbstractFileStatusFilter > # FileStatusFilter -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (HBASE-16819) findHangingTests.py should recognize tests with same name from different modules
[
https://issues.apache.org/jira/browse/HBASE-16819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu resolved HBASE-16819.
Resolution: Later
> findHangingTests.py should recognize tests with same name from different
> modules
>
>
> Key: HBASE-16819
> URL: https://issues.apache.org/jira/browse/HBASE-16819
> Project: HBase
> Issue Type: Test
>Reporter: Ted Yu
>Priority: Minor
>
> I was using findHangingTests.py on one of the 1.4 Jenkins builds:
> {code}
> ERROR! Multiple tests with same name 'TestTableMapReduceUtil'. Might get
> wrong results for this test.
> ERROR! No test 'TestTableMapReduceUtil' found in hanging_tests. Might get
> wrong results for this test.
> ERROR! Multiple tests with same name 'TestHTablePool'. Might get wrong
> results for this test.
> ERROR! No test 'TestHTablePool' found in hanging_tests. Might get wrong
> results for this test.
> {code}
> There are mapred.TestTableMapReduceUtil and mapreduce.TestTableMapReduceUtil
> which confused findHangingTests.py
> Similar issue with tests whose name contains $:
> {code}
> Running org.apache.hadoop.hbase.client.TestHTablePool$TestHTableReusablePool
> Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.273 sec -
> in org.apache.hadoop.hbase.client.TestHTablePool$TestHTableReusablePool
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19066) Correct the directory of openjdk-8 for jenkins
[
https://issues.apache.org/jira/browse/HBASE-19066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214490#comment-16214490
]
Hadoop QA commented on HBASE-19066:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
17s{color} | {color:blue} Docker mode activated. {color} |
| {color:blue}0{color} | {color:blue} shelldocs {color} | {color:blue} 0m
10s{color} | {color:blue} Shelldocs was not available. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
23s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
10s{color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m
51s{color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
33s{color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 1m
30s{color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 3m
58s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
0s{color} | {color:blue} Skipped patched modules with no Java source: . {color}
|
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
46s{color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 5m
27s{color} | {color:green} branch-1 passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
22s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
5s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m
54s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 2m
54s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
30s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 1m
25s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} shellcheck {color} | {color:green} 0m
5s{color} | {color:green} There were no new shellcheck issues. {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 3m
58s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
45m 20s{color} | {color:green} Patch does not cause any errors with Hadoop
2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3.
{color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
0s{color} | {color:blue} Skipped patched modules with no Java source: . {color}
|
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
10s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 5m
40s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}176m 15s{color}
| {color:red} root in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
28s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}261m 0s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:4bf71c3 |
[jira] [Commented] (HBASE-19046) RegionObserver#postCompactSelection Passing an ImmutableList param of PB type
[
https://issues.apache.org/jira/browse/HBASE-19046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214488#comment-16214488
]
Hadoop QA commented on HBASE-19046:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 22m
29s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 7m
58s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
34s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
20s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
38s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 8m
34s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 5m
12s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
12s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 7m
43s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
28s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
28s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
24s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
38s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 6m
28s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
76m 22s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 6m
50s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
30s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}207m 37s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
21s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}351m 58s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.regionserver.TestRegionReplicaFailover |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:cb5c477 |
| JIRA Issue | HBASE-19046 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12893464/HBASE-19046.patch |
| Optional Tests | asflicense javac javadoc unit findbugs shadedjars
hadoopcheck hbaseanti checkstyle compile |
| uname | Linux cbe6b5745817 3.13.0-116-generic #163-Ubuntu SMP Fri Mar 31
14:13:22 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / 2ee8690 |
| Default Java | 1.8.0_141 |
| findbugs | v3.1.0-RC3 |
| unit |
https://builds.apache.org/job/PreCommit-HBASE-Build/9329/artifact/patchprocess/patch-unit-hbase-server.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/9329/testReport/ |
| modules | C: hbase-server U: hbase-server |
| Console output |
[jira] [Updated] (HBASE-19019) QA fails on hbase-thrift module with timeout
[
https://issues.apache.org/jira/browse/HBASE-19019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated HBASE-19019:
---
Attachment: HBASE-19019.branch-1.2.no_para.patch
Re-implement the {{parameterized}} via for-loop.
> QA fails on hbase-thrift module with timeout
>
>
> Key: HBASE-19019
> URL: https://issues.apache.org/jira/browse/HBASE-19019
> Project: HBase
> Issue Type: Bug
> Components: Thrift
>Reporter: Peter Somogyi
>Assignee: Chia-Ping Tsai
>Priority: Critical
> Attachments: HBASE-19019.branch-1.001.patch,
> HBASE-19019.branch-1.002.patch, HBASE-19019.branch-1.1.dummy.patch,
> HBASE-19019.branch-1.2.dummy.patch, HBASE-19019.branch-1.2.no_para.patch,
> HBASE-19019.master.001.patch
>
>
> For any modification in hbase-thrift module the precommit build fails with
> timeout for {{TestThriftServerCmdLine}}. I noticed this failure on multiple
> patches: HBASE-18967 and HBASE-18996 even when the patch did not contain any
> modification
> (https://issues.apache.org/jira/secure/attachment/12892414/HBASE-18967.branch-1.3.002.patch)
> The {{TestThriftServerCmdLine}} test passes locally on both mentioned patches.
> One failure: https://builds.apache.org/job/PreCommit-HBASE-Build/9127/
> {code}
> [INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ hbase-thrift ---
> [INFO] Surefire report directory:
> /testptch/hbase/hbase-thrift/target/surefire-reports
> [INFO] Using configured provider
> org.apache.maven.surefire.junitcore.JUnitCoreProvider
> [INFO] parallel='none', perCoreThreadCount=true, threadCount=0,
> useUnlimitedThreads=false, threadCountSuites=0, threadCountClasses=0,
> threadCountMethods=0, parallelOptimized=true
> ---
> T E S T S
> ---
> Running org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandler
> Tests run: 29, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 48.201 sec -
> in org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandler
> Running
> org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithReadOnly
> Tests run: 15, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.257 sec -
> in org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithReadOnly
> Running
> org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithLabels
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.621 sec -
> in org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithLabels
> Running org.apache.hadoop.hbase.thrift.TestCallQueue
> Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.473 sec -
> in org.apache.hadoop.hbase.thrift.TestCallQueue
> Running org.apache.hadoop.hbase.thrift.TestThriftHttpServer
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.239 sec -
> in org.apache.hadoop.hbase.thrift.TestThriftHttpServer
> Running org.apache.hadoop.hbase.thrift.TestThriftServer
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 75.55 sec -
> in org.apache.hadoop.hbase.thrift.TestThriftServer
> Running org.apache.hadoop.hbase.thrift.TestThriftServerCmdLine
> Results :
> Tests run: 72, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 18:33.104s
> [INFO] Finished at: Mon Oct 16 03:42:59 UTC 2017
> [INFO] Final Memory: 61M/1299M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test (default-test) on
> project hbase-thrift: There was a timeout or other error in the fork -> [Help
> 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19019) QA fails on hbase-thrift module with timeout
[
https://issues.apache.org/jira/browse/HBASE-19019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated HBASE-19019:
---
Status: Patch Available (was: Open)
> QA fails on hbase-thrift module with timeout
>
>
> Key: HBASE-19019
> URL: https://issues.apache.org/jira/browse/HBASE-19019
> Project: HBase
> Issue Type: Bug
> Components: Thrift
>Reporter: Peter Somogyi
>Assignee: Chia-Ping Tsai
>Priority: Critical
> Attachments: HBASE-19019.branch-1.001.patch,
> HBASE-19019.branch-1.002.patch, HBASE-19019.branch-1.1.dummy.patch,
> HBASE-19019.branch-1.2.dummy.patch, HBASE-19019.branch-1.2.no_para.patch,
> HBASE-19019.master.001.patch
>
>
> For any modification in hbase-thrift module the precommit build fails with
> timeout for {{TestThriftServerCmdLine}}. I noticed this failure on multiple
> patches: HBASE-18967 and HBASE-18996 even when the patch did not contain any
> modification
> (https://issues.apache.org/jira/secure/attachment/12892414/HBASE-18967.branch-1.3.002.patch)
> The {{TestThriftServerCmdLine}} test passes locally on both mentioned patches.
> One failure: https://builds.apache.org/job/PreCommit-HBASE-Build/9127/
> {code}
> [INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ hbase-thrift ---
> [INFO] Surefire report directory:
> /testptch/hbase/hbase-thrift/target/surefire-reports
> [INFO] Using configured provider
> org.apache.maven.surefire.junitcore.JUnitCoreProvider
> [INFO] parallel='none', perCoreThreadCount=true, threadCount=0,
> useUnlimitedThreads=false, threadCountSuites=0, threadCountClasses=0,
> threadCountMethods=0, parallelOptimized=true
> ---
> T E S T S
> ---
> Running org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandler
> Tests run: 29, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 48.201 sec -
> in org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandler
> Running
> org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithReadOnly
> Tests run: 15, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.257 sec -
> in org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithReadOnly
> Running
> org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithLabels
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.621 sec -
> in org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithLabels
> Running org.apache.hadoop.hbase.thrift.TestCallQueue
> Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.473 sec -
> in org.apache.hadoop.hbase.thrift.TestCallQueue
> Running org.apache.hadoop.hbase.thrift.TestThriftHttpServer
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.239 sec -
> in org.apache.hadoop.hbase.thrift.TestThriftHttpServer
> Running org.apache.hadoop.hbase.thrift.TestThriftServer
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 75.55 sec -
> in org.apache.hadoop.hbase.thrift.TestThriftServer
> Running org.apache.hadoop.hbase.thrift.TestThriftServerCmdLine
> Results :
> Tests run: 72, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 18:33.104s
> [INFO] Finished at: Mon Oct 16 03:42:59 UTC 2017
> [INFO] Final Memory: 61M/1299M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test (default-test) on
> project hbase-thrift: There was a timeout or other error in the fork -> [Help
> 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19019) QA fails on hbase-thrift module with timeout
[
https://issues.apache.org/jira/browse/HBASE-19019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated HBASE-19019:
---
Status: Open (was: Patch Available)
> QA fails on hbase-thrift module with timeout
>
>
> Key: HBASE-19019
> URL: https://issues.apache.org/jira/browse/HBASE-19019
> Project: HBase
> Issue Type: Bug
> Components: Thrift
>Reporter: Peter Somogyi
>Assignee: Chia-Ping Tsai
>Priority: Critical
> Attachments: HBASE-19019.branch-1.001.patch,
> HBASE-19019.branch-1.002.patch, HBASE-19019.branch-1.1.dummy.patch,
> HBASE-19019.branch-1.2.dummy.patch, HBASE-19019.master.001.patch
>
>
> For any modification in hbase-thrift module the precommit build fails with
> timeout for {{TestThriftServerCmdLine}}. I noticed this failure on multiple
> patches: HBASE-18967 and HBASE-18996 even when the patch did not contain any
> modification
> (https://issues.apache.org/jira/secure/attachment/12892414/HBASE-18967.branch-1.3.002.patch)
> The {{TestThriftServerCmdLine}} test passes locally on both mentioned patches.
> One failure: https://builds.apache.org/job/PreCommit-HBASE-Build/9127/
> {code}
> [INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ hbase-thrift ---
> [INFO] Surefire report directory:
> /testptch/hbase/hbase-thrift/target/surefire-reports
> [INFO] Using configured provider
> org.apache.maven.surefire.junitcore.JUnitCoreProvider
> [INFO] parallel='none', perCoreThreadCount=true, threadCount=0,
> useUnlimitedThreads=false, threadCountSuites=0, threadCountClasses=0,
> threadCountMethods=0, parallelOptimized=true
> ---
> T E S T S
> ---
> Running org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandler
> Tests run: 29, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 48.201 sec -
> in org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandler
> Running
> org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithReadOnly
> Tests run: 15, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.257 sec -
> in org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithReadOnly
> Running
> org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithLabels
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.621 sec -
> in org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithLabels
> Running org.apache.hadoop.hbase.thrift.TestCallQueue
> Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.473 sec -
> in org.apache.hadoop.hbase.thrift.TestCallQueue
> Running org.apache.hadoop.hbase.thrift.TestThriftHttpServer
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.239 sec -
> in org.apache.hadoop.hbase.thrift.TestThriftHttpServer
> Running org.apache.hadoop.hbase.thrift.TestThriftServer
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 75.55 sec -
> in org.apache.hadoop.hbase.thrift.TestThriftServer
> Running org.apache.hadoop.hbase.thrift.TestThriftServerCmdLine
> Results :
> Tests run: 72, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 18:33.104s
> [INFO] Finished at: Mon Oct 16 03:42:59 UTC 2017
> [INFO] Final Memory: 61M/1299M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test (default-test) on
> project hbase-thrift: There was a timeout or other error in the fork -> [Help
> 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19065) HRegion#bulkLoadHFiles() should wait for concurrent Region#flush() to finish
[
https://issues.apache.org/jira/browse/HBASE-19065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214451#comment-16214451
]
Hadoop QA commented on HBASE-19065:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
12s{color} | {color:blue} Docker mode activated. {color} |
| {color:blue}0{color} | {color:blue} patch {color} | {color:blue} 0m
2s{color} | {color:blue} The patch file was not named according to hbase's
naming conventions. Please see
https://yetus.apache.org/documentation/0.4.0/precommit-patchnames for
instructions. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
27s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
56s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
55s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
23s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 6m
4s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m
49s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
46s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
27s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
2s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
2s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
58s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
21s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
51s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
51m 3s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m
25s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
35s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}121m
13s{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
14s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}201m 59s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:cb5c477 |
| JIRA Issue | HBASE-19065 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12893463/19065.v1.txt |
| Optional Tests | asflicense javac javadoc unit findbugs shadedjars
hadoopcheck hbaseanti checkstyle compile |
| uname | Linux e7f9e0b11cd3 3.13.0-119-generic #166-Ubuntu SMP Wed May 3
12:18:55 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build@2/component/dev-support/hbase-personality.sh
|
| git revision | master / 2ee8690 |
| Default Java | 1.8.0_141 |
| findbugs | v3.1.0-RC3 |
| Test Results |
[jira] [Commented] (HBASE-19019) QA fails on hbase-thrift module with timeout
[
https://issues.apache.org/jira/browse/HBASE-19019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214438#comment-16214438
]
Chia-Ping Tsai commented on HBASE-19019:
The trouble we encounter is similar to SUREFIRE-1430. Will submit a patch to
remove the {{Parameterized}} from TestThriftServerCmdLine.
> QA fails on hbase-thrift module with timeout
>
>
> Key: HBASE-19019
> URL: https://issues.apache.org/jira/browse/HBASE-19019
> Project: HBase
> Issue Type: Bug
> Components: Thrift
>Reporter: Peter Somogyi
>Assignee: Chia-Ping Tsai
>Priority: Critical
> Attachments: HBASE-19019.branch-1.001.patch,
> HBASE-19019.branch-1.002.patch, HBASE-19019.branch-1.1.dummy.patch,
> HBASE-19019.branch-1.2.dummy.patch, HBASE-19019.master.001.patch
>
>
> For any modification in hbase-thrift module the precommit build fails with
> timeout for {{TestThriftServerCmdLine}}. I noticed this failure on multiple
> patches: HBASE-18967 and HBASE-18996 even when the patch did not contain any
> modification
> (https://issues.apache.org/jira/secure/attachment/12892414/HBASE-18967.branch-1.3.002.patch)
> The {{TestThriftServerCmdLine}} test passes locally on both mentioned patches.
> One failure: https://builds.apache.org/job/PreCommit-HBASE-Build/9127/
> {code}
> [INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ hbase-thrift ---
> [INFO] Surefire report directory:
> /testptch/hbase/hbase-thrift/target/surefire-reports
> [INFO] Using configured provider
> org.apache.maven.surefire.junitcore.JUnitCoreProvider
> [INFO] parallel='none', perCoreThreadCount=true, threadCount=0,
> useUnlimitedThreads=false, threadCountSuites=0, threadCountClasses=0,
> threadCountMethods=0, parallelOptimized=true
> ---
> T E S T S
> ---
> Running org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandler
> Tests run: 29, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 48.201 sec -
> in org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandler
> Running
> org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithReadOnly
> Tests run: 15, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.257 sec -
> in org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithReadOnly
> Running
> org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithLabels
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.621 sec -
> in org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithLabels
> Running org.apache.hadoop.hbase.thrift.TestCallQueue
> Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.473 sec -
> in org.apache.hadoop.hbase.thrift.TestCallQueue
> Running org.apache.hadoop.hbase.thrift.TestThriftHttpServer
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.239 sec -
> in org.apache.hadoop.hbase.thrift.TestThriftHttpServer
> Running org.apache.hadoop.hbase.thrift.TestThriftServer
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 75.55 sec -
> in org.apache.hadoop.hbase.thrift.TestThriftServer
> Running org.apache.hadoop.hbase.thrift.TestThriftServerCmdLine
> Results :
> Tests run: 72, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 18:33.104s
> [INFO] Finished at: Mon Oct 16 03:42:59 UTC 2017
> [INFO] Final Memory: 61M/1299M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test (default-test) on
> project hbase-thrift: There was a timeout or other error in the fork -> [Help
> 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19066) Correct the directory of openjdk-8 for jenkins
[
https://issues.apache.org/jira/browse/HBASE-19066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated HBASE-19066:
---
Description:
{code}
10:22:28 JAVA_HOME: /home/jenkins/tools/java/latest1.7 does not exist.
Dockermode: attempting to switch to another.
10:22:28 Setting /usr/lib/jvm/java-7-openjdk-amd64 as the JAVA_HOME.
10:22:28 WARNING: Cannot locate JDK directory /usr/lib/jvm/java-8-oracle:
ignoring
10:22:28 Modes: MultiJDK Jenkins Robot Docker ResetRepo UnitTests
{code}
It breaks the multi-jdk check, such as doc and compile.
was:
{code}
10:22:28 JAVA_HOME: /home/jenkins/tools/java/latest1.7 does not exist.
Dockermode: attempting to switch to another.
10:22:28 Setting /usr/lib/jvm/java-7-openjdk-amd64 as the JAVA_HOME.
10:22:28 WARNING: Cannot locate JDK directory /usr/lib/jvm/java-8-oracle:
ignoring
10:22:28 Modes: MultiJDK Jenkins Robot Docker ResetRepo UnitTests
{code}
For branch-1.x, it breaks the multi-jdk check, such as doc and compile.
> Correct the directory of openjdk-8 for jenkins
> --
>
> Key: HBASE-19066
> URL: https://issues.apache.org/jira/browse/HBASE-19066
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
> Fix For: 2.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13
>
> Attachments: HBASE-19066.branch-1.v0.dummy.patch,
> HBASE-19066.branch-1.v0.patch
>
>
> {code}
> 10:22:28 JAVA_HOME: /home/jenkins/tools/java/latest1.7 does not exist.
> Dockermode: attempting to switch to another.
> 10:22:28 Setting /usr/lib/jvm/java-7-openjdk-amd64 as the JAVA_HOME.
> 10:22:28 WARNING: Cannot locate JDK directory /usr/lib/jvm/java-8-oracle:
> ignoring
> 10:22:28 Modes: MultiJDK Jenkins Robot Docker ResetRepo UnitTests
> {code}
> It breaks the multi-jdk check, such as doc and compile.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19066) Correct the directory of openjdk-8 for jenkins
[
https://issues.apache.org/jira/browse/HBASE-19066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated HBASE-19066:
---
Attachment: HBASE-19066.branch-1.v0.dummy.patch
add a dummy change in client module.
> Correct the directory of openjdk-8 for jenkins
> --
>
> Key: HBASE-19066
> URL: https://issues.apache.org/jira/browse/HBASE-19066
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
> Fix For: 2.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13
>
> Attachments: HBASE-19066.branch-1.v0.dummy.patch,
> HBASE-19066.branch-1.v0.patch
>
>
> {code}
> 10:22:28 JAVA_HOME: /home/jenkins/tools/java/latest1.7 does not exist.
> Dockermode: attempting to switch to another.
> 10:22:28 Setting /usr/lib/jvm/java-7-openjdk-amd64 as the JAVA_HOME.
> 10:22:28 WARNING: Cannot locate JDK directory /usr/lib/jvm/java-8-oracle:
> ignoring
> 10:22:28 Modes: MultiJDK Jenkins Robot Docker ResetRepo UnitTests
> {code}
> For branch-1.x, it breaks the multi-jdk check, such as doc and compile.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19066) Correct the directory of openjdk-8 for jenkins
[
https://issues.apache.org/jira/browse/HBASE-19066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated HBASE-19066:
---
Status: Patch Available (was: Open)
> Correct the directory of openjdk-8 for jenkins
> --
>
> Key: HBASE-19066
> URL: https://issues.apache.org/jira/browse/HBASE-19066
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
> Fix For: 2.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13
>
> Attachments: HBASE-19066.branch-1.v0.dummy.patch,
> HBASE-19066.branch-1.v0.patch
>
>
> {code}
> 10:22:28 JAVA_HOME: /home/jenkins/tools/java/latest1.7 does not exist.
> Dockermode: attempting to switch to another.
> 10:22:28 Setting /usr/lib/jvm/java-7-openjdk-amd64 as the JAVA_HOME.
> 10:22:28 WARNING: Cannot locate JDK directory /usr/lib/jvm/java-8-oracle:
> ignoring
> 10:22:28 Modes: MultiJDK Jenkins Robot Docker ResetRepo UnitTests
> {code}
> For branch-1.x, it breaks the multi-jdk check, such as doc and compile.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19066) Correct the directory of openjdk-8 for jenkins
[
https://issues.apache.org/jira/browse/HBASE-19066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated HBASE-19066:
---
Status: Open (was: Patch Available)
> Correct the directory of openjdk-8 for jenkins
> --
>
> Key: HBASE-19066
> URL: https://issues.apache.org/jira/browse/HBASE-19066
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
> Fix For: 2.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13
>
> Attachments: HBASE-19066.branch-1.v0.dummy.patch,
> HBASE-19066.branch-1.v0.patch
>
>
> {code}
> 10:22:28 JAVA_HOME: /home/jenkins/tools/java/latest1.7 does not exist.
> Dockermode: attempting to switch to another.
> 10:22:28 Setting /usr/lib/jvm/java-7-openjdk-amd64 as the JAVA_HOME.
> 10:22:28 WARNING: Cannot locate JDK directory /usr/lib/jvm/java-8-oracle:
> ignoring
> 10:22:28 Modes: MultiJDK Jenkins Robot Docker ResetRepo UnitTests
> {code}
> For branch-1.x, it breaks the multi-jdk check, such as doc and compile.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19066) Correct the directory of openjdk-8 for jenkins
[
https://issues.apache.org/jira/browse/HBASE-19066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated HBASE-19066:
---
Fix Version/s: 2.0.0
> Correct the directory of openjdk-8 for jenkins
> --
>
> Key: HBASE-19066
> URL: https://issues.apache.org/jira/browse/HBASE-19066
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
> Fix For: 2.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13
>
> Attachments: HBASE-19066.branch-1.v0.patch
>
>
> {code}
> 10:22:28 JAVA_HOME: /home/jenkins/tools/java/latest1.7 does not exist.
> Dockermode: attempting to switch to another.
> 10:22:28 Setting /usr/lib/jvm/java-7-openjdk-amd64 as the JAVA_HOME.
> 10:22:28 WARNING: Cannot locate JDK directory /usr/lib/jvm/java-8-oracle:
> ignoring
> 10:22:28 Modes: MultiJDK Jenkins Robot Docker ResetRepo UnitTests
> {code}
> For branch-1.x, it breaks the multi-jdk check, such as doc and compile.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19066) Correct the directory of openjdk-8 for jenkins
[
https://issues.apache.org/jira/browse/HBASE-19066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214427#comment-16214427
]
Hadoop QA commented on HBASE-19066:
---
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
19s{color} | {color:blue} Docker mode activated. {color} |
| {color:blue}0{color} | {color:blue} shelldocs {color} | {color:blue} 0m
11s{color} | {color:blue} Shelldocs was not available. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} shellcheck {color} | {color:green} 0m
5s{color} | {color:green} There were no new shellcheck issues. {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
21s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 1m 10s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:4bf71c3 |
| JIRA Issue | HBASE-19066 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12893466/HBASE-19066.branch-1.v0.patch
|
| Optional Tests | asflicense shellcheck shelldocs |
| uname | Linux 0fee1c1bb0c5 3.13.0-129-generic #178-Ubuntu SMP Fri Aug 11
12:48:20 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | branch-1 / ae6a951 |
| shellcheck | v0.4.6 |
| modules | C: . U: . |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/9330/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> Correct the directory of openjdk-8 for jenkins
> --
>
> Key: HBASE-19066
> URL: https://issues.apache.org/jira/browse/HBASE-19066
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
> Fix For: 2.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13
>
> Attachments: HBASE-19066.branch-1.v0.patch
>
>
> {code}
> 10:22:28 JAVA_HOME: /home/jenkins/tools/java/latest1.7 does not exist.
> Dockermode: attempting to switch to another.
> 10:22:28 Setting /usr/lib/jvm/java-7-openjdk-amd64 as the JAVA_HOME.
> 10:22:28 WARNING: Cannot locate JDK directory /usr/lib/jvm/java-8-oracle:
> ignoring
> 10:22:28 Modes: MultiJDK Jenkins Robot Docker ResetRepo UnitTests
> {code}
> For branch-1.x, it breaks the multi-jdk check, such as doc and compile.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19066) Correct the directory of openjdk-8 for jenkins
[
https://issues.apache.org/jira/browse/HBASE-19066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214426#comment-16214426
]
Chia-Ping Tsai commented on HBASE-19066:
For consistency, the fix should be pushed to branch-2 and master also.
> Correct the directory of openjdk-8 for jenkins
> --
>
> Key: HBASE-19066
> URL: https://issues.apache.org/jira/browse/HBASE-19066
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
> Fix For: 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13
>
> Attachments: HBASE-19066.branch-1.v0.patch
>
>
> {code}
> 10:22:28 JAVA_HOME: /home/jenkins/tools/java/latest1.7 does not exist.
> Dockermode: attempting to switch to another.
> 10:22:28 Setting /usr/lib/jvm/java-7-openjdk-amd64 as the JAVA_HOME.
> 10:22:28 WARNING: Cannot locate JDK directory /usr/lib/jvm/java-8-oracle:
> ignoring
> 10:22:28 Modes: MultiJDK Jenkins Robot Docker ResetRepo UnitTests
> {code}
> For branch-1.x, it breaks the multi-jdk check, such as doc and compile.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19066) Correct the directory of openjdk-8 for jenkins
[
https://issues.apache.org/jira/browse/HBASE-19066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated HBASE-19066:
---
Status: Patch Available (was: Open)
> Correct the directory of openjdk-8 for jenkins
> --
>
> Key: HBASE-19066
> URL: https://issues.apache.org/jira/browse/HBASE-19066
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
> Fix For: 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13
>
> Attachments: HBASE-19066.branch-1.v0.patch
>
>
> {code}
> 10:22:28 JAVA_HOME: /home/jenkins/tools/java/latest1.7 does not exist.
> Dockermode: attempting to switch to another.
> 10:22:28 Setting /usr/lib/jvm/java-7-openjdk-amd64 as the JAVA_HOME.
> 10:22:28 WARNING: Cannot locate JDK directory /usr/lib/jvm/java-8-oracle:
> ignoring
> 10:22:28 Modes: MultiJDK Jenkins Robot Docker ResetRepo UnitTests
> {code}
> For branch-1.x, it breaks the multi-jdk check, such as doc and compile.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19066) Correct the directory of openjdk-8 for jenkins
[
https://issues.apache.org/jira/browse/HBASE-19066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated HBASE-19066:
---
Attachment: HBASE-19066.branch-1.v0.patch
Replace */usr/lib/jvm/java-8-oracle* by */usr/lib/jvm/java-8-openjdk-amd64*
> Correct the directory of openjdk-8 for jenkins
> --
>
> Key: HBASE-19066
> URL: https://issues.apache.org/jira/browse/HBASE-19066
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
> Fix For: 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13
>
> Attachments: HBASE-19066.branch-1.v0.patch
>
>
> {code}
> 10:22:28 JAVA_HOME: /home/jenkins/tools/java/latest1.7 does not exist.
> Dockermode: attempting to switch to another.
> 10:22:28 Setting /usr/lib/jvm/java-7-openjdk-amd64 as the JAVA_HOME.
> 10:22:28 WARNING: Cannot locate JDK directory /usr/lib/jvm/java-8-oracle:
> ignoring
> 10:22:28 Modes: MultiJDK Jenkins Robot Docker ResetRepo UnitTests
> {code}
> For branch-1.x, it breaks the multi-jdk check, such as doc and compile.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (HBASE-19066) Correct the directory of openjdk-8 for jenkins
Chia-Ping Tsai created HBASE-19066:
--
Summary: Correct the directory of openjdk-8 for jenkins
Key: HBASE-19066
URL: https://issues.apache.org/jira/browse/HBASE-19066
Project: HBase
Issue Type: Bug
Components: build
Reporter: Chia-Ping Tsai
Assignee: Chia-Ping Tsai
Fix For: 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13
{code}
10:22:28 JAVA_HOME: /home/jenkins/tools/java/latest1.7 does not exist.
Dockermode: attempting to switch to another.
10:22:28 Setting /usr/lib/jvm/java-7-openjdk-amd64 as the JAVA_HOME.
10:22:28 WARNING: Cannot locate JDK directory /usr/lib/jvm/java-8-oracle:
ignoring
10:22:28 Modes: MultiJDK Jenkins Robot Docker ResetRepo UnitTests
{code}
For branch-1.x, it breaks the multi-jdk check, such as doc and compile.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19046) RegionObserver#postCompactSelection Passing an ImmutableList param of PB type
[ https://issues.apache.org/jira/browse/HBASE-19046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anoop Sam John updated HBASE-19046: --- Attachment: HBASE-19046.patch > RegionObserver#postCompactSelection Passing an ImmutableList param of PB type > -- > > Key: HBASE-19046 > URL: https://issues.apache.org/jira/browse/HBASE-19046 > Project: HBase > Issue Type: Sub-task > Components: Coprocessors >Reporter: Anoop Sam John >Assignee: Anoop Sam John > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-19046.patch, HBASE-19046.patch > > > Dont think there is any specific need for passing this PB type. We can just > pass an unmodifiableList list object. Javadoc can say this is an > unmodifiableList . Thats it . No need that the type itself to be > Immutable... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19065) HRegion#bulkLoadHFiles() should wait for concurrent Region#flush() to finish
[
https://issues.apache.org/jira/browse/HBASE-19065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214392#comment-16214392
]
Ted Yu commented on HBASE-19065:
Patch v1 utilizes the method introduced by HBASE-18099.
> HRegion#bulkLoadHFiles() should wait for concurrent Region#flush() to finish
>
>
> Key: HBASE-19065
> URL: https://issues.apache.org/jira/browse/HBASE-19065
> Project: HBase
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Ted Yu
> Attachments: 19065.v1.txt
>
>
> When I was debugging bulk load failure, I saw the following in region server
> log:
> {code}
> 2017-10-17 23:05:28,795 DEBUG
> [B.defaultRpcServer.handler=0,queue=0,port=16020] regionserver.HRegion: NOT
> flushing memstore for region mx_,
> f449669a8b0341e4edbd2ebdacc72094f449669a8b0341e4edbd2ebdacc7209420150711,1504909319142.52d496ba39036e0c2cc9522895ad438f.,
> flushing=true, writesEnabled=true
> 2017-10-17 23:05:28,796 ERROR
> [B.defaultRpcServer.handler=0,queue=0,port=16020]
> access.SecureBulkLoadEndpoint: Failed to complete bulk load
> java.io.IOException: Could not bulk load with an assigned sequential ID
> because the flush didn't run. Reason for not flushing: Not flushing since
> already flushing
> at
> org.apache.hadoop.hbase.regionserver.HRegion.bulkLoadHFiles(HRegion.java:5282)
> at
> org.apache.hadoop.hbase.security.access.SecureBulkLoadEndpoint$1.run(SecureBulkLoadEndpoint.java:292)
> at
> org.apache.hadoop.hbase.security.access.SecureBulkLoadEndpoint$1.run(SecureBulkLoadEndpoint.java:275)
> {code}
> HRegion#bulkLoadHFiles() should wait for the concurrent flush to complete.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19065) HRegion#bulkLoadHFiles() should wait for concurrent Region#flush() to finish
[
https://issues.apache.org/jira/browse/HBASE-19065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-19065:
---
Status: Patch Available (was: Open)
> HRegion#bulkLoadHFiles() should wait for concurrent Region#flush() to finish
>
>
> Key: HBASE-19065
> URL: https://issues.apache.org/jira/browse/HBASE-19065
> Project: HBase
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Ted Yu
> Attachments: 19065.v1.txt
>
>
> When I was debugging bulk load failure, I saw the following in region server
> log:
> {code}
> 2017-10-17 23:05:28,795 DEBUG
> [B.defaultRpcServer.handler=0,queue=0,port=16020] regionserver.HRegion: NOT
> flushing memstore for region mx_,
> f449669a8b0341e4edbd2ebdacc72094f449669a8b0341e4edbd2ebdacc7209420150711,1504909319142.52d496ba39036e0c2cc9522895ad438f.,
> flushing=true, writesEnabled=true
> 2017-10-17 23:05:28,796 ERROR
> [B.defaultRpcServer.handler=0,queue=0,port=16020]
> access.SecureBulkLoadEndpoint: Failed to complete bulk load
> java.io.IOException: Could not bulk load with an assigned sequential ID
> because the flush didn't run. Reason for not flushing: Not flushing since
> already flushing
> at
> org.apache.hadoop.hbase.regionserver.HRegion.bulkLoadHFiles(HRegion.java:5282)
> at
> org.apache.hadoop.hbase.security.access.SecureBulkLoadEndpoint$1.run(SecureBulkLoadEndpoint.java:292)
> at
> org.apache.hadoop.hbase.security.access.SecureBulkLoadEndpoint$1.run(SecureBulkLoadEndpoint.java:275)
> {code}
> HRegion#bulkLoadHFiles() should wait for the concurrent flush to complete.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19065) HRegion#bulkLoadHFiles() should wait for concurrent Region#flush() to finish
[
https://issues.apache.org/jira/browse/HBASE-19065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-19065:
---
Attachment: 19065.v1.txt
> HRegion#bulkLoadHFiles() should wait for concurrent Region#flush() to finish
>
>
> Key: HBASE-19065
> URL: https://issues.apache.org/jira/browse/HBASE-19065
> Project: HBase
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Ted Yu
> Attachments: 19065.v1.txt
>
>
> When I was debugging bulk load failure, I saw the following in region server
> log:
> {code}
> 2017-10-17 23:05:28,795 DEBUG
> [B.defaultRpcServer.handler=0,queue=0,port=16020] regionserver.HRegion: NOT
> flushing memstore for region mx_,
> f449669a8b0341e4edbd2ebdacc72094f449669a8b0341e4edbd2ebdacc7209420150711,1504909319142.52d496ba39036e0c2cc9522895ad438f.,
> flushing=true, writesEnabled=true
> 2017-10-17 23:05:28,796 ERROR
> [B.defaultRpcServer.handler=0,queue=0,port=16020]
> access.SecureBulkLoadEndpoint: Failed to complete bulk load
> java.io.IOException: Could not bulk load with an assigned sequential ID
> because the flush didn't run. Reason for not flushing: Not flushing since
> already flushing
> at
> org.apache.hadoop.hbase.regionserver.HRegion.bulkLoadHFiles(HRegion.java:5282)
> at
> org.apache.hadoop.hbase.security.access.SecureBulkLoadEndpoint$1.run(SecureBulkLoadEndpoint.java:292)
> at
> org.apache.hadoop.hbase.security.access.SecureBulkLoadEndpoint$1.run(SecureBulkLoadEndpoint.java:275)
> {code}
> HRegion#bulkLoadHFiles() should wait for the concurrent flush to complete.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (HBASE-19065) HRegion#bulkLoadHFiles() should wait for concurrent Region#flush() to finish
Ted Yu created HBASE-19065:
--
Summary: HRegion#bulkLoadHFiles() should wait for concurrent
Region#flush() to finish
Key: HBASE-19065
URL: https://issues.apache.org/jira/browse/HBASE-19065
Project: HBase
Issue Type: Bug
Reporter: Ted Yu
Assignee: Ted Yu
When I was debugging bulk load failure, I saw the following in region server
log:
{code}
2017-10-17 23:05:28,795 DEBUG [B.defaultRpcServer.handler=0,queue=0,port=16020]
regionserver.HRegion: NOT flushing memstore for region mx_,
f449669a8b0341e4edbd2ebdacc72094f449669a8b0341e4edbd2ebdacc7209420150711,1504909319142.52d496ba39036e0c2cc9522895ad438f.,
flushing=true, writesEnabled=true
2017-10-17 23:05:28,796 ERROR [B.defaultRpcServer.handler=0,queue=0,port=16020]
access.SecureBulkLoadEndpoint: Failed to complete bulk load
java.io.IOException: Could not bulk load with an assigned sequential ID because
the flush didn't run. Reason for not flushing: Not flushing since already
flushing
at
org.apache.hadoop.hbase.regionserver.HRegion.bulkLoadHFiles(HRegion.java:5282)
at
org.apache.hadoop.hbase.security.access.SecureBulkLoadEndpoint$1.run(SecureBulkLoadEndpoint.java:292)
at
org.apache.hadoop.hbase.security.access.SecureBulkLoadEndpoint$1.run(SecureBulkLoadEndpoint.java:275)
{code}
HRegion#bulkLoadHFiles() should wait for the concurrent flush to complete.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19057) Merge branch HBASE-18410 to master branch
[
https://issues.apache.org/jira/browse/HBASE-19057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214380#comment-16214380
]
Anoop Sam John commented on HBASE-19057:
[~openinx] Checked the test case and got it.. So the order of filter methods
invocation- This is being used by filters like PrefixFilter. Only at
filterRowKey, the prefix is been checked. So if we change this now , it will
be big behave change. So better dont do this. Checking the old code, seems
even for AND filter, we were not doing the bypass.
{code}
for (int i = 0; i < listize; i++) {
Filter filter = filters.get(i);
if (this.operator == Operator.MUST_PASS_ALL) {
if (filter.filterAllRemaining() || filter.filterRowKey(firstRowCell)) {
flag = true;
}
} else if (this.operator == Operator.MUST_PASS_ONE) {
if (!filter.filterAllRemaining() && !filter.filterRowKey(firstRowCell))
{
flag = false;
}
}
}
return flag;
{code}
So we better not change even that. Pls add some fat comments here saying why
we are not doing the short circuit return path.
> Merge branch HBASE-18410 to master branch
> -
>
> Key: HBASE-19057
> URL: https://issues.apache.org/jira/browse/HBASE-19057
> Project: HBase
> Issue Type: Sub-task
> Components: Filters
>Reporter: Zheng Hu
>Assignee: Zheng Hu
>Priority: Blocker
> Fix For: 2.0.0-alpha-4
>
> Attachments: HBASE-19057-HBASE-18410.v1.patch
>
>
> Open this issue to fix conflict , run HadoopQA and gather other feedback.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18352) Enable Replica tests that were disabled by Proc-V2 AM in HBASE-14614
[ https://issues.apache.org/jira/browse/HBASE-18352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214363#comment-16214363 ] huaxiang sun commented on HBASE-18352: -- Posting the progress so far, testCreateTableWithMultipleReplicas failed after enabling this test. Even with HBASE-18946, still saw the failure with the whole cluster shutdown and comes up. // Now shut the whole cluster down, and verify the assignments are kept so that the // availability constraints are met. The issue is that when the cluster is up, it tries to retain the assignment, and since in local unittest environment, all hostname(ip) for region server are same, then it will try to randomly assign these regions and result in primary/replica region being assigned to the same host. I need to check how it works in branch-1, maybe I am missing something here. > Enable Replica tests that were disabled by Proc-V2 AM in HBASE-14614 > > > Key: HBASE-18352 > URL: https://issues.apache.org/jira/browse/HBASE-18352 > Project: HBase > Issue Type: Bug > Components: test >Affects Versions: 2.0.0-alpha-1 >Reporter: Stephen Yuan Jiang >Assignee: huaxiang sun > > The following replica tests were disabled by Core Proc-V2 AM in HBASE-14614: > - Disabled parts of...testCreateTableWithMultipleReplicas in > TestMasterOperationsForRegionReplicas There is an issue w/ assigning more > replicas if number of replicas is changed on us. See '/* DISABLED! FOR > NOW'. > - Disabled testRegionReplicasOnMidClusterHighReplication in > TestStochasticLoadBalancer2 > - Disabled testFlushAndCompactionsInPrimary in TestRegionReplicas > This JIRA tracks the work to enable them (or modify/remove if not applicable). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-16290) Dump summary of callQueue content; can help debugging
[
https://issues.apache.org/jira/browse/HBASE-16290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214334#comment-16214334
]
Hadoop QA commented on HBASE-16290:
---
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
11s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 3 new or modified test
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
29s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
36s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
42s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
14s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
41s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
11s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
32s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
42s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
37s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
37s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
45s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
18s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 3m
51s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
37m 29s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
30s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
26s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 94m
17s{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
12s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}152m 16s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:cb5c477 |
| JIRA Issue | HBASE-16290 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12893452/HBASE-16290.master.007.patch
|
| Optional Tests | asflicense javac javadoc unit findbugs shadedjars
hadoopcheck hbaseanti checkstyle compile |
| uname | Linux 2489afc03fff 3.13.0-119-generic #166-Ubuntu SMP Wed May 3
12:18:55 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / 2ee8690 |
| Default Java | 1.8.0_141 |
| findbugs | v3.1.0-RC3 |
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/9325/testReport/ |
| modules | C: hbase-server U: hbase-server |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/9325/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> Dump summary of callQueue content; can help debugging
>
[jira] [Commented] (HBASE-18824) Add meaningful comment to HConstants.LATEST_TIMESTAMP to explain why it is MAX_VALUE
[
https://issues.apache.org/jira/browse/HBASE-18824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214320#comment-16214320
]
Xiang Li commented on HBASE-18824:
--
Thanks very much [~jerryhe] for the suggestion!
> Add meaningful comment to HConstants.LATEST_TIMESTAMP to explain why it is
> MAX_VALUE
>
>
> Key: HBASE-18824
> URL: https://issues.apache.org/jira/browse/HBASE-18824
> Project: HBase
> Issue Type: Improvement
>Reporter: Xiang Li
>Assignee: Xiang Li
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-18824.master.000.patch,
> HBASE-18824.master.001.patch, HBASE-18824.master.002.patch,
> HBASE-18824.master.003.patch, HBASE-18824.master.004.patch,
> HBASE-18824.master.005.patch
>
>
> Thanks to [Jerry and Chia-Ping Tsai's
> comments|https://issues.apache.org/jira/browse/HBASE-18824?focusedCommentId=16167392=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16167392]
> to correct my wrong understanding.
> The following documentation says that by default(when the timestamp is not
> specified for Put or Delete), system uses the server's {{currentTimeMillis}}.
> 1. In chapter 27.2.4 Put
> bq. Doing a put always creates a new version of a cell, at a certain
> timestamp. {color:#205081}By default the system uses the server’s
> currentTimeMillis{color}, ...
> 2. In chapter 27.2.5 Delete
> bq. Deletes work by creating tombstone markers. For example, let’s suppose we
> want to delete a row. For this you can specify a version, or else
> {color:#205081}by default the currentTimeMillis is used.{color}...
> It seems not consistent with the code. Because in the client side's code,
> when timestamp is not specified, HConstants.LATEST_TIMESTAMP is used, which
> is Long.MAX_VALUE, rather than {{System.currentTimeMillis()}}.
> However, the documentation is correct, because on the server side, timestamp
> of Put cell with HConstants.LATEST_TIMESTAMP will be replaced with server's
> {{currentTimeMillis}}.
> So we decide to add more comments to HConstants.LATEST_TIMESTAMP to help the
> new comers steer clear of the confusion.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18824) Add meaningful comment to HConstants.LATEST_TIMESTAMP to explain why it is MAX_VALUE
[
https://issues.apache.org/jira/browse/HBASE-18824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214319#comment-16214319
]
Xiang Li commented on HBASE-18824:
--
Thanks very much [~chia7712] for the suggestion and patience!
> Add meaningful comment to HConstants.LATEST_TIMESTAMP to explain why it is
> MAX_VALUE
>
>
> Key: HBASE-18824
> URL: https://issues.apache.org/jira/browse/HBASE-18824
> Project: HBase
> Issue Type: Improvement
>Reporter: Xiang Li
>Assignee: Xiang Li
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-18824.master.000.patch,
> HBASE-18824.master.001.patch, HBASE-18824.master.002.patch,
> HBASE-18824.master.003.patch, HBASE-18824.master.004.patch,
> HBASE-18824.master.005.patch
>
>
> Thanks to [Jerry and Chia-Ping Tsai's
> comments|https://issues.apache.org/jira/browse/HBASE-18824?focusedCommentId=16167392=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16167392]
> to correct my wrong understanding.
> The following documentation says that by default(when the timestamp is not
> specified for Put or Delete), system uses the server's {{currentTimeMillis}}.
> 1. In chapter 27.2.4 Put
> bq. Doing a put always creates a new version of a cell, at a certain
> timestamp. {color:#205081}By default the system uses the server’s
> currentTimeMillis{color}, ...
> 2. In chapter 27.2.5 Delete
> bq. Deletes work by creating tombstone markers. For example, let’s suppose we
> want to delete a row. For this you can specify a version, or else
> {color:#205081}by default the currentTimeMillis is used.{color}...
> It seems not consistent with the code. Because in the client side's code,
> when timestamp is not specified, HConstants.LATEST_TIMESTAMP is used, which
> is Long.MAX_VALUE, rather than {{System.currentTimeMillis()}}.
> However, the documentation is correct, because on the server side, timestamp
> of Put cell with HConstants.LATEST_TIMESTAMP will be replaced with server's
> {{currentTimeMillis}}.
> So we decide to add more comments to HConstants.LATEST_TIMESTAMP to help the
> new comers steer clear of the confusion.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19053) Split out o.a.h.h.http from hbase-server into a separate module
[
https://issues.apache.org/jira/browse/HBASE-19053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214312#comment-16214312
]
Hadoop QA commented on HBASE-19053:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
16s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 41 new or modified test
files. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
27s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
29s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 6m
14s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 3m
43s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
0s{color} | {color:blue} Skipped patched modules with no Java source:
hbase-shaded/hbase-shaded-mapreduce . {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 5m
23s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 5m
27s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
11s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 7m
21s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 6m
41s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 6m
41s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 0m
24s{color} | {color:red} hbase-common: The patch generated 19 new + 0 unchanged
- 0 fixed = 19 total (was 0) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 0m
15s{color} | {color:red} hbase-http: The patch generated 113 new + 0 unchanged
- 0 fixed = 113 total (was 0) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 1m
51s{color} | {color:red} root: The patch generated 39 new + 239 unchanged - 39
fixed = 278 total (was 278) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 0m
16s{color} | {color:red} hbase-rest: The patch generated 1 new + 15 unchanged -
2 fixed = 16 total (was 17) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 0m
51s{color} | {color:red} hbase-server: The patch generated 1 new + 129
unchanged - 132 fixed = 130 total (was 261) {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red} 0m
0s{color} | {color:red} The patch has 2 line(s) that end in whitespace. Use git
apply --whitespace=fix <>. Refer https://git-scm.com/docs/git-apply
{color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green} 0m
8s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 1m
8s{color} | {color:red} The patch causes 16 errors with Hadoop v2.4.0. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 2m
7s{color} | {color:red} The patch causes 16 errors with Hadoop v2.4.1. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 3m
6s{color} | {color:red} The patch causes 16 errors with Hadoop v2.5.0. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 4m
9s{color} | {color:red} The patch causes 16 errors with Hadoop v2.5.1. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 5m
12s{color} | {color:red} The patch causes 16 errors with Hadoop v2.5.2. {color}
|
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
0s{color} | {color:blue} Skipped patched modules with no Java source: .
hbase-shaded/hbase-shaded-mapreduce {color} |
|
[jira] [Commented] (HBASE-18754) Get rid of Writable from TimeRangeTracker
[
https://issues.apache.org/jira/browse/HBASE-18754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214302#comment-16214302
]
Hadoop QA commented on HBASE-18754:
---
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
10s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 2 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
30s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
52s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
27s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
25s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
41s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 5m
7s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 5m
2s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
53s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
20s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
55s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
27s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} cc {color} | {color:green} 1m
27s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
27s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
23s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
47s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 3m
51s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
37m 21s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} hbaseprotoc {color} | {color:green}
1m 6s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 4m
54s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
49s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
27s{color} | {color:green} hbase-protocol-shaded in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 88m
59s{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 10m
26s{color} | {color:green} hbase-mapreduce in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
46s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}169m 30s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:cb5c477 |
| JIRA Issue | HBASE-18754 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12893448/HBASE-18754.v0.patch |
| Optional Tests | asflicense javac javadoc unit
[jira] [Updated] (HBASE-16290) Dump summary of callQueue content; can help debugging
[ https://issues.apache.org/jira/browse/HBASE-16290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreeram Venkatasubramanian updated HBASE-16290: --- Attachment: HBASE-16290.master.007.patch > Dump summary of callQueue content; can help debugging > - > > Key: HBASE-16290 > URL: https://issues.apache.org/jira/browse/HBASE-16290 > Project: HBase > Issue Type: Bug > Components: Operability >Affects Versions: 2.0.0 >Reporter: stack >Assignee: Sreeram Venkatasubramanian > Labels: beginner > Fix For: 2.0.0 > > Attachments: DebugDump_screenshot.png, HBASE-16290.master.001.patch, > HBASE-16290.master.002.patch, HBASE-16290.master.003.patch, > HBASE-16290.master.004.patch, HBASE-16290.master.005.patch, > HBASE-16290.master.006.patch, HBASE-16290.master.007.patch, Sample Summary.txt > > > Being able to get a clue what is in a backedup callQueue could give insight > on what is going on on a jacked server. Just needs to summarize count, sizes, > call types. Useful debugging. In a servlet? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-16417) In-Memory MemStore Policy for Flattening and Compactions
[ https://issues.apache.org/jira/browse/HBASE-16417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214297#comment-16214297 ] Eshcar Hillel commented on HBASE-16417: --- QA passed. Any more comments? > In-Memory MemStore Policy for Flattening and Compactions > > > Key: HBASE-16417 > URL: https://issues.apache.org/jira/browse/HBASE-16417 > Project: HBase > Issue Type: Sub-task >Reporter: Anastasia Braginsky >Assignee: Eshcar Hillel > Fix For: 3.0.0 > > Attachments: HBASE-16417 - Adaptive Compaction Policy - 20171001.pdf, > HBASE-16417 - parameter tuning - 20171001.pdf, HBASE-16417-V01.patch, > HBASE-16417-benchmarkresults-20161101.pdf, > HBASE-16417-benchmarkresults-20161110.pdf, > HBASE-16417-benchmarkresults-20161123.pdf, > HBASE-16417-benchmarkresults-20161205.pdf, > HBASE-16417-benchmarkresults-20170309.pdf, > HBASE-16417-benchmarkresults-20170317.pdf, HBASE-16417.01.patch, > HBASE-16417.02.patch, HBASE-16417.03.patch, HBASE-16417.04.patch, > HBASE-16417.05.patch, HBASE-16417.06.patch, HBASE-16417.07.patch, > HBASE-16417.07.patch, HBASE-16417.08.patch, HBASE-16417.09.patch, > HBASE-16417.10.patch > > > This Jira explores the performance of different memstore compaction policies. > It presents the result of write-only workload evaluation as well as read > performance in read-write workloads. > We investigate several settings of hardware (SSD, HDD), key distribution > (Zipf, uniform), with multiple settings of the system, and compare measures > like write throughput, read latency, write volume, total gc time, etc. > The submitted patch sets some system properties at the values yielding > optimal performance. In addition we suggest a new Adaptive memstore > compaction policy that shows good tradeoffs between write throughput and > write volume. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19019) QA fails on hbase-thrift module with timeout
[
https://issues.apache.org/jira/browse/HBASE-19019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214283#comment-16214283
]
Hadoop QA commented on HBASE-19019:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
20s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 7m
39s{color} | {color:green} branch-1.1 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
23s{color} | {color:green} branch-1.1 passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
26s{color} | {color:green} branch-1.1 passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
32s{color} | {color:green} branch-1.1 passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 3m
11s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
16s{color} | {color:green} branch-1.1 passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
36s{color} | {color:green} branch-1.1 passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
25s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
22s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
22s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
21s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
17s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
1s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 2m
5s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
19m 22s{color} | {color:green} Patch does not cause any errors with Hadoop
2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3.
{color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
31s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
34s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 18m 32s{color}
| {color:red} hbase-thrift in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
9s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 56m 25s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.thrift.TestThriftHttpServer |
| Timed out junit tests |
org.apache.hadoop.hbase.thrift.TestThriftServerCmdLine |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:a527708 |
| JIRA Issue | HBASE-19019 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12893449/HBASE-19019.branch-1.1.dummy.patch
|
| Optional Tests | asflicense javac javadoc unit findbugs shadedjars
hadoopcheck hbaseanti checkstyle compile |
| uname | Linux a3706c66baf6 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12
13:48:03 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | branch-1.1 / a527708 |
| Default Java | 1.7.0_151 |
| findbugs | v3.0.0 |
| unit |
[jira] [Commented] (HBASE-16417) In-Memory MemStore Policy for Flattening and Compactions
[
https://issues.apache.org/jira/browse/HBASE-16417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214277#comment-16214277
]
Hadoop QA commented on HBASE-16417:
---
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
13s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 6 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
20s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
37s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
12s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
59s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
33s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 5m
36s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 4m
23s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
8s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
20s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
16s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
25s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
25s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
10s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
38s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
10s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
41m 48s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 4m
21s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
3s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m
32s{color} | {color:green} hbase-common in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m
51s{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}110m
30s{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
35s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}189m 2s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:cb5c477 |
| JIRA Issue | HBASE-16417 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12893447/HBASE-16417.10.patch |
| Optional Tests | asflicense javac javadoc unit findbugs shadedjars
hadoopcheck hbaseanti checkstyle compile |
| uname | Linux 7cebf7e210b7 3.13.0-119-generic #166-Ubuntu SMP Wed May 3
12:18:55 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
[jira] [Updated] (HBASE-19019) QA fails on hbase-thrift module with timeout
[
https://issues.apache.org/jira/browse/HBASE-19019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated HBASE-19019:
---
Status: Patch Available (was: Open)
> QA fails on hbase-thrift module with timeout
>
>
> Key: HBASE-19019
> URL: https://issues.apache.org/jira/browse/HBASE-19019
> Project: HBase
> Issue Type: Bug
> Components: Thrift
>Reporter: Peter Somogyi
>Assignee: Chia-Ping Tsai
>Priority: Critical
> Attachments: HBASE-19019.branch-1.001.patch,
> HBASE-19019.branch-1.002.patch, HBASE-19019.branch-1.1.dummy.patch,
> HBASE-19019.branch-1.2.dummy.patch, HBASE-19019.master.001.patch
>
>
> For any modification in hbase-thrift module the precommit build fails with
> timeout for {{TestThriftServerCmdLine}}. I noticed this failure on multiple
> patches: HBASE-18967 and HBASE-18996 even when the patch did not contain any
> modification
> (https://issues.apache.org/jira/secure/attachment/12892414/HBASE-18967.branch-1.3.002.patch)
> The {{TestThriftServerCmdLine}} test passes locally on both mentioned patches.
> One failure: https://builds.apache.org/job/PreCommit-HBASE-Build/9127/
> {code}
> [INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ hbase-thrift ---
> [INFO] Surefire report directory:
> /testptch/hbase/hbase-thrift/target/surefire-reports
> [INFO] Using configured provider
> org.apache.maven.surefire.junitcore.JUnitCoreProvider
> [INFO] parallel='none', perCoreThreadCount=true, threadCount=0,
> useUnlimitedThreads=false, threadCountSuites=0, threadCountClasses=0,
> threadCountMethods=0, parallelOptimized=true
> ---
> T E S T S
> ---
> Running org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandler
> Tests run: 29, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 48.201 sec -
> in org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandler
> Running
> org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithReadOnly
> Tests run: 15, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.257 sec -
> in org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithReadOnly
> Running
> org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithLabels
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.621 sec -
> in org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithLabels
> Running org.apache.hadoop.hbase.thrift.TestCallQueue
> Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.473 sec -
> in org.apache.hadoop.hbase.thrift.TestCallQueue
> Running org.apache.hadoop.hbase.thrift.TestThriftHttpServer
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.239 sec -
> in org.apache.hadoop.hbase.thrift.TestThriftHttpServer
> Running org.apache.hadoop.hbase.thrift.TestThriftServer
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 75.55 sec -
> in org.apache.hadoop.hbase.thrift.TestThriftServer
> Running org.apache.hadoop.hbase.thrift.TestThriftServerCmdLine
> Results :
> Tests run: 72, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 18:33.104s
> [INFO] Finished at: Mon Oct 16 03:42:59 UTC 2017
> [INFO] Final Memory: 61M/1299M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test (default-test) on
> project hbase-thrift: There was a timeout or other error in the fork -> [Help
> 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19019) QA fails on hbase-thrift module with timeout
[
https://issues.apache.org/jira/browse/HBASE-19019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated HBASE-19019:
---
Attachment: HBASE-19019.branch-1.1.dummy.patch
> QA fails on hbase-thrift module with timeout
>
>
> Key: HBASE-19019
> URL: https://issues.apache.org/jira/browse/HBASE-19019
> Project: HBase
> Issue Type: Bug
> Components: Thrift
>Reporter: Peter Somogyi
>Assignee: Chia-Ping Tsai
>Priority: Critical
> Attachments: HBASE-19019.branch-1.001.patch,
> HBASE-19019.branch-1.002.patch, HBASE-19019.branch-1.1.dummy.patch,
> HBASE-19019.branch-1.2.dummy.patch, HBASE-19019.master.001.patch
>
>
> For any modification in hbase-thrift module the precommit build fails with
> timeout for {{TestThriftServerCmdLine}}. I noticed this failure on multiple
> patches: HBASE-18967 and HBASE-18996 even when the patch did not contain any
> modification
> (https://issues.apache.org/jira/secure/attachment/12892414/HBASE-18967.branch-1.3.002.patch)
> The {{TestThriftServerCmdLine}} test passes locally on both mentioned patches.
> One failure: https://builds.apache.org/job/PreCommit-HBASE-Build/9127/
> {code}
> [INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ hbase-thrift ---
> [INFO] Surefire report directory:
> /testptch/hbase/hbase-thrift/target/surefire-reports
> [INFO] Using configured provider
> org.apache.maven.surefire.junitcore.JUnitCoreProvider
> [INFO] parallel='none', perCoreThreadCount=true, threadCount=0,
> useUnlimitedThreads=false, threadCountSuites=0, threadCountClasses=0,
> threadCountMethods=0, parallelOptimized=true
> ---
> T E S T S
> ---
> Running org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandler
> Tests run: 29, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 48.201 sec -
> in org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandler
> Running
> org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithReadOnly
> Tests run: 15, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.257 sec -
> in org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithReadOnly
> Running
> org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithLabels
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.621 sec -
> in org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithLabels
> Running org.apache.hadoop.hbase.thrift.TestCallQueue
> Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.473 sec -
> in org.apache.hadoop.hbase.thrift.TestCallQueue
> Running org.apache.hadoop.hbase.thrift.TestThriftHttpServer
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.239 sec -
> in org.apache.hadoop.hbase.thrift.TestThriftHttpServer
> Running org.apache.hadoop.hbase.thrift.TestThriftServer
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 75.55 sec -
> in org.apache.hadoop.hbase.thrift.TestThriftServer
> Running org.apache.hadoop.hbase.thrift.TestThriftServerCmdLine
> Results :
> Tests run: 72, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 18:33.104s
> [INFO] Finished at: Mon Oct 16 03:42:59 UTC 2017
> [INFO] Final Memory: 61M/1299M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test (default-test) on
> project hbase-thrift: There was a timeout or other error in the fork -> [Help
> 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19019) QA fails on hbase-thrift module with timeout
[
https://issues.apache.org/jira/browse/HBASE-19019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated HBASE-19019:
---
Status: Open (was: Patch Available)
> QA fails on hbase-thrift module with timeout
>
>
> Key: HBASE-19019
> URL: https://issues.apache.org/jira/browse/HBASE-19019
> Project: HBase
> Issue Type: Bug
> Components: Thrift
>Reporter: Peter Somogyi
>Assignee: Chia-Ping Tsai
>Priority: Critical
> Attachments: HBASE-19019.branch-1.001.patch,
> HBASE-19019.branch-1.002.patch, HBASE-19019.branch-1.1.dummy.patch,
> HBASE-19019.branch-1.2.dummy.patch, HBASE-19019.master.001.patch
>
>
> For any modification in hbase-thrift module the precommit build fails with
> timeout for {{TestThriftServerCmdLine}}. I noticed this failure on multiple
> patches: HBASE-18967 and HBASE-18996 even when the patch did not contain any
> modification
> (https://issues.apache.org/jira/secure/attachment/12892414/HBASE-18967.branch-1.3.002.patch)
> The {{TestThriftServerCmdLine}} test passes locally on both mentioned patches.
> One failure: https://builds.apache.org/job/PreCommit-HBASE-Build/9127/
> {code}
> [INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ hbase-thrift ---
> [INFO] Surefire report directory:
> /testptch/hbase/hbase-thrift/target/surefire-reports
> [INFO] Using configured provider
> org.apache.maven.surefire.junitcore.JUnitCoreProvider
> [INFO] parallel='none', perCoreThreadCount=true, threadCount=0,
> useUnlimitedThreads=false, threadCountSuites=0, threadCountClasses=0,
> threadCountMethods=0, parallelOptimized=true
> ---
> T E S T S
> ---
> Running org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandler
> Tests run: 29, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 48.201 sec -
> in org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandler
> Running
> org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithReadOnly
> Tests run: 15, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.257 sec -
> in org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithReadOnly
> Running
> org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithLabels
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.621 sec -
> in org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithLabels
> Running org.apache.hadoop.hbase.thrift.TestCallQueue
> Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.473 sec -
> in org.apache.hadoop.hbase.thrift.TestCallQueue
> Running org.apache.hadoop.hbase.thrift.TestThriftHttpServer
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.239 sec -
> in org.apache.hadoop.hbase.thrift.TestThriftHttpServer
> Running org.apache.hadoop.hbase.thrift.TestThriftServer
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 75.55 sec -
> in org.apache.hadoop.hbase.thrift.TestThriftServer
> Running org.apache.hadoop.hbase.thrift.TestThriftServerCmdLine
> Results :
> Tests run: 72, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 18:33.104s
> [INFO] Finished at: Mon Oct 16 03:42:59 UTC 2017
> [INFO] Final Memory: 61M/1299M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test (default-test) on
> project hbase-thrift: There was a timeout or other error in the fork -> [Help
> 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (HBASE-19019) QA fails on hbase-thrift module with timeout
[
https://issues.apache.org/jira/browse/HBASE-19019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai reassigned HBASE-19019:
--
Assignee: Chia-Ping Tsai
> QA fails on hbase-thrift module with timeout
>
>
> Key: HBASE-19019
> URL: https://issues.apache.org/jira/browse/HBASE-19019
> Project: HBase
> Issue Type: Bug
> Components: Thrift
>Reporter: Peter Somogyi
>Assignee: Chia-Ping Tsai
>Priority: Critical
> Attachments: HBASE-19019.branch-1.001.patch,
> HBASE-19019.branch-1.002.patch, HBASE-19019.branch-1.2.dummy.patch,
> HBASE-19019.master.001.patch
>
>
> For any modification in hbase-thrift module the precommit build fails with
> timeout for {{TestThriftServerCmdLine}}. I noticed this failure on multiple
> patches: HBASE-18967 and HBASE-18996 even when the patch did not contain any
> modification
> (https://issues.apache.org/jira/secure/attachment/12892414/HBASE-18967.branch-1.3.002.patch)
> The {{TestThriftServerCmdLine}} test passes locally on both mentioned patches.
> One failure: https://builds.apache.org/job/PreCommit-HBASE-Build/9127/
> {code}
> [INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ hbase-thrift ---
> [INFO] Surefire report directory:
> /testptch/hbase/hbase-thrift/target/surefire-reports
> [INFO] Using configured provider
> org.apache.maven.surefire.junitcore.JUnitCoreProvider
> [INFO] parallel='none', perCoreThreadCount=true, threadCount=0,
> useUnlimitedThreads=false, threadCountSuites=0, threadCountClasses=0,
> threadCountMethods=0, parallelOptimized=true
> ---
> T E S T S
> ---
> Running org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandler
> Tests run: 29, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 48.201 sec -
> in org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandler
> Running
> org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithReadOnly
> Tests run: 15, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.257 sec -
> in org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithReadOnly
> Running
> org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithLabels
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.621 sec -
> in org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithLabels
> Running org.apache.hadoop.hbase.thrift.TestCallQueue
> Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.473 sec -
> in org.apache.hadoop.hbase.thrift.TestCallQueue
> Running org.apache.hadoop.hbase.thrift.TestThriftHttpServer
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.239 sec -
> in org.apache.hadoop.hbase.thrift.TestThriftHttpServer
> Running org.apache.hadoop.hbase.thrift.TestThriftServer
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 75.55 sec -
> in org.apache.hadoop.hbase.thrift.TestThriftServer
> Running org.apache.hadoop.hbase.thrift.TestThriftServerCmdLine
> Results :
> Tests run: 72, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 18:33.104s
> [INFO] Finished at: Mon Oct 16 03:42:59 UTC 2017
> [INFO] Final Memory: 61M/1299M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test (default-test) on
> project hbase-thrift: There was a timeout or other error in the fork -> [Help
> 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18754) Get rid of Writable from TimeRangeTracker
[ https://issues.apache.org/jira/browse/HBASE-18754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18754: --- Status: Patch Available (was: Open) > Get rid of Writable from TimeRangeTracker > - > > Key: HBASE-18754 > URL: https://issues.apache.org/jira/browse/HBASE-18754 > Project: HBase > Issue Type: Sub-task >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai > Attachments: HBASE-18754.v0.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18754) Get rid of Writable from TimeRangeTracker
[ https://issues.apache.org/jira/browse/HBASE-18754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18754: --- Attachment: HBASE-18754.v0.patch > Get rid of Writable from TimeRangeTracker > - > > Key: HBASE-18754 > URL: https://issues.apache.org/jira/browse/HBASE-18754 > Project: HBase > Issue Type: Sub-task >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai > Attachments: HBASE-18754.v0.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18690) Replace o.a.h.c.InterfaceAudience by o.a.h.h.c.InterfaceAudience
[ https://issues.apache.org/jira/browse/HBASE-18690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214235#comment-16214235 ] Chia-Ping Tsai commented on HBASE-18690: Will commit it tomorrow if no objections. FYI [~busbey] > Replace o.a.h.c.InterfaceAudience by o.a.h.h.c.InterfaceAudience > > > Key: HBASE-18690 > URL: https://issues.apache.org/jira/browse/HBASE-18690 > Project: HBase > Issue Type: Task >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai >Priority: Minor > Fix For: 1.4.0, 1.3.2, 1.5.0, 1.2.8 > > Attachments: HBASE-18690.branch-1.v0.patch, > HBASE-18690.branch-1.v0.patch, HBASE-18690.branch-1.v0.patch, > HBASE-18690.v0.patch, HBASE-18690.v0.patch > > > Some classes still import the hadoop's InterfaceAudience. > # Interns > # MetricsInfoImpl > # RestCsrfPreventionFilter > # AbstractFileStatusFilter > # FileStatusFilter -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18690) Replace o.a.h.c.InterfaceAudience by o.a.h.h.c.InterfaceAudience
[ https://issues.apache.org/jira/browse/HBASE-18690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated HBASE-18690: Fix Version/s: (was: 1.2.7) 1.2.8 > Replace o.a.h.c.InterfaceAudience by o.a.h.h.c.InterfaceAudience > > > Key: HBASE-18690 > URL: https://issues.apache.org/jira/browse/HBASE-18690 > Project: HBase > Issue Type: Task >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai >Priority: Minor > Fix For: 1.4.0, 1.3.2, 1.5.0, 1.2.8 > > Attachments: HBASE-18690.branch-1.v0.patch, > HBASE-18690.branch-1.v0.patch, HBASE-18690.branch-1.v0.patch, > HBASE-18690.v0.patch, HBASE-18690.v0.patch > > > Some classes still import the hadoop's InterfaceAudience. > # Interns > # MetricsInfoImpl > # RestCsrfPreventionFilter > # AbstractFileStatusFilter > # FileStatusFilter -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-16417) In-Memory MemStore Policy for Flattening and Compactions
[ https://issues.apache.org/jira/browse/HBASE-16417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eshcar Hillel updated HBASE-16417: -- Status: Patch Available (was: Open) > In-Memory MemStore Policy for Flattening and Compactions > > > Key: HBASE-16417 > URL: https://issues.apache.org/jira/browse/HBASE-16417 > Project: HBase > Issue Type: Sub-task >Reporter: Anastasia Braginsky >Assignee: Eshcar Hillel > Fix For: 3.0.0 > > Attachments: HBASE-16417 - Adaptive Compaction Policy - 20171001.pdf, > HBASE-16417 - parameter tuning - 20171001.pdf, HBASE-16417-V01.patch, > HBASE-16417-benchmarkresults-20161101.pdf, > HBASE-16417-benchmarkresults-20161110.pdf, > HBASE-16417-benchmarkresults-20161123.pdf, > HBASE-16417-benchmarkresults-20161205.pdf, > HBASE-16417-benchmarkresults-20170309.pdf, > HBASE-16417-benchmarkresults-20170317.pdf, HBASE-16417.01.patch, > HBASE-16417.02.patch, HBASE-16417.03.patch, HBASE-16417.04.patch, > HBASE-16417.05.patch, HBASE-16417.06.patch, HBASE-16417.07.patch, > HBASE-16417.07.patch, HBASE-16417.08.patch, HBASE-16417.09.patch, > HBASE-16417.10.patch > > > This Jira explores the performance of different memstore compaction policies. > It presents the result of write-only workload evaluation as well as read > performance in read-write workloads. > We investigate several settings of hardware (SSD, HDD), key distribution > (Zipf, uniform), with multiple settings of the system, and compare measures > like write throughput, read latency, write volume, total gc time, etc. > The submitted patch sets some system properties at the values yielding > optimal performance. In addition we suggest a new Adaptive memstore > compaction policy that shows good tradeoffs between write throughput and > write volume. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-16417) In-Memory MemStore Policy for Flattening and Compactions
[ https://issues.apache.org/jira/browse/HBASE-16417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eshcar Hillel updated HBASE-16417: -- Attachment: HBASE-16417.10.patch > In-Memory MemStore Policy for Flattening and Compactions > > > Key: HBASE-16417 > URL: https://issues.apache.org/jira/browse/HBASE-16417 > Project: HBase > Issue Type: Sub-task >Reporter: Anastasia Braginsky >Assignee: Eshcar Hillel > Fix For: 3.0.0 > > Attachments: HBASE-16417 - Adaptive Compaction Policy - 20171001.pdf, > HBASE-16417 - parameter tuning - 20171001.pdf, HBASE-16417-V01.patch, > HBASE-16417-benchmarkresults-20161101.pdf, > HBASE-16417-benchmarkresults-20161110.pdf, > HBASE-16417-benchmarkresults-20161123.pdf, > HBASE-16417-benchmarkresults-20161205.pdf, > HBASE-16417-benchmarkresults-20170309.pdf, > HBASE-16417-benchmarkresults-20170317.pdf, HBASE-16417.01.patch, > HBASE-16417.02.patch, HBASE-16417.03.patch, HBASE-16417.04.patch, > HBASE-16417.05.patch, HBASE-16417.06.patch, HBASE-16417.07.patch, > HBASE-16417.07.patch, HBASE-16417.08.patch, HBASE-16417.09.patch, > HBASE-16417.10.patch > > > This Jira explores the performance of different memstore compaction policies. > It presents the result of write-only workload evaluation as well as read > performance in read-write workloads. > We investigate several settings of hardware (SSD, HDD), key distribution > (Zipf, uniform), with multiple settings of the system, and compare measures > like write throughput, read latency, write volume, total gc time, etc. > The submitted patch sets some system properties at the values yielding > optimal performance. In addition we suggest a new Adaptive memstore > compaction policy that shows good tradeoffs between write throughput and > write volume. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-16417) In-Memory MemStore Policy for Flattening and Compactions
[ https://issues.apache.org/jira/browse/HBASE-16417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eshcar Hillel updated HBASE-16417: -- Status: Open (was: Patch Available) > In-Memory MemStore Policy for Flattening and Compactions > > > Key: HBASE-16417 > URL: https://issues.apache.org/jira/browse/HBASE-16417 > Project: HBase > Issue Type: Sub-task >Reporter: Anastasia Braginsky >Assignee: Eshcar Hillel > Fix For: 3.0.0 > > Attachments: HBASE-16417 - Adaptive Compaction Policy - 20171001.pdf, > HBASE-16417 - parameter tuning - 20171001.pdf, HBASE-16417-V01.patch, > HBASE-16417-benchmarkresults-20161101.pdf, > HBASE-16417-benchmarkresults-20161110.pdf, > HBASE-16417-benchmarkresults-20161123.pdf, > HBASE-16417-benchmarkresults-20161205.pdf, > HBASE-16417-benchmarkresults-20170309.pdf, > HBASE-16417-benchmarkresults-20170317.pdf, HBASE-16417.01.patch, > HBASE-16417.02.patch, HBASE-16417.03.patch, HBASE-16417.04.patch, > HBASE-16417.05.patch, HBASE-16417.06.patch, HBASE-16417.07.patch, > HBASE-16417.07.patch, HBASE-16417.08.patch, HBASE-16417.09.patch > > > This Jira explores the performance of different memstore compaction policies. > It presents the result of write-only workload evaluation as well as read > performance in read-write workloads. > We investigate several settings of hardware (SSD, HDD), key distribution > (Zipf, uniform), with multiple settings of the system, and compare measures > like write throughput, read latency, write volume, total gc time, etc. > The submitted patch sets some system properties at the values yielding > optimal performance. In addition we suggest a new Adaptive memstore > compaction policy that shows good tradeoffs between write throughput and > write volume. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18846) Accommodate the hbase-indexer/lily/SEP consumer deploy-type
[
https://issues.apache.org/jira/browse/HBASE-18846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214223#comment-16214223
]
Hadoop QA commented on HBASE-18846:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
11s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
45s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
53s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
58s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
22s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 6m
8s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m
0s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
38s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
54s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
51s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
51s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
56s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
21s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 5m
0s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
49m 17s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m
25s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
40s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 98m 46s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
14s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}175m 25s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests |
hadoop.hbase.security.token.TestDelegationTokenWithEncryption |
| | hadoop.hbase.security.token.TestGenerateDelegationToken |
| | hadoop.hbase.TestInfoServers |
| | hadoop.hbase.master.TestGetInfoPort |
| | hadoop.hbase.client.TestAsyncClusterAdminApi |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:cb5c477 |
| JIRA Issue | HBASE-18846 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12893444/HBASE-18846.master.005.patch
|
| Optional Tests | asflicense javac javadoc unit findbugs shadedjars
hadoopcheck hbaseanti checkstyle compile |
| uname | Linux 84c527a0c19e 3.13.0-119-generic #166-Ubuntu SMP Wed May 3
12:18:55 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build@2/component/dev-support/hbase-personality.sh
|
| git revision | master / 2ee8690 |
| Default Java | 1.8.0_141 |
| findbugs | v3.1.0-RC3 |
| unit |
[jira] [Updated] (HBASE-19064) Synchronous replication for HBase
[ https://issues.apache.org/jira/browse/HBASE-19064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-19064: -- Description: The guys from Alibaba made a presentation on HBaseCon Asia about the synchronous replication for HBase. We(Xiaomi) think this is a very useful feature for HBase so we want to bring it into the community version. This is a big feature so we plan to do it in a feature branch. was: The guys from Alibaba made a presentation in HBaseCon Asia about the synchronous replication for HBase. We(Xiaomi) think this is a very useful feature for HBase so we want to bring it into the community version. This is a big feature so we plan to do it in a feature branch. > Synchronous replication for HBase > - > > Key: HBASE-19064 > URL: https://issues.apache.org/jira/browse/HBASE-19064 > Project: HBase > Issue Type: New Feature > Components: Replication >Reporter: Duo Zhang >Assignee: Duo Zhang > Fix For: 3.0.0 > > > The guys from Alibaba made a presentation on HBaseCon Asia about the > synchronous replication for HBase. We(Xiaomi) think this is a very useful > feature for HBase so we want to bring it into the community version. > This is a big feature so we plan to do it in a feature branch. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (HBASE-19064) Synchronous replication for HBase
[ https://issues.apache.org/jira/browse/HBASE-19064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang reassigned HBASE-19064: - Assignee: Duo Zhang > Synchronous replication for HBase > - > > Key: HBASE-19064 > URL: https://issues.apache.org/jira/browse/HBASE-19064 > Project: HBase > Issue Type: New Feature > Components: Replication >Reporter: Duo Zhang >Assignee: Duo Zhang > Fix For: 3.0.0 > > > The guys from Alibaba made a presentation in HBaseCon Asia about the > synchronous replication for HBase. We(Xiaomi) think this is a very useful > feature for HBase so we want to bring it into the community version. > This is a big feature so we plan to do it in a feature branch. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-19064) Synchronous replication for HBase
Duo Zhang created HBASE-19064: - Summary: Synchronous replication for HBase Key: HBASE-19064 URL: https://issues.apache.org/jira/browse/HBASE-19064 Project: HBase Issue Type: New Feature Components: Replication Reporter: Duo Zhang Fix For: 3.0.0 The guys from Alibaba made a presentation in HBaseCon Asia about the synchronous replication for HBase. We(Xiaomi) think this is a very useful feature for HBase so we want to bring it into the community version. This is a big feature so we plan to do it in a feature branch. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19057) Merge branch HBASE-18410 to master branch
[ https://issues.apache.org/jira/browse/HBASE-19057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214205#comment-16214205 ] Duo Zhang commented on HBASE-19057: --- So what is a typical way of merging back a feature branch sir [~stack]? Do a rebase and force push on the feature branch first? So that it can be merged cleanly? Thanks. > Merge branch HBASE-18410 to master branch > - > > Key: HBASE-19057 > URL: https://issues.apache.org/jira/browse/HBASE-19057 > Project: HBase > Issue Type: Sub-task > Components: Filters >Reporter: Zheng Hu >Assignee: Zheng Hu >Priority: Blocker > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-19057-HBASE-18410.v1.patch > > > Open this issue to fix conflict , run HadoopQA and gather other feedback. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19057) Merge branch HBASE-18410 to master branch
[ https://issues.apache.org/jira/browse/HBASE-19057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-19057: -- Fix Version/s: (was: 2.0.0-beta-1) 2.0.0-alpha-4 > Merge branch HBASE-18410 to master branch > - > > Key: HBASE-19057 > URL: https://issues.apache.org/jira/browse/HBASE-19057 > Project: HBase > Issue Type: Sub-task > Components: Filters >Reporter: Zheng Hu >Assignee: Zheng Hu > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-19057-HBASE-18410.v1.patch > > > Open this issue to fix conflict , run HadoopQA and gather other feedback. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19057) Merge branch HBASE-18410 to master branch
[ https://issues.apache.org/jira/browse/HBASE-19057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-19057: -- Priority: Blocker (was: Major) > Merge branch HBASE-18410 to master branch > - > > Key: HBASE-19057 > URL: https://issues.apache.org/jira/browse/HBASE-19057 > Project: HBase > Issue Type: Sub-task > Components: Filters >Reporter: Zheng Hu >Assignee: Zheng Hu >Priority: Blocker > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-19057-HBASE-18410.v1.patch > > > Open this issue to fix conflict , run HadoopQA and gather other feedback. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19053) Split out o.a.h.h.http from hbase-server into a separate module
[
https://issues.apache.org/jira/browse/HBASE-19053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214202#comment-16214202
]
Hadoop QA commented on HBASE-19053:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
10s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 41 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
27s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
34s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 4m
56s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 2m
14s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 3m
28s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 9m
53s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
0s{color} | {color:blue} Skipped patched modules with no Java source:
hbase-shaded/hbase-shaded-mapreduce . {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 4m
12s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 4m
16s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
19s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
47s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 5m
44s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 5m
44s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 2m
22s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 3m
21s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red} 0m
0s{color} | {color:red} The patch has 2 line(s) that end in whitespace. Use git
apply --whitespace=fix <>. Refer https://git-scm.com/docs/git-apply
{color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green} 0m
7s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:red}-1{color} | {color:red} shadedjars {color} | {color:red} 4m
27s{color} | {color:red} patch has 12 errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
37m 6s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
0s{color} | {color:blue} Skipped patched modules with no Java source:
hbase-shaded/hbase-shaded-mapreduce . {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 4m
40s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 3m
53s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}112m 25s{color}
| {color:red} root in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
17s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}202m 32s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:cb5c477 |
| JIRA Issue | HBASE-19053 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12893441/HBASE-19053.master.003.patch
|
| Optional Tests
