[jira] [Created] (ZOOKEEPER-4798) Secure prometheus support
Purshotam Shah created ZOOKEEPER-4798: - Summary: Secure prometheus support Key: ZOOKEEPER-4798 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4798 Project: ZooKeeper Issue Type: Improvement Reporter: Purshotam Shah -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ZOOKEEPER-4797) Allow for -XX:MaxRamPercentage JVM setting
Frederiko Costa created ZOOKEEPER-4797: -- Summary: Allow for -XX:MaxRamPercentage JVM setting Key: ZOOKEEPER-4797 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4797 Project: ZooKeeper Issue Type: Improvement Components: scripts Reporter: Frederiko Costa When running Zk in a containerized environment, it's sometimes desirable to express your heap size in terms of percentage of available memory allocated to a container. As it stands, zkEnv.sh forces your to have -Xmx, which defaults to 1GB. Some environments wanted to set it to more, mostly related to the amount of Ram. This is a request to implement the option of using -XX:MaxRamPercentage option when starting zookeeper. Suggested implementation is to also make a variable ZK_SERVER_MAXRAMPERCENTAGE available to be added to SERVER_JVMFLAGS. If the variable is set, ZK_HEAP_SERVER is ignored, if no ZK_SERVER_MAXRAMPERCENTAGE, ZK_SERVER_HEAP is set as usual. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ZOOKEEPER-4796) Requests submitted first may carry a larger xid resulting in ZRUNTIMEINCONSISTENCY
fanyang created ZOOKEEPER-4796: -- Summary: Requests submitted first may carry a larger xid resulting in ZRUNTIMEINCONSISTENCY Key: ZOOKEEPER-4796 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4796 Project: ZooKeeper Issue Type: Bug Components: c client Reporter: fanyang When multiple threads attempt to submit requests, it's possible for a request from a thread that acquired its xid earlier to be inserted after a request from a thread that acquired its xid later in the submission queue, which causes a ZRUNTIMEINCONSISTENCY error. To fix it, acquires the lock before get_xid() and releases it after request submission. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: Moving 3.7 to End-of-Life
Thanks guys. Sounds like we have 3 binding +1 votes. Andor On Sat, 2024-01-27 at 09:29 +0100, Enrico Olivelli wrote: > Il Sab 27 Gen 2024, 00:27 Patrick Hunt ha scritto: > > > Markmail search for apache mail archive is gone? and unfortunately > > Apache > > mail archive search seems to be broken (no results coming back...) > > I > > managed to track this ref down > > https://lists.apache.org/thread/b8sm8gxmohs9gl4vrltd2jr4slqvrg9n > > but I distinctly remember seeing something about this, just can't > > find it. > > > > According to this it's already eol: > > https://endoflife.date/zookeeper > > > > Our own release page makes it clear that folks should move given > > stable and > > current have been out for a while. I think we can call it EOL at > > this > > point. > > > > > +1 to mark 3.7 release line as EOL > > Enrico > > > > > Regards, > > > > Patrick > > > > On Fri, Jan 26, 2024 at 7:33 AM Andor Molnar > > wrote: > > > > > Hi zk community, > > > > > > According to our Releases [1] page ZooKeeper 3.8.2 became the > > > first > > > stable version of 3.8.x line on 3 Aug, 2023 (when 3.9.0 was > > > released). > > > > > > The previous stable version "in approximately half a year will be > > > announced as End-of-Life". 6 months will pass on 3 Feb, 2024, so > > > we > > > should think about announcing EoL soon. > > > > > > What do you think? > > > > > > Regards, > > > Andor > > > > > > > > > [1] https://zookeeper.apache.org/releases.html > > > > > > > > > > > > > >
