[
https://issues.apache.org/jira/browse/TS-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-489:
Attachment: ts_489_testing.txt
We did an experiment with ts2.0.1 stable version following the way you setup
the
[
https://issues.apache.org/jira/browse/TS-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12931001#action_12931001
]
mohan_zl commented on TS-435:
-
we have reproduce this problem when using latest trunk, and looks
[
https://issues.apache.org/jira/browse/TS-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12933427#action_12933427
]
mohan_zl commented on TS-435:
-
Leif:
we did some change with splitdns in the following
[
https://issues.apache.org/jira/browse/TS-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-608:
Attachment: TS-608.patch
change the logic:
1 if we trigger max server connections, remove one keep-alive connections
[
https://issues.apache.org/jira/browse/TS-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-489:
Attachment: TS-489.patch
I think there are two tasks for us to fix this problem:
(1) There seems to be something wrong
[
https://issues.apache.org/jira/browse/TS-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-654:
Attachment: Passive-L7-Health-Check.patch
Imitating the http state machine, we write a l7 health check module.
Trying
[
https://issues.apache.org/jira/browse/TS-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-489:
Attachment: code_clean_up.patch
The logic with connection collapsing break the logic of proxy/http and
iocore/cache,
[
https://issues.apache.org/jira/browse/TS-489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12992262#comment-12992262
]
mohan_zl commented on TS-489:
-
I'm sorry, i think that is not a bug in the old code, just my fault
Logic wrong in the method of class Store
Key: TS-676
URL: https://issues.apache.org/jira/browse/TS-676
Project: Traffic Server
Issue Type: Bug
Reporter: mohan_zl
The logic of method
[
https://issues.apache.org/jira/browse/TS-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13003772#comment-13003772
]
mohan_zl commented on TS-685:
-
Why not use cache_partition.config directly, because the structure
[
https://issues.apache.org/jira/browse/TS-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-654:
Attachment: TS-654-v2.patch
Keep up with latest trunk
request for support of Layer7 http health checking for Origin
[
https://issues.apache.org/jira/browse/TS-654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13011903#comment-13011903
]
mohan_zl commented on TS-654:
-
Right now i don't want to push the new patch, because in current
Support ssd
---
Key: TS-745
URL: https://issues.apache.org/jira/browse/TS-745
Project: Traffic Server
Issue Type: New Feature
Components: Cache
Reporter: mohan_zl
Assignee: mohan_zl
A patch for
[
https://issues.apache.org/jira/browse/TS-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-745:
Attachment: ssd_support.patch
The demand is described in https://cwiki.apache.org/TS/ssdsupport.html, now i
write a
[
https://issues.apache.org/jira/browse/TS-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-745:
Attachment: ssd_support2.patch
Add missing file
Support ssd
---
Key: TS-745
[
https://issues.apache.org/jira/browse/TS-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-745:
Attachment: ssd_cache.patch
Support ssd
---
Key: TS-745
URL:
[
https://issues.apache.org/jira/browse/TS-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-654:
Attachment: health_check.patch
Add a new patch to keep up with trunk, right now the autoconfig is not
supported, that
[
https://issues.apache.org/jira/browse/TS-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-654:
Attachment: (was: Passive-L7-Health-Check.patch)
request for support of Layer7 http health checking for Origin
[
https://issues.apache.org/jira/browse/TS-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13035178#comment-13035178
]
mohan_zl commented on TS-745:
-
+1 on a branch. I am busy on preparing ts for online use these
[
https://issues.apache.org/jira/browse/TS-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-745:
Attachment: ssd_cache2.patch
I'm sorry John, maybe we could not use http://codereview.appspot.com/ for
detailed
[
https://issues.apache.org/jira/browse/TS-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13038371#comment-13038371
]
mohan_zl commented on TS-745:
-
In my thoughts, if we use the same CacheVC to write after calling
[
https://issues.apache.org/jira/browse/TS-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13038374#comment-13038374
]
mohan_zl commented on TS-745:
-
My boss have give me another passport to visit
[
https://issues.apache.org/jira/browse/TS-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050173#comment-13050173
]
mohan_zl commented on TS-833:
-
{quote}
#0 0x004d2c5c in Continuation::handleEvent
[
https://issues.apache.org/jira/browse/TS-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050173#comment-13050173
]
mohan_zl edited comment on TS-833 at 6/16/11 1:08 AM:
--
{code}
#0
[
https://issues.apache.org/jira/browse/TS-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050174#comment-13050174
]
mohan_zl commented on TS-833:
-
@John I think this bug has not been fixed yet.
Crash Report:
[
https://issues.apache.org/jira/browse/TS-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050836#comment-13050836
]
mohan_zl commented on TS-833:
-
@John yeah, i use TS-833-3.diff with the latest trunk.
Crash
[
https://issues.apache.org/jira/browse/TS-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050861#comment-13050861
]
mohan_zl commented on TS-833:
-
@John, is there any possibilities that these problem is caused by
[
https://issues.apache.org/jira/browse/TS-844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13051760#comment-13051760
]
mohan_zl commented on TS-844:
-
The enviroment is like this:
{quota}
[root@cache180 ~]# uname -a
[
https://issues.apache.org/jira/browse/TS-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13051784#comment-13051784
]
mohan_zl commented on TS-833:
-
By the way, now we found an interesting problem, we use 20 machines
[
https://issues.apache.org/jira/browse/TS-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13052302#comment-13052302
]
mohan_zl commented on TS-833:
-
{code}
#0 0x0063f9f5 in get_dns (h=0x18ea3070, id=27816)
[
https://issues.apache.org/jira/browse/TS-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-844:
Attachment: TS-844.patch
Use TS-844.patch and test again, now no related problem coming.
ReadFromWriter fail in
[
https://issues.apache.org/jira/browse/TS-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-745:
Attachment: TS-ssd.patch
Latest ssd patch.
Support ssd
---
Key: TS-745
[
https://issues.apache.org/jira/browse/TS-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-745:
Attachment: TS-ssd.patch
Support ssd
---
Key: TS-745
URL:
[
https://issues.apache.org/jira/browse/TS-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-745:
Attachment: (was: ssd_cache2.patch)
Support ssd
---
Key: TS-745
URL:
[
https://issues.apache.org/jira/browse/TS-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-745:
Attachment: TS-ssd.patch
Support ssd
---
Key: TS-745
URL:
[
https://issues.apache.org/jira/browse/TS-857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13058160#comment-13058160
]
mohan_zl commented on TS-857:
-
#0 ink_stack_trace_get (stack=value optimized out, len=value
[
https://issues.apache.org/jira/browse/TS-857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13058160#comment-13058160
]
mohan_zl edited comment on TS-857 at 7/1/11 12:55 AM:
--
The following
The stat code for ram_cache miss is lost
Key: TS-869
URL: https://issues.apache.org/jira/browse/TS-869
Project: Traffic Server
Issue Type: Bug
Reporter: mohan_zl
Use echo
[
https://issues.apache.org/jira/browse/TS-869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-869:
Attachment: ram_cache_miss.patch
The patch have fixed this problem.
The stat code for ram_cache miss is lost
Something wrong with the evacuate relevant codes in cache
-
Key: TS-870
URL: https://issues.apache.org/jira/browse/TS-870
Project: Traffic Server
Issue Type: Bug
Reporter:
[
https://issues.apache.org/jira/browse/TS-870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13060434#comment-13060434
]
mohan_zl commented on TS-870:
-
Try to fix this problem, the default behavior is not use the
[
https://issues.apache.org/jira/browse/TS-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13060436#comment-13060436
]
mohan_zl commented on TS-869:
-
The attached patch fixes this problem.
The stat code for
[
https://issues.apache.org/jira/browse/TS-869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-869:
Comment: was deleted
(was: The attached patch fixes this problem.)
The stat code for ram_cache miss is lost
Wrong code in iocore/net/UnixNet.cc
---
Key: TS-873
URL: https://issues.apache.org/jira/browse/TS-873
Project: Traffic Server
Issue Type: Bug
Reporter: mohan_zl
I think somebody write a wrong
[
https://issues.apache.org/jira/browse/TS-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-745:
Attachment: TS-ssd-2.patch
TS-ssd-2.patch correct the log stats, and add a
proxy.config.cache.ram_cache.ssd_percent
[
https://issues.apache.org/jira/browse/TS-874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl resolved TS-874.
-
Resolution: Fixed
fixed, and closed
asf-dist should be git nice
---
[
https://issues.apache.org/jira/browse/TS-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-813:
Fix Version/s: (was: 3.1.0)
3.1.1
http_ui /stat/ should response with content type
[
https://issues.apache.org/jira/browse/TS-849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-849:
Fix Version/s: (was: 3.1.0)
3.1.1
proxy.config.http.slow.log.threshold is unable to set from
[
https://issues.apache.org/jira/browse/TS-796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-796:
Fix Version/s: (was: 3.1.0)
3.1.1
Crash Report: mime_str_u16_set, possible
[
https://issues.apache.org/jira/browse/TS-852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl closed TS-852.
---
Resolution: Fixed
This issue is covered by TS-833
hostdb and dns system hangup
[
https://issues.apache.org/jira/browse/TS-726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl closed TS-726.
---
Resolution: Fixed
Never reproduce this problem, close and wait for another issue.
Crash Report: DNSEntry::post in
[
https://issues.apache.org/jira/browse/TS-801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-801:
Fix Version/s: (was: 3.1.0)
3.1.1
Crash Report: enable update will triger Segmentation fault
[
https://issues.apache.org/jira/browse/TS-835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl closed TS-835.
---
Resolution: Fixed
Not reproduce this problem again, now first close it and wait for another
report.
Crash Report:
[
https://issues.apache.org/jira/browse/TS-851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl closed TS-851.
---
Resolution: Fixed
unable to run TS without a real interface
-
[
https://issues.apache.org/jira/browse/TS-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-857:
Fix Version/s: (was: 3.1.0)
3.1.1
Crash Report: HttpTunnel::chain_abort_all -
[
https://issues.apache.org/jira/browse/TS-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-654:
Attachment: hc.patch
request for support of Layer7 http health checking for Origin Servers
Code cleanup
Key: TS-887
URL: https://issues.apache.org/jira/browse/TS-887
Project: Traffic Server
Issue Type: Bug
Reporter: mohan_zl
Try to nuke some unused codes, not changing current logic.
--
This message is
[
https://issues.apache.org/jira/browse/TS-887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-887:
Attachment: code_cleanup1.patch
Correct the code format
Code cleanup
Key: TS-887
[
https://issues.apache.org/jira/browse/TS-887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-887:
Attachment: code_cleanup2.patch
I think the enum structure is not used, so nuke it.
Code cleanup
[
https://issues.apache.org/jira/browse/TS-887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-887:
Attachment: code_cleanup3.patch
I don't know why current codes is implemented like this, in linux, kernel
2.6.38, i
[
https://issues.apache.org/jira/browse/TS-909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-909:
Attachment: TS-format-fix_1.patch
Fix the net format error
code cleanup for format
---
[
https://issues.apache.org/jira/browse/TS-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-844:
Attachment: TS-844-2.patch
@John Plevyak
This problem is hard to reproduce now, but i think the reason is because:
[
https://issues.apache.org/jira/browse/TS-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-844:
Attachment: (was: TS-844-2.patch)
ReadFromWriter fail in CacheRead.cc
---
[
https://issues.apache.org/jira/browse/TS-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-844:
Comment: was deleted
(was: @John Plevyak
This problem is hard to reproduce now, but i think the reason is because:
[
https://issues.apache.org/jira/browse/TS-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-844:
Attachment: (was: TS-844-2.patch)
ReadFromWriter fail in CacheRead.cc
---
[
https://issues.apache.org/jira/browse/TS-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-844:
Attachment: (was: TS-844-2.patch)
ReadFromWriter fail in CacheRead.cc
---
[
https://issues.apache.org/jira/browse/TS-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-844:
Attachment: TS-844-2.patch
ReadFromWriter fail in CacheRead.cc
---
[
https://issues.apache.org/jira/browse/TS-880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan_zl updated TS-880:
Attachment: performance_2nd_req_another_version.patch
Thank you William for your work, we tested your first diff file,
[
https://issues.apache.org/jira/browse/TS-947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13107719#comment-13107719
]
mohan_zl commented on TS-947:
-
One question:
The variable sleep_wait in struct AIOThreadInfo is
69 matches
Mail list logo
