While the problem may be sl6 malloc as that's the OS we have installed, the suggestions didn't help. We're currently not running a proxy as the access should not transit any firewalls and setting the MALLOC_ARENA_MAX didn't change the behavior. I haven't suggested tcmalloc or jemalloc to the admins yet.

Any other ideas how to debug? I still think it's odd that access from one cluster with the same OS & same xrootd client binaries has this issue but access from the other cluster doesn't.

thanks

—
Reply to this email directly or view it on GitHub.

{"@context":"http://schema.org","@type":"EmailMessage","description":"View this Issue on GitHub","action":{"@type":"ViewAction","url":"https://github.com/xrootd/xrootd/issues/142#issuecomment-57200536","name":"View Issue"}}

Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1