Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

archive issue: consume log exception #322

Open
minusmajun opened this issue Dec 11, 2020 · 3 comments
Open

archive issue: consume log exception #322

minusmajun opened this issue Dec 11, 2020 · 3 comments
Assignees
@minusmajun

Comments

@minusmajun
Copy link

归档功能异常：消费归档功能里，在批量进行读取消费记录日志文件的时候，如果读取是在两个文件里进行的(比如批量1000条，500条读取完后再进行下一个文件的500条读取)，操作hbase存储如果出现异常的话进行位置回退处理，此时的回退处理是对1000条整体位置的偏移量进行回退，但偏移量横跨两个文件进行读取计算的，所以会导致回退偏移量设置异常，从而影响整个消费记录日志的存储线程。
@llIlll llIlll assigned llIlll and minusmajun and unassigned llIlll Dec 11, 2020
@minusmajun
Copy link
Author

针对增量文件改造，避免频繁生成新文件，通过写入偏移量和读取文件控制，提高读取速率和降低空跑率。

@minusmajun
Copy link
Author

加入归档功能整体限流功能，可针对具体主题和app整体限流，也可以针对单个broker限流

@minusmajun
Copy link
Author

加入hbase写入重试机制

minusmajun pushed a commit to minusmajun/joyqueue that referenced this issue Dec 12, 2020
https://github.com/chubaostream/joyqueue/issues/322
2bfef81 
archive issue: consume log exception jd-opensource#322

归档功能异常：消费归档功能里，在批量进行读取消费记录日志文件的时候，如果读取是在两个文件里进行的(比如批量1000条，500条读取完后再进行下一个文件的500条读取)，操作hbase存储如果出现异常的话进行位置回退处理，此时的回退处理是对1000条整体位置的偏移量进行回退，但偏移量横跨两个文件进行读取计算的，所以会导致回退偏移量设置异常，从而影响整个消费记录日志的存储线程。
@minusmajun minusmajun mentioned this issue Dec 13, 2020
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@minusmajun minusmajun

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@minusmajun @llIlll