Hi Haonan, > From the Apache IoTDB side, we are mainly interested in the following two gRPC-related improvements:
Would it work if we roll the next release from the current master? It also contains some important bug fixes such as RATIS-2499 (see this comment [2]). > Would it be possible to publish a SNAPSHOT version containing these changes first? ... Sure, just have deployed a 3.3.0-b60fcf6-SNAPSHOT [1]. Please try. It is over the current master commit b60fcf6 (RATIS-2552). Deploying snapshots is very easy. Please feel free to let us know. Tsz-Wo [1] https://repository.apache.org/content/repositories/snapshots/org/apache/ratis/ratis-bom/3.3.0-b60fcf6-SNAPSHOT/ [2] https://github.com/apache/ratis/pull/1425#pullrequestreview-4070436127 On Thu, Jun 4, 2026 at 12:35 AM Haonan Hou <[email protected]> wrote: > Hi Xinyu and Tsz-Wo, > > Thanks for the discussion and for driving the next release forward. > > From the Apache IoTDB side, we are mainly interested in the following two > gRPC-related > improvements: > > * RATIS-2529: Bound gRPC worker EventLoopGroup thread count > * RATIS-2537: Support configurable gRPC TLS provider and cipher suites > > Both are important for us in production deployments. RATIS-2529 helps > avoid unexpected long- > lived gRPC worker thread inflation after follower restart/catch-up, and > RATIS-2537 allows > downstream projects to use specific TLS/JSSE providers, protocols, and > cipher suites when > required by deployment or compliance environments. > > Since these two issues were fixed and are important for our downstream > integration, we would > like to verify them on the IoTDB side. > > Would it be possible to publish a SNAPSHOT version containing these > changes first? With a > SNAPSHOT build available, we can upgrade the Ratis dependency in IoTDB and > perform > integration testing before the official release. > > Best, > Haonan > > On 2026/06/04 00:35:09 Tsz-Wo Nicholas Sze wrote: > > Hi Haonan, > > > > > We are currently tracking some recent changes in Ratis ... > > > > Could you share the changes? > > > > Sorry that Ratis releases do not have a concrete schedule -- We usually > > release on demand, and if there is no demand, we release around twice a > > year. If there is a need, we could roll a release right away. Please > feel > > free to let us know. > > > > Tsz-Wo > > > > > > > > > > On Wed, Jun 3, 2026 at 4:05 AM Xinyu Tan <[email protected]> wrote: > > > > > Hi Haonan, > > > > > > Thanks for reaching out. > > > > > > The latest Ratis release, 3.2.2, was published on April 3, 2026. It has > > > been about two months since then. Looking at the current diff from > > > release-3.2.2 to master, the accumulated changes do not look very > large at > > > this point, so we do not have a fixed timeline for the next release > yet. > > > > > > That said, we can certainly evaluate the timing based on downstream > > > community needs. If there are specific fixes or changes that your > > > downstream project is waiting for, please let us know which ones are > > > important for your upgrade plan. That would help us decide whether it > makes > > > sense to start preparing the next release sooner. > > > > > > Help with testing and verification would also be very welcome once we > > > identify the target changes for the next release. > > > > > > Best regards, > > > Xinyu Tan > > > > > > On 2026/06/01 06:36:04 Haonan Hou wrote: > > > > Hi Ratis community, > > > > > > > > I would like to ask whether there is any plan or estimated timeline > for > > > the next Apache Ratis > > > > release. > > > > > > > > We are currently tracking some recent changes in Ratis and would > like to > > > understand when they > > > > might become available in an official release, so that we can better > > > plan our downstream > > > > dependency upgrade. > > > > > > > > Please let us know if there is already a planned release schedule, > or if > > > any help is needed with > > > > testing or verification for the upcoming release. > > > > > > > > Best regards, > > > > Haonan Hou > > > > > > > > > >
