[jira] [Created] (HBASE-28341) [JDK17] Fix Failure TestLdapHttpServer
Rajeshbabu Chintaguntla created HBASE-28341:
---
Summary: [JDK17] Fix Failure TestLdapHttpServer
Key: HBASE-28341
URL: https://issues.apache.org/jira/browse/HBASE-28341
Project: HBase
Issue Type: Sub-task
Environment: TestLdapHttpServer is failing with JDK17 because of
internal APIs usage.
{code:java}
[INFO] Running org.apache.hadoop.hbase.http.TestLdapHttpServer
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 7.18 s
<<< FAILURE! - in org.apache.hadoop.hbase.http.TestLdapHttpServer
[ERROR] org.apache.hadoop.hbase.http.TestLdapHttpServer Time elapsed: 7.165 s
<<< ERROR!
java.lang.IllegalAccessError: class
org.apache.directory.server.core.security.CertificateUtil (in unnamed module
@0x25bbf683) cannot access class sun.security.x509.X500Name (in module
java.base) because module java.base does not export sun.security.x509 to
unnamed module @0x25bbf683
at
org.apache.directory.server.core.security.CertificateUtil.createTempKeyStore(CertificateUtil.java:334)
at
org.apache.directory.server.factory.ServerAnnotationProcessor.instantiateLdapServer(ServerAnnotationProcessor.java:158)
at
org.apache.directory.server.factory.ServerAnnotationProcessor.createLdapServer(ServerAnnotationProcessor.java:318)
at
org.apache.directory.server.factory.ServerAnnotationProcessor.createLdapServer(ServerAnnotationProcessor.java:351)
at
org.apache.directory.server.core.integ.CreateLdapServerRule$2.evaluate(CreateLdapServerRule.java:112)
at
org.apache.directory.server.core.integ.CreateDsRule$2.evaluate(CreateDsRule.java:124)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:316)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:240)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:214)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:155)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:385)
at
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
at
org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:507)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:495)
[INFO]
[INFO] Results:
[INFO]
[ERROR] Errors:
[ERROR] TestLdapHttpServer » IllegalAccess class
org.apache.directory.server.core.security.CertificateUtil (in unnamed module
@0x25bbf683) cannot access class sun.security.x509.X500Name (in module
java.base) because module java.base does not export sun.security.x509 to
unnamed module @0x25bbf683
[INFO]
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
{code}
Reporter: Rajeshbabu Chintaguntla
Assignee: Rajeshbabu Chintaguntla
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (HBASE-28340) Add trust/key store type settings to ZK TLS settings handled by HBase
Andor Molnar created HBASE-28340:
Summary: Add trust/key store type settings to ZK TLS settings
handled by HBase
Key: HBASE-28340
URL: https://issues.apache.org/jira/browse/HBASE-28340
Project: HBase
Issue Type: Sub-task
Components: Zookeeper
Affects Versions: 2.5.7, 3.0.0-beta-1, 2.4.17
Reporter: Andor Molnar
Assignee: Andor Molnar
Let's add the following settings as well. Last time we missed it.
{noformat}
zookeeper.ssl.keyStore.type
zookeeper.ssl.trustStore.type{noformat}
Handle them in hbase-site.xml as:
{noformat}
hbase.zookeeper.property.ssl.keyStore.type
hbase.zookeeper.property.ssl.trustStore.type{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (HBASE-28339) HBaseReplicationEndpoint creates new ZooKeeper client every time it tries to reconnect
Andor Molnar created HBASE-28339:
Summary: HBaseReplicationEndpoint creates new ZooKeeper client
every time it tries to reconnect
Key: HBASE-28339
URL: https://issues.apache.org/jira/browse/HBASE-28339
Project: HBase
Issue Type: Bug
Components: Replication
Affects Versions: 2.5.7, 3.0.0-beta-1, 2.4.17, 2.6.0, 2.7.0
Reporter: Andor Molnar
Assignee: Andor Molnar
Asbtract base class {{HBaseReplicationEndpoint}} and therefore
{{HBaseInterClusterReplicationEndpoint}} creates new ZooKeeper client instance
every time there's an error occurs in communication and it tries to reconnect.
This was not a problem with ZooKeeper 3.4.x versions, because the TGT Login
thread was a static reference and only created once for all clients in the same
JVM. With the upgrade to ZooKeeper 3.5.x the login thread is dedicated to the
client instance, hence we have a new login thread every time the replication
endpoint reconnects.
{code:java}
/**
* A private method used to re-establish a zookeeper session with a peer
cluster.
*/
protected void reconnect(KeeperException ke) {
if (
ke instanceof ConnectionLossException || ke instanceof
SessionExpiredException
|| ke instanceof AuthFailedException
) {
String clusterKey = ctx.getPeerConfig().getClusterKey();
LOG.warn("Lost the ZooKeeper connection for peer " + clusterKey, ke);
try {
reloadZkWatcher();
} catch (IOException io) {
LOG.warn("Creation of ZookeeperWatcher failed for peer " + clusterKey,
io);
}
}
}{code}
{code:java}
/**
* Closes the current ZKW (if not null) and creates a new one
* @throws IOException If anything goes wrong connecting
*/
synchronized void reloadZkWatcher() throws IOException {
if (zkw != null) zkw.close();
zkw = new ZKWatcher(ctx.getConfiguration(), "connection to cluster: " +
ctx.getPeerId(), this);
getZkw().registerListener(new PeerRegionServerListener(this));
} {code}
If the target cluster of replication is unavailable for some reason, the
replication endpoint keeps trying to reconnect to ZooKeeper destroying and
creating new Login threads constantly which will carpet bomb the KDC host with
login requests.
I'm not sure how to fix this yet, trying to create a unit test first.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (HBASE-28325) Enable infra automation to add label on a Jira when a new PR is posted
[ https://issues.apache.org/jira/browse/HBASE-28325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28325. --- Fix Version/s: 4.0.0-alpha-1 Resolution: Fixed Should be OK now. > Enable infra automation to add label on a Jira when a new PR is posted > -- > > Key: HBASE-28325 > URL: https://issues.apache.org/jira/browse/HBASE-28325 > Project: HBase > Issue Type: Task > Components: community >Reporter: Nick Dimiduk >Assignee: Nick Dimiduk >Priority: Minor > Fix For: 4.0.0-alpha-1 > > > https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Jiranotificationoptions > Currently we make use of the "link" feature. This does not send a > notification to watchers, so I propose that we add the "comment" feature, so > that a comment will also be sent, and watchers can find out about the > availability of the PR. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: Contribution request
This is all set On Thu, Feb 1, 2024 at 7:13 AM Ahmad Alhour wrote: > Hello HBase, > > I am Ahmad Alhour and I work at HubSpot, my HBase team is thinking of > proposing a contribution to the HBase repo and I'd like to be added as a > contributor in order to create, and get assigned to, JIRA tickets. > > Regards, > Ahmad >
Contribution request
Hello HBase, I am Ahmad Alhour and I work at HubSpot, my HBase team is thinking of proposing a contribution to the HBase repo and I'd like to be added as a contributor in order to create, and get assigned to, JIRA tickets. Regards, Ahmad
