question

TanmoyDas-9282 avatar image
0 Votes"
TanmoyDas-9282 asked AllenXu-MSFT commented

Huge traffic on port 16500 in SP 2013

Hi All,

We have 7 search servers, out of that 5 are Query and index components.

Server A - internal web / query/index
Server B - internal web/ query/ index
Server C (DMZ server) - External web/ query/ index
Server D (DMZ server) - External web/ query/ index
Server E (DMZ server) - External web/ query/ index

We have noticed huge traffic between Server A and Server C on port 16500
What type of communication can happen on port 16500 between 2 query/index servers?

office-sharepoint-server-administration
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

AllenXu-MSFT avatar image
0 Votes"
AllenXu-MSFT answered AllenXu-MSFT commented

Hi anonymous user ,

You can get the PID of the process listening on the port 16500 by exectuing the Powershell commnad: netstat -ano|findstr "16500". As displayed in below screenshot, I got the PID 2236. And then, you can find the process noderunner.exe by the PID using command: tasklist|findstr "PID".
114870-image.png

Noderunner.exe (Microsoft SharePoint Search Component) is a component of SharePoint 2013 Search managed by the SharePoint Search Host Controller Service, and each Noderunner.exe process hosts one of the following Search components: Crawl, Content Processing, Index, Analytics Processing, Query Processing and Search Administration.

If the search is running a crawl, indexing or exectuing large query, I think it is normal that you experience a lot of traffic. If not, did you detect any memory leak issue or SharePoint search performance issue on your servers? Have a try to the below steps to fix it if any memory leak or performance issue exists:

  • Open the SharePoint PowerShell window and execute the command: Set-SPEnterpriseSearchService –PerformanceLevel Reduced.

  • Open the config file at C:\Program Files\Microsoft Office Servers\15.0\Search\Runtime\1.0\noderunner.exe.config and change the value ofmemoryLimitMegabytes in noderunner node to some other value other than 0, say 100 or 200 which sets the cap limit for memory to be used.

     <nodeRunnerSettings memoryLimitMegabytes="250" />
     #By Default it is set to <nodeRunnerSettings memoryLimitMegabytes=”0″ /> here 0 means unlimited use of RAM#
    
  • Finally Restart the SharePoint Search Host Controller service.


If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


image.png (7.7 KiB)
· 5
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Can you please explain to me how index gets partitioned into several servers. I have 5 query and index servers and index partition is 0.
Does it mean that the index is equally getting divided and partitioned into the 5 index servers?

0 Votes 0 ·

anonymous user ,

No. Indexed items are stored in index servers as index replicas. From your description, I suppose that you have only 1 index partition which contains 5 index servers in your environment.(index partition 0 doesn't mean 0 index partition existing, it is a code name). Each partition contains one or more replicas of the partition based on your own index component configuration. The replicas are the same and they are stored in each server respectively. It is designed for fault tolerance to make sure SharePoint search can still work normally if one or several servers crash.

0 Votes 0 ·

I still have confusion
I have noticed server A was communicating with the server C server on port 16005.
Both the servers are web servers also apart from being query/index.

Now if the same index replica resides in all the index servers then why do they communicate?
I thought they communicate to query the index based on search queries. But if the same replica is there in all index servers locally then they do not need to communicate with each other, is not it? Am I missing something here?

0 Votes 0 ·
Show more comments