Rescale structure? That seems to
> be
> > a transient field that should be derived via the AdaptiveScheduler's
> state.
>
> Thank you very much for the reminder.
> This is exactly the point I have been reconsidering.
> After introducing TerminalState and TerminatedRea
f this current rescale
> process terminates, an immutable rescale snapshot of this event is created
> that is saved in the rescale history.
>
> Sorry for my previous wording was ambiguous and inconsistent with the
> documentation. Thanks a lot for pointing it out. This is actually
5#FLIP495:SupportAdaptiveSchedulerrecordandquerytherescalehistory-Aboutrescaleeventsstorage.1
> [2]https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=334760525#FLIP495:SupportAdaptiveSchedulerrecordandquerytherescalehistory-ThemainscenarioswhereRescalestatusswitchestoterminated
Hi Yuepeng,
thanks for reminding me of this FLIP. I went over it and have a few items
which we might need to address before we can actually finalize the vote:
1. You mention a few options for when it comes to storing the data which is
good. The FLIP doesn't point out, though, what option you're go
Matthias Pohl created FLINK-37412:
-
Summary: Add slot allocation strategy to for selecting TMs first
that have already slots assigned
Key: FLINK-37412
URL: https://issues.apache.org/jira/browse/FLINK-37412
e/FLINK-34331
On Thu, Feb 13, 2025 at 2:21 PM Tom Cooper wrote:
> Hi all,
>
> I was hoping to sync up on the progress on moving from Azure CI to GitHub
> Actions for the main Flink repository. There was FLIP-396 [1] by Matthias
> Pohl detailing the plan to trial GitHub Actions and
Matthias Pohl created FLINK-37259:
-
Summary: StreamCheckpointingITCase times out
Key: FLINK-37259
URL: https://issues.apache.org/jira/browse/FLINK-37259
Project: Flink
Issue Type: Bug
Matthias Pohl created FLINK-37232:
-
Summary: FLIP-272 breaks some synchronization assumption on the
AdaptiveScheduler's side
Key: FLINK-37232
URL: https://issues.apache.org/jira/browse/FLINK-
FYI: The nightly runs for 1.18 are deactivated in Azure and GHA
On Mon, Jan 6, 2025 at 1:02 PM Matthias Pohl wrote:
> Ok, thanks for your feedback. I will go ahead with disabling CI for 1.18
> next week if no other objections are shared.
>
> On Fri, Jan 3, 2025 at 5:21 PM Rui
Matthias Pohl created FLINK-37220:
-
Summary: GuavaRateLimiter creates an ExecutorService without
shutting it down properly leaking threads
Key: FLINK-37220
URL: https://issues.apache.org/jira/browse/FLINK-37220
Matthias Pohl created FLINK-37215:
-
Summary: SlotAllocationException throwing can be moved from
TaskExecutor#allocateSlot to TaskSlotTableImpl#allocateSlot
Key: FLINK-37215
URL: https://issues.apache.org/jira
Matthias Pohl created FLINK-37214:
-
Summary: Migrate TaskSlotTableImplTest from using the test thread
as the main thread
Key: FLINK-37214
URL: https://issues.apache.org/jira/browse/FLINK-37214
Matthias Pohl created FLINK-37170:
-
Summary: Disable 1.18 CI
Key: FLINK-37170
URL: https://issues.apache.org/jira/browse/FLINK-37170
Project: Flink
Issue Type: Technical Debt
Hi Yupeng,
I managed to find some time to respond. See my answers inlined below.
Matthias
On Fri, Jan 3, 2025 at 11:48 AM Yuepeng Pan wrote:
> [...]
> Sorry for not expressing this part clearly earlier.
> IIUC, based on the Adaptive Scheduler state diagram [1],
> when a stop-with-savepoint oper
est,
> Rui
>
> On Fri, Jan 3, 2025 at 11:45 PM Robert Metzger
> wrote:
>
> > Hey Matthias,
> >
> > it seems that there is no traction for creating another 1.18.x bugfix
> > release, so *I'm +1 for disabling CI for 1.18.*
> >
> > On Wed, Dec 1
Hi everyone and sorry for the late reply. I was mostly off in November and
forgot about that topic in December last year.
Thanks for summarizing and bringing up user feedback. I see the problem and
agree with your view that it's a topic that we might want to address in the
1.x LTS version. I see h
Thanks Yuepeng for your response. I added my comments to the individual
paragraphs below:
> Thank you very much for the reminding The proposal makes sense to me.
> Additionally, I'd like to confirm whether each rescale cycle/event
> requires a status field, such as FAILED, IGNORED, SUCCESS, PENDI
Matthias Pohl created FLINK-36979:
-
Summary: Revert netty bump for 1.20 and 1.19
Key: FLINK-36979
URL: https://issues.apache.org/jira/browse/FLINK-36979
Project: Flink
Issue Type: Bug
fyi: The following Flink Jira issues are related to this comment:
- FLINK-36290 [1] OOM in CI
- FLINK-36510 [2]: netty version bump which was backported to 1.20 and 1.19
[1] https://issues.apache.org/jira/browse/FLINK-36290
[2] https://issues.apache.org/jira/browse/FLINK-36510
On Sat, Dec 28, 202
Hi everyone,
with the release of 1.20.0 [1], 1.18 reached its EOL. The community has
decided to do a final "flush out" release in this case if it's requested
(and, I guess, there is someone volunteering to do this). There was a
question about release 1.18.2 [2] in the past. 1.18.2 contains 76 fixes
+1 for adding the automation considering that other projects are doing this
as well and the high amount of open PRs doesn't help. Thanks for
summarizing the current state in such detail.
X + Y should probably be larger than our usual release cycles. X=6m and
Y=3m might be alright in this regard.
Hi Yuepeng,
Sorry for not finding the time to respond earlier. I went over FLIP-495 [1]
and the previous FLIP-487 discussion [2]. Thanks for putting it all
together in a FLIP. That makes it easier to discuss the next iteration.
Here are a few comments I have:
Rescale ID section
- How is the resour
x
>
>
>
> On Mon, 2 Dec 2024 at 21:12, Sergey Nuyanzin wrote:
>
> > Thanks, Matthias
> >
> > confirm, now there is only one unreleased version for 1.19 and one for
> 1.20
> >
> > On Mon, Dec 2, 2024 at 10:17 AM Matthias Pohl wrote:
> >
> > >
Matthias Pohl created FLINK-36888:
-
Summary: Building flink-shaded-netty-tcnative-static for the
OpenSSL e2e tests timed out
Key: FLINK-36888
URL: https://issues.apache.org/jira/browse/FLINK-36888
Thanks for bringing this up, Sergey. You're right.
I went over the issues that had these versions assigned, assigned them to
the right patch versions and deleted the versions 1.19.3 and 1.20.2 so that
contributors don't accidentally assign new Jira issues to those versions
again.
Best,
Matthias
Hi Yuepeng,
thanks for the proposal. Having a way to see the history of rescales is a
nice feature, I guess. I went over the draft and have a few questions:
Can we reorganize the draft? Right now, we have some (for RescaleEvent,
Required/AcquiredParallelism) schema defined in the "Proposed Changes
+1 (binding)
* Downloaded all artifacts
* Extracted and built sources
* Diff of git tag checkout with downloaded sources
* Verified SHA512 checksums & GPG certification
* Checked that all POMs have the right expected version
* Generated diffs to compare pom file changes with NOTICE files
Thanks A
Matthias Pohl created FLINK-36512:
-
Summary: Make rescale trigger based on failed checkpoints depend
on the cause
Key: FLINK-36512
URL: https://issues.apache.org/jira/browse/FLINK-36512
Project
Matthias Pohl created FLINK-36356:
-
Summary: HadoopRecoverableWriterTest.testRecoverWithState due to
IOException
Key: FLINK-36356
URL: https://issues.apache.org/jira/browse/FLINK-36356
Project: Flink
Matthias Pohl created FLINK-36350:
-
Summary: IllegalAccessError detected in JDK17+ runs
Key: FLINK-36350
URL: https://issues.apache.org/jira/browse/FLINK-36350
Project: Flink
Issue Type: Bug
Matthias Pohl created FLINK-36349:
-
Summary: ClassNotFoundException due to
org.apache.flink.runtime.types.FlinkScalaKryoInstantiator missing
Key: FLINK-36349
URL: https://issues.apache.org/jira/browse/FLINK-36349
Matthias Pohl created FLINK-36324:
-
Summary: MiscAggFunctionITCase expected to raise Throwable
Key: FLINK-36324
URL: https://issues.apache.org/jira/browse/FLINK-36324
Project: Flink
Issue
Matthias Pohl created FLINK-36317:
-
Summary: Populate the ArchivedExecutionGraph with
CheckpointStatsSnapshot data if in WaitingForResources state with a
previousExecutionGraph being set
Key: FLINK-36317
URL
Matthias Pohl created FLINK-36302:
-
Summary: FileSourceTextLinesITCase timed out
Key: FLINK-36302
URL: https://issues.apache.org/jira/browse/FLINK-36302
Project: Flink
Issue Type: Bug
Matthias Pohl created FLINK-36301:
-
Summary: TPC-H end-to-end test fails due to TimeoutException
Key: FLINK-36301
URL: https://issues.apache.org/jira/browse/FLINK-36301
Project: Flink
Issue
Matthias Pohl created FLINK-36300:
-
Summary:
TableEnvHiveConnectorITCase.testDateTimestampPartitionColumns times out
Key: FLINK-36300
URL: https://issues.apache.org/jira/browse/FLINK-36300
Project
Matthias Pohl created FLINK-36299:
-
Summary: AdaptiveSchedulerTest.testStatusMetrics times out
Key: FLINK-36299
URL: https://issues.apache.org/jira/browse/FLINK-36299
Project: Flink
Issue
Matthias Pohl created FLINK-36298:
-
Summary: NullPointerException in Calcite causes a PyFlink test
failure
Key: FLINK-36298
URL: https://issues.apache.org/jira/browse/FLINK-36298
Project: Flink
Matthias Pohl created FLINK-36297:
-
Summary: SIGSEGV caused CI failure
Key: FLINK-36297
URL: https://issues.apache.org/jira/browse/FLINK-36297
Project: Flink
Issue Type: Bug
Matthias Pohl created FLINK-36295:
-
Summary: AdaptiveSchedulerClusterITCase.
testCheckpointStatsPersistedAcrossRescale failed with
Key: FLINK-36295
URL: https://issues.apache.org/jira/browse/FLINK-36295
Matthias Pohl created FLINK-36294:
-
Summary: table stage failed with general junit5 TestEngine failure
Key: FLINK-36294
URL: https://issues.apache.org/jira/browse/FLINK-36294
Project: Flink
Matthias Pohl created FLINK-36293:
-
Summary: RocksDBWriteBatchWrapperTest.testAsyncCancellation
Key: FLINK-36293
URL: https://issues.apache.org/jira/browse/FLINK-36293
Project: Flink
Issue
Matthias Pohl created FLINK-36292:
-
Summary:
SplitFetcherManagerTest.testCloseCleansUpPreviouslyClosedFetcher times out
Key: FLINK-36292
URL: https://issues.apache.org/jira/browse/FLINK-36292
Project
Matthias Pohl created FLINK-36291:
-
Summary: java.lang.IllegalMonitorStateException causing a fatal
error on the TaskManager side
Key: FLINK-36291
URL: https://issues.apache.org/jira/browse/FLINK-36291
Matthias Pohl created FLINK-36290:
-
Summary: OutOfMemoryError in connect test run
Key: FLINK-36290
URL: https://issues.apache.org/jira/browse/FLINK-36290
Project: Flink
Issue Type: Bug
Matthias Pohl created FLINK-36279:
-
Summary: RescaleOnCheckpointITCase.testRescaleOnCheckpoint fails
Key: FLINK-36279
URL: https://issues.apache.org/jira/browse/FLINK-36279
Project: Flink
Matthias Pohl created FLINK-36272:
-
Summary: YarnFileStageTestS3ITCase fails on master
Key: FLINK-36272
URL: https://issues.apache.org/jira/browse/FLINK-36272
Project: Flink
Issue Type: Bug
risk it that we break something which was not
> > intended, but fixing those
> > hopefully small amount of cases is less effort than maintaining an
> endless
> > list.
> >
> > BR,
> > G
> >
> >
> > On Thu, Aug 29, 2024 at 11:40 AM Matthias Pohl
Matthias Pohl created FLINK-36207:
-
Summary: Disabling japicmp plugin for deprecated APIs
Key: FLINK-36207
URL: https://issues.apache.org/jira/browse/FLINK-36207
Project: Flink
Issue Type
Matthias Pohl created FLINK-36194:
-
Summary: Shutdown hook for ExecutionGraphInfo store runs
concurrently to cluster shutdown hook causing race conditions
Key: FLINK-36194
URL: https://issues.apache.org/jira
Hi everyone,
for the 2.0 work, we are expecting to run into public API changes quite a
bit. This would get picked up by the japicmp plugin. The usual way is to
add exclusions to the plugin configuration [1] generating a (presumably
long) list of API changes.
I'm wondering whether we, instead, woul
Matthias Pohl created FLINK-36168:
-
Summary: AdaptiveSchedulerTest doesn't follow the production
lifecycle
Key: FLINK-36168
URL: https://issues.apache.org/jira/browse/FLINK-36168
Project:
Matthias Pohl created FLINK-36147:
-
Summary: Removes deprecated location field
Key: FLINK-36147
URL: https://issues.apache.org/jira/browse/FLINK-36147
Project: Flink
Issue Type: Technical
Matthias Pohl created FLINK-36099:
-
Summary: JobIDLoggingITCase fails due to "Cannot find task to fail
for execution [...]" info log message in TM logs
Key: FLINK-36099
URL: https://issues.apache.org/j
+1 (binding)
On Mon, Aug 5, 2024 at 11:05 AM David Morávek wrote:
> +1 (binding)
>
> Best,
> D.
>
> On Mon, Aug 5, 2024 at 9:24 AM yuanfeng hu wrote:
>
> > +1 (no-binding)
> >
> > Rui Fan <1996fan...@gmail.com> 于2024年8月5日周一 15:18写道：
> >
> > > +1(binding)
> > >
> > > Best,
> > > Rui
> > >
> > >
ectly, and don't need to consider them as
> fallback
> > options, right?
> >
> > - jobmanager.adaptive-scheduler.scale-on-failed-checkpoints-count
> > - jobmanager.adaptive-scheduler.max-delay-for-scale-trigger
> >
> > Best,
> > Rui
> >
> &g
t;
> >>> > Thanks, Mathias, for your opinions.
> >>> >
> >>> > I see two scenarios where different values for starting and rescaling
> >>> would
> >>> > be appropriate:
> >>> >
> >>> > 1) Flink serv
Thanks Zdenek for your proposal on aligning the resource control logic
within the AdaptiveScheduler and cleaning up the rescaling code.
Consolidating the parameters and the code as part of the 2.0 release makes
sense in my opinion: The proposed change adds consistent behavior to the
WaitingForReso
Hi love_h1...@126.com,
Thanks for reaching out to the Flink community. Just a few general remarks:
- Flink's Jira [1] should be used to report potential bugs. The dev mailing
list is used for design and community-related discussions.
- It's also useful to provide not only snippets of the logs but a
FYI: We're doing something similar in the GHA workflow for Apache Flink [1].
[1]
https://github.com/apache/flink/blob/master/.github/actions/job_init/action.yml#L54-L69
On Wed, Jul 10, 2024 at 3:53 PM João Boto wrote:
> I will send this with better format..
> Sorry for that
>
> On 2024/07/10 1
; > > might
> > > > > be a little early to drop support for Java 11. We can discuss this
> > > > > separately.
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Jiangjie (Becket) Qin
> > > > >
> >
Matthias Pohl created FLINK-35748:
-
Summary: DeduplicateITCase.testLastRowWithoutAllChangelogOnRowtime
with MiniBatch mode and RocksDB backend enabled
Key: FLINK-35748
URL: https://issues.apache.org/jira/browse
Matthias Pohl created FLINK-35729:
-
Summary: HiveITCase.testReadWriteHive
Key: FLINK-35729
URL: https://issues.apache.org/jira/browse/FLINK-35729
Project: Flink
Issue Type: Bug
Matthias Pohl created FLINK-35728:
-
Summary: PyFlink end-to-end test because miniconda couldn't be
downloaded
Key: FLINK-35728
URL: https://issues.apache.org/jira/browse/FLINK-35728
Project:
Matthias Pohl created FLINK-35727:
-
Summary: "Run kubernetes pyflink application test" failed due to
access denied issue
Key: FLINK-35727
URL: https://issues.apache.org/jira/browse/F
Matthias Pohl created FLINK-35722:
-
Summary:
CoordinatorEventsToStreamOperatorRecipientExactlyOnceITCase.testCheckpoint
fails because of missed operator event
Key: FLINK-35722
URL: https://issues.apache.org/jira
Hi 2.0 release managers,
With the 1.20 release branch being cut [1], master is now referring to
2.0-SNAPSHOT. I remember that, initially, the community had the idea of
keeping the 2.0 release as small as possible focusing on API changes [2].
What does this mean for new features? I guess blocking t
, 2024 at 11:38 AM Gabor Somogyi
> wrote:
>
> > +1 (binding)
> >
> > G
> >
> >
> > On Mon, Jun 17, 2024 at 10:24 AM Matthias Pohl
> wrote:
> >
> > > Hi everyone,
> > > the discussion in [1] about FLIP-461 [2] is kind of concluded. I
Hi everyone,
the vote [1] for FLIP-461 [2] is over. The number of required binding votes
(3) was reached (total: 10, binding: 7, non-binding: 3). No objections were
raised.
- David Morávek (binding)
- Rui Fan (binding)
- Zakelly Lan (binding)
- Gyula Fóra (binding)
- Weijie Guo (binding)
- Gabor S
Hi everyone,
the discussion in [1] about FLIP-461 [2] is kind of concluded. I am
starting a vote on this one here.
The vote will be open for at least 72 hours (i.e. until June 20, 2024;
8:30am UTC) unless there are any objections. The FLIP will be considered
accepted if 3 binding votes (from activ
://cwiki.apache.org/confluence/display/FLINK/FLIP-461%3A+Synchronize+rescaling+with+checkpoint+creation+to+minimize+reprocessing+for+the+AdaptiveScheduler
On Fri, Jun 7, 2024 at 6:42 PM Matthias Pohl wrote:
> Hi Zakelly,
> good point. I updated the FLIP to use "scale-on-failed-checkpoints-count&
+1 (binding)
* Downloaded all artifacts
* Extracted sources and ran compilation on sources
* Diff of git tag checkout with downloaded sources
* Verified SHA512 & GPG checksums
* Checked that all POMs have the right expected version
* Generated diffs to compare pom file changes with NOTICE files
*
we might have to reprocess a substantial backlog.
> >
> > I think in the future we might actually want to enhance this by
> triggering
> > some kind of specialized "rescaling" checkpoint that prepares the cluster
> > for rescaling (eg. by replicating state to ne
Matthias Pohl created FLINK-35553:
-
Summary: Integrate newly added trigger interface with checkpointing
Key: FLINK-35553
URL: https://issues.apache.org/jira/browse/FLINK-35553
Project: Flink
Matthias Pohl created FLINK-35552:
-
Summary: Move CheckpointStatsTracker out of ExecutionGraph into
Scheduler
Key: FLINK-35552
URL: https://issues.apache.org/jira/browse/FLINK-35552
Project: Flink
Matthias Pohl created FLINK-35551:
-
Summary: Introduces RescaleManager#onTrigger endpoint
Key: FLINK-35551
URL: https://issues.apache.org/jira/browse/FLINK-35551
Project: Flink
Issue Type
Matthias Pohl created FLINK-35550:
-
Summary: Introduce new component RescaleManager
Key: FLINK-35550
URL: https://issues.apache.org/jira/browse/FLINK-35550
Project: Flink
Issue Type: Sub
Matthias Pohl created FLINK-35549:
-
Summary: FLIP-461: Synchronize rescaling with checkpoint creation
to minimize reprocessing for the AdaptiveScheduler
Key: FLINK-35549
URL: https://issues.apache.org/jira/browse
One reason could be that the savepoints are self-contained, owned by the
user rather than Flink and, therefore, could be moved. Flink wouldn't have
a proper reference in that case anymore.
I don't have a link to a discussion, though.
Best,
Matthias
On Fri, Jun 7, 2024 at 8:47 AM Gyula Fóra wrot
id confusion.
> Best,
> Zakelly
>
> On Wed, Jun 5, 2024 at 3:02 PM Matthias Pohl wrote:
>
> > Hi ConradJam,
> > thanks for your response.
> >
> > The CheckpointStatsTracker gets notified about the checkpoint completion
> > after th
I updated the FLIPs title.
>
> Also, I also don't understand why this proposal needs to care about the
> checkpoint type is unaligned checkpoint or aligned checkpoint.
>
> Please correct me if anything is wrong, thanks.
>
> Best,
> Rui
On Wed, Jun 5, 2024 at 3:01 PM Ma
d, Jun 5, 2024 at 4:46 AM ConradJam wrote:
> I have a few questions:
> Unaligned checkpoints Do we need to enable this feature? Whether this
> feature should be disabled for checkpoints that do not check it
>
> Matthias Pohl 于2024年6月4日周二 18:03写道：
>
> > Hi everyone,
> >
Hi everyone,
I'd like to discuss FLIP-461 [1]. The FLIP proposes the synchronization of
rescaling and the completion of checkpoints. The idea is to reduce the
amount of data that needs to be processed after rescaling happened. A more
detailed motivation can be found in FLIP-461.
I'm looking forwar
Congratulations, Weijie!
Matthias
On Tue, Jun 4, 2024 at 11:12 AM Guowei Ma wrote:
> Congratulations!
>
> Best,
> Guowei
>
>
> On Tue, Jun 4, 2024 at 4:55 PM gongzhongqiang
> wrote:
>
> > Congratulations Weijie! Best,
> > Zhongqiang Gong
> >
> > Xintong Song 于2024年6月4日周二 14:46写道：
> >
> > > Hi
> > > > formalize
> > > > > > > > > > the result of this discussion in a FLIP. That's just
> easier
> > > to
> > > > > > point
> > > > > > > > > >
I run isn't the best
option, either. But I still want to be transparent about your options.
Matthias
[1] https://issues.apache.org/jira/browse/FLINK-34999
[2]
https://dev.azure.com/apache-flink/apache-flink/_build?definitionId=1&_a=summary
--
[image: Aiven] <https://www.aiven.io
Matthias Pohl created FLINK-35000:
-
Summary: PullRequest template doesn't use the correct format to
refer to the testing code convention
Key: FLINK-35000
URL: https://issues.apache.org/jira/browse/FLINK-
Matthias Pohl created FLINK-34999:
-
Summary: PR CI stopped operating
Key: FLINK-34999
URL: https://issues.apache.org/jira/browse/FLINK-34999
Project: Flink
Issue Type: Bug
Matthias Pohl created FLINK-34989:
-
Summary: Apache Infra requests to reduce the runner usage for a
project
Key: FLINK-34989
URL: https://issues.apache.org/jira/browse/FLINK-34989
Project: Flink
Matthias Pohl created FLINK-34988:
-
Summary: Class loading issues in JDK17 and JDK21
Key: FLINK-34988
URL: https://issues.apache.org/jira/browse/FLINK-34988
Project: Flink
Issue Type: Bug
Matthias Pohl created FLINK-34961:
-
Summary: GitHub Actions statistcs can be monitored per workflow
name
Key: FLINK-34961
URL: https://issues.apache.org/jira/browse/FLINK-34961
Project: Flink
Matthias Pohl created FLINK-34940:
-
Summary: LeaderContender implementations handle invalid state
Key: FLINK-34940
URL: https://issues.apache.org/jira/browse/FLINK-34940
Project: Flink
Issue
Matthias Pohl created FLINK-34939:
-
Summary: Harden TestingLeaderElection
Key: FLINK-34939
URL: https://issues.apache.org/jira/browse/FLINK-34939
Project: Flink
Issue Type: Bug
Matthias Pohl created FLINK-34937:
-
Summary: Apache Infra GHA policy update
Key: FLINK-34937
URL: https://issues.apache.org/jira/browse/FLINK-34937
Project: Flink
Issue Type: Bug
Matthias Pohl created FLINK-34933:
-
Summary:
JobMasterServiceLeadershipRunnerTest#testResultFutureCompletionOfOutdatedLeaderIsIgnored
isn't implemented properly
Key: FLINK-34933
URL: https://issues.apach
Matthias Pohl created FLINK-34921:
-
Summary: SystemProcessingTimeServiceTest fails due to missing
output
Key: FLINK-34921
URL: https://issues.apache.org/jira/browse/FLINK-34921
Project: Flink
Matthias Pohl created FLINK-34897:
-
Summary:
JobMasterServiceLeadershipRunnerTest#testJobMasterServiceLeadershipRunnerCloseWhenElectionServiceGrantLeaderShip
needs to be enabled again
Key: FLINK-34897
URL: https
Matthias Pohl created FLINK-34695:
-
Summary: Move Flink's CI docker container into a public repo
Key: FLINK-34695
URL: https://issues.apache.org/jira/browse/FLINK-34695
Project: Flink
s working ok
>
> however to be on the safe side what if we mark it for removal or deprecated
> first
> and then remove together with dropping support of 1.17 where GHA is not
> supported IIUC?
>
> On Thu, Mar 14, 2024 at 11:42 AM Matthias Pohl
> wrote:
>
> > Hi everyone,
&g
Hi everyone,
I'm wondering whether anyone has objections against removing the Azure
Pipelines Tutorial to "set up CI for a fork of the Flink repository" in the
Flink wiki. Flink's GitHub Actions workflow seems to work fine for forks
(at least for 1.18+ changes). No need to guide contributors to the
1 - 100 of 975 matches
Mail list logo
