[jira] [Commented] (ZOOKEEPER-3667) set jute.maxbuffer hexadecimal number throw parseInt error
[ https://issues.apache.org/jira/browse/ZOOKEEPER-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17016785#comment-17016785 ] Sujith Simon commented on ZOOKEEPER-3667: - I can take this issue up :) > set jute.maxbuffer hexadecimal number throw parseInt error > -- > > Key: ZOOKEEPER-3667 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3667 > Project: ZooKeeper > Issue Type: Bug > Components: java client >Affects Versions: 3.5.6 >Reporter: bright.zhou >Assignee: Sujith Simon >Priority: Major > Labels: pull-request-available > Attachments: 20191227-204631(eSpace).png > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ZOOKEEPER-3667) set jute.maxbuffer hexadecimal number throw parseInt error
[ https://issues.apache.org/jira/browse/ZOOKEEPER-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sujith Simon reassigned ZOOKEEPER-3667: --- Assignee: Sujith Simon > set jute.maxbuffer hexadecimal number throw parseInt error > -- > > Key: ZOOKEEPER-3667 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3667 > Project: ZooKeeper > Issue Type: Bug > Components: java client >Affects Versions: 3.5.6 >Reporter: bright.zhou >Assignee: Sujith Simon >Priority: Major > Attachments: 20191227-204631(eSpace).png > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ZOOKEEPER-3613) ZKConfig fails to return proper value on getBoolean() when user accidentally includes spaces at the end of the value
[
https://issues.apache.org/jira/browse/ZOOKEEPER-3613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sujith Simon reassigned ZOOKEEPER-3613:
---
Assignee: Sujith Simon
> ZKConfig fails to return proper value on getBoolean() when user accidentally
> includes spaces at the end of the value
>
>
> Key: ZOOKEEPER-3613
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3613
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
>Affects Versions: 3.5.5
>Reporter: Scott Guminy
>Assignee: Sujith Simon
>Priority: Minor
>
> I was using ZooKeeper client in WebSphere Liberty and attempting to configure
> SSL/TLS for client connections.
> To do so, I must add the system property {{zookeeper.client.secure=true}}.
> In WebSphere Liberty, java system properties are placed in a file called
> bootstrap.properties - each property on a separate line. I accidentally
> added a space at the end of the line. When {{ZKConfig.getBoolean()}}
> attempted to convert this string to a {{boolean}}, it returned {{false}} due
> to the space at the end.
> {{ZKConfig.getBoolean()}} should trim the string before attempting to convert
> to a boolean.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ZOOKEEPER-3613) ZKConfig fails to return proper value on getBoolean() when user accidentally includes spaces at the end of the value
[
https://issues.apache.org/jira/browse/ZOOKEEPER-3613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16999764#comment-16999764
]
Sujith Simon commented on ZOOKEEPER-3613:
-
I can take up this issue
> ZKConfig fails to return proper value on getBoolean() when user accidentally
> includes spaces at the end of the value
>
>
> Key: ZOOKEEPER-3613
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3613
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
>Affects Versions: 3.5.5
>Reporter: Scott Guminy
>Assignee: Sujith Simon
>Priority: Minor
>
> I was using ZooKeeper client in WebSphere Liberty and attempting to configure
> SSL/TLS for client connections.
> To do so, I must add the system property {{zookeeper.client.secure=true}}.
> In WebSphere Liberty, java system properties are placed in a file called
> bootstrap.properties - each property on a separate line. I accidentally
> added a space at the end of the line. When {{ZKConfig.getBoolean()}}
> attempted to convert this string to a {{boolean}}, it returned {{false}} due
> to the space at the end.
> {{ZKConfig.getBoolean()}} should trim the string before attempting to convert
> to a boolean.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ZOOKEEPER-3653) Audit Log feature fails in a stand alone zookeeper setup
[ https://issues.apache.org/jira/browse/ZOOKEEPER-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sujith Simon updated ZOOKEEPER-3653: Summary: Audit Log feature fails in a stand alone zookeeper setup (was: Audit Log feature throws EndofFile exception in stand alone zookeeper setup) > Audit Log feature fails in a stand alone zookeeper setup > > > Key: ZOOKEEPER-3653 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3653 > Project: ZooKeeper > Issue Type: Bug > Components: audit >Reporter: Sujith Simon >Assignee: Sujith Simon >Priority: Major > > When the Audit Log feature is enabled in a standalone zookeeper setup, an > error pops up which states "Failed to audit log request" with an EndOfFile > exception due to an issue with the deserialization in the AuditHelper.java > when the request.request.slice() returns an empty pointer. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ZOOKEEPER-3653) Audit Log feature throws EndofFile exception in stand alone zookeeper setup
Sujith Simon created ZOOKEEPER-3653: --- Summary: Audit Log feature throws EndofFile exception in stand alone zookeeper setup Key: ZOOKEEPER-3653 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3653 Project: ZooKeeper Issue Type: Bug Components: audit Reporter: Sujith Simon Assignee: Sujith Simon When the Audit Log feature is enabled in a standalone zookeeper setup, an error pops up which states "Failed to audit log request" with an EndOfFile exception due to an issue with the deserialization in the AuditHelper.java when the request.request.slice() returns an empty pointer. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ZOOKEEPER-2354) ZOOKEEPER-1653 not merged in master and 3.5 branch
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sujith Simon reassigned ZOOKEEPER-2354: --- Assignee: Sujith Simon (was: Mohammad Arshad) > ZOOKEEPER-1653 not merged in master and 3.5 branch > -- > > Key: ZOOKEEPER-2354 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2354 > Project: ZooKeeper > Issue Type: Bug >Reporter: Mohammad Arshad >Assignee: Sujith Simon >Priority: Major > Labels: pull-request-available > Fix For: 3.6.0, 3.5.7 > > Attachments: ZOOKEEPER-2354-01.patch > > Time Spent: 1h > Remaining Estimate: 0h > > ZOOKEEPER-1653 is merged only to 3.4 branch. > It should be merged to 3.5 and master branch as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ZOOKEEPER-2238) Support limiting the maximum number of connections/clients to a zookeeper server.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sujith Simon reassigned ZOOKEEPER-2238: --- Assignee: Sujith Simon > Support limiting the maximum number of connections/clients to a zookeeper > server. > - > > Key: ZOOKEEPER-2238 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2238 > Project: ZooKeeper > Issue Type: Improvement >Reporter: nijel >Assignee: Sujith Simon >Priority: Major > Labels: pull-request-available > Attachments: ZOOKEEPER-2238-05.patch, ZOOKEEPER-2238-06.patch, > ZOOKEEPER-2238-07.patch, ZOOKEEPER-2238.2.patch, ZOOKEEPER-2238.3.patch, > ZOOKEEPER-2238.4.patch, ZOOKEEPER-2238.diff > > Time Spent: 1.5h > Remaining Estimate: 0h > > Currently zookeeper have the feature of limiting the maximum number of > connection/client per IP or Host (maxClientCnxns). > But to safe guard zookeeper server from DoS attack due to many clients from > different IPs, it is better to have a limit of total number of > connections/clients to a a single member of the ZooKeeper ensemble as well. > So the idea is to introduce a new configuration to limit the maximum number > of total connections/clients. > Please share your thoughts. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ZOOKEEPER-1467) Make server principal configurable at client side.
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16950876#comment-16950876
]
Sujith Simon commented on ZOOKEEPER-1467:
-
Thanks [~arshad.mohammad] :)
> Make server principal configurable at client side.
> --
>
> Key: ZOOKEEPER-1467
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1467
> Project: ZooKeeper
> Issue Type: Improvement
> Components: java client
>Affects Versions: 3.4.3, 3.4.4, 3.5.0
>Reporter: Laxman
>Assignee: Sujith Simon
>Priority: Major
> Labels: Security, client, kerberos, pull-request-available, sasl
> Fix For: 3.6.0, 3.5.7
>
> Attachments: ZOOKEEPER-1467.patch, ZOOKEEPER-1467.patch
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> Server principal on client side is derived using hostname.
> org.apache.zookeeper.ClientCnxn.SendThread.startConnect()
> {code}
>try {
> zooKeeperSaslClient = new
> ZooKeeperSaslClient("zookeeper/"+addr.getHostName());
> }
> {code}
> This may have problems when admin wanted some customized principals like
> zookeeper/cluste...@hadoop.com where clusterid is the cluster identifier but
> not the host name.
> IMO, server principal also should be configurable as hadoop is doing.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ZOOKEEPER-1467) Make server principal configurable at client side.
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sujith Simon reassigned ZOOKEEPER-1467:
---
Assignee: Sujith Simon (was: Eugene Joseph Koontz)
> Make server principal configurable at client side.
> --
>
> Key: ZOOKEEPER-1467
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1467
> Project: ZooKeeper
> Issue Type: Improvement
> Components: java client
>Affects Versions: 3.4.3, 3.4.4, 3.5.0
>Reporter: Laxman
>Assignee: Sujith Simon
>Priority: Major
> Labels: Security, client, kerberos, pull-request-available, sasl
> Fix For: 3.6.0, 3.5.7
>
> Attachments: ZOOKEEPER-1467.patch, ZOOKEEPER-1467.patch
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> Server principal on client side is derived using hostname.
> org.apache.zookeeper.ClientCnxn.SendThread.startConnect()
> {code}
>try {
> zooKeeperSaslClient = new
> ZooKeeperSaslClient("zookeeper/"+addr.getHostName());
> }
> {code}
> This may have problems when admin wanted some customized principals like
> zookeeper/cluste...@hadoop.com where clusterid is the cluster identifier but
> not the host name.
> IMO, server principal also should be configurable as hadoop is doing.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ZOOKEEPER-2354) ZOOKEEPER-1653 not merged in master and 3.5 branch
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16941703#comment-16941703 ] Sujith Simon commented on ZOOKEEPER-2354: - I'll raise PR for this issue > ZOOKEEPER-1653 not merged in master and 3.5 branch > -- > > Key: ZOOKEEPER-2354 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2354 > Project: ZooKeeper > Issue Type: Bug >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Fix For: 3.6.0, 3.5.7 > > Attachments: ZOOKEEPER-2354-01.patch > > > ZOOKEEPER-1653 is merged only to 3.4 branch. > It should be merged to 3.5 and master branch as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ZOOKEEPER-1467) Make server principal configurable at client side.
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16941699#comment-16941699
]
Sujith Simon commented on ZOOKEEPER-1467:
-
Can someone pls add me into the contributor list ? Thanks
> Make server principal configurable at client side.
> --
>
> Key: ZOOKEEPER-1467
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1467
> Project: ZooKeeper
> Issue Type: Improvement
> Components: java client
>Affects Versions: 3.4.3, 3.4.4, 3.5.0
>Reporter: Laxman
>Assignee: Eugene Joseph Koontz
>Priority: Major
> Labels: Security, client, kerberos, pull-request-available, sasl
> Fix For: 3.6.0, 3.5.7
>
> Attachments: ZOOKEEPER-1467.patch, ZOOKEEPER-1467.patch
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> Server principal on client side is derived using hostname.
> org.apache.zookeeper.ClientCnxn.SendThread.startConnect()
> {code}
>try {
> zooKeeperSaslClient = new
> ZooKeeperSaslClient("zookeeper/"+addr.getHostName());
> }
> {code}
> This may have problems when admin wanted some customized principals like
> zookeeper/cluste...@hadoop.com where clusterid is the cluster identifier but
> not the host name.
> IMO, server principal also should be configurable as hadoop is doing.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (ZOOKEEPER-1467) Server principal on client side is derived using hostname.
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16940654#comment-16940654
]
Sujith Simon edited comment on ZOOKEEPER-1467 at 9/30/19 5:02 AM:
--
[~beeflyme] 4 letter commands discouraged and by default all of them other than
srvr command are disabled.
Also users need to configure server principal to fallback on incase it fails
to get the principal from server, in such a case is not better idea to use the
configured principal itself ?
was (Author: sujithsimon22):
[~beeflyme] 4 letter commands discouraged and by default all of them other srvr
command are disabled.
Also users need to configure server principal to fallback on incase it fails to
get the principal from server, in such a case is not better idea to use the
configured principal itself ?
> Server principal on client side is derived using hostname.
> --
>
> Key: ZOOKEEPER-1467
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1467
> Project: ZooKeeper
> Issue Type: Improvement
> Components: java client
>Affects Versions: 3.4.3, 3.4.4, 3.5.0
>Reporter: Laxman
>Assignee: Eugene Joseph Koontz
>Priority: Major
> Labels: Security, client, kerberos, pull-request-available, sasl
> Fix For: 3.6.0
>
> Attachments: ZOOKEEPER-1467.patch, ZOOKEEPER-1467.patch
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Server principal on client side is derived using hostname.
> org.apache.zookeeper.ClientCnxn.SendThread.startConnect()
> {code}
>try {
> zooKeeperSaslClient = new
> ZooKeeperSaslClient("zookeeper/"+addr.getHostName());
> }
> {code}
> This may have problems when admin wanted some customized principals like
> zookeeper/cluste...@hadoop.com where clusterid is the cluster identifier but
> not the host name.
> IMO, server principal also should be configurable as hadoop is doing.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ZOOKEEPER-1467) Server principal on client side is derived using hostname.
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16940654#comment-16940654
]
Sujith Simon commented on ZOOKEEPER-1467:
-
[~beeflyme] 4 letter commands discouraged and by default all of them other srvr
command are disabled.
Also users need to configure server principal to fallback on incase it fails to
get the principal from server, in such a case is not better idea to use the
configured principal itself ?
> Server principal on client side is derived using hostname.
> --
>
> Key: ZOOKEEPER-1467
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1467
> Project: ZooKeeper
> Issue Type: Improvement
> Components: java client
>Affects Versions: 3.4.3, 3.4.4, 3.5.0
>Reporter: Laxman
>Assignee: Eugene Joseph Koontz
>Priority: Major
> Labels: Security, client, kerberos, pull-request-available, sasl
> Fix For: 3.6.0
>
> Attachments: ZOOKEEPER-1467.patch, ZOOKEEPER-1467.patch
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Server principal on client side is derived using hostname.
> org.apache.zookeeper.ClientCnxn.SendThread.startConnect()
> {code}
>try {
> zooKeeperSaslClient = new
> ZooKeeperSaslClient("zookeeper/"+addr.getHostName());
> }
> {code}
> This may have problems when admin wanted some customized principals like
> zookeeper/cluste...@hadoop.com where clusterid is the cluster identifier but
> not the host name.
> IMO, server principal also should be configurable as hadoop is doing.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ZOOKEEPER-1467) Server principal on client side is derived using hostname.
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16939312#comment-16939312
]
Sujith Simon commented on ZOOKEEPER-1467:
-
[~arshad.mohammad] I would like to raise a PR for this. Will raise the PR
soon :)
> Server principal on client side is derived using hostname.
> --
>
> Key: ZOOKEEPER-1467
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1467
> Project: ZooKeeper
> Issue Type: Improvement
> Components: java client
>Affects Versions: 3.4.3, 3.4.4, 3.5.0
>Reporter: Laxman
>Assignee: Eugene Joseph Koontz
>Priority: Major
> Labels: Security, client, kerberos, sasl
> Fix For: 3.6.0
>
> Attachments: ZOOKEEPER-1467.patch, ZOOKEEPER-1467.patch
>
>
> Server principal on client side is derived using hostname.
> org.apache.zookeeper.ClientCnxn.SendThread.startConnect()
> {code}
>try {
> zooKeeperSaslClient = new
> ZooKeeperSaslClient("zookeeper/"+addr.getHostName());
> }
> {code}
> This may have problems when admin wanted some customized principals like
> zookeeper/cluste...@hadoop.com where clusterid is the cluster identifier but
> not the host name.
> IMO, server principal also should be configurable as hadoop is doing.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
