Any changes in Database packages and procedure does require datasource reset to take effect of the change.
Changing the initial capacity and minimum capacity to 0, does it require to reset the Weblogic Datasource.
Please share your thoughts.
I want to avoid reset process in Weblogic and share your views.
Related
We are having an Apache Ignite grid where we have persistence enabled but we are facing issues with persistence as we often face grid getting hung due locking while checkpointing.
We now want to move to non persistence grid but the problem is that non-persistent grid is auto active from start itself which we dont want. If grid is auto enabled then it doesn't give us time to do some initial checks before starting processing of tasks.
Is there any way to achieve this either in form of some initial delay or starting grid in inactive form?
Yes, the desired behaviour is totally achievable.
You can specify it as a part of your IgniteConfiguration, here is the right property. Possible options are:
ClusterState.INACTIVE
ClusterState.ACTIVE
ClusterState.ACTIVE_READ_ONLY
Please note, this property should be strictly consistent across a cluster.
Our analytics data is taking up almost 100% disk space on the file system. How do we remove the old er data, and prevent such situation from occurring again?
You can follow the url, https://mobilefirstplatform.ibmcloud.com/tutorials/en/foundation/8.0/installation-configuration/production/server-configuration/#setting-up-jndi-properties-for-mobilefirst-server-web-applications to setup JNDI properties in Mobilefirst. You need to
set the TTL values base on you business requirements, and keep the values as short as possible, so that huge data accumulation does not occur again. To clean up the existing data, you can perform the following
Setup the Analytics server with JNDI properties set for TTL and other configuration
Stop the Analytics Server
Delete the /analyticsData directory contents to discard any initial data (this will not affect as there is no data accumulated yet. So that there is no directories within the analyticsData directory) Note:
/analyticsData is the default location, please refer
http://mobilefirstplatform.ibmcloud.com/tutorials/en/foundation/8.0/installation-configuration/production/analytics/configuration/ to verify the actual value in your environment.
Restart the Analytics server. (Now the index will be created brand new with TTL in effect causing the proper data purging in place)
So here's the problem, I've created a database model. When I create the model, a = Model(args), and then perform a.put(), GAE seems to automatically update the memcache, because all the data seems up-to-date even without me hitting the database. Logging the number of elements in the cache works also shows the correct number of elements. But I'm not manually updating the cache. How do I prevent this? Cheers.
You can set policy functions:
Automatic caching is convenient for most applications but maybe your application is unusual and you want to turn off automatic caching for some or all entities. You can control the behavior of the caches by setting policy functions.
Memcache Policy
That's for NDB. You don't say what language/DB you are using but I'm sure it's all similar.
We're using siteCore 6.5 and each time we start to publish items, users who are browsing the website will get server 500 errors which end up being
Transaction (Process ID ##) was deadlocked on lock resources with
another process and has been chosen as the deadlock victim. Rerun the
transaction.
How can we setup SQL Server to give priority to a specific application? We cannnot modify any queries or code so it has to be done via SQL Server (or connection string)
I've seen "deadlock victim" in transaction, how to change the priority? and looked at http://msdn.microsoft.com/en-us/library/ms186736(v=SQL.105).aspx but these seem to be per session, not globally.
I don't care if it's a fix/change to SiteCore or a SQL solution.
I don't think you can set the deadlock priority globally - it's a session-only setting. There are not any connection string settings that I know of. The list of possible SqlConnection string settings can be found here.
It sounds to me like you're actually having a problem with the cache and every time you publish, it's clearing the cache and thus you're getting deadlocks with all these calls made at the same time. I haven't seen this sort of thing happen with 6.5 so you might also want to check into your caching. It would help a lot to look at your Sitecore logs and see if this is happening when caches are being created. Either way, check the caching guide on the SDN and see if that helps.
I've been reading about locking the various persistent variables, application, session, etc. and I understand the race conditions that exists with reading application variables that are updated often.
I'm not so sure about session variables and application variables that don't change. I am on a single server and CF9. I'm locking the session variables when I set them, but is it really necessary to lock them when reading them. Doesn't each user have their own set of session variables. How would changing values for one user effect an different user viewing the same page at the same time.
Also, I set application variables in my application.cfc file and they do not change. Are locks needed every time I read the application.dsn variable?
You don't need to lock session variables unless you have part of your app that is going to be modifying the user's session directly (which is part of an undocumented feature in CF, so it's not likely you're doing that anyway).
As for Application variables, you shouldn't need to lock those either if you're just setting them once and never messing with them again.