Assigned
Status Update
No update yet.
Comments
pa...@google.com
ze...@getcruise.com
Hello,
This issue report has been forwarded to the Cloud AI Platform team so that they may investigate it, but there is no ETA for a resolution today. Future updates regarding this issue will be provided here.
pa...@google.com
Attached is a screenshot of the redact button missing
Corey Salej
Service Center Supervisor
PENN Interactive
Corey.Salej@Penn-Interactive.com
pennentertainment.com
[cid:b2acab27-f82d-466b-873f-45d15f928d6f]
Confidentiality Notice: This email and all attachments may be confidential information and are intended solely for the individual or entity named in the email address. If you receive this email in error or if it is improperly forwarded to you, please notify the sender immediately by reply email, and delete/destroy the original and all copies, including any attachments. Any unauthorized review, use, disclosure, reproduction, or distribution in part or in whole, is strictly prohibited and may be unlawful.
________________________________
From: buganizer-system@google.com <buganizer-system@google.com>
Sent: Thursday, September 26, 2024 10:35 AM
To: b-system+1793728677@google.com <b-system+1793728677@google.com>
Cc: Corey Salej <Corey.Salej@thescore.com>
Subject: Re:
Replying to this email means your email address will be shared with the team that works on this product.
https://issuetracker.google.com/issues/369636234
Changed
assignee: je...@google.com �$B"*�(B gc...@google.com
_______________________________
Reference Info: 369636234 Issue with CCAI Redact buttons
component: Public Trackers > Cloud Platform > AI & Machine Learning > AI Platform<https://issuetracker.google.com/components/187220 >
status: Assigned
reporter: corey.salej@thescore.com
assignee: gc...@google.com
cc: corey.salej@thescore.com, je...@google.com
type: Feature Request
access level: Default access
priority: P2
severity: S2
blocked by: 369817338<https://issuetracker.google.com/issues/369817338 >
retention: Component default
Generated by Google IssueTracker notification system.
You're receiving this email because you are subscribed to updates on Google IssueTrackerhttps://issuetracker.google.com/issues/369636234 > where you have the roles: starred, reporter, cc
Unsubscribe from this issue.<https://issuetracker.google.com/issues/369636234?unsubscribe=true >
This email and all attachments are confidential information and are intended solely for the intended recipient(s). If you have received this email and attachments in error, please notify the sender immediately and delete/destroy the original and all copies (including all attachments) from your system. Any and all unauthorized review, use, disclosure, dissemination, reproduction, alteration, or distribution, in part or in whole, is strictly prohibited and may be unlawful. Any views or opinions presented in this email and attachments are those of the author and may not represent those of PENN Entertainment, Inc. or any of its subsidiaries and affiliates.
Corey Salej
Service Center Supervisor
PENN Interactive
Corey.Salej@Penn-Interactive.com
[cid:b2acab27-f82d-466b-873f-45d15f928d6f]
Confidentiality Notice: This email and all attachments may be confidential information and are intended solely for the individual or entity named in the email address. If you receive this email in error or if it is improperly forwarded to you, please notify the sender immediately by reply email, and delete/destroy the original and all copies, including any attachments. Any unauthorized review, use, disclosure, reproduction, or distribution in part or in whole, is strictly prohibited and may be unlawful.
________________________________
From: buganizer-system@google.com <buganizer-system@google.com>
Sent: Thursday, September 26, 2024 10:35 AM
To: b-system+1793728677@google.com <b-system+1793728677@google.com>
Cc: Corey Salej <Corey.Salej@thescore.com>
Subject: Re:
Replying to this email means your email address will be shared with the team that works on this product.
Changed
assignee: je...@google.com �$B"*�(B gc...@google.com
_______________________________
Reference Info: 369636234 Issue with CCAI Redact buttons
component: Public Trackers > Cloud Platform > AI & Machine Learning > AI Platform<
status: Assigned
reporter: corey.salej@thescore.com
assignee: gc...@google.com
cc: corey.salej@thescore.com, je...@google.com
type: Feature Request
access level: Default access
priority: P2
severity: S2
blocked by: 369817338<
retention: Component default
Generated by Google IssueTracker notification system.
You're receiving this email because you are subscribed to updates on Google IssueTracker
Unsubscribe from this issue.<
This email and all attachments are confidential information and are intended solely for the intended recipient(s). If you have received this email and attachments in error, please notify the sender immediately and delete/destroy the original and all copies (including all attachments) from your system. Any and all unauthorized review, use, disclosure, dissemination, reproduction, alteration, or distribution, in part or in whole, is strictly prohibited and may be unlawful. Any views or opinions presented in this email and attachments are those of the author and may not represent those of PENN Entertainment, Inc. or any of its subsidiaries and affiliates.
Description
Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.
Problem you have encountered:
Customer was trying to run the AL job to train the data using custom training but all jobs failed with the same error[1].
[1] <container..> was reset due to preemption
As discussed with the Engineering team, customers need to perform the following steps or config changes on computation to mitigate the issue.
1- run the jobs with GPUs in the head node.
or
2- larger VM and disk for master node.
Option 1 worked and the customer confirmed, they did not see the error. As a workaround, customer will apply the changes on job configuration for computation.
Engineering team will continuously work for a permanent fix.
What you expected to happen:
Job should not fail due to preemption.
Steps to reproduce:
Other information (workarounds you have tried, documentation consulted, etc):