Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[WebJobs/EventHubs] Extension migration causes an invalid checkpoint message

See original GitHub issue

[2021-01-08T20:16:27.746Z] Function 'FunctionApp1.ProcessMessages.Run': An invalid checkpoint was found for partition: '8' of FullyQualifiedNamespace: 'pbatum-track2.servicebus.windows.net'; EventHubName: 'hub1'; ConsumerGroup: '$Default'.  This checkpoint is not valid and will be ignored

Issue Analytics

State:
Created 3 years ago
Comments:5

Top GitHub Comments

1reaction

shivanigoyal0705commented, Jul 12, 2022

Hi,

We upgraded eventhub packages from 4.2.0 to 5.1.1 and ran into same issue. From issue #17896 I can see change has been merged but I am still getting same issue. @pakrym - How did you resolve the issue ?

0reactions

shivanigoyal0705commented, Dec 2, 2022

I am also using same way. As a workaround,

Setup a migration utility using the code shared in migration guide.
First deployed the upgraded function app with all EventHubTriggerFunction in disabled mode to stop re-processing messages immediately.
Ran the utility locally to migrate checkpoint for each event hub.
Once checkpoints are restored at new location in new format , re-enabled EventHubTrigger functions . This was manual activity for one-time. By doing this eventhub trigger resumed events from last checkpoint.
Deployed function app again to revert disable setting of event hub trigger functions. This step was to avoid manual intervention for future deployments.

We use EventHubTrigger with Function App so checkpoints are managed for us, but we end up with processing the same messages multiple times. tor. 1. des. 2022 kl. 15:21 skrev shivanigoyal0705 @.*** … : We are also facing this problem, the checkpoints written to blob storage are 0 bytes after upgrading from 4.* to 5.* so we end up consuming the same messages multiple times. blob storages will be 0 bytes because checkpoints are now stored as properties from event hub 5.* onwards. We had to migrate checkpoints https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/eventhub/Azure.Messaging.EventHubs/MigrationGuide.md#migrating-eventprocessorhost-checkpoints — Reply to this email directly, view it on GitHub <#17882 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAF5VV7DZ4MHXDJCAEJFTMTWLCX5FANCNFSM4V55EO2Q . You are receiving this because you commented.Message ID: @.***>

Top Results From Across the Web

Troubleshooting "site is not responding" Issues

Scenario 6: "Site is not responding" message is displayed by the Endpoint Security Client while trying to create a new VPN Site.

How to migrate a competitor's database to Check Point with ...

Check Point understands that migrating a security database is a security-level critical mission for your organization. The Check Point SmartMove Tool converts a ......

Remote Access VPN clients and Endpoint services fail after ...

Check Point issued a small (2MB) and quick-to-install Patch for this issue. It replaces an existing .SYS file, delivering a fix that is...

you deserve the best security - Check Point Support Center

Cloud Migration Security · Compliance in the Cloud · Cloud Threat Hunting · Developer Security. Network Security. Hybrid Data Center · SD-WAN Security....

After users enter correct AD credentials, login to Remote ...

After users enter correct AD credentials, login to Remote Access VPN fails and a "<code>Wrong username or password</code>" message appears.