The options I can think of are:
1) Have multiple frontends each with a different port.
2) Have multiple frontends each with a different hostname but the same port.
3) Have a single frontend with the same hostname and same port using ACLs to route based on URI
We have currently got 12 distinct services (micro services) that we'd like to load balance. It may grow a bit.
What are the compelling reasons to choose any of these approaches?
I am seeing a few of my services suffering/crashing with errors along the lines of "Error allocating memory" or "Can't create new process" etc.
I'm slightly confused by this since logs show that at the time the system has lots of free memory (around 26GB in one case) of memory available and is not particularly stressed in any other way.
After noting a JVM crash with similar error with the added query of "Out of swap space?" it made me dig a little deeper.
It turns out that someone has configured our zone with a 2GB swap file. Our zone doesn't have capped memory and currently has access to as much of the 128GB of the RAM as it need. Our SAs are planning to cap this at 32GB when they get the chance.
My current thinking is that whilst there is memory aplenty for the OS to allocate, the swap space seems grossly undersized (based on other answers here). It seems as though Solaris is wanting to make sure there's enough swap space in case things have to swap out (i.e. it's reserving the swap space).
Is this thinking right or is there some other reason that I get memory allocation errors with this large amount of memory free and seemingly undersized swap space?
I'm wondering if anyone knows of a nice way to partially duplicate (hard link) files between two directory structures?
My current fall back is a script invoked by cron.
As background:
I ask since I have two groups who both need to access a body of files in a directory structure served via HTTP using Tomcat. A privileged group may access all the files and a less privileged group may only access a "public" subset. These sets are not aligned to particular directories but the different class of file can be identified by their naming convention (but not extension).
Therefore my current idea is to serve two separate directories, one containing only private (possibly password protected) and the other containing public. Then to run some periodic process whereby I create hardlinks from the public files so they appear in the private directories for the convienence of the privileged users. I choose to link in that direction since it's more important that the file is available immediately for the unprivileged users. (priv = admin, unpriv = regular user)
I hope that makes sense. I'll try to clarify if anyone has any questions.
I have a Windows 2008 SP2 VM and I am attempting to configure it to allow people to log into it using MSTSC client. As far as I understand you can set this up locally enabling RDP and adding users to the list of those allowed.
However I would like to set things up using AD and GPOs. As per KB954369 I have my machine sat in an OU, against which I have applied policy to enable RDP and another to define restricted users. I have tried to double check these things but as far as I can see, it looks to be correct.
Edit: The domain administrator user can login via RDP. Therefore I'm ruling out any lower level network issues.
I'm a Windows admin novice and am beginning to tear my hair out and wonder if anyone can shed any light or suggest any schoolboy mistakes that I might have made. Specific pointers would of course be appreciated, but I would also be happy to be directed to more general principles, tools or techniques for debugging these things.
I've been given the task of defining a server build and build process for a move to Windows Server 2008 for a few hundred physical machines and a few hundred VMs.
I'm from a Solaris background and am trying to pick things up from someone who has moved on and left no documentation for previous processes.
I have discovered various Microsoft tools, including WDS, WAIK, MDT, but I'm struggling to find anything that gives a coherent overview of how they fit together and how to do it. (I fear that my reliance on googling will not serve me as well for MS products).
I realise that this is a big topic, but is anyone able to make any recommendations as to the best tools and techniques for creating a Windows Server 2008 build including applications.
Thanks in advance. Tom