Hi ismcagdas,
We experiencing that jobs intended for a tenant is using server instances from the available servers regardless of regions.
For example:
Tenant1 has 10 jobs queued in the host db. Host db has many tenants, with different regions (south central & norhcentral). Those 10jobs is randomly selecting server from those tenants app services. Often will select the one's in northcentral, which cause latency issues - very slow.
I have checked the hangfire "Configuring Job Queues". The docs shows how to prioritize jobs in queue. I think this not applicable to our current situation. PLease advise.
Looking forward for your response.
Regards, Jur
Got the same error. I am updatting from version 8.2 to 10.1
We just had updated our aspnet zero into 8.2
After the update, majority of our Linq does not work anymore. Like said above EF 3.0 is the caused of it.
Do you had a recommended approach/workaround on those query with GroupBy.?
I created workaround by using the the web.config of the frontend..
I put there a rewrite setting that will reditrect the page to my custom angular page whenever the frontend experiencing a internal server error.
Thanks
Hi ismcagdas,
Do you mean emailing you to [email protected] the details of the job?
If so, what specific you want to know? I can share with you the whole code.
Thanks
Thanks for the info.
Im not sure if Redis already supported by zero, if not may i ask advise How do I setup redis with aspnet zero?
This is related to what i want to accomplished which is Hangfire.Pro.Redis functionality.