Re: [DISCUSS] Alternative way of posting FLIPs
+1 for option 1. Hi Yun, > I am concerned about whether we can view the history of design docs > If someone has editor permissions, they can also view the editing history of Google Docs[1]. If the change history of the design document is equally important, would it be possible to selectively share the editor link with the developers involved in the discussion for the FLIP? [1] https://support.google.com/docs/answer/190843?sjid=8405245178977557481-NC Best, Jane On Fri, Feb 9, 2024 at 5:33 PM Sergey Nuyanzin wrote: > +1 for option 1 > > On Fri, Feb 9, 2024 at 10:18 AM Jing Ge > wrote: > > > +1 for option 1. The Github discussions look more like an overlap to the > ML > > instead of a wiki tool like Confluence. > > > > Best regards, > > Jing > > > > On Fri, Feb 9, 2024 at 10:08 AM Yun Tang wrote: > > > > > For the first solution, I am concerned about whether we can view the > > > history of design docs, which is supported by Confluence wiki and > GitHub > > > discussions. From my understanding, even the discussion history could > let > > > others know the evolution of this feature and the history of a design > doc > > > is also really important. > > > > > > Best > > > Yun Tang > > > > > > From: Piotr Nowojski > > > Sent: Thursday, February 8, 2024 14:17 > > > To: dev@flink.apache.org > > > Subject: Re: [DISCUSS] Alternative way of posting FLIPs > > > > > > +1 for the first option as well > > > > > > Best, > > > Piotrek > > > > > > śr., 7 lut 2024 o 16:48 Matthias Pohl > > > napisał(a): > > > > > > > +1 for option 1 since it's a reasonable temporary workaround > > > > > > > > Moving to GitHub discussions would either mean moving the current > FLIP > > > > collection or having the FLIPs in two locations. Both options do not > > seem > > > > to be optimal. Another concern I had was that GitHub Discussions > > wouldn't > > > > allow integrating diagrams that easily. But it looks like they > support > > > > Mermaid [1] for diagrams. > > > > > > > > One flaw of the GoogleDocs approach is, though, that we have to rely > on > > > > diagrams being provided as PNG/JPG/SVG rather than draw.io diagrams. > > > > draw.io > > > > is more tightly integrated with the Confluence wiki which allows > > > > editing/updating diagrams in the wiki rather than using some external > > > tool. > > > > Google Draw is also not that convenient to use in my opinion. Anyway, > > > > that's a minor issue, I guess. > > > > > > > > Matthias > > > > > > > > [1] > > > > > > > > > > > > > > https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams > > > > > > > > On Wed, Feb 7, 2024 at 3:30 PM Lincoln Lee > > > wrote: > > > > > > > > > Thanks Martijn moving this forward! > > > > > > > > > > +1 for the first solution, because as of now it looks like this is > a > > > > > temporary solution and we're still looking forward to the > improvement > > > by > > > > > ASF Infra, when the access is ok for contributors, we can back to > the > > > > > current workflow. > > > > > > > > > > For solution 2, one visible downside is that it becomes > inconvenient > > to > > > > > look for flips (unless we permanently switch to github discussion). > > > > > > > > > > Looking forward to hearing more thoughts. > > > > > > > > > > Best, > > > > > Lincoln Lee > > > > > > > > > > > > > > > Martijn Visser 于2024年2月7日周三 21:51写道： > > > > > > > > > > > Hi all, > > > > > > > > > > > > ASF Infra has confirmed to me that only ASF committers can access > > the > > > > > > ASF Confluence site since a recent change. One of the results of > > this > > > > > > decision is that users can't signup and access Confluence, so > only > > > > > > committers+ can create FLIPs. > > > > > > > > > > > > ASF Infra hopes to improve this situation when they move to the > > Cloud > > > > > > shortly (as in: some months), but they haven't committed on an > > actual > > > > > > date. The idea would be that we find a temporary solution until > > > anyone > > > > > > can request access to Confluence. > > > > > > > > > > > > There are a couple of ways we could resolve this situation: > > > > > > 1. Contributors create a Google Doc and make that view-only, and > > post > > > > > > that Google Doc to the mailing list for a discussion thread. When > > the > > > > > > discussions have been resolved, the contributor ask on the Dev > > > mailing > > > > > > list to a committer/PMC to copy the contents from the Google Doc, > > and > > > > > > create a FLIP number for them. The contributor can then use that > > FLIP > > > > > > to actually have a VOTE thread. > > > > > > 2. We could consider moving FLIPs to "Discussions" on Github, > like > > > > > > Airflow does at https://github.com/apache/airflow/discussions > > > > > > 3. Perhaps someone else has another good idea. > > > > > > > > > > > > Looking forward to your thoughts. > > > > > > > > > > > > Best regards, > > > > > > > > > > > > Martijn > > > > > > > > >
RE: Issues running with Flink 1.20-SNAPSHOT
Hi Martijn, Yes the Maven wrapper works, so it is a local issue. Thank you for the pointer, I am glad it is not anything serious, Kind regards, David. From: Martijn Visser Date: Friday, 9 February 2024 at 16:27 To: dev@flink.apache.org Subject: [EXTERNAL] Re: Issues running with Flink 1.20-SNAPSHOT Hi, There's never a flink_dist, this is most likely because of a local build problem. See https://repository.apache.org/content/groups/snapshots/org/apache/flink/flink-dist/1.19-SNAPSHOT/ which also doesn't exist. This is most likely a local build problem; are you using the Maven wrapper? Best regards, Martijn On Fri, Feb 9, 2024 at 4:43 PM David Radley wrote: > > Hello, > I am git cloned the latest flink to a new folder. I emptied my .m2 folder for > Flink then ran. > > mvn clean > > and see error > > [ERROR] Failed to execute goal on project flink-dist_2.12: Could not resolve > dependencies for project org.apache.flink:flink-dist_2.12:jar:1.20-SNAPSHOT: > The following artifacts could not be resolved: > org.apache.flink:flink-dist-scala_2.12:jar:1.20-SNAPSHOT, > org.apache.flink:flink-examples-streaming-state-machine:jar:1.20-SNAPSHOT: > Could not find artifact > org.apache.flink:flink-dist-scala_2.12:jar:1.20-SNAPSHOT in apache.snapshots > (https://repository.apache.org/snapshots ) -> [Help 1] > > I look in > https://repository.apache.org/content/groups/snapshots/org/apache/flink/ and > do not see flink-dist-scala_2.12:jar > > My environment is > > mvn -version > Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63) > Maven home: /Applications/apache-maven-3.8.6 > Java version: 11.0.18, vendor: Eclipse Adoptium, runtime: > /Library/Java/JavaVirtualMachines/temurin-11.jdk/Contents/Home > Default locale: en_GB, platform encoding: UTF-8 > OS name: "mac os x", version: "14.2.1", arch: "aarch64", family: "mac" > (base) davidradley@Davids-MBP-2 flink120 % mvn -version > Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63) > Maven home: /Applications/apache-maven-3.8.6 > Java version: 11.0.18, vendor: Eclipse Adoptium, runtime: > /Library/Java/JavaVirtualMachines/temurin-11.jdk/Contents/Home > Default locale: en_GB, platform encoding: UTF-8 > OS name: "mac os x", version: "14.2.1", arch: "aarch64", family: "mac" > > It looks like the new snapshot is not completely there. I was expecting to > see a folder for flink-dist-scala_2.12:jar > similar to > https://repository.apache.org/content/groups/snapshots/org/apache/flink/flink-core/1.20-SNAPSHOT/ > >Kind regards, David. > > > > Unless otherwise stated above: > > IBM United Kingdom Limited > Registered in England and Wales with number 741598 > Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU Unless otherwise stated above: IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU
Re: Issues running with Flink 1.20-SNAPSHOT
Hi, There's never a flink_dist, this is most likely because of a local build problem. See https://repository.apache.org/content/groups/snapshots/org/apache/flink/flink-dist/1.19-SNAPSHOT/ which also doesn't exist. This is most likely a local build problem; are you using the Maven wrapper? Best regards, Martijn On Fri, Feb 9, 2024 at 4:43 PM David Radley wrote: > > Hello, > I am git cloned the latest flink to a new folder. I emptied my .m2 folder for > Flink then ran. > > mvn clean > > and see error > > [ERROR] Failed to execute goal on project flink-dist_2.12: Could not resolve > dependencies for project org.apache.flink:flink-dist_2.12:jar:1.20-SNAPSHOT: > The following artifacts could not be resolved: > org.apache.flink:flink-dist-scala_2.12:jar:1.20-SNAPSHOT, > org.apache.flink:flink-examples-streaming-state-machine:jar:1.20-SNAPSHOT: > Could not find artifact > org.apache.flink:flink-dist-scala_2.12:jar:1.20-SNAPSHOT in apache.snapshots > (https://repository.apache.org/snapshots) -> [Help 1] > > I look in > https://repository.apache.org/content/groups/snapshots/org/apache/flink/ and > do not see flink-dist-scala_2.12:jar > > My environment is > > mvn -version > Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63) > Maven home: /Applications/apache-maven-3.8.6 > Java version: 11.0.18, vendor: Eclipse Adoptium, runtime: > /Library/Java/JavaVirtualMachines/temurin-11.jdk/Contents/Home > Default locale: en_GB, platform encoding: UTF-8 > OS name: "mac os x", version: "14.2.1", arch: "aarch64", family: "mac" > (base) davidradley@Davids-MBP-2 flink120 % mvn -version > Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63) > Maven home: /Applications/apache-maven-3.8.6 > Java version: 11.0.18, vendor: Eclipse Adoptium, runtime: > /Library/Java/JavaVirtualMachines/temurin-11.jdk/Contents/Home > Default locale: en_GB, platform encoding: UTF-8 > OS name: "mac os x", version: "14.2.1", arch: "aarch64", family: "mac" > > It looks like the new snapshot is not completely there. I was expecting to > see a folder for flink-dist-scala_2.12:jar > similar to > https://repository.apache.org/content/groups/snapshots/org/apache/flink/flink-core/1.20-SNAPSHOT/ > >Kind regards, David. > > > > Unless otherwise stated above: > > IBM United Kingdom Limited > Registered in England and Wales with number 741598 > Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU
Issues running with Flink 1.20-SNAPSHOT
Hello, I am git cloned the latest flink to a new folder. I emptied my .m2 folder for Flink then ran. mvn clean and see error [ERROR] Failed to execute goal on project flink-dist_2.12: Could not resolve dependencies for project org.apache.flink:flink-dist_2.12:jar:1.20-SNAPSHOT: The following artifacts could not be resolved: org.apache.flink:flink-dist-scala_2.12:jar:1.20-SNAPSHOT, org.apache.flink:flink-examples-streaming-state-machine:jar:1.20-SNAPSHOT: Could not find artifact org.apache.flink:flink-dist-scala_2.12:jar:1.20-SNAPSHOT in apache.snapshots (https://repository.apache.org/snapshots) -> [Help 1] I look in https://repository.apache.org/content/groups/snapshots/org/apache/flink/ and do not see flink-dist-scala_2.12:jar My environment is mvn -version Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63) Maven home: /Applications/apache-maven-3.8.6 Java version: 11.0.18, vendor: Eclipse Adoptium, runtime: /Library/Java/JavaVirtualMachines/temurin-11.jdk/Contents/Home Default locale: en_GB, platform encoding: UTF-8 OS name: "mac os x", version: "14.2.1", arch: "aarch64", family: "mac" (base) davidradley@Davids-MBP-2 flink120 % mvn -version Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63) Maven home: /Applications/apache-maven-3.8.6 Java version: 11.0.18, vendor: Eclipse Adoptium, runtime: /Library/Java/JavaVirtualMachines/temurin-11.jdk/Contents/Home Default locale: en_GB, platform encoding: UTF-8 OS name: "mac os x", version: "14.2.1", arch: "aarch64", family: "mac" It looks like the new snapshot is not completely there. I was expecting to see a folder for flink-dist-scala_2.12:jar similar to https://repository.apache.org/content/groups/snapshots/org/apache/flink/flink-core/1.20-SNAPSHOT/ Kind regards, David. Unless otherwise stated above: IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU
[jira] [Created] (FLINK-34419) flink-docker's .github/workflows/snapshot.yml doesn't support JDK 17 and 21
Matthias Pohl created FLINK-34419: - Summary: flink-docker's .github/workflows/snapshot.yml doesn't support JDK 17 and 21 Key: FLINK-34419 URL: https://issues.apache.org/jira/browse/FLINK-34419 Project: Flink Issue Type: Technical Debt Components: Build System / CI Reporter: Matthias Pohl [.github/workflows/snapshot.yml|https://github.com/apache/flink-docker/blob/master/.github/workflows/snapshot.yml#L40] needs to be updated: JDK 17 support was added in 1.18 (FLINK-15736). JDK 21 support was added in 1.19 (FLINK-33163) -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [DISCUSS] Alternative way of posting FLIPs
+1 for option 1 On Fri, Feb 9, 2024 at 10:18 AM Jing Ge wrote: > +1 for option 1. The Github discussions look more like an overlap to the ML > instead of a wiki tool like Confluence. > > Best regards, > Jing > > On Fri, Feb 9, 2024 at 10:08 AM Yun Tang wrote: > > > For the first solution, I am concerned about whether we can view the > > history of design docs, which is supported by Confluence wiki and GitHub > > discussions. From my understanding, even the discussion history could let > > others know the evolution of this feature and the history of a design doc > > is also really important. > > > > Best > > Yun Tang > > > > From: Piotr Nowojski > > Sent: Thursday, February 8, 2024 14:17 > > To: dev@flink.apache.org > > Subject: Re: [DISCUSS] Alternative way of posting FLIPs > > > > +1 for the first option as well > > > > Best, > > Piotrek > > > > śr., 7 lut 2024 o 16:48 Matthias Pohl > > napisał(a): > > > > > +1 for option 1 since it's a reasonable temporary workaround > > > > > > Moving to GitHub discussions would either mean moving the current FLIP > > > collection or having the FLIPs in two locations. Both options do not > seem > > > to be optimal. Another concern I had was that GitHub Discussions > wouldn't > > > allow integrating diagrams that easily. But it looks like they support > > > Mermaid [1] for diagrams. > > > > > > One flaw of the GoogleDocs approach is, though, that we have to rely on > > > diagrams being provided as PNG/JPG/SVG rather than draw.io diagrams. > > > draw.io > > > is more tightly integrated with the Confluence wiki which allows > > > editing/updating diagrams in the wiki rather than using some external > > tool. > > > Google Draw is also not that convenient to use in my opinion. Anyway, > > > that's a minor issue, I guess. > > > > > > Matthias > > > > > > [1] > > > > > > > > > https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams > > > > > > On Wed, Feb 7, 2024 at 3:30 PM Lincoln Lee > > wrote: > > > > > > > Thanks Martijn moving this forward! > > > > > > > > +1 for the first solution, because as of now it looks like this is a > > > > temporary solution and we're still looking forward to the improvement > > by > > > > ASF Infra, when the access is ok for contributors, we can back to the > > > > current workflow. > > > > > > > > For solution 2, one visible downside is that it becomes inconvenient > to > > > > look for flips (unless we permanently switch to github discussion). > > > > > > > > Looking forward to hearing more thoughts. > > > > > > > > Best, > > > > Lincoln Lee > > > > > > > > > > > > Martijn Visser 于2024年2月7日周三 21:51写道： > > > > > > > > > Hi all, > > > > > > > > > > ASF Infra has confirmed to me that only ASF committers can access > the > > > > > ASF Confluence site since a recent change. One of the results of > this > > > > > decision is that users can't signup and access Confluence, so only > > > > > committers+ can create FLIPs. > > > > > > > > > > ASF Infra hopes to improve this situation when they move to the > Cloud > > > > > shortly (as in: some months), but they haven't committed on an > actual > > > > > date. The idea would be that we find a temporary solution until > > anyone > > > > > can request access to Confluence. > > > > > > > > > > There are a couple of ways we could resolve this situation: > > > > > 1. Contributors create a Google Doc and make that view-only, and > post > > > > > that Google Doc to the mailing list for a discussion thread. When > the > > > > > discussions have been resolved, the contributor ask on the Dev > > mailing > > > > > list to a committer/PMC to copy the contents from the Google Doc, > and > > > > > create a FLIP number for them. The contributor can then use that > FLIP > > > > > to actually have a VOTE thread. > > > > > 2. We could consider moving FLIPs to "Discussions" on Github, like > > > > > Airflow does at https://github.com/apache/airflow/discussions > > > > > 3. Perhaps someone else has another good idea. > > > > > > > > > > Looking forward to your thoughts. > > > > > > > > > > Best regards, > > > > > > > > > > Martijn > > > > > > > > > > > > > > > -- Best regards, Sergey
Re: [DISCUSS] Alternative way of posting FLIPs
+1 for option 1. The Github discussions look more like an overlap to the ML instead of a wiki tool like Confluence. Best regards, Jing On Fri, Feb 9, 2024 at 10:08 AM Yun Tang wrote: > For the first solution, I am concerned about whether we can view the > history of design docs, which is supported by Confluence wiki and GitHub > discussions. From my understanding, even the discussion history could let > others know the evolution of this feature and the history of a design doc > is also really important. > > Best > Yun Tang > > From: Piotr Nowojski > Sent: Thursday, February 8, 2024 14:17 > To: dev@flink.apache.org > Subject: Re: [DISCUSS] Alternative way of posting FLIPs > > +1 for the first option as well > > Best, > Piotrek > > śr., 7 lut 2024 o 16:48 Matthias Pohl > napisał(a): > > > +1 for option 1 since it's a reasonable temporary workaround > > > > Moving to GitHub discussions would either mean moving the current FLIP > > collection or having the FLIPs in two locations. Both options do not seem > > to be optimal. Another concern I had was that GitHub Discussions wouldn't > > allow integrating diagrams that easily. But it looks like they support > > Mermaid [1] for diagrams. > > > > One flaw of the GoogleDocs approach is, though, that we have to rely on > > diagrams being provided as PNG/JPG/SVG rather than draw.io diagrams. > > draw.io > > is more tightly integrated with the Confluence wiki which allows > > editing/updating diagrams in the wiki rather than using some external > tool. > > Google Draw is also not that convenient to use in my opinion. Anyway, > > that's a minor issue, I guess. > > > > Matthias > > > > [1] > > > > > https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams > > > > On Wed, Feb 7, 2024 at 3:30 PM Lincoln Lee > wrote: > > > > > Thanks Martijn moving this forward! > > > > > > +1 for the first solution, because as of now it looks like this is a > > > temporary solution and we're still looking forward to the improvement > by > > > ASF Infra, when the access is ok for contributors, we can back to the > > > current workflow. > > > > > > For solution 2, one visible downside is that it becomes inconvenient to > > > look for flips (unless we permanently switch to github discussion). > > > > > > Looking forward to hearing more thoughts. > > > > > > Best, > > > Lincoln Lee > > > > > > > > > Martijn Visser 于2024年2月7日周三 21:51写道： > > > > > > > Hi all, > > > > > > > > ASF Infra has confirmed to me that only ASF committers can access the > > > > ASF Confluence site since a recent change. One of the results of this > > > > decision is that users can't signup and access Confluence, so only > > > > committers+ can create FLIPs. > > > > > > > > ASF Infra hopes to improve this situation when they move to the Cloud > > > > shortly (as in: some months), but they haven't committed on an actual > > > > date. The idea would be that we find a temporary solution until > anyone > > > > can request access to Confluence. > > > > > > > > There are a couple of ways we could resolve this situation: > > > > 1. Contributors create a Google Doc and make that view-only, and post > > > > that Google Doc to the mailing list for a discussion thread. When the > > > > discussions have been resolved, the contributor ask on the Dev > mailing > > > > list to a committer/PMC to copy the contents from the Google Doc, and > > > > create a FLIP number for them. The contributor can then use that FLIP > > > > to actually have a VOTE thread. > > > > 2. We could consider moving FLIPs to "Discussions" on Github, like > > > > Airflow does at https://github.com/apache/airflow/discussions > > > > 3. Perhaps someone else has another good idea. > > > > > > > > Looking forward to your thoughts. > > > > > > > > Best regards, > > > > > > > > Martijn > > > > > > > > > >
Re: [DISCUSS] Alternative way of posting FLIPs
For the first solution, I am concerned about whether we can view the history of design docs, which is supported by Confluence wiki and GitHub discussions. From my understanding, even the discussion history could let others know the evolution of this feature and the history of a design doc is also really important. Best Yun Tang From: Piotr Nowojski Sent: Thursday, February 8, 2024 14:17 To: dev@flink.apache.org Subject: Re: [DISCUSS] Alternative way of posting FLIPs +1 for the first option as well Best, Piotrek śr., 7 lut 2024 o 16:48 Matthias Pohl napisał(a): > +1 for option 1 since it's a reasonable temporary workaround > > Moving to GitHub discussions would either mean moving the current FLIP > collection or having the FLIPs in two locations. Both options do not seem > to be optimal. Another concern I had was that GitHub Discussions wouldn't > allow integrating diagrams that easily. But it looks like they support > Mermaid [1] for diagrams. > > One flaw of the GoogleDocs approach is, though, that we have to rely on > diagrams being provided as PNG/JPG/SVG rather than draw.io diagrams. > draw.io > is more tightly integrated with the Confluence wiki which allows > editing/updating diagrams in the wiki rather than using some external tool. > Google Draw is also not that convenient to use in my opinion. Anyway, > that's a minor issue, I guess. > > Matthias > > [1] > > https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams > > On Wed, Feb 7, 2024 at 3:30 PM Lincoln Lee wrote: > > > Thanks Martijn moving this forward! > > > > +1 for the first solution, because as of now it looks like this is a > > temporary solution and we're still looking forward to the improvement by > > ASF Infra, when the access is ok for contributors, we can back to the > > current workflow. > > > > For solution 2, one visible downside is that it becomes inconvenient to > > look for flips (unless we permanently switch to github discussion). > > > > Looking forward to hearing more thoughts. > > > > Best, > > Lincoln Lee > > > > > > Martijn Visser 于2024年2月7日周三 21:51写道： > > > > > Hi all, > > > > > > ASF Infra has confirmed to me that only ASF committers can access the > > > ASF Confluence site since a recent change. One of the results of this > > > decision is that users can't signup and access Confluence, so only > > > committers+ can create FLIPs. > > > > > > ASF Infra hopes to improve this situation when they move to the Cloud > > > shortly (as in: some months), but they haven't committed on an actual > > > date. The idea would be that we find a temporary solution until anyone > > > can request access to Confluence. > > > > > > There are a couple of ways we could resolve this situation: > > > 1. Contributors create a Google Doc and make that view-only, and post > > > that Google Doc to the mailing list for a discussion thread. When the > > > discussions have been resolved, the contributor ask on the Dev mailing > > > list to a committer/PMC to copy the contents from the Google Doc, and > > > create a FLIP number for them. The contributor can then use that FLIP > > > to actually have a VOTE thread. > > > 2. We could consider moving FLIPs to "Discussions" on Github, like > > > Airflow does at https://github.com/apache/airflow/discussions > > > 3. Perhaps someone else has another good idea. > > > > > > Looking forward to your thoughts. > > > > > > Best regards, > > > > > > Martijn > > > > > >
[jira] [Created] (FLINK-34418) YARNSessionCapacitySchedulerITCase.testVCoresAreSetCorrectlyAndJobManagerHostnameAreShownInWebInterfaceAndDynamicPropertiesAndYarnApplicationNameAndTaskManagerSlots fail
Matthias Pohl created FLINK-34418:
-
Summary:
YARNSessionCapacitySchedulerITCase.testVCoresAreSetCorrectlyAndJobManagerHostnameAreShownInWebInterfaceAndDynamicPropertiesAndYarnApplicationNameAndTaskManagerSlots
failed due to disk space
Key: FLINK-34418
URL: https://issues.apache.org/jira/browse/FLINK-34418
Project: Flink
Issue Type: Bug
Components: Test Infrastructure
Affects Versions: 1.18.1, 1.19.0, 1.20.0
Reporter: Matthias Pohl
[https://github.com/apache/flink/actions/runs/7838691874/job/21390739806#step:10:27746]
{code:java}
[...]
Feb 09 03:00:13 Caused by: java.io.IOException: No space left on device
27608Feb 09 03:00:13at java.io.FileOutputStream.writeBytes(Native Method)
27609Feb 09 03:00:13at
java.io.FileOutputStream.write(FileOutputStream.java:326)
27610Feb 09 03:00:13at
org.apache.logging.log4j.core.appender.OutputStreamManager.writeToDestination(OutputStreamManager.java:250)
27611Feb 09 03:00:13... 39 more
[...] {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
