Re: 2.1 Release TODO

2022-04-04 Thread Mike Miller
I think I can finish the FATE refactor PR [1] for 2.1. I had been keeping it up to date with the latest in main but stopped because it was too much work. I was waiting until the ZK property changes are completed before resolving the latest conflicts. I don't think it is much of a risk. It is mostly

Re: Scan Server discussion [WAS: Re: 2.1 Release TODO]

2022-04-04 Thread Christopher
On Mon, Apr 4, 2022 at 1:11 PM Dave Marion wrote: > > I understand the desire to see less coupling for the optional features, but > getting to that point for ScanServers (and less so for ExternalCompactions) > would be a ton of work I think. The likelihood of it being a lot of work doesn't mean i

Re: Scan Server discussion [WAS: Re: 2.1 Release TODO]

2022-04-04 Thread Dave Marion
I understand the desire to see less coupling for the optional features, but getting to that point for ScanServers (and less so for ExternalCompactions) would be a ton of work I think. The concern that I brought up in the "2.1 Release TODOs" thread regarding planning has not been addressed. If there

Scan Server discussion [WAS: Re: 2.1 Release TODO]

2022-04-04 Thread Christopher
On Mon, Apr 4, 2022 at 11:50 AM Keith Turner wrote: > > On Mon, Apr 4, 2022 at 11:17 AM Christopher wrote: > > > > However, I'm reluctant to include #2422, because I don't think it's near > > ready enough, and by the time it is, it will be very last minute, and I > > don't want to delay 2.1 furth

Re: 2.1 Release TODO

2022-04-04 Thread Keith Turner
On Mon, Apr 4, 2022 at 11:17 AM Christopher wrote: > > I haven't seen the metrics test fail very often lately. If it's stable, I > don't mind removing the blocker on that issue, but I'd be reluctant to > close it entirely just yet, until we can verify it doesn't happen anymore. > > As for the orig

Re: 2.1 Release TODO

2022-04-04 Thread Christopher
I haven't seen the metrics test fail very often lately. If it's stable, I don't mind removing the blocker on that issue, but I'd be reluctant to close it entirely just yet, until we can verify it doesn't happen anymore. As for the original list of potential issues to include, I'm in favor of tryin

Re: 2.1 Release TODO

2022-04-04 Thread Dave Marion
I think [3] is OBE and can be closed. On Mon, Apr 4, 2022 at 9:11 AM Mike Miller wrote: > Yes I agree, that was the goal of this email thread. I found a few more > tickets that should be addressed for the next release. > > Ivan - There was some work done on this PR but it has been some time. Do

Re: 2.1 Release TODO

2022-04-04 Thread Mike Miller
Yes I agree, that was the goal of this email thread. I found a few more tickets that should be addressed for the next release. Ivan - There was some work done on this PR but it has been some time. Do you want to take a look at it? Implement a Thread limit. [1] Keith T - I think we should get this