geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dan Smith <dsm...@pivotal.io>
Subject Re: Propose GEODE-6544 fix for release 1.9.0
Date Mon, 22 Apr 2019 18:06:01 GMT
Owen and I talked to Kirk and Aaron. It sounds like this issue does not
need to hold up release 1.9.0 because it's been in all previous versions.
If we need to create another RC we will get this fix in there.

-Dan

On Fri, Apr 19, 2019 at 1:50 PM Owen Nichols <onichols@pivotal.io> wrote:

> Hi Aaron, Kirk and Geode community,
>
> FYI, 1.9.0.RC4 has already been tagged and is being prepared for a VOTE
> email to go out later today.
>
> [As usual] if you or anyone else feels that 1.9.0 should not ship without
> this or other changes, you may cast a “-1” vote once you receive the
> 1.9.0.RC4 VOTE email later today.
>
> -Owen
>
> > On Apr 19, 2019, at 12:35 PM, Aaron Lindsey <alindsey@pivotal.io> wrote:
> >
> > We'd like to propose including this fix into 1.9.0 as well:
> > https://github.com/apache/geode/pull/3362
> > https://jira.apache.org/jira/browse/GEODE-6544
> >
> > This fixes a memory leak caused by a thread leak in Pulse. Every time a
> > user signs out, a thread is left running. The fix for GEODE-6544 stops
> that
> > thread when the user signs out.
> >
> > - Aaron and Kirk
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message