I have a similar reaction to this idea as what I imagine support is thinking - the consequences are not immediately apparent.

True that your insightiq user has a different uid/gid then this - however, there are processes on the cluster that gather the data insightiq needs for analytics.  It's not immediately clear if any of these operations utilize this specific account. 

If you have a test environment I would obviously recommend using that first before making the change in a production environment. 

When making the change, make sure the FSAnalyze job runs to successful completion, and then test the InsightIQ connection, and that all of the data you are seeing is current data.  If all of that works, then I imagine all is clear to move forward.  If there is going to be a problem it may be in the gathering of FSAnalyze data - writing it to the SQLite DB, or accessing that DB by the IIQ connection to read the data and present it to you through the interface. 

If you do make the change, please let us know how it goes.  I'd be interested to know more about your experience here.

As Chris mentioned, I expect you'll see problems with the InsightIQ appliance being able to gather the FSAnalyze data from the cluster. It uses and NFS connection to get the data from the cluster so it will provide UID 15 and GID 15 to the cluster as part of that connection. I don't think changing the group will matter much, but it might cause an issue. Changing the User ID is likely to cause a greater problem.

Also note that the name associated with UID or GID is only for us. The file has GID 15 on it. Meaning any client that provides GID 15 for access will have access to the file. When you do an ls of the file on the remote computer, you will see it is owned by a different group (whatever name is applied to GID 15 on that specific machine).

Noel