Import failed after purge

Maciej Żelaszczyk

unread,

May 28, 2021, 8:59:02 AM5/28/21

to cloud-recommendations-users

Hi,

After a purge of userEvents, the stats for one event type go negative. Other threads suggest this is a known issue. My problem is that for this specific event type, I cannot successfully run an import operation for this event type (other event types work fine).

Best,

Maciek

Maciej Żelaszczyk

unread,

Jul 6, 2021, 7:16:22 AM7/6/21

to cloud-recommendations-users

The problem seems to persist and prevents me from importing new userEvents.

Best,

Maciek

Patrick Hess

unread,

Jul 6, 2021, 9:24:55 AM7/6/21

to Maciej Żelaszczyk, cloud-recommendations-users

Hi Maciej,

Yes this is a known bug on our end that came up recently, we trying to fix but in meantime discouraging purge if possible.

Why is this preventing more events from being ingested?

Cheers,

Patrick

--
You received this message because you are subscribed to the Google Groups "cloud-recommendations-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cloud-recommendatio...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cloud-recommendations-users/ba4668e9-d2bf-43fe-ad03-aad70efa791bn%40googlegroups.com.

Maciej Żelaszczyk

unread,

Jul 7, 2021, 5:10:48 AM7/7/21

to Patrick Hess, cloud-recommendations-users

Whenever I try to schedule an import operation for an event type with a negative event count the operation is scheduled correctly but after a while I get the following error in the `Import activity` dashboard: `Internal error occurred. Please try again. If the issue persists please contact https://groups.google.com/g/cloud-recommendations-users.` For events with zero counts the import works OK.

--

Maciej Żelaszczyk
Senior Data Scientist

Yosh.AI Ltd
UK office: Craven House,
40-44 Uxbridge Road, W5 2BS London
Poland office: ul. Foksal 16, 00-372 Warsaw

Patrick Hess

unread,

Jul 7, 2021, 9:53:49 AM7/7/21

to Maciej Żelaszczyk, cloud-recommendations-users

Hi Maciej,

Thanks for flagging. This is odd indeed. What is your project #?

Regards,

Patrick

Maciej Żelaszczyk

unread,

Jul 7, 2021, 9:57:15 AM7/7/21

to Patrick Hess, cloud-recommendations-users

Thanks for the reply. Project number: 71468179804

Best,

Maciek

Patrick Hess

unread,

Jul 7, 2021, 10:03:10 AM7/7/21

to Maciej Żelaszczyk, cloud-recommendations-users

Hi Maciej,

Forwarded to an internal team to review. My personal suggestion, if possible, would be to try with a fresh project from scratch while we work to resolve this issue. It's not ideal, but its a workaround.

Regards,

Patrick

Patrick Hess

unread,

Jul 7, 2021, 12:41:12 PM7/7/21

to Maciej Żelaszczyk, cloud-recommendations-users

Hi Maciej,

The issue might be unrelated to stats - i think this is a bug where if the file name is too long, it exceeds some internal limits (we append some timestamp). We are rolling out a fix to truncate file name length - but will take sometime to rollout - for a workaround consider shortening the file name length. Let me know if that helps!

Cheers,
Patrick

Maciej Żelaszczyk

unread,

Jul 8, 2021, 10:33:39 AM7/8/21

to Patrick Hess, cloud-recommendations-users

Hi Patrick,

I have tried the approach of shortening the file name but cutting it down to "train" (that's the whole name after the change) does not seem to help - I get the same error as before.

Best,

Maciek

Peng Ren

unread,

Jul 8, 2021, 9:26:11 PM7/8/21

to cloud-recommendations-users

Hi Maciej,

We did some check on our side. Your import failure was due to another issue not related to the filename. Sorry about that.

Our debug logs indicate that when we tried to export your Bigquery data, the Bigquery worker encountered "Resources exceeded during query execution". Maybe you have lots of data in your Bigquery table? Could you please try to split your table into smaller parts and try to import them again? We will also explore ways to fix this issue in the long term. Sorry for the inconvenience.