Redis cluster support on various platforms - redis

Are there any issues in setting up Redis cluster on various platforms like windows , Mac or Solaris. Currently Redis website says there is support for these platforms but I just want to know is there any caveat in cluster deployment on these?

Redis cluster (i.e. v3) should be runnable on all supported platforms (i.e. *nix). The Windows version is not an official port but the last time I checked (now) it was still at v2.8 so I don't see how you could use the cluster with it.

The MSOpenTech windows port of Redis has released a beta version 3.0 supporting Redis cluster:
https://github.com/MSOpenTech/redis/releases/tag/win-3.0.300-beta1

Related

What is the most robust way to install and run Redis on Windows Server 2012? (Updated for 2018)

I know this question has been asked before, but it was asked back in 2014. The proposed solution was running Microsoft's port of Redis. However, that port hasn't been touched since 2016.
OK... that answer is Good and Official but this one is the future.
Windows Linux Subsystem supports fork (the reason they say it is not recommended) and I was able to run the RQ tutorial on my Windows 10 laptop.
https://learn.microsoft.com/en-us/windows/wsl/install-win10
As far as I can tell, "Not Recommended" is the official answer:
https://redislabs.com/ebook/appendix-a/a-3-installing-on-windows/
Before we get into how to install Redis on Windows, I’d like to point
out that running Redis on Windows isn’t recommended, for a variety of
reasons. In this section we’ll cover these points:
Reasons why you shouldn’t be running Redis on Windows. How to
download, install, and run a precompiled Windows binary. How to
download and install Python for Windows. How to install the Redis
client library.
But even that ebook page (next page) points to the now archived MSFT Redis project.
I would go with running Redis in Docker
https://hub.docker.com/r/_/redis/

how to setup Thingworx 7.0 for high availability?

I am currently trying to instantiate 2 or more instances of thingworx on a single machine for trying Thingworx for high availability.Can you specify the different software along with their version that are required to setup Thingworx 7.0 for high availability?.Are their any tutorials that can help me with the setup?
If you want to use two or more ThingWorx instances on same machine then you can install two or more Apache tomcat server on same machine with different ports (check stackoverflow question for the same) and deploy ThingWorx on both of them.
And you can refer Installing and Upgrading ThingWorx to install ThingWorx guide to install ThingWorx.
To decrease the duration of outage for critical internet of things systems ,you can configure thingwrox core for high availability .This requires a complex setup which you can configure by this guide
http://support.ptc.com/WCMS/files/171336/en/ThingWorx_7.0_High_Availability_Administrators_Guide.pdf

Hybrid container support in ACS-Engine

I know that ACS does not currently support Windows and Linux Containers on the same Kubernetes cluster. Does ACS-Engine currently support Windows and Linux containers on the same Kubernetes cluster?
Yes hybrid clusters are supported in acs-engine
https://github.com/Azure/acs-engine/blob/master/examples/windows/kubernetes-hybrid.json

Spark long deploying time on EC2 with custom Windows AMI

I am trying to run a Spark cluster with some Windows instances on an Amazon EC2 infrastructure, but I am facing some issues with extremely high deploying times.
My project needs to be run on a Windows environment, and therefore I am using an alternative AMI by indicating it with the -a flag provided by Spark's spark-ec2 script. When I run the script, the process keeps stuck waiting for the instances to be up and running, with the following message:
Waiting for all instances in cluster to enter 'ssh-ready' state.............
When I use the default AMI, instead, the cluster launches normally after very few minutes of waiting.
I have searched for similar problems with other users, and so far I have only been able to find this statement about long deploying time with custom AMI-s (see Josh Rosen's answer).
I am using the version 1.2.0 of Spark. The call that launches the cluster looks something like the following:
./spark-ec2 -k MyKeyPair
-i MyKeyPair.pem
-s 10
-a ami-905fe9e7
--instance-type=t1.micro
--region=eu-west-1
--spark-version=1.2.0
launch MyCluster
The AMI indicated above refers to:
Microsoft Windows Server 2012 R2 Base - ami-905fe9e7
Desc: Microsoft Windows 2012 R2 Standard edition with 64-bit architecture. [English]
Any help or acclaration abouth this issue would be greatly appreciated.
I think I have figured out the problem. It seems Spark does not support the creation of clusters on a Windows environment with its default scripts. I think it is still possible to create a cluster with some manual tweaking, but it goes out of my limited knowledge. Here is the official post that explains it.
Instead, as a temporal solution, I am considering the usage of a Microsoft Azure cluster, which has just released an experimental tool that makes able to use a variant of Apache Hadoop (Spark) on their HDinsight clusters. Here is the article that explains it better.

is Redis stable on Windows?

This afternoon, I used python script to test the performance of Redis on Windows.
It worked normally when the number of threads was only 10, but some exceptions occured when the number of threads reached 100.
Exception message:
3 [main] redis-server 1448
_cygtls::handle_exceptions: Exception: STATUS_A CCESS_VIOLATION 1394 [main]
redis-server 1448 open_stackdumpfile:
Dumping stack trace to redi
s-server.exe.stackdump
Is Redis stable on Windows?
Redis is not officially supported on Windows. Some unofficial ports exist (such as the one you're using), but I believe stability is not guaranteed for these ports.
Redis prime dev Salvatore Sanfilippo ('antirez'), December 2011:
I don't think Redis running under win32 is a very important feature. It is cool to have a win32 port that can be used for testing, as we had before, and as we have in a different implementation thanks to the Microsoft patch, so developers using Windows can easily test Redis and develop their projects. But what is the point in providing a production quality win32 port?
Regardless, parties within Microsoft are still improving the Windows build
Here’s to the first release from MS Open Tech: Redis on Windows
Claudio Caldato 26 Apr 2012 12:01 PM 8
We consider this not to be production ready code, but a solid code base to be shared with the community to solicit feedback: as such, while we pursue stabilization, we are keeping the older version as default/stable on the GitHub repository. To try out the new code, please go to the bksavecow branch.
The Redis download page now says "The Redis project does not directly support win32/win64, however we look at interest to projects trying to make a win32/win64 port that is separated from the main project...Currently both ports are not production quality but can be used for development purposes..."
We maintain a stable and production ready Windows port (native!) of Redis.
The Developer Edition is free.
Check out Memurai.
see:
Redis on Windows stable and reliable
I use it in my projects till last month and didn't experience any problems yet.