HBASE-24280 TestSecureRESTServer started failing in nightlies for Had…#1603
HBASE-24280 TestSecureRESTServer started failing in nightlies for Had…#1603stoty wants to merge 1 commit intoapache:masterfrom
Conversation
…oop3 revert to using -Dhadoop.profile
|
(!) A patch to the testing environment has been detected. |
2 similar comments
|
(!) A patch to the testing environment has been detected. |
|
(!) A patch to the testing environment has been detected. |
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
joshelser
left a comment
There was a problem hiding this comment.
Looks good to me. I'd have to go digging into why activating via system property and not profile is important in Maven (I remember there being a reason).
I want to wait for Duo to come back though, since this is essentially undo'ing a change of his from 2 weeks ago.
|
Fixed by HBASE-24215 ? |
|
HBASE-24215 may or may not fix the test error (I did not check), See the JIRA for details on how it doesn't work. |
|
@stoty ok. Thanks. Maybe issue needs renaming then? Good work. |
saintstack
left a comment
There was a problem hiding this comment.
Activation is basic:
<profile> <id>hadoop-2.0</id> <activation> <property> <!--Below formatting for dev-support/generate-hadoopX-poms.sh--> <!--h2--><name>!hadoop.profile</name> </property> </activation>
Wasn't there a reason for using -P rather than this -Dhadoop.profile in the issue that made the change?
|
From what I gather, The problem was that in 3.0, only Hadoop 3 is supported, and it was part of the solution to make hadoop3 the default. However, in a later patch it was solved by setting property to 3.0 by default, which is compatible with the branch-2 profile activation scheme. |
|
So, this patch is not fit given hbase-personality is used on all branches as Nick points out up on on the issue (master doesn't have the hadoop.version property). Looking at master, it is trying to do profile AND property -- -P and -D -- but I'm not sure that activation stuff works for profiles. ... Thinking on what this issue has turned up, let me go back to HBASE-24215 . I'm now of the opinion that the (painful) 'fix' there actually would not be needed if we didn't have both hadoop2 and hadoop3 profiles activated as you found here (no wonder I was having trouble repro'ing what was happening up on jenkins). Let me put this comment up in JIRA. Better suited there. |
|
Closing because the JIRA is resolved. Good stuff in here toward figuring out what root issue was around this test failing. Thanks @stoty |
…oop3
revert to using -Dhadoop.profile