I have installed memcache and its required package on ubuntu and enable memcache module in drupal 7. Memcache worked well but when a new node is created or updated, view should be updated but it always provide the cache version of page not updated version of page.
i want to expire memcache cache when we create or update a node.
Cache must be rebuild.
I am using these package version:
Drupal 7.24
Php 5.5.3
Ubuntu 13.10.2
Memcached 1.4.14
Drupal memcache module 7.x
Do you mean the view isn't updated or the node isn't updated?
See if the following module is helphul: https://www.drupal.org/project/expire
Related
We just deployed our new website on the same domain but with a different stack. the old stack was create-react-app and it had service workers which is caching for offline usage.
Now after the new version is deployed, it still shows up the old version because of the cache. is there anyway i can force all users who visits the website to clear cache automatically?
When I deploy a project I get this error
INVALID_ARGUMENT: Your app may not have more than 15 versions. Please delete one of the existing versions before trying to create a new version.
I also went to versions on google cloud and tried to delete it manually but it says you can not delete a version with traffic shares.
Please help, any advice are greatly appreciated
You'll need to keep one version (latest maybe?) and then migrate all traffic to it with the "Split Traffic" link here, away from all the other versions you want to delete.
Then you will be able to select and delete those versions since they no longer handle traffic.
Finally you deploy the new version (in fact you could do that as soon as you deleted enough versions to no longer see that error) and, if needed, migrate traffic to it.
Also see gcloud app deploy for options related to versioning and traffic migration right at deployment time which could help you prevent such situation in the future:
--promote
Promote the deployed version to receive all traffic.
True by default. To change the default behavior for your current
environment, run:
$ gcloud config set app/promote_by_default false
Overrides the default promote_by_default property value for this
command invocation. Use --no-promote to disable.
--stop-previous-version
Stop the previously running version when deploying a new version
that receives all traffic. Overrides the default
stop_previous_version property value for this command invocation.
Use --no-stop-previous-version to disable.
--version=VERSION, -v VERSION
The version of the app that will be created or replaced by this
deployment. If you do not specify a version, one will be generated for
you.
Solr reload is not picking up the latest changes from Zookeeper.
Configuration Details:
Solr: 6.0.0
Zookeeper: 3.4.6
OS: AWS Linux
We are facing an issue that when we RELOAD an existing collection in solr to pick up the latest configuration from zookeeper (which we upconfig in Zookeeper) the changes are not reflected on the collection. We verified the same using the solr admin ui. But the changes we made were available on zookeeper, we have verified the same by connecting to zookeeper using zkcli.sh script.
Note: We are able to see the latest config picked correctly if we create a new collection based on the config we uploaded to zookeeper. Issue occurs only for the solr RELOAD call.
Please help us narrow down the issue.
I am using apache solr and I have created another core and its works fine.But once i shutdown my server and restart it,the new core gets deleted. But the folder seems to be there in the solr dir.Can any one tell me why does it get deleted from my apache solr? Thanks in advance
Check for the persistent attribute in the solr.xml <solr persistent="true"> which will persist the changes made through Admin UI and these would be available after restarts as well.
If persistence is enabled (persist=true), the configuration for this
new core will be saved in 'solr.xml'.
If I build an app for Windows Phone 7 and release V1 they purchase it and download it from the app store. Now let's say there's a bug or I release a new version. How do I publish a new version of the app without them having to pay for downloading a new version of the app?
You publish the update via the marketplace in the same way that you releassed the original version. (Except you say that it's an update.)
Anyone with the app installed will be told that there is an update available and given the option to install it. You can't force the update.
You can't force the upgrade on users.
All updates are free.
If you wanted a paid upgrade/update this would need to be a new app in the Marketplace. You could also remove the old version if/as necessary.
More information at http://developer.windowsphone.com/Marketplace.aspx